Most startups spend their AI on doing the same work in fewer hours, which is the smaller half of what is on offer. A story about a board meeting, thirty one percent, and the three strategies on the table.
A startup has two genuinely different AI strategies available, plus a third that combines them. Most take the first one by accident and never notice the other two.
Full argument below · about 14 minutes
The number on the slide is thirty one percent, and everybody in the room is pleased with it.
It is a Series A company, forty two people, eight months into taking agents seriously. The slide is honest. Support resolves a ticket in a bit over half the time it used to take. Engineering is merging more than it did in January with the same eleven people. The two sales reps are each running the research and follow up that used to occupy most of a third. Burn is flat. The founder has been looking forward to this slide for a while.
The question comes from the board member who says the least, which is usually how it goes. She is not challenging the number. She wants to know what happened to it.
You have a company that produces about a third more than it did in January, she says, with the same people and the same money. What did you do with the third?
The founder answers with the roadmap. Everything on it is landing earlier than planned. Two features that were slated for Q4 are already in beta. The board member lets him finish and then points out the thing that nobody in the room had said out loud yet, which is that the roadmap he is delivering early was written in October, by a company that could not do any of this.
Nobody is being unfair here. The team executed well and the technology worked. The awkwardness is that a genuine increase in capacity went straight back into a plan that predated it, and no one made that decision. It happened by default, the way water finds a level.
•••
A startup does not fail at AI the way a large company fails at it. The enterprise problem is that changing anything requires moving an organization that does not want to move, which is why the redesign work never gets done and the pilots die. A startup has almost none of that. It can change its own processes in an afternoon, because there are eleven people and most of the process lives in one person's head.
Which sounds like an advantage, and is one, but it produces a different failure. A company that can move quickly tends to spend its new capacity on going faster along the line it was already travelling. That is the thirty one percent, absorbed. Nothing was wasted exactly. It just did not change anything about what the company is.
There are two genuinely different things a startup can do with AI, and a third that puts them together. Almost every adoption plan we see is a detailed version of the first with a paragraph of intent about the second.
The cost savings strategy points agents at the work you already do. Same customers, same product, same roadmap, fewer hours consumed per unit of output. It is fast, it is cheap, it is measurable inside a quarter, and it is available on Monday. It is also the right first move for nearly everyone, and nothing in this piece argues otherwise.
The realign strategy asks what the company could do that it previously could not afford to do at all, and then reorganizes around the answer. New segments, new products, new markets, and, just as importantly, a shorter list of things you are doing in the first place. It is slow, it is uncomfortable, and it does not show up on a slide for two or three quarters.
The combined strategy runs the first in order to fund the second. It returns the most of the three and it asks the most of you, and it is emphatically not what you get by doing the first one and hoping.
Because the first two are not stages of the same journey. Running the cost savings play does not deliver you to the realignment. Efficiency does not convert itself into strategy, and capacity does not allocate itself. Left alone, the savings are consumed by the plan that was already running, and the company arrives at the board meeting above.
Take the tactical work seriously, because it funds everything after it. The qualifying shape is the same as it has always been: high volume, shallow judgment, data you already own. In a startup that ground is easy to name, and most founders can list it from memory.
First response and triage on support, with a human on anything that has a refund or a churn risk attached. Research, enrichment and follow up drafting on the sales side, which is where most of a rep's week goes and almost none of their talent. First pass code review, test generation, migrations, and the documentation nobody writes. Screening and scheduling on recruiting. Reconciliation, invoicing and the collections chase in finance. The internal reporting layer, which in a forty person company quietly consumes about a day a week of somebody senior.
The payback here is real and it arrives in weeks. It is measured in hours per person per week, and it goes to the bottom line or to output, depending on what you decide. Deploy carefully, keep a person accountable for anything a customer sees, and this part works.
What it will not do is give you an advantage. Three limits are worth being honest about before you build a strategy on it.
It is copyable, completely and quickly. Every competitor you have can license the same models on the same terms inside a week, and most of them are doing it right now. Efficiency of this kind does not become an edge, it becomes table stakes, and the window in which it looks like an edge is about as long as a sales cycle.
It is bounded. You can only remove work that already exists, so its ceiling is your current cost base, and you approach that ceiling fast. The first quarter returns more than the fourth.
And it is quietly self consuming. Freed hours do not sit in an account waiting for instructions. They get absorbed by the work already in flight, invisibly, and the only trace is that the roadmap starts landing early.
Efficiency is the one advantage your competitor can buy on the same terms as you, in the same week, with a company card.
This is the hinge of the whole thing, and it is a scheduling decision more than a technology one. When automation returns hours, those hours have exactly three destinations, and if nobody chooses, the first one wins every time.
They go back into the existing plan, which is the default. The roadmap accelerates, everyone feels productive, and the company at the end of the year is the same company doing the same things somewhat sooner.
They come out as margin, which is a real and sometimes correct choice. If runway is the binding constraint and the next raise is the whole game, converting capacity into a lower burn multiple is a defensible strategy and you should say so out loud, in those words, so that everybody knows the choice was made.
Or they go into work the company could not previously do, which is the only destination that changes what the business is. Choosing that one, on purpose, in advance, is the combined strategy, and it is the whole of the difference between it and the default.
The mistake is not picking the wrong destination. It is not picking. Decide where the hours are going before you deploy the thing that frees them, because afterwards they are already gone and you will be reconstructing the answer from a burn chart.
Before any of that capacity gets reinvested, there is a pass worth running, and it is the least popular meeting on the calendar.
Startups accumulate work at a startling rate. A customer you should never have signed. A feature built for one account that is still in the codebase two years later. A report that exists because an investor asked a question once in 2024. A market you entered by accident because an inbound lead was flattering. A weekly meeting that survives because cancelling it would be a statement. None of it was a bad decision at the time. It is just sediment.
Automation is dangerous here in a specific way. It lowers the cost of the wrong activity just enough that you stop feeling the pain that would eventually have made you kill it. The report that took a day a week now takes twenty minutes, so it survives another two years, and nobody ever asks the question again.
Automation does not kill bad work. It preserves it, at a discount, indefinitely.
There is a fast test for this. For each activity, ask whether you would hire someone tomorrow to do it, at market rate, if that were the only way to keep it. Most things pass easily. The ones that do not should be stopped rather than automated, and stopping them is usually what funds the interesting part of the plan. A startup that runs this pass honestly tends to find somewhere between ten and twenty percent of its own activity has no owner who will defend it.
Here is the part that gets described as visionary and is really just arithmetic.
Every company has a cost to serve, and that number, more than any strategic preference, is what draws the boundary of the market it can address. Segments sit outside the line because serving them profitably would take more people than the revenue supports. Products stay unbuilt because they need a team you cannot staff. Geographies stay closed because the support load in another time zone needs headcount you do not have. None of those are decisions about ambition. They are consequences of a number.
Change the number and the boundary moves. That is the whole of it. The mid market accounts you politely decline because each one eats fourteen hours of onboarding become viable at four hours. The second product that needed six engineers needs two. The integration work that was always a regretful no becomes a yes, and integrations are how you get into other people's ecosystems. The vertical you avoided because it demanded compliance documentation you had nobody to write becomes reachable.
This is where the revenue component lives, and it is worth being precise about why it belongs to you rather than to your competitor. The models are common property. What is not common property is that you redesigned your delivery model around them, that you own the operational data the agents run on, and that your customers are already inside a relationship you can extend. A competitor can buy the same subscription tomorrow. They cannot buy the eighteen months in which you rebuilt what you sell around a lower cost to serve.
And a startup is unusually well placed to do this, which is the argument for doing it now rather than after the next raise. The reason incumbents cannot realign is that it requires unwinding processes that thousands of people and several careers are attached to. You have almost none of that. The redesign that is nearly impossible at scale costs you a fortnight and a difficult conversation, and that asymmetry is the most valuable thing on your balance sheet right now. It also has an expiry date, because you are busy becoming an incumbent.
| Function | Cost savings, on Monday | Realign, what it puts in reach |
|---|---|---|
| Support | Triage, first response, tier one resolution, knowledge base upkeep. | Serving a segment whose support load made it unservable. Support depth becomes a paid tier rather than a cost line. |
| Sales | Research, enrichment, follow up drafting, pipeline hygiene. | Covering a vertical or geography you could never staff, and selling profitably to accounts that were previously too small to touch. |
| Engineering | Review, tests, migrations, boilerplate, the documentation debt. | The second product. The integrations you kept declining, which are the way into somebody else's platform and customer base. |
| Finance | Reconciliation, invoicing, collections, the monthly reporting pack. | Pricing by segment instead of by instinct, and running the scenarios weekly, which is when they are worth something. |
| People | Screening, scheduling, onboarding packs, policy questions. | Hiring into markets where you have no recruiter, and onboarding fast enough that a new market is a decision rather than a project. |
The two plays get presented as a choice, and they are only a choice if you are forced to pick. The third option is to run the cost savings strategy precisely so that it pays for the realignment, and to decide that before the savings arrive rather than after.
Mechanically it is not complicated. The savings are the funding. Automating triage, reconciliation and first pass drafting releases hours and lowers your cost to serve, and both of those are exactly what the realignment needs: the hours to do the redesign work, and the lower cost base that makes the new segment viable in the first place. Run them apart and you fund the realignment out of headcount you do not have. Run them together and it funds itself.
What makes this hard is not the mechanics. It is that the combined strategy and the default strategy are indistinguishable for the first two quarters. Both start with agents pointed at existing work. Both produce a happy slide about cycle time. They diverge only at the moment the hours actually come free, and by then the decision has either been made or been made for you.
The combined strategy and the accidental one look identical until the hours arrive. The difference is whether anybody wrote down in advance where they were going.
It also is not free, which is the part worth being honest about. Running both means the realignment competes for attention with a roadmap that is now moving faster than it was, and a faster roadmap is very good at absorbing the people you needed for something else. That is why the combined line in the chart above sits below the sum of the other two rather than on top of it.
So there is a case for not doing it. If runway is short enough that the next raise is the only thing that matters, run the cost savings strategy cleanly, bank the margin, and say out loud that this is what you chose. If the team is small enough that the same four people would have to carry both, sequence them instead: one quarter of savings, a subtraction pass, then the realignment with the capacity you just created. Sequencing beats splitting when there is not enough of you to split.
For most companies past that point, though, the combined strategy is simply what the first two look like when somebody is actually managing them.
None of this argues for skipping the tactical work. It argues for a sequence, and the sequence is not the one most plans follow.
Run the cost savings play now, because it is cheap and it teaches you where these tools genuinely work rather than where the demo suggested they might. But book the release: name the hours you expect back, per function, before you start. Unbooked capacity is indistinguishable from no capacity by the time anyone goes looking.
Run the subtraction pass before you reinvest anything, because automating work you should have stopped is the most expensive form of efficiency available to you. Then decide the destination of the hours, deliberately and out loud, and accept that margin is a legitimate answer if runway is the constraint.
Then ask the realign question properly. At the new cost to serve, what is now inside the boundary that was outside it in January? Pick one. Not five, one, with a named owner who is not the founder by reflex, and a number attached that somebody outside the company would recognize as revenue.
What all of this buys, in the end, is not a smaller payroll. In a forty person company the constraint was never labor cost. It is the number of hours your best six or seven people get to spend on the things only they can do, and every hour moved out of the first pile and into that one compounds in a way that a cost saving does not.
You are not automating so that the company can be cheaper. You are automating so that it can attempt things it had to decline last year.
Rather than debating whether any of this is right, it is more useful to write down what would have to be true a year from now, and then find out whether it is. The list for a startup comes out short.
If most of that is true, the technology paid, and it paid in the currency that matters at the next raise. If most of it is not, you have probably had a productive and entirely forgettable year.
•••
Back to the board meeting, because the founder's answer was available to him and he did not have it.
He could have said: we took about a third out of the cost of delivering the core product, and here is where that went. We cancelled two roadmap items that only existed because we happened to have the people. We stopped a reporting cycle nobody could name an owner for. And we put the capacity into the mid market accounts we spent two years declining, which we can now onboard in four hours instead of fourteen, which is why there is a line on this slide that read zero in January.
That answer does not require better technology than the company already had in the room. It requires somebody to have decided, in advance, that the capacity was going somewhere in particular, and to have been willing to stop things in order to send it there.
That is the real change, and it is more uncomfortable than the technology. Your operating plan used to age slowly enough that rewriting it once a year was reasonable. It does not any more, because the company underneath it now changes shape every couple of quarters, and a plan written by the smaller, slower version of your company will faithfully steer you back toward being it.
The cost savings strategy is a decision about cost. The realign strategy is a decision about what business you are in. The combined strategy is both, in that order, deliberately. Most startups only ever make the first one, and they make it by accident.
Talk to an advisor →