Customers are software users, not software designers. They can identify what hurts, but they can't prescribe the right fix for a broad user base. Your job is to look past the patch request and find the structural problem underneath.
Where this was said
At 5:08 · chapter starts 3:08
DHH opens with a wry observation: open source contributors don't pay him, so he feels zero guilt telling them they're completely wrong. That bluntness, he argues, is a pressure valve — it lets him stay measured and professional when dealing with paying Basecamp customers who deserve a more considered response. But the substance cuts deeper than just professional etiquette. [1] — David Heinemeier Hansson "Customers are software users, not software designers. They can identify what hurts, but they can't prescribe the right fix for a broad user…" 05:08 He draws a sharp distinction between the customer as pain-identifier and the customer as solution-designer, arguing these are entirely different skill sets. Most customers are software users, not software designers — they can point at what hurts but cannot prescribe the right fix for a broad audience. The real insight, he explains, is that seemingly unrelated feature requests often trace back to the same underlying wound: your job as a designer is to recognise the constellation and find the grander simplification. The worst outcome is taking customers at their word and just applying duct tape to whatever is visibly sticking out — it looks awful and leaves the structural problem untouched. [1] — David Heinemeier Hansson "Customers are software users, not software designers. They can identify what hurts, but they can't prescribe the right fix for a broad user…" 05:08
On open source projects, DHH can tell contributors they're wrong without professional consequence — because they don't pay him. That candor is a pressure valve. It lets him stay measured and professional when dealing with paying Basecamp customers, where the same bluntness would be inappropriate.
Customers know what doesn't feel right but are rarely equipped to know how to fix it or what the right solution is for a broad user base.
Seemingly unrelated feature requests often stem from one underlying problem, and a designer's job is to identify and solve that core issue.
Microsoft famously prioritized features by tallying request counts, which Apple criticized as the wrong way to build great software.
Microsoft once ranked features by how many requests they received. Apple's charge against them was that this is entirely wrong. You only hear about the duct-tape fixes customers can articulate — not the structural problems, and not the people who never signed up because the product was wrong for them.
SiteGPT attracted over 1 million visitors and $500K in total revenue without spending a cent on paid marketing. The secret: engineering as marketing — building free tools that rank on Google.
Bhanu quit his first job after just 8 months, moved back to his parents' house to cut costs, and started building. One product sold for $250K; the next hit $10K MRR in its first month.
90% of SiteGPT's Google search traffic comes not from the main product but from ~50 free tools Bhanu built. Each tool targets a low-competition keyword and funnels users back to the paid product.
50,000 monthly visitors become 200 leads, 60 trials, and roughly 15–24 new customers per month at ~$100 average revenue each. Add a $1,700–$1,800 LTV and you have a very healthy SaaS.
Start with a blank Ahrefs search, layer in keyword filters (include term, KD < 10, volume > 1,000), list candidates in Notion, design a CTA linking to your main product, then score by volume, difficulty, build effort, and product relevance. That's the whole playbook.
Marketing feels painful for most builders. Engineering as marketing flips the script: instead of writing cold emails or blog posts, you build things — and those things rank on Google forever.
Don't spend months perfecting before launch. Ship the core feature, get real users, and let their feedback dictate the product roadmap. Premature polish is a trap.
SiteGPT launched and hit $10,000 MRR within its first month. That momentum was so overwhelming that Bhanu sold his existing SaaS, Feather, for $250,000 to free up all his time.
PropGPT launched with 20 downloads a day and strong influencer marketing but hit a ceiling at $1,000–$2,000 MRR. High download numbers masked a critical flaw: almost nobody stuck around after the free trial ended.
We use essential and analytics cookies to run Vuci. To understand how the site is used: Privacy Policy.
Install Vuci on your phone
Add it to your home screen for a faster, app-like experience.
Install Vuci on your phone
Tap the Share button, then “Add to Home Screen”.
A new version is available
Reload to get the latest Vuci.