Writing

Not everything that makes money should scale

For a startup, money is the most honest signal there is. If someone pays, you did something right. That is exactly why money can also be the most dangerous trap: it talks you into continuing what works today, even when it gets in the way of tomorrow.

Not everything that makes money should scale. And not everything that doesn’t scale should be dropped.

Startups keep running into two similar dilemmas. They look like different questions — one about a client, one about a channel. In fact, they are the same question.

Dilemma one: the profitable client who pulls you sideways

Should you walk away from a profitable client if their requests pull the product away from your core strategy?

I wouldn’t drop a client just because their requests aren’t on the current roadmap. Strategy isn’t dogma. Sometimes it’s the client who shows you an opportunity the team hasn’t noticed yet. Some of the best product turns start with an odd request from a single person.

But here it matters to tell a market signal from custom development.

One question that sorts it out

The key question: if this client leaves tomorrow, will what you built for them still be valuable to the product and to your other target users?

If yes, maybe your strategy needs refining. The client brought you a market, not just an invoice.

If no, the request shouldn’t land on the main roadmap automatically, however well the client pays. A client can be profitable financially and loss-making strategically. They take the team’s attention, make the product more complex, and slowly turn a product company into a services company.

So what you walk away from isn’t necessarily the client. It’s their right to set the direction of the product.

Dilemma two: the channel that won’t scale

Should you keep using an acquisition channel that reliably brings in customers but is unlikely ever to scale?

Yes — as long as it stays profitable, predictable, brings the right audience and doesn’t eat a disproportionate share of resources.

Not every channel has to scale. The company has to.

Founder-led sales, for example, don’t scale on their own. A founder can’t take a thousand calls a week. But those calls can bring in users who stay in the product, pay, invite others, and kick off a growth loop that does scale.

The channel as a starter motor

A channel like this is a car’s starter motor. Its job isn’t to keep the car moving. Its job is to start the engine.

Nobody drives on the starter. But nobody rips it out of the car either, just because it doesn’t turn the wheels on the highway.

The trouble starts when the engine never shows up. When every next stage of growth takes proportionally more of the founder’s time, more people, more manual work. When you’ve been cranking the starter for a year and calling it motion.

It really is one question

Both situations come down to the same thing: today’s revenue should fund the next growth engine, but it shouldn’t get to decide the company’s whole future.

A profitable client isn’t the problem. Neither is a channel that doesn’t scale.

The problem starts when the client steers the roadmap and the channel becomes the only growth strategy.

A few rules I’ve taken from this:

  • Before any custom request, ask: will this still be valuable if the client leaves tomorrow?
  • Listen to the client, but don’t hand them the wheel.
  • Judge a channel not by whether it scales itself, but by whether it starts something that does.
  • If every step of growth costs you proportionally more of your own time, there’s no engine yet.