A Fifty-Person SaaS Company With No AI Owner: What the First Six Months Look Like

Fifty employees. Roughly eighteen in engineering, six in support, the rest across sales, marketing, finance and customer success. Revenue growing, an engineering roadmap booked solid through two quarters, and a leadership team that has read the same nine articles about agents that everyone else has read.

Start with the software, because that is the part with a number on it. Zylo's 2026 SaaS Management Index, built on more than 40 million licenses and $75 billion of spend, puts median SaaS spend at $9,455 per employee per year. Fifty people is about $472,750 a year of tools. The same report finds 36% of licenses go unused and that business units, not IT, control 81% of the spend. So somewhere around $170,000 a year is leaving for seats nobody opens, and the person who could cancel them doesn't have the list.

The AI half is worse, because it is invisible rather than merely wasteful. PagerDuty surveyed 1,250 office professionals in 2026 and found 66% had used AI at work believing their company's policy did not permit it, and 88% had shared work information with a public tool like ChatGPT, Claude or Gemini. Here is the part that should stop the meeting: 86% of them believe their employer already has an AI policy. Both of those are true at the same time, in the same building, about the same people.

And the company is not behind. Census Bureau data put AI use across US businesses between 17% and 20% from December 2025 to May 2026, rising with size: 32% of firms with 100 to 249 employees, 37% of firms with 250 or more. Nobody publishes the fifty-person band, but that gradient only runs one way. Which means nobody here is falling behind a peer group. The peer group is standing still too.

The intuition is that a company full of engineers has this covered. It is backwards, and the mechanism is boring rather than dramatic.

Your product roadmap has an owner, a sprint, a review, and someone whose quarter depends on it. Your AI work has none of those. So in every planning meeting AI loses, and it does not lose because anyone argued against it. It loses because nothing was arguing for it. Eighteen engineers who could build almost anything build the thing with a name on it. That isn't a culture problem. It's how prioritization works when one item has an owner and the other one has enthusiasm.

MIT's Project NANDA analyzed 300 public AI deployments and found that about 5% of pilots accelerate revenue while the vast majority stall with little to no measurable impact on P&L. McKinsey's global survey puts the ownership problem plainly from the other end: on average, two leaders are in charge of AI governance. Two owners is a committee. A committee is nobody with a slower calendar.

So the thing a fractional AI officer is actually being bought for at this size is not technical capability. You have that. It is the decision, and the willingness to defend it in the room where the roadmap gets set. If you are still weighing whether the answer is an outside owner or a full-time hire, we worked that comparison through separately.

Month one produces a list, and the list is the entire deliverable. Not a maturity assessment, not a strategy document, not a workshop. One spreadsheet naming every AI tool in the building, who pays for it, on which card, what data it touches, who actually uses it, and which of the two stalled pilots it belongs to.

At fifty people this takes about two weeks, and that is the size advantage nobody mentions. A 5,000-person company cannot finish this inventory in a quarter. You can finish it before the second invoice.

Three things come out of it every time. The tool count is higher than leadership guessed, because Zylo found expense-based SaaS spend rose 267% year over year, which is the accounting signature of software arriving through personal expense claims instead of procurement. The two official pilots turn out to have four unofficial siblings, usually one in marketing and one in support, and at least one of them is working better than the funded ones. And somewhere in the list is a subscription being paid twice under two spellings of the same vendor name.

What leadership gets at the end of month one is not a plan. It is the first honest picture of what is already happening, with costs attached and a name next to each line. That picture is most of what we sell as an audit, and it is deliberately the cheapest thing in the engagement, because a company that will not look at this list will not act on anything that comes after it.

Month two is where you find out whether you actually handed over authority or just handed over a title.

The output is a ranked list with exactly one thing above the line and a kill date on everything below it. Both stalled pilots get a decision in writing: resourced, restarted with a new owner, or stopped. Stopping one is the point. An AI owner who has not killed anything by the end of month two has not been given a veto, and you are paying for advice that nobody is obliged to take.

The governance half of month two is one page, not a framework. Which tools are approved. What customer data may never go into a general-purpose model. Who signs off on a new tool, and how long that takes. That page exists because of the numbers above: only 42% of mid-market firms have a formal AI policy with actively enforced controls, and only 53% have full visibility into what their staff are using. One page that people read beats a twelve-page policy that sits in a drive nobody opens.

The fights start here, and they are worth having early. The sales team likes the tool that is about to be banned. An engineer has strong views about which model. Somebody will say the roadmap cannot absorb this quarter. All three are real, and all three are the reason the last six months produced nothing.

By day ninety there is one thing live, running against real data, with real users touching it. Not a demo, not a sandbox, not a pilot with five hand-picked inputs. If month three is still a document, the engagement has already failed and months four through six will not rescue it.

For a B2B SaaS company the first build is almost always support, and the reason is arithmetic rather than fashion. Six support people, a documented product, and a ticket queue with a long tail of the same twelve questions asked in forty different ways. Intercom publishes an average Fin resolution rate of 76% across more than 7,000 teams as of June 2026. Read that number the way it deserves to be read: it is a vendor reporting an average across its own installed base, weighted toward customers who kept paying. Treat it as the ceiling, not the forecast. B2B tickets run harder than consumer ones, and a company whose docs are three releases out of date will land nowhere near it.

