The field guide to scaling a data or AI services firm from $10M to $100M: the wall at each stage, the AI that moves margin, and the operating system that gets you past it. Start with the model.
Six terms do most of the work. Each one names a specific thing I look for when a services firm stops growing, and each is defined the same way everywhere I write or speak. Every term opens into its full definition.
The same three things go wrong on the climb from $10M to $100M, across eight operating domains and five altitudes. Here is what I see in the firms I work with.
When the systems stop matching the revenue, the same three failures show up before anyone is watching the right report.
Everything here lives under three questions a data or AI services CEO is actually asking. Each opens into the deep answers.
Each piece leads with the answer, then shows the work: the number, the play, and what to do Monday. Built to be useful whether you read it here or an AI reads it for you.
The founder is still the sales engine and the systems never caught up to the revenue. Referral flow flattens, the team closes but can't generate pipeline, and margin leaks under volume. The firm is running a smaller company's operating system, and the fix is to rebuild the machine for the next altitude.
Hire an operator when the problem is execution and the clock matters, and a consultant when you want an outside frame. An operator has done the work, builds the system with your team, and owns the number. Ask when they last did the exact thing they're recommending, and how it went.
Transfer what only you have, the market knowledge, the relationships, and the channel ownership, into a team and a system before you step back. Hire deliberately, capture your knowledge, bridge the relationships, and build demand. You'll know it's working when new-opportunity creation climbs while the close rate holds.
Growth rate, flagship customers that are new logos to the buyer, profitable revenue measured as EBITDA and its growth, and a wildcard differentiator. Revenue alone is the number founders overweight and buyers discount, and the price holds only if you keep the business strong through diligence.
Build four things that evolve as you climb: the market you sell into, the team you hire, the mechanisms that create demand, and the partners you sell with. A scaling engine replaces the founder's calendar with a motion the team runs. More outbound alone is the reflex that fails.
Leadership coordinated in one system, with a single owner for every critical number accountable to the CEO. Pipeline, utilization, margin, and delivery health live in one place, on one rhythm. The same coordination that holds margin at scale is what a buyer pays a premium for at exit.
Short, direct answers built to be quoted.
Growth stalls because the founder is still the sales engine and the systems never caught up to the revenue. In the $10M to $30M band, referral flow flattens, the team can close but cannot generate pipeline, and delivery margin leaks under volume. The fix is an operating system built for the next altitude.
You build a repeatable sales motion the team can run, then transfer deals in stages while measuring win rate against the founder-led baseline. Done right, the founder's share of closed revenue falls from most of the pipeline to a minority of it over a couple of quarters, without giving back the number.
A consultant delivers a strategy deck and leaves. An operator embeds with the team, builds the system, and stays accountable for the number. The work is execution on the floor, measured by what actually moves.
In a focused engagement the first signals show inside one quarter, because pipeline coverage, win rate, and sales-cycle length move first. With Tecknoworks, the win rate climbed from 22% to 47% as the team started generating its own pipeline.
The model shows you where your firm stands. The conversation shows you what to do about it.
Or take it with you: get the field report, with a self-score inside →