The First Ninety Days: What Actually Ships

All of them promise the same shape, and most of them promise it without a single citation. We read the pages currently ranking for this question. They run from about 1,800 to 4,500 words. They split the quarter into days 1 to 30, 31 to 60, and 61 to 90. They name between four and ten deliverables per phase. The longest of them carried no external source at all. Just its own cost bands and a proprietary methodology name it never actually explains.

Here is the pattern nobody comments on. Go through the deliverable lists and count the items that are a working system. Scorecard, assessment, inventory, roadmap, blueprint, framework, training kit, measurement framework, operating model, execution plan. Every one of those is a file. The word "pilot" shows up, usually as "the first initiative moves from plan to pilot", which is a verb doing a lot of hiding.

That is not a small stylistic complaint. It is the whole difference between a quarter that compounds and a quarter that ends with a leadership team politely thanking someone. A fractional AI officer who bills for three months and hands over ten documents has sold the same thing a consultancy sells, at a discount, with a better title on it. We wrote about that split at length in the question of whether the hire comes with delivery capacity, because it is the one thing buyers get wrong before they sign anything.

So the framework below is organized around a single distinction. In each phase, what is running, and what is only written down.

Two weeks, one deliverable, and it is a written one: a list of every AI tool and every half-built automation already running inside the company, with an owner and a cost against each line. It skips the strategy, the roadmap, the forty-slide future-of-work deck. Just a list. The plan document is a different object and it lands earlier: what should be on the table by Friday of week one is the scope, the gates and the acceptance test, not the finished inventory.

It takes two weeks because the list is never the list leadership has in their head. UpGuard's 2025 state of shadow AI research surveyed 500 security leaders and 1,000 employees and found 81% of employees and 88% of security leaders reporting use of unapproved AI tools, with 40% of employees using them daily despite having sat through the training. So the gap is rarely one or two tools. It is the zap that has been quietly moving customer records since spring, the browser extension nobody in IT has heard of, and the account somebody set up on a personal card because procurement was going to take a month.

The second half of the two weeks is ranking, and the rank order is where the argument happens. This is the same walk-the-work exercise that sits underneath our 10x audit: function by function, where do the hours actually go, and which of that work is safe to hand to a machine now. The output is one page with a numbered list on it and one item circled. That circled item is what weeks three to six build.

What does not ship in weeks one and two: a governance framework. Writing rules for AI work before you have any AI work in production produces a policy that regulates a hypothetical, and it is a comfortable place to hide for a full month.

One workflow, live, against production data, with the people who do that work using it. That is the whole deliverable for weeks three to six, and it is the one the published plans replace with the word "pilot".

Four weeks is not an aggressive target and we are not being clever about it. Taking one scoped workflow to production is a two-week job when the data access is clear, which is why our sprint is priced as a fixed two-week piece of work. A four-week window for the first build inside a broader engagement therefore has a fortnight of slack in it on purpose. That slack is not for the model. It is for the two conversations that always happen: who owns the credentials, and which exceptions still need a human.

The build itself is ordinary work, and it is the kind of thing our embedded engineers do on the production side rather than in a notebook. Read the inbox, draft against the rules, escalate what does not fit. Connect the CRM to the billing system so a person stops carrying data between tabs. Nothing here is research.

Then the gate. Did it run in week six, with real users, on real data, rather than a demo that is ready or a build still sitting in UAT. If the answer is no, the engagement has learned something expensive and true, and the correct response is to say the plan was wrong and rescope it. Pushing the same plan into weeks seven to twelve is how a quarter ends with a slide that says "foundations laid".

Three things ship in the back half, and only one of them is another system.

The second build is the easy one, because by week seven the arguments about credentials and exceptions have already been had once. The rules come next, and they are written now rather than in week two because they can be specific: what these two systems may touch, what stays with a person, where the audit trail lives, who gets paged when a run fails. A policy written against two live workflows is a page. A policy written against a hypothesis is a chapter, and nobody reads it.

The third is the one clients rarely ask for and always need. A named internal owner, sitting in the reviews, with the runbook and the evaluation criteria in their hands. Grant Thornton's 2026 AI Impact Survey found 46% of operations leaders at $1.1B to $5B companies naming workforce skill gaps as the primary obstacle to AI, against 29% in the midmarket. Handing back a working system to a company that cannot operate it is a slower kind of failure, and it does not show up until the quarter after the invoice.

