The Macro: The Support Ticket You Never Asked to Own
There is a whole category of unpaid technical support that nobody talks about seriously. It lives in family group chats and Sunday phone calls and that specific sigh you make when a parent says ‘it’s not working’ without any further context. Every person who grew up with computers in the house knows this role. You did not apply for it. You cannot quit.
The funny thing is that the tools built for this problem are usually aimed at the wrong person. Remote desktop apps, screen recorders, YouTube tutorials. All of those assume the person who needs help is going to go find the help themselves. That is not how it works. The person who needs help calls you. You are the help.
Software documentation tooling has been growing quietly for years on the B2B side. Notion, Confluence, Loom, Scribe. All solid, all basically designed for teams with Slack and a product manager. None of them are designed for the person trying to explain to their 68-year-old dad why his email looks different after the iOS update.
The home improvement market (and I’m using the market research framing loosely here, because GuideYou got tagged under it) is projected to reach somewhere between $894 billion and $1.3 trillion by 2034 depending on which forecast you believe. The actual software layer that helps non-technical homeowners navigate increasingly complicated smart devices and apps inside those homes is comparatively tiny and pretty underdeveloped.
That gap is real. Whether it’s big enough to build a standalone business around is the actual question.
The Micro: Screenshot, Annotate, Never Explain Again
GuideYou’s core loop is simple. You upload screenshots from whatever device or app you’re trying to document. You highlight the relevant elements, like literally draw attention to the button someone needs to tap. You write a step. You repeat until you have a complete guide. Then you share it into a family workspace where the people who need it can pull it up whenever.
The ‘family workspace’ framing is doing real work here. This is not just a guide builder. It’s a shared context layer for a household. The idea is that mom can open the workspace, find the guide for ‘how to add a contact on your Android,’ and follow it herself. Asynchronously. Without calling you.
A few product decisions stand out to me. The feedback loop for when screens change is interesting. Apps update constantly and screenshots go stale, which is the main reason most how-to documentation falls apart. GuideYou apparently surfaces some kind of notification or feedback mechanism when that happens, though the product website wasn’t loading fully when I checked, so I’m working from the product description here.
The ‘stays signed in’ feature sounds minor but it’s not. Forcing a non-technical user to remember a password to access a guide is enough friction to kill the whole use case.
It got solid traction on launch day on Product Hunt, which at minimum signals that the ‘I am my family’s IT department’ pain point resonates with a pretty online audience.
The honest thing I want to know is how guides actually look on the receiving end. The creation side sounds clean enough. But a 70-year-old following a guide on their tablet is a completely different UX problem than the one being solved during the upload flow.
The Verdict
I want this to work. That’s my actual position.
The problem is real, it is widespread, and it is genuinely underserved by anything currently on the market. The family workspace angle is smart because it gives the product a container with clear membership, which is something most documentation tools completely ignore.
The 30-day risk is retention on the creation side. Guide builders are easy to launch and hard to keep using. If the person making the guides has to do too much work per guide, they’ll fall back to just answering the phone call.
The 60-day risk is whether the receiving end actually works for the intended audience. If grandma can’t open the workspace without friction, the whole premise collapses.
What I’d actually want to know: what does guide creation take, in minutes, for a non-trivial flow like setting up a new email account? And what does consumption look like on a low-end Android tablet with a slow connection?
If those two experiences are genuinely smooth, this has a real shot at becoming something people pay for to protect their Saturday afternoons.