It’s late on a Friday. You finish a long piece of writing. You drop it into the tool you built and watch it render into a video. Scene three loads with the wrong music. You feel the wince before you think the thought.
That wince is the gold.
Recently I ran a Trends.vc report through Multi.
The wince is the bug report writing itself.
- The button that sits a thumb’s width too low
- The step that drags for thirty seconds
- The output that’s almost useful
Eating your own cooking makes empathy automatic. The product breaks while you use it and you fix it before you close the laptop. You’re the customer and the founder.
The hedge: your workload will map imperfectly onto every customer’s. The solo founder publishing daily reports through Multi hits different edges than the marketing team running a weekly campaign. But your workload is a real load. It beats the hypothetical one you’d otherwise have to imagine into existence.
Compare it to the alternative. A ticket lands in someone’s inbox. A stranger describes a frustration in words. The PM files it, prioritizes it against other tickets, schedules the fix for next sprint. The friction reaches them secondhand. Words on a screen, written by someone who already moved on.
When you are the user, the diagnosis and the decision sit in the same head. You feel the pain, you write the fix. The roadmap fills in from the friction you feel.
📡
What daily problem could you solve with a tool you’d ship and refine yourself?
