The Founder Who Won't Use His Own Product Already Knows Why Customers Churn
If the person who built the product routes around its broken parts, they've cut themselves off from the exact friction their users feel. On dogfooding, and why it's uncomfortable on purpose.
A founder I know built a B2B SaaS tool for sales teams. Twelve months in, decent revenue, growing slowly. I asked him whether he used it to run his own sales pipeline. He said, “It’s not really built for someone like me.”
That sentence does a lot of work. If the person who spent a year building it, who knows every feature and wrote the copy explaining why it’s useful, won’t touch it, the question of why customers churn mostly answers itself.
The real reason founders stop using their own products
It’s rarely because the product is bad. It’s because they know where the bodies are buried. They know which features are half-built, which edge cases break, which bug got pushed three sprints in a row. So they route around the rough parts, and eventually they route around the product entirely, just to avoid the friction.
And that’s the trap, because the friction was the information. Every time a real user hits one of those broken edges, they feel something the founder has trained themselves not to feel. The founder has automated around the pain. The user just churns.
What using your own product actually means
It isn’t logging in once a month to check the dashboard loads. It means using the thing under the same constraints your users have. Same onboarding, same flow, same information, no admin shortcuts, no backdoor, no asking an engineer to hand-fix your account.
I use Jobtune for my own job applications. Not a demo account. My real resume, against real job descriptions, for roles I actually want. Last week the AI roast told me to cut my insurance product experience because it “adds noise.” That experience is my single strongest differentiator for fintech roles, and the model had no idea. I fixed the prompt the next day. That fix came from feeling the exact frustration a job-seeking PM would feel, because I am one, not from a support ticket weeks later.
The signal customers can feel
There’s a version of this that’s purely about product quality, and there’s a separate version that’s about trust. When you say “I use this myself,” customers can tell whether it’s true. Real users ask specific questions: I noticed when you do X it does Y, is that intentional? Founders who actually use the product answer instantly. The ones who don’t, hedge. Customers notice the hedge. It isn’t subtle.
The part nobody enjoys
Using your own product is uncomfortable. You will find things that don’t work, you will get annoyed, and you will want to ask your engineer to quietly fix your account so you don’t have to sit in it. Don’t. The friction you feel is the same friction every user meets before they decide whether to come back.
Whether your product is perfect was never the interesting question. Whether you’re willing to feel what your users feel is. If the answer is no, you already know what your retention problem is, and no dashboard is going to tell you anything you’re not refusing to notice.