In growth, your tools quietly decide your velocity

In growth, speed is the game, and a shitty tool is the silent killer of it. The instinct to buy best-in-class for every category is quietly expensive: feedback fragments, syncs multiply, decisions slow down, and none of it appears on an invoice. The answer is the right system, not the best tool per job.

Your team isn't slow because it needs better tools.

It's slow because it has TOO MANY perfect ones.

Tooling is one of the most important topics in growth that almost nobody talks about. Every growth person will tell you the name of the game is speed. A shitty tool is the silent killer of velocity: it slows you down every single day, and you put up with it anyway, on top of the evaluation, contracting, and switching costs.

The right tool does the opposite. It lifts team output and compounds as you build momentum.

Fragmentation is the tax nobody accounts for

The instinct is to grab the best-in-class tool for every job. One for chat, one for docs, one for projects, one for whiteboards. It feels responsible. It's quietly expensive.

Feedback gets buried across platforms. "Quick syncs" multiply. Simple decisions take three times longer than they should. New hires take longer to ramp.

None of that shows up on an invoice. That's the bill for best-in-class, and it never arrives as a bill. 🙂

Which is exactly why it doesn't get fixed. Every line item in the stack is individually defensible, each one was chosen by someone sensible for a good reason, and the cost lives in the gaps between them where nobody owns it.

The four bars a tool has to clear

For early and scale-up stage teams, the right tool in a category usually clears four:

1. Has the features you'll actually use, without the bloat you won't.
2. Reasonable, balanced pricing for both starting and scaling stages.
3. Vetted by the industry, with the resources to still be a front-runner in three years.
4. Genuinely easy to use, because ease of use is what drives team-wide adoption.

That last one gets ignored constantly. A powerful tool nobody adopts loses to a simple tool everyone actually lives in (every time, not most of the time).

Having led growth across a handful of early and scale-stage companies, I've lost count of how many tool evaluations I've run. Consolidation beat "best-in-class" nearly every time.

When best-in-class is actually right

Now of course it isn't always wrong, and I'd be overstating it if I said consolidate everything.

The exception is the category that is your actual craft. If experimentation is the thing your growth team does all day, the experimentation platform should be the best one you can run, and you should absorb the fragmentation cost knowingly. Same for analytics if your whole practice is built on it. The general rule is that you can afford best-in-class in the one or two categories where the depth is the work, and you pay for it everywhere else.

The failure isn't picking a specialized tool. It's picking four of them, in four categories where a good-enough option inside a system you already have would have done the job.

How to actually consolidate

Two practical notes, because "consolidate" is easy to say and unpleasant to do.

Switching costs are real and they're front-loaded. A migration costs you weeks of velocity to buy back months of it, and if you run three migrations at once you will simply be slow for a quarter and everyone will remember that rather than the payoff. Do one category at a time, finish it, let people feel the difference.

The decision needs an owner, not a consensus. Tool choices made by committee optimize for nobody objecting, which reliably produces the bloated stack you're trying to escape. Somebody picks, and the bar they're picking against is the four above.

The takeaway

Treat your tool stack as a velocity decision, because that's what it is.

Resist collecting a best-in-class app for every job. Spend that budget in the one or two categories where depth is genuinely your craft, and take the well-fit, easy-to-adopt option everywhere else.

You already know which tool your team quietly works around. That's the one to look at.

Common questions

Does the tool stack really affect growth?

Yes, through velocity. Speed is the core constraint in growth, and a fragmented stack slows every day of work, while the right tools compound output and momentum. The cost is invisible because it never appears on an invoice.

Is a best-in-class tool for every job the right approach?

Usually not. It's right in the one or two categories where the depth is your actual craft, like experimentation for a team that runs experiments all day. Everywhere else, fragmentation costs more than the specialized tool saves.

How do I choose a growth tool?

Four bars: it has the features you'll use without bloat, its pricing is balanced for starting and scaling, it's industry-vetted and likely to stay a front-runner, and it's genuinely easy to use so the team adopts it. The last one is the one people underweight.

How do I consolidate without wrecking a quarter?

One category at a time, finished before the next one starts, with a named owner making the call rather than a committee. Three simultaneous migrations just make you slow, and that's the part the team will remember.