Knowledge base
Build for scale, not for the exception
3 June 2026
Your first big customer feels like a breakthrough. Finally someone who wants to use your product, or pay for it. To you it is proof that you have something good in your hands. And that is exactly the moment when things often go wrong.
How the exception takes the lead
I see it regularly with startups that have just landed their first customers. A pilot comes along with a big customer who is enthusiastic and eager to think along. That is where you start adjusting your roadmap, tailoring it more and more to that one customer. Features get added, and before you know it you are building for the exception instead of for the model.
A sentence I hear a lot: “We put so much effort into getting in with this customer, now we have to push through.” And so the customer becomes the one driving your choices, not your strategy. Before you know it your company stops growing, because the scalability has disappeared from your model.
What goes wrong
In the beginning, building on customer requests feels logical: you are customer-focused and flexible. But those choices come at the expense of your scalability.
I have spoken with startups that launched their first product with a lot of enthusiasm. Customers used it happily, but as the product grew more complex, with more functions, more logic, more exceptions, usage dropped. In the end the very first, simple version turned out to fit the need better. Not because it was perfect, but because it solved a problem.
Building more seems attractive, but it increases the chance that your product becomes cluttered, your team gets fragmented, and your customer loses sight of the core of your solution.
An example outside tech
A few years ago I helped a well-run restaurant that at first glance had hit its ceiling. Full every evening, reservations weeks ahead, a team that ran smoothly. The ambition was growth, and the first thought was logical: a second location. After an analysis we saw that the biggest opportunity was not in expansion, but in optimizing what was already there.
We did something counterintuitive: the reservation system went away. No lists, no time slots, just walk in and full is full. What happened was interesting. Customers came earlier to be sure of a table, the peak shifted from one to two moments per evening, and with the same team in the same building more revenue could be generated.
Taking something away instead of adding it allowed the restaurant to keep growing. Not through more complexity, but through simplicity. That is strategy in action.
What you need is a filter
Before you decide on features or custom work, one thing is crucial: enough insight into your market. Who are your comparable customers? Do they experience the same problem, at the same time? Or are they currently using an alternative that works but is far from ideal? That is exactly where your opportunity lies.
Without that information you keep building with a big blind spot. A customer for whom you adjust everything can lead to a product that is no longer scalable, or to dependence on a customer who walks away tomorrow. Meanwhile others overtake you, simply because they do build for the bigger model.
Bringing focus does not mean you ignore customers. It means you weigh their requests against your strategy. Does it fit within your scale model? Is it repeatable? Would a next customer want this too? That sometimes calls for firm choices, and for someone who looks along with you without getting swept up in the issues of the day.
How we do this at Confidato
We help founders build from direction, not from noise. We look critically at your choices: do they contribute to a scalable model, or are you building something that only works for customer number one? Sometimes the gain is not in what you add, but in what you dare to leave out.