Scale without sellingyour soul
(* or your company)
Your growth. Your equity. My problem.
The model for modern business is broken
Pace without purpose
Go hard or go home … move fast and break things … scale or fail … sleep when you’re dead … you hear it all the time. Speed, growth, more. But where’s purpose?
You didn’t start your company to go fast. You started it for a purpose. Without purpose, pace is vanity. With it, pace is your advantage.
But what happens when not everyone with ownership shares your purpose?
Capital without control
You take the capital. You do what they advise … scale scale scale. You hire fast, pay well, and hand out equity. Then your next “growth stage” arrives, and you need more.
Every round costs you control. You want to serve your purpose. They want a return. You want to build something that matters. They want an exit.
Your best business is built with time. Their exits are built with speed.
It’s success on someone else’s terms.
Build for impact
Purpose with pace.
Control with creativity.
Scale with soul.
Build with intent. Deliver outcomes with impact.
Pace with understanding
You don’t need to build everything, just the right things. Build on assumptions and you burn runway on the wrong ones. Build on signals and you don’t.
Speed won’t fix it. Staying close to your customers will. Build deliberately, validate obsessively, and treat every release as a theory to prove.
You don’t find product-market fit by going faster. You find it by listening.
Scale with intent
When growth arrives, your instinct is to hire. But headcount without structure creates chaos, and chaos makes outside capital feel necessary.
Build the systems, culture, and processes that compound, so each hire multiplies rather than adds. Then your growth doesn’t need fresh capital every 18 months just to stay alive.
Your business grows because of how you build, not just what you build.
This is success on your own terms.
Prove it.
Most problems are an absence of trust, purpose, or both.
Ok … take receipts
The teams that forgot why they existed
Problem
A post-merger engineering function spread across North America, Europe, and Asia. A little over 30 engineers working in silos and shipping reliably less than half the time. The technology wasn’t the problem … the people had stopped trusting each other, and stopped believing in why they were there.
Approach
You don’t fix that with process. You fix it with clarity. Six months of building the foundations that should have been there from the start: structures, shared language, and genuine clarity about what the work was for.
Outcome
Delivery reliability went from below 50% to above 90%. A $300K account that was leaving, stayed. But the number was the consequence, not the point.
The point was that 30 people came to work on a Monday with a reason to be there.
The company that confused size and speed
Problem
Seventy engineers in six teams, shipping on a three-month cycle, inside a culture of command and control that had spent a long time trying to fix it with pressure. Everyone had agreed the problem was speed. Nobody had asked what was actually slowing it down.
Approach
It was confusion, not effort. The six teams moved from waterfall to scrum, and the delivery managers who had been running them became scrum masters and engineering managers rather than being replaced … the people who knew where the work was buried were the ones best placed to dig it out.
Outcome
Three months became two weeks or less. In the same year, the function returned the only positive eNPS score in the department.
The speed came from clarity and autonomy, not from pushing harder. The pressure had been the thing slowing them down.
The engineers everyone forgot to keep
Problem
The same 70-person function, and no shared answer to what any of those jobs actually was. No clarity on what a role meant, no honest way to hold a performance conversation, and no visible way up. So people left, and the leavers were rarely the ones anyone expected.
Approach
A careers framework, and not a grid to be measured against … a shared language for what the work is, so that a manager and an engineer could have the same conversation twice. Built for one function of 70, then adopted across the company’s entire software organisation: the other functions on the same product, and the teams building the other products, 300 engineers in all.
Outcome
Churn fell by around 30%.
Retention was the symptom. Being seen was the cause.
But don’t take my word for it … take theirs
Tom, thank you for existing.
A rare set of qualities … immense creative flair alongside a grounded and methodical approach.
You’ve got a rare mix of keeping things human while also bringing much-needed structure and discipline to the chaos.
Your ability to balance results with people, creating an environment where the team felt supported, challenged, and motivated to do their best work. That’s not easy to achieve.
Resonates?
Let’s talk …
If you’ve read this far, it’s worth a conversation. No intake form, and no discovery call disguised as a sales pitch. We’ll work out the rest from there.
If it’s the thinking that caught you, start with the philosophy.
The ideas are free. Making them real is the work.
The Desk
Where my thinking happens in public.