The process was carrying the rules
We used to enforce governance by making software annoying. That worked right up until people could route around the software entirely.
You can already see what this has to become. Getting there means decisions across product, systems, marketing and cost at the same time, and everyone advising you has only ever run one of them.
I work with software and SaaS CEOs at $10M to $50M on what the next version has to be, what’s stopping it, and what closing that gap is worth.
So when growth slows we go looking for the department responsible. Pipeline’s weak, that’s a marketing problem. Deals won’t close, sales problem. It’s a reasonable way to think, and I’ve watched it be wrong more often than right. The expensive problems live in the seams between departments, and nobody owns a seam.
Written from the middle of live engagements. Not frameworks, and nothing to download.
We used to enforce governance by making software annoying. That worked right up until people could route around the software entirely.
Walk into a company holding a hammer and you will see nails. The second question is the one that earns you the right to swing.
AI made software cheaper to build. It didn’t make it cheaper to own.
Experienced judgment isn’t knowing the answer sooner. It’s getting to a useful model faster, and that almost always starts with a guess that turns out to be wrong.
A category-leading brand with a 77-year heritage was steering its spend by an agency dashboard. Reconciled against the bank, one “winning” campaign had made $918 on $600 of spend. The reporting looked fine, so nobody had reason to check it. So we stopped buying more traffic, tuned the store and the email flows, brought marketing in-house and taught their own team to run it with AI. Same traffic, conversion from 0.97% to 2.73%. Every number in it reconciles to their own books, and they run it themselves now.
0.97% → 2.73%
Site conversion after the adjustment, on the same traffic. A leading 77-year-old skincare brand.
5 → 1
Competing visions, then one accountable owner. A leading $100M engineering consultancy.
One of the leading firms in its field had grown a $3–5M software business on the strength of its consulting. The team was capable and working hard, and leadership could see the output wasn’t matching the effort. Fifteen interviews in, the lowest scores sat above the code. Five leaders held five different visions of what the software business was for, so any of them could veto and none could greenlight. The company had never formally decided it was building a software business, because until then it hadn’t needed to. Seven symptoms, one decision underneath all of them.
Move faster, make more money, get rid of work that shouldn’t exist. Different rooms, same job every time.
So we can decide what to do next, and what it’s worth.
Ask people what’s holding the company back and you get people-shaped answers: a decision nobody made, a thing nobody owns. Start instead with what the business actually did, the billings, the cohorts, the spend, every lost deal rather than a sample, and the roadmap comes back with numbers on it.
Which matters, because a roadmap without economics is a wish list. The point isn’t the finding. It’s knowing which three things to do first and what each one is worth.
Then your people run it. Every engagement has ended with the client owning a capability they didn’t have: PerformLine’s team still builds on that platform, the skincare brand runs its own marketing, the agency’s designers run the automation. A fix that needs me in the room forever isn’t a fix.
Both engagements above are anonymised, one at the client’s request and one at mine. Every number reconciles to the client’s own reporting.
Twenty minutes. Tell me where you want this company to be in two years and I’ll tell you what I’d go look at first.
I take a handful of these a quarter.