Which is why the first build usually comes with an unglamorous prerequisite, and why month three is honest about it. The agent is only as good as what it reads. If the knowledge base is stale, month three ships the ingestion and the escalation path and a resolution rate in the thirties, and the roadmap for month four is fixing the docs. That is a real result. A slide claiming 76% is not.

The deliverable at ninety days is three things: the workflow live, a measured before-and-after on one metric that existed before you started, and a handover document written while it was being built rather than promised for later.

Months four and five are the quiet ones, and they are the months that decide whether any of this survives the engagement ending.

Month four is the second build, and it moves faster than the first because the arguments are already settled. Which model, who approves, where the logs go, what happens when it is wrong. Those took three weeks in month three and take three days now. At a SaaS company the second build is usually internal rather than customer-facing: sales research and account briefs, or the finance close, or the pile of security questionnaires that eats a week of somebody's month every month.

Month five is the third build, and by then the requests stop coming from the AI owner. Your own people start proposing them, and the proposals get better because they have watched two of these land and they know what a good candidate looks like. That shift is the actual product of the engagement. Not the three agents, the taste.

The handover is the part nobody asks for and everybody needs. Each build ships with the prompts, the failure cases, the escalation path, and the named person inside the company who owns it after the retainer ends. Not documentation written at the end as a courtesy. Written during, because a handover assembled in the final week is a handover nobody has ever tested.

Month six is a report to leadership with three numbers in it: what shipped, what it returned against a baseline that existed before you started, and what got cut.

That third number is the one people skip, and it is the most credible one on the page. Killing a subscription and reporting the saving is a checkable claim. So is deflecting a measured share of a ticket queue you were already counting. McKinsey found 39% of respondents attribute any EBIT impact at all to AI, and most of those say it is under 5%. Against that background, three live workflows with honest before-and-after numbers is not a modest result. It puts you in the minority that can answer the question at all, and we wrote up what the ROI evidence actually supports rather than what the vendor decks claim.

Six months does not end with AI solved, and any engagement promising that is selling you a feeling. It ends with three things live, one page of rules people have actually read, a named internal owner, and a leadership meeting where the AI line has a number next to it. Only 26% of mid-market firms say AI is scaled and governed across the company. That is the bar, and it is lower than the noise suggests.

Six months at our retainer floor of $5,000 a month is $30,000. If the company wants one scoped thing shipped before committing to any of the above, a starter build runs $1,500 to $2,500 fixed, and one full workflow live in about two weeks is $5,000 fixed. The whole ladder is on our pricing page, and the retainer floor is a floor on ongoing work rather than a minimum you have to spend to talk to us.

The public bands for fractional AI leadership run roughly $5,000 to $30,000 a month, and the awkward part is that no rate survey exists behind any of them. No labor department tracks the occupation. Every range you can find, this one included, traces back to somebody quoting their own card.

So compare it against something real instead. Built In puts US base pay for a senior AI leadership seat at $224,550, which is $112,275 for six months before a single employer cost, and closer to $160,000 once you apply the BLS wage share. That figure still counts no recruiter fee, no equity, and none of the months the seat sits empty while you search.

And compare it against the money already moving. At the Zylo median, 36% of a fifty-person company's software spend goes to licenses nobody opens, which is about $85,000 across the same six months. The unused seats cost more than the person who would have found them.

Four signals, and every one of them is countable by someone who was not in the meetings.

Month three produced a document. This is the whole test and it is binary. A roadmap in month three is month two arriving late.

Nothing was stopped. If every tool that existed in month one still exists in month six, no one exercised a veto, and the engagement was advisory work wearing an executive title. Additive-only AI leadership is the tell that authority never transferred.

The report has no number that predates the engagement. A before-and-after needs a before. If every metric in the month-six read was invented in month five to make the month-six read look good, you have a marketing artifact and not a measurement.

Your own people are not proposing builds. By month five the ideas should be arriving from support and finance and sales, not only from the person you are paying. If the AI owner is still the sole source of candidates, nothing has transferred and you will restart from zero when they leave.

One of these is a bad month. Two of them mean the shape is wrong. Renegotiate the mandate rather than renewing the retainer, and be specific about which decisions the owner gets to make alone.

The SaaS company is the hard version of this problem, which is why it is worth walking through. It has engineers, so nobody believes it needs help, and the engineers are booked, so nothing gets built. That combination produces the longest gap between capability and output of any company shape we look at.

A fifty-person company whose product is not software runs the same six months with two differences. The inventory takes less time, because the tool sprawl is smaller and lives mostly in one or two departments. And the build capacity has to come from outside, which sounds like a disadvantage and usually isn't, because outside capacity turns up on the day it is scheduled and an internal team turns up after the roadmap says so. That is the honest reason month three lands on time more often there than at a software company.

The cadence does not change with headcount either, only the duration of each step. At two hundred people the inventory is a month rather than two weeks and the fights in month two involve more people. Month three is still ninety days and still binary. If a proposal you are reading stretches the first build past ninety days because you are bigger, ask which specific dependency needs the extra sixty days, and get the answer in writing before you sign.