What happens to your product knowledge when you're sick for a week?
I asked this to three indie hackers last month.
All three gave the same answer: everything slows down, or stops.
Not because the product broke. Because everything about how it works lives in one person's head.
Which payment flow triggers which email. What happens when a user hits the free limit. How to manually fix a broken onboarding.
None of it written down anywhere.
I'm building a tool to fix this. But before I ship anything else, I want to know: do you have any of this documented? Even badly?
Drop a yes or no in the comments. Genuinely curious where the baseline is.
The question that came to mind wasn't whether it's documented.
It's whether the founder would discover the missing documentation before or after something important breaks.
Those are very different moments.
Before, ideally. That's the whole bet — if capturing knowledge is fast enough, founders do it in the moment instead of putting it off until after the crisis.
That's what I'm building. Zero friction documentation so the map exists before you need it.
Possibly.
I'd still be careful.
A lot of products end up solving the behavior they want users to have rather than the behavior users already have.
That's one of those things I'd be careful unpacking casually in a thread.
If you're interested, drop your email and I'll send over the fuller thought.
'A lot of products end up solving the behavior they want users to have rather than the behavior users already have.' — that's a fair warning, and honestly one I think about. Would love the fuller thought. victorgonz96@gmail.com
Just sent you a note.