AI Strategy Audit or sprint, when each one fits.

When a founder shows up to the offering page, there are two front doors. One is the AI Strategy Audit, which is a seventy-five hundred dollar engagement that runs as a half-day working session with Roy, produces a written roadmap of which functions to fractionalize and in what order, and closes with a sequenced sprint plan you can take to your team. The other is a direct sprint application, which scopes a single fractional department, kicks off in seven to ten days, and ships live output by day fourteen. Both are real entry points. The question is which one fits the specific shape of your team and your current pain.

The honest framing is that the audit is the right answer in roughly thirty percent of cases and the sprint is the right answer in the other seventy. Most founders who land on the page have already done the diagnostic work themselves. They know which function is failing. They know what the year-one plan looks like with and without a fractional layer. They want to move on the sprint and stop thinking about it. For these teams the audit is a slower start with extra steps. For the teams where multiple functions are bleeding and the sequencing is unclear, the audit is the one move that prevents a five-figure mistake in week one.

The audit fee is credited against the first sprint retainer when you sign one, which removes the cost objection from the decision. You are not choosing between paying for the audit and paying for the sprint. You are choosing whether the first half-day of the engagement is spent on roadmap or on kickoff. The decision is about which mode of work matches your actual confidence level on the sequencing question. We wrote about the underlying structure in What is a Fractional AI Department.

The audit is the right first move when you can name three or four gaps and you cannot rank them with confidence. The SDR motion is underperforming and the blog has not shipped in months and the COO is doing Sunday reporting and the support inbox is stacking. The founder cannot tell which gap is most expensive, which gap pays back fastest, or which gap is the structural bottleneck that the others depend on. In that situation a sprint into the wrong function is a five-figure mistake against an unclear baseline. The audit is the cheap way to make sure the first sprint goes into the right function.

The half-day audit session works through the org chart, the cap table, the current revenue motion, the team gaps that are already on the next-hire list, the calendar of the senior team, and the actual cash flow model. By the end of the session there is a written roadmap that names which function is the first sprint, which function is the second sprint, what the inputs are for each, and what the expected payback window looks like for each. The output is not a deck. It is a sequenced plan you can take to your co-founder, your CFO, and your board.

The second case for the audit is when the team is multi-functional and the founder is not the only decision maker. CEO and COO and head of product all have different intuitions about which function is the priority. The half-day session aligns the senior team on a single plan before the engagement starts, which prevents the situation where the sprint goes live and the head of product is asking why we did not run Content first because she was sure that was the gap. The alignment is the value as much as the roadmap is.

The third case is when there is a real funding event in the near term. Pre-fundraise or post-fundraise teams sometimes want a written plan to take to the board or to the new investor. The audit produces a credible artifact for that conversation. The artifact is not a sales document. It is a sequenced operating plan that names the next four fractional sprints and what each one is expected to produce in year one. Boards engage with that shape of plan more easily than they engage with a single sprint pitch.

The sprint is the right first move when one function is clearly the gap and the founder can name it in fifteen seconds. The SDR team is sending eighty emails a day at one percent reply and the founder is doing the third and fourth outbound conversations personally. The blog has not shipped in four months and the founder is writing LinkedIn posts at midnight to keep the brand alive. The COO spent the last three Sundays on board prep and is on the edge of burnout. The support inbox has eight hundred unread tickets and the head of CS is on her third overnight contractor search. In each of these shapes the function is obvious. The half-day audit conversation would surface what the founder already knows.

In these situations the audit is a delay, not a clarity-add. The team spends seventy-five hundred dollars and a half-day on a session that confirms what was already clear, then signs the sprint a week later. That week is real money. The Sales sprint that starts a week later produces the warm replies a week later. The Content sprint that starts a week later starts compounding a week later. For a team where the function is obvious, the right move is to apply for the sprint directly and use the kickoff call to handle the scoping work the audit would have handled.

The honest filter is whether you can name the failing function in fifteen seconds without hedging. If yes, sprint. If you find yourself listing three or four gaps and qualifying which one is biggest, audit. The hedging is the signal. The audit is what the hedging is asking for.

The first question is the fifteen-second test. Can you name the single failing function without hedging? If yes, sprint. If you find yourself listing three or four gaps and qualifying which one is biggest, audit. The hedging is the signal. The audit is what the hedging is asking for.

The second question is the senior team test. Is the founder the only decision maker, or does the senior team have to align before the engagement starts? If founder-only, sprint. If the COO and head of product and head of growth all have to agree on the sequencing, audit. The half-day session is faster than four separate one-on-one conversations across the senior team, and the written roadmap is what the team aligns against.

The third question is the fundraise timing test. Is there a funding event in the next ninety days where a written plan would carry weight? If no, sprint. If yes and the board or new investor would engage with a sequenced operating plan more easily than with a single sprint pitch, audit. The roadmap is a credible artifact for that conversation. The artifact is the value as much as the sequencing is.

If you answered sprint to all three, sprint. If you answered audit to one or more, the audit is the right first move. The decision is rarely close once the three questions get honest answers. We see the close calls in roughly ten percent of cases, and those usually resolve toward the audit because the cost of being wrong on the sequencing is higher than the cost of the half-day session.

A Series A SaaS team, fifteen people, outbound bottleneck. Two SDRs producing two qualified opportunities a month, founder doing the third conversation personally, board asking about pipeline at the next meeting. This team did not need an audit. The Sales function was obviously failing and the founder could name it in ten seconds. They applied for a Sales sprint directly, kicked off in seven days, had warm replies in week three, and added a Content sprint in week eight when the Sales cadence was stable. Total time from inquiry to live output: fourteen days.

A seed-stage developer tools team, eight people, mixed signals. Open source traction was building, the blog had not shipped in three months, the COO was wearing three hats, the SDRs they had hired ramped slowly because the buyer was inbound-led. The founder could not pick between Content, Ops, and Sales because each one had real pain and the sequencing was not obvious. They ran the audit. The written roadmap put Content first because the market was warm and the cluster strategy was the structural unlock. Ops was sprint two because freeing the COO was the next-highest leverage move. Sales was sprint three because the inbound from content made the outbound easier to scale on top of. The audit prevented a Sales-first sprint that would have under-delivered against an inbound-led buyer.

A pre-Series B fintech team, thirty-five people, real funding event in ninety days. Multiple bleeding functions, senior team not aligned on the priority, board member asking for a written plan before signing off on the spend. They ran the audit not because the sequencing was unclear in the founder head but because the artifact was the value. The roadmap went to the board in advance of the next meeting. The board signed off on a four-sprint plan. The first sprint kicked off the day after the board meeting. The audit was the wedge that got the spend approved cleanly.