Day ninety is a read, not a celebration. What shipped, what got cut and why, what the two live workflows are worth in hours or errors or cycle time, and what the next quarter should attempt. Naming what got cut is the part that makes the rest of the report believable.

Model choice is not on the list. It is the thing buyers ask about first and it is close to the least consequential decision in the quarter.

Data access. Somebody has to grant a service account read access to the system the workflow depends on, and that request lands in a queue behind everything else IT is doing. Cloudera's numbers put the scale of it plainly: nearly 80% of 1,270 IT leaders say limited data access across environments is holding AI back, while 18% say their data is fully governed. Gartner's 2025 research found 63% of 248 data management leaders either lacking or unsure of the right data management practices for AI, and predicted that through 2026 organizations would abandon 60% of AI projects unsupported by AI-ready data.

The workflow redesign. Wiring a model into the process exactly as it exists today gets you a faster version of a process that was already bad. Redoing the process is where the return lives, and it is also the part that requires the people who do the work to change how they do it. BCG's guidance, published across several of its 2026 pieces including Scaling AI Requires New Processes, Not Just New Tools, puts 10% of the effort on algorithms, 20% on technology and data, and 70% on people and processes. Deloitte's 2026 survey of 3,235 leaders across 24 countries found 37% still using AI at surface level with minimal process change.

The named owner. Somebody inside the company has to hold this after the engagement ends, and that person has a day job. If the owner is named in week eleven, the handover is a calendar invite. If they are named in week two and sit in every review, the handover is a formality.

Sponsor attention. The executive who wanted this is the same executive with a reorg and a board meeting. Attention decays, and it decays fastest in the fortnight after the first thing goes live, which is exactly when the second build needs decisions.

A gate is only a gate if failing it changes something. Otherwise it is a status meeting with a better name.

Gate one, end of week two. Is there one workflow that is scoped, owned by a named person on the client side, and unblocked on data access? Not three candidates. One. If the answer is no, the honest conclusion is that the engagement has produced a survey, and the next conversation is about whether the blocker is fixable in a fortnight or whether this company is not ready to buy delivery yet.

Gate two, end of week six. Did the first workflow run in production against real data with real users? If yes, weeks seven to twelve proceed. If no, the plan gets rewritten around the actual blocker rather than around the original ambition. Naming the blocker is the deliverable here, and it is worth more than the six weeks of work that failed to route around it.

That is the difference between a fractional AI leader and a retained advisor, and it is the whole reason the seat exists. An advisor's ninety days ends with a recommendation. An owner's ninety days ends with something running and a written account of what did not.

Because a case study we cannot show you the evidence for is worth nothing, and we would rather publish nothing than publish that.

This matters more than it sounds like it should. The archetype this post belongs to is the first-party delivery study, and the honest version of it for a firm our size is the framework and the gates, not a set of numbers with a logo next to them. Every provider in this category can produce a page of results. Almost none of them can produce the raw material behind those results, and you have no way to tell the two apart from the outside.

So take this instead. The cadence above is what we run and what we will be held to. The gates are stated in advance, with the failure condition written next to each one, which means you can hold up your own engagement against them at week two and week six and get a straight answer. That is a harder thing to publish than a testimonial, and it is checkable in a way a testimonial never is.

Where the numbers in this post came from is stated on every chart. All of them are third-party research. None of it is ours to claim.

Three cases, and we would rather say them here than three weeks into an engagement.

If you have one clearly defined workflow and no ambition beyond it, ninety days of leadership is overkill. Buy the build. A starter build runs $1,500 to $2,500 fixed and a two-week sprint puts one full workflow into production for $5,000, and neither of those needs anybody sitting in your leadership meetings.

If nobody will give the work a budget and a veto, ninety days will produce a very good plan that loses every subsequent planning meeting to the product roadmap, because the roadmap has an owner and a bonus attached and your AI work does not. That is not a delivery problem and no cadence fixes it.

And if your data lives in a system that nobody has been able to get an export out of in two years, the first gate will fail and you already know it will. Fix that first. It is unglamorous work and it is the actual prerequisite, whatever anybody's phase-one deliverable list says.