Your Parents Are Still Calling You About the Printer. GuideYou Thinks It Can Fix That.

The Macro: Why We’ve Ignored the Trillion-Dollar Interruption Tax

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.

Here’s what bothers me about the current market: we’ve built an entire software industry around optimizing every other kind of workflow except this one. 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. We’ve decided that family support doesn’t count as work, so we haven’t built for it. But it is work. It’s just unpaid and invisible.

The home improvement market is projected to reach somewhere between 894 billion and 1.3 trillion dollars by 2034. The actual software layer that helps non-technical homeowners navigate increasingly complicated smart devices and apps inside those homes is comparatively tiny and underdeveloped. That gap is real, and to me, it reveals something the tech industry gets fundamentally wrong: problems that don’t have a clear purchaser don’t get solved, even when they affect millions of people and consume hundreds of billions in hours annually. Whether GuideYou’s market is big enough to build a stand-alone company on is still an open question. Whether the problem itself matters is not.

---

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: This Works If, and Only If, Grandma’s Experience Is Better Than a Phone Call

GuideYou will exist in two years or it won’t, and it comes down to one thing: whether a 70-year-old can actually use this without calling you anyway.

The problem is real. It is widespread. It is genuinely underserved. The family workspace angle is clever because it gives the product a container with clear membership, which is something most documentation tools completely ignore. That’s good instinct.

But here’s where I think the team needs to be honest: guide builders are easy to launch and impossibly hard to keep using. If you’re the person making these guides, you’re spending 20 minutes per guide because you want to be thorough. After three guides, you’re back to just answering the phone. That’s the retention killer on the creation side.

The bigger problem is consumption. This lives or dies on whether receiving a guide actually works for the intended audience on real hardware with real internet. If grandma opens the workspace and sees friction, if the guide takes too long to load on her slow Android tablet, if she has to think about where to find it or how to navigate it, the whole premise collapses. She’s calling you anyway. You’ve just added an extra step.

I need to see actual numbers: How many minutes does it take to create a non-trivial guide like setting up a new email account? What does consumption look like on a 2019 tablet with mediocre bandwidth? If creation takes under five minutes and consumption is genuinely frictionless, this has a real shot. If either one is clunky, it’s a nice feature inside a bigger product, not a company.