The 5-Customer Rule: Stop Building Features Nobody Asked For

2026-07-10

Here's the most expensive mistake I've made in software: I once spent six months building integrations.

Stripe webhooks. Slack notifications. Google Calendar sync. Zapier triggers. A REST API with beautiful documentation. The works.

We launched to our first ten beta customers, and you know what every single one of them asked for?

A bulk CSV import button.

That's it. They didn't want webhooks or Slack bots or a REST API. They wanted to upload a spreadsheet and be done. And we'd built everything except that.

The trap

It's seductive. You're building your SaaS, and you start thinking like an engineer instead of a business owner. You imagine scale. You picture thousands of users hitting your API, triggering workflows, integrating with enterprise toolchains. It feels professional.

But at zero users, you're solving problems that don't exist yet — and might never exist. Meanwhile, the actual humans trying to use your product are stuck because you never built the boring, unsexy thing they actually need.

The 5-customer rule

After that six-month detour, I made myself a rule: I don't ship a feature until five paying customers ask for it.

Not prospects. Not free trial users. Not people who might sign up if you add X. Five people who have already given you money and are saying "I need this to keep using your product."

Here's what this rule does:

• Filters noise. One person asking for something is a data point. Five is a pattern. Most feature requests are one-offs that never surface again.
• Proves value. If five paying customers all want the same thing, it's probably the thing keeping them from upgrading, referring others, or sticking around.
• Kills pet projects. It's a lot harder to justify your pet integration when the spreadsheet says two people asked for it and one of them is you.
• Builds the right thing. The feature you end up shipping is shaped by real usage patterns, not your imagination of how people should use your product.

What actually happened

We built the CSV import. Took two days. Customers were happy. Then, three months later, five of them asked for the same thing: automated CSV imports on a schedule. So we built that. Then five asked for webhooks to trigger on import completion. So we built that.

Same features. Right order. Years saved.

The hard part

The rule only works if you're actually talking to customers. Like, having conversations. Reading support tickets. Sharing a Slack channel with your power users. If the only feedback loop is your own brain and Twitter, you're still guessing.

The 5-customer rule isn't really about the number five. It's about humility — admitting that your users know what they need better than you do. And it's about patience — letting demand prove itself before you commit.

Build less. Listen more. Wait for the fifth ask.