Different feature requests, same root pain
Seemingly unrelated feature requests often stem from one underlying problem, and a designer's job is to identify and solve that core issue.
Where this was said
Handling feedback on the technical and open source side
At 6:35 · 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
The Open Source Pressure Valve
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 Reveal Pain, Not Solutions
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.
Customers reveal pain, not solutions
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.
Microsoft ranked requests by volume — wrong
Microsoft famously prioritized features by tallying request counts, which Apple criticized as the wrong way to build great software.
Microsoft's Fatal Mistake: Ranking by Request Count
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.
Similar snapshots
50 free tools built total
Bhanu and his team built approximately 50 free tools to attract search traffic, each linked back to SiteGPT.
New tool built in under 5 minutes
With AI coding tools like Cursor, Bhanu can now create a new free marketing tool in less than 5 minutes by referencing existing tools.
KD filter < 10 for rankable keywords
Bhanu filters Ahrefs keyword results to show only those with a keyword difficulty below 10, making them realistic ranking targets for any decent website.
Minimum 1,000 monthly search volume
Bhanu sets a minimum search volume of 1,000 monthly searches when selecting keywords to target with free tools.
20 downloads/day at launch
PropGPT averaged 20 downloads per day right after launching on the App Store through influencer marketing.
4 months of rebuilding with no marketing
Eyal and Yali shut down all marketing and spent 4 months completely rebuilding PropGPT from scratch.
Over 40,000 downloads total
PropGPT has accumulated over 40,000 total downloads since launch.
LLM costs only $20/month
PropGPT's large language model (AI) operating costs are just $20 per month, and the cost is continually falling.
Ad monetization for games
Ad-based monetization works well for game apps where users spend extended time in-session, as seen with Grid and Wordle.
