In the first quarter of 2026, Gartner surveyed 12,004 employees and managers across 40 countries. Of the ones whose employer had already given them enterprise AI access, 88% were using their own personal AI tools for work anyway.

That is a verdict. The people the centre exists to serve have already priced its output and routed around it.

The argument

A centre of excellence can only supply the things it controls. It controls tools, standards and approvals. It does not control workflows. Workflow redesign is the one variable that separates the companies getting AI value from the companies getting AI invoices. So the centre is structurally incapable of producing the outcome it was funded to produce. It is not a capability function. It is a permission desk with a budget.

What the numbers actually say

McKinsey ran its global AI survey between 4 May and 8 June 2026: 1,719 respondents across 97 nations, 36% of them at companies above one billion dollars in revenue. Thirty-seven percent attribute at least some EBIT impact to AI, which is about the same share as the year before. Six percent are high performers who attribute 5% or more of EBIT to AI use. The thing that separates them is not their model choice. Nearly three quarters of the high performers report fundamentally redesigning workflows, against 25% of everyone else.

Now put the spend next to it. BCG’s AI Radar 2026, published January 2026, surveyed 2,360 executives including 640 CEOs across 15 markets. AI investment is set to roughly double this year, from about 0.8% of annual revenue to about 1.7%. On a one billion dollar business that is a move from roughly 8 million dollars to roughly 17 million dollars in twelve months. In the same survey, 94% of CEOs said they would keep investing even if 2026 initiatives underperformed.

The spend doubles. The share of companies reporting any EBIT impact does not move. The marginal nine million dollars bought no measured change in the odds of impact.

Here is why. That money is being spent by a function whose authority stops at the tool. A centre of excellence can buy a model, set a standard, run an evaluation, approve a vendor and publish a prompt library. It cannot tell the claims team to stop doing the second review. It cannot collapse three handoffs into one. It cannot change who signs. Those are the acts that move a line in the P&L, and they belong to whoever owns the line.

MIT’s NANDA study on the GenAI divide ran from January to June 2025 across 52 structured interviews, 153 survey responses and more than 300 publicly disclosed initiatives. Its finding on organisational design is one sentence long and almost nobody quotes it: the organisations that succeeded sourced their AI initiatives from frontline managers, not central labs. The same study found pilots built through external partnerships reached full deployment 66% of the time, against 33% for pilots built internally. Task-specific internal tools reached production 5% of the time. General purpose tools bought off the shelf reached production 40% of the time.

A centre of excellence is an internal build shop staffed by people whose standing depends on internal builds.

I stopped opening engagements with the AI strategy deck about two years ago. I ask for two artefacts instead: the list of people who can change a business process without seeking approval, and the central team’s intake queue. The list usually fits on one hand. The queue usually runs to dozens. Everything that goes wrong over the following year is already legible in that ratio, and thirty years of writing software has not shown me a tool that repairs it.

The mechanism

A use case is found by the person doing the work. Everything after that is decided by one question: who is allowed to change the process. If the central team holds the tools and nothing else, the idea goes onto an intake form, waits for a monthly rubric, and comes back as an approved tool sitting on top of an untouched workflow. That is a pilot with no line in the P&L. If the unit that owns the process holds the decision, the workflow is redesigned first and tooled second, and the impact lands in that unit’s own numbers. Same idea, same model, same vendor. Different owner, different outcome.

Three things that have already been measured

The shadow economy was counted twice, a year apart, and it grew. In mid 2025 MIT found that only 40% of companies had bought an official LLM subscription while workers at more than 90% of surveyed companies were using personal AI tools for work. The obvious reading was a procurement gap: buy the licences and the shadow disappears. Gartner’s first quarter 2026 data says it did not. Among employees who had enterprise access, 88% still used personal tools, and those hybrid users were 1.7 times more likely to report significant time savings than the compliant ones. The shadow is not a licensing failure. It is people avoiding the latency of the approved path, and they are right to, because it makes them faster.

Uniform governance is the only kind a central body can produce. On 26 May 2026 Gartner predicted that 40% of enterprises will demote or decommission autonomous AI agents by 2027 after governance gaps surface in production. Shiva Varma, the analyst behind it, put the cause plainly: enterprises treat agent governance as binary, either locked down or fully trusted, and that is the root of the failure. Over-restriction of simple agents, in his words, slows delivery and drives shadow development. A central body cannot hold the context of forty different workflows, so it writes one rule and applies it to all of them. That is not a staffing problem. It is what centralisation is.

The talent leaves. On 13 May 2026 Gartner predicted that half of enterprises without a people-centric AI strategy will lose their top AI talent to competitors by 2027. In the same research, 27% of executives reported having a comprehensive AI strategy and 20% of leaders believed their workforce was AI-ready. A centre of excellence takes the scarcest engineers in the company, concentrates them in one team, and hands them a queue of intake forms to triage. There is no faster way to lose them.

Where this breaks

Four places, and I will not pretend they are small.

Comparing BCG’s spending figure with McKinsey’s impact figure is not a panel study. Different samples, different questions, different months. The doubling and the flat line are directional, not a measurement, and anyone who wants to reject that inference is entitled to.

The MIT sample is small, partly recruited at conferences, and the fieldwork is now more than a year old. Its 95% headline has been over-read by almost everyone who has quoted it, including people arguing my side. The frontline-managers finding is qualitative and it is one sentence.

Regulated industries are a real exception. Model risk management in a bank, clinical safety in a hospital, anything touching defence. There a central body is a legal requirement and removing it is not an option. In those settings the right question is how fast the central body can say yes, not whether it should exist.

And the strongest objection, which I hold myself: some things must be central. Identity, the evaluation harness, data contracts, model procurement, the audit trail. That is a platform team, and platform teams belong in the middle. The failure mode is not centralisation. It is merging the platform team with the permission desk, so that the group who builds the substrate is also the group who decides who is allowed to use it. Below roughly two hundred people none of this applies, because there is no centre to dismantle.

What I would do on Monday

1. Write down every person who can change a business process without asking anyone. If that list does not contain a person who touches the workflow you want AI inside, nothing you buy this year will show up in the P&L.

2. Split the central team on paper into two functions. Platform keeps identity, evaluation, data contracts and model procurement. Permission is deleted, and the decision moves to whoever carries the P&L line.

3. Set a dollar threshold under which no approval is required, only a note afterwards. Pick the number that makes your CFO slightly uncomfortable and publish it where everyone can see it.

4. Measure approval latency. Count the days from a named person having an idea to that same person being allowed to try it. If the answer is longer than five days, the 88% is your number too.

5. Default to buying. Sixty-six percent against thirty-three percent. Put the ratio into the intake criteria and make anyone proposing an internal build argue against it in writing.

The intake form is not the problem. The form is the confession. It says the company has decided that the risk of one person trying the wrong thing is larger than the risk of nobody trying anything, and most of the money burned in the last three years sits inside that sentence.

Keep the platform. Keep the evaluation harness. Burn the form.

I spend most of my week inside delivery organisations working out why an approved tool never reached the P&L. If that is the gap you are looking at, book a call.

That page was the best converting page on most of those sites for about fifteen years. It was the middle of the funnel, written down.

I have not watched one of those pages earn a click in months. It still ranks. It is still being read. It is being read by a model, and the model is not sending anyone.

The thesis

Zero-click is not the death of search. It is the death of one stage of the funnel, and it is the middle one. Buyers still start with a question and they still end with a purchase. What they no longer do is visit you while they are deciding between you and three other people.

The decline is not spread evenly, and that is the whole story

Start with the number everyone quotes. SparkToro, using Similarweb clickstream data for January to April 2026, found 68.01% of United States Google searches ended without a click. That was 60.45% in 2024 and 49% in 2019. Rand Fishkin also put AI Overviews in more than 20% of searches, cutting clickthrough by roughly 60% where they appear. Ahrefs, tracking Google referral share across more than 75,000 domains, measured an eight percentage point fall between June 2025 and May 2026, about a 22% drop.

Most people read those numbers as a flat tax. Everything goes down a fifth, so write more content and hold on.

Then look at where the answer box actually went. Semrush tracked more than 600,000 keywords across ten industries on the United States desktop database from November 2025 to April 2026. AI Overview presence on commercial-intent queries grew 71% over those six months. On transactional-intent queries it fell 5%. In finance, commercial-intent presence grew 231.25%.

Commercial intent is not a technical term you can wave past. It is the query class where somebody types “best”, “vs”, “alternatives”, “compared”, “review”. Transactional intent is “buy”, “pricing”, “demo”, “login”. One of those is your middle funnel. The other is your bottom.

So the answer box is not taxing your site evenly. It is expanding fastest at exactly the point where a buyer is choosing between vendors, and retreating at the point where they have already chosen and want to transact. If you average the decline across your whole site you will conclude you have an SEO problem. You have a stage problem, and the stage that took nearly all of the damage is the one that used to produce your pipeline.

The shortlist is now built before you know the account exists

6sense surveyed more than 4,000 B2B buyers across North America, EMEA and APAC for its 2025 Buyer Experience Report. The split between independent research and seller engagement moved from 70/30 to 60/40. Then the finding that should stop you: 94% of buying groups had already ranked a preferred vendor before they made contact with any vendor at all. 77% of purchases went to that preliminary favourite. The pre-engagement favourite wins 80% of deals. And 94% of buyers said they used a large language model to synthesise and organise their research.

Put the two datasets next to each other. The stage where the shortlist gets built is the stage where the click disappeared, and the tool doing the building is a model that never visits.

And the model is not reading the page that ranks

This is the part most marketing teams have not absorbed. Ahrefs ran 15,000 long-tail queries through Brand Radar and checked where the cited URLs sat in Google. Across ChatGPT, Gemini and Copilot, an average of 12% of AI-cited URLs ranked in Google’s top 10 for the same query. ChatGPT in-text citations: 8.0%. Gemini: 8.6%. Copilot: 8.2%. Perplexity was the outlier at 28.6%. Roughly 80% of citations did not rank anywhere for the query they answered.

Your comparison page won the middle of the funnel by ranking. Ranking is now a poor predictor of being quoted. Those are two different retrieval systems with two different tastes, and you have been optimising for one of them for fifteen years.

I stopped asking for the rankings report about a year ago. When I sit down with a marketing team now, the first artefact I ask for is the list of domains cited underneath the answers their buyers get, and almost nobody has one. I have asked for it often enough to know the reaction: a pause, then someone offers me the Search Console export instead. That export measures a channel that has stopped being the one that decides.

What replaces the middle of the funnel

Not more content. Three changes, and they are uncomfortable in a way that content calendars are not.

Comparison content has to stop being self-serving. A model asked to compare four vendors will not lift a table where one vendor wins every row, because that table is not useful for the job it was given. It lifts the source that concedes something. The page that says “if you need X, buy the other one” is the page that gets quoted, and being quoted is now the thing you wanted from ranking.

Your presence has to exist off your own domain. Given that 80% of citations rank nowhere, the sources being pulled are review sites, forums, documentation, analyst write-ups and third-party comparisons. You cannot publish your way to a citation on a domain you control. You can be the vendor those sources have something specific to say about.

The metric has to change from sessions to mentions. If your dashboard counts visits, the middle of your funnel now looks like it has stopped existing. It has not. It has become invisible to the instrument you are holding.

Where this breaks

Four honest limits, and I would not publish this without them.

The 68% figure comes from a clickstream panel, United States only, four months. Panels over-represent some users and under-represent others. The direction has held across seven years of this study, so I trust the trend. I would not build a board slide on the second decimal place.

The Ahrefs overlap result is long-tail queries specifically. Head terms almost certainly overlap more, because head terms are where the well-known sources sit. If your category is three words wide, your mileage differs.

The 6sense numbers are buyers self-reporting after the fact, and people reconstruct their own decisions to look more orderly than they were. Nobody remembers being influenced. Everybody remembers deciding.

And the honest one: Semrush also reports that a visitor arriving from a language model is worth 4.4 times an organic search visitor, which is the statistic every AI search vendor has been quoting all year. It has no published sample size or method, and it has an obvious selection effect. Someone who arrives from a model arrives late, already informed, already close to buying. Of course they convert better. That does not mean the model created the demand, and treating it as proof of channel value is the same error as claiming credit for branded search.

If you sell into formal procurement, or you sell a commodity, or your revenue is renewals, your middle funnel was never on the open internet and none of this touches you.

What I would do on Monday

1. Tag every landing page as informational, commercial or transactional, then pull twelve months of traffic by tag. If the loss is concentrated in commercial, you have this problem. If it is flat across all three, you have a different one and this post is not it.

2. Write down the five questions a buyer asks in the four weeks before they shortlist. Ask them in ChatGPT, Gemini, Copilot and Perplexity. Record whether you were named and what was said about you. That is under an hour and it is a baseline.

3. Read the citations under those answers, not your rankings. Most will not be you and most will not rank. That list is your actual distribution channel now.

4. Take one comparison page and concede a real case where a competitor is the better choice. Name it. Then watch whether it starts getting quoted.

5. Put named-in-answer rate on the dashboard next to sessions. A number nobody owns is a number nobody moves.

The page is still there

That “X vs Y” page is still sitting on the site, still ranking, still being read more than it ever was. It is doing the job it was built for. It is comparing two products for a buyer who is deciding.

The buyer just never arrives to say thank you.

I spend most of my week inside companies working out why the pipeline thinned before the traffic did. If that is the month you are having, book a call.

The money arrived in the technology seat. Almost nobody announced it.

The thesis

The CTO job split in two this year. One half became capital allocation: deciding what gets funded, at what unit cost, and what gets stopped. The other half, the half whose authority was denominated in headcount, is being deleted by the same technology that delivered the money. Most people holding the title are still doing the second job and calling it the first.

What actually moved

Three things happened in about fourteen months, and they are usually reported separately.

The amount got large. Gartner put worldwide AI spending at $2.52 trillion for 2026 in its 15 January release, up 44% on $1.757 trillion in 2025. That is not a line item. In most large enterprises it is now the biggest discretionary number the technology function touches, and it is growing faster than the function that governs it.

The composition is hostile to a builder. Inside that $2.52 trillion, AI infrastructure is $1.366 trillion. AI services are $588.6 billion. AI software is $452.5 billion. AI models are $26.4 billion. AI data is $3.1 billion.

Divide the first by the last. For every dollar the world spends on AI data this year, it spends $441 on AI infrastructure.

I have not seen a capital allocation ratio like that survive contact with a board. Infrastructure is bought at a price three vendors set, and it reprices every time they do. Data is the only line in that list that compounds inside your company and cannot be bought by your competitor on the same terms. A capital allocator looks at 441 to 1 and asks whether that is the return maximising split. A delivery manager looks at 441 to 1 and approves the invoice, because approving invoices was never the part of the job anyone was measured on.

The org chart made a new seat. IBM’s Institute for Business Value surveyed 2,000 CEOs across 33 countries and 21 industries with Oxford Economics between February and April 2026. 76% of organisations now have a chief AI officer. Twelve months earlier it was 26%. In the same study, 77% said talent and technology leadership roles are converging, and 85% said every functional leader has to become a technology expert inside their own domain.

Read those two findings together. The mandate is leaving the technology seat at the same time the money is arriving in it. Whoever can price a decision keeps both. Whoever cannot keeps neither.

What an allocator has to say out loud

A delivery manager is measured on shipping. An allocator has to state three things before spending anything, and I have watched a lot of capable technology leaders fail to state any of the three for AI.

The unit. One sentence: what is one unit of output from this, and what does it cost today. Not productivity. A countable thing with a dollar figure attached to it.

The hurdle. What return clears. The FinOps survey found a growing number of organisations now requiring AI investment to be self funded out of efficiency gains. That is a hurdle rate. It was set by finance, not by technology. If you did not write it, you are not the allocator. You are the applicant.

The kill criterion. The date and the number that ends it. Deloitte surveyed 3,235 business and technology leaders across 24 countries for its 2026 State of AI in the Enterprise report. Only 25% had moved 40% or more of their AI pilots into production. Only 21% reported mature governance for agentic AI. A portfolio where three quarters of the positions never reach production and four fifths carry no governance is not underperforming. It is unmanaged.

The half being deleted

Gergely Orosz published a piece on 18 August 2026 on engineering leaders taking career breaks. He interviewed roughly twenty of them. Six of ten CTO level contacts told him they were on the way out. The reasons he recorded are worth reading in order: unrealistic AI expectations, cost cuts of 20 to 50%, equity sitting behind a preference stack, and smaller teams reducing the need for the leadership layer at all. Several said they would rather work fractionally than take another full time seat.

I have a direct interest in that last sentence. I do fractional CTO work through PADISO and enterprise AI delivery through Brightlume, so the pattern Orosz describes is also my order book. I am not neutral about it. I also think he is describing a structural change rather than a mood. If your authority came from managing 60 engineers and the organisation now needs 25, the authority left with the 35. Seniority does not replace it. The people leaving are the ones who worked that out first.

Where this breaks

Four honest limits.

Gartner’s category boundaries are doing a lot of work in my 441 to 1 figure. AI data at $3.1 billion almost certainly excludes the data engineering labour, the warehouse spend and the integration work already booked under other lines. The real ratio is better than 441 to 1. The direction holds. The magnitude is arguable, and I would not put that number in a board pack without the footnote attached.

The chief AI officer figure is self reported titles collected from CEOs. A title can be created with no budget behind it. Twenty six to seventy six in twelve months is also too fast to be a stable structure, and some of those seats will not exist in 2028. What it proves is that boards decided the technology seat as it stood was not sufficient. It does not prove they built the right replacement.

Orosz’s sample is about twenty people and he says so himself. It is a signal from a well connected observer, not a measurement.

And the split does not apply below a certain size. Under roughly fifty engineers the allocator and the builder are the same person on the same day, and pretending otherwise produces a CTO who writes memos while the product stalls. This is a problem of scale. It arrives at the point where the AI bill starts to rival the engineering payroll.

What I would do on Monday

1. Write the unit for every AI initiative you fund. One sentence each: the countable output, and its cost today. If you cannot write it in a sentence, you are not funding a position, you are funding an activity.

2. Find out who set the hurdle. If AI at your company has to pay for itself out of efficiency gains, name the efficiency line and the quarter it lands in. If finance wrote that and you did not, fix the order.

3. Write the kill criterion before the next invoice. A date and a number. Put it in the same document as the business case, not in a review deck six months later.

4. Pull last quarter’s AI spend apart into infrastructure, licences, models and data, and compute your own ratio. Compare it to 441 to 1. If yours is worse, you have an allocation problem, not a technology problem.

5. If a chief AI officer was appointed at your company in the last twelve months, find out this week whether they hold the pen or the press release. The answer tells you which half of the job you still have.

I built D30 to pull three statement fact files out of ASX annual reports instead of hiring analysts to read them, because one of those options has a unit cost that falls every year and the other has one that rises. That was a capital decision taken from a technology seat. It is the only kind of decision that seat gets judged on from here.

The FinOps Foundation changed one word. Cloud became Technology. It reads like housekeeping. It is a charter, and charters get written after the power has already moved.

Brightlume does this work with enterprise teams. If the gap between the AI pilot and the P&L is the problem you have, talk to me.

In March 2025 S&P Global Market Intelligence surveyed more than 1,000 companies across North America and Europe. 42% had scrapped most of their AI initiatives that year, up from 17% the year before. On average, 46% of proofs of concept were killed before they reached production.

Six years apart. Two different technologies. The same arithmetic.

The thesis

Your AI transformation will fail where your digital transformation failed: at the handoff between the people who understand the business and the people who build. That part is not new. What is new is the artefact that has to cross the handoff, and the fact that nobody has been assigned to own it.

In digital transformation the artefact was requirements. Requirements have a named owner, a template, a sign-off and a change process. Every organisation over 200 people has a settled opinion about who writes them.

In AI the artefact is the evaluation set. It is a dated, versioned list of real inputs, each paired with a judgement on whether the output was correct, written by somebody who knows the business. Almost nobody owns it. The business side assumes it is technical because it lives next to the code. Engineering assumes it is a business input because an engineer cannot say whether a claims summary is right. So it never gets written, and the system ships against taste.

What actually changed

I have written software since 1995. For most of that time the hard part of a handoff was ambiguity in a spec. You wrote the requirement, an engineer misread it, a test caught the gap. The test was cheap because correct was a property of the code. Two plus two returns four or it does not.

A language model moved correct out of the code and into the business. Whether a summary of a 60 page annual report is right is not a property of the function. It is a property of what your analysts would have written, and the only people who can say are your analysts.

That is a job. It has a size. Hamel Husain, who teaches this discipline to engineering teams, puts it at 60 to 80% of development time spent on error analysis and evaluation. His method is specific: appoint one principal domain expert as the final word on quality, have that person personally annotate at least 30 traces before anything is automated, push to 100 or more, and make every judgement binary pass or fail rather than one to five, because a five point scale lets an annotator hedge into the middle.

Read that as an org chart problem rather than an engineering one. Between 60 and 80% of the work on your AI system belongs to a person whose day job is claims, or lending, or clinical coding. Nobody has taken that person off their normal duties. Nobody has written the role into the program plan. The steering pack reports adoption, licences and pilot counts, because those are countable without a domain expert. So the build runs for nine months with no measured definition of correct, and then somebody asks what it returned.

Three places this shows up

Buy beats build by exactly this margin. MIT NANDA reviewed 300 plus public AI deployments between January and June 2025, with 52 structured interviews and 153 survey responses. 95% of enterprise GenAI pilots produced zero measurable return against 30 to 40 billion dollars of spend. Tools purchased from specialist vendors reached deployment about two thirds of the time. Internal builds managed about one third. The usual reading is that vendors are better engineers. I do not accept that. A vendor arrives carrying an evaluation set already built across dozens of customers, and it encodes what correct looks like for that task. Your internal team starts with an empty file and no authority to requisition the one person who could fill it.

The same instrument gap repeats at the cost layer. KPMG surveyed 204 US C-suite leaders at companies above 1 billion dollars in revenue between 28 April and 25 May 2026. 53% have deployed agents. 18% orchestrate multiple agents, double the previous quarter. Average planned investment is 202 million dollars over the next twelve months. Only 26% have real-time visibility of what those agents cost to run, and only 36% have token or usage controls. In asset management and private equity, full cost visibility sits at 4%. Same shape as the evaluation gap: money committed at scale, no instrument attached, and the numbers came from the people who signed the cheque.

Gartner’s forecast lands on top of that. More than 40% of agentic AI projects cancelled by the end of 2027, on escalating costs, unclear business value and inadequate risk controls. Unclear business value is not a cause. It is the name we give a missing measurement once the invoice arrives.

I got the order wrong myself. D30 pulls three statement fact files out of ASX annual reports. I built the extraction engine before I wrote the articulation gates, which is backwards, and I paid for it in a rebuild. The gates are now the definition of correct and the model does not get a vote on them. SearchFIT’s unit is one tracked prompt scanned across the answer engines, and whether the answer is right is a judgement about brand positioning that a marketing lead has to make, not an engineer. D23 runs managed Apache Superset, where a dashboard is correct when the finance lead would put their name on it. In all three the definition of correct has one person against it. In client programs I now decline to start a build until that name exists.

Where this breaks

Not every task has a correct output. Ideation, drafting, exploratory analysis: there is no single right answer, and forcing a pass or fail set produces a metric that punishes range. Preference comparison between two candidate outputs is the right instrument there, and it is a different build with a different cost.

Gartner puts the constraint upstream of mine. Its February 2025 release, drawn from 1,203 data management leaders surveyed in July 2024, predicts organisations will abandon 60% of AI projects through 2026 for want of AI-ready data, and reports 63% either lacking the right practices or unsure whether they have them. If you cannot assemble the data you never reach the handoff, and the evaluation set is moot. My answer is that these are the same failure at two depths. That is an argument, not a proof.

Evaluation sets decay. A set written against one model version can be passed by a newer model that is worse at the thing you actually care about, because the set encodes last year’s failure modes. That is why 60 to 80% is ongoing spend and not a setup cost. Any executive who signs it as a one-off has signed the wrong thing.

The 70% transformation failure statistic also deserves the scepticism it gets. BCG’s study is 70 companies and 825 executives, not a law of nature. I use it because the S&P and MIT numbers were collected differently, five years later, and landed in the same band.

What I would do on Monday

1. Name one person per AI system as the principal domain expert. One, not a committee. Put the name in the program plan next to the engineering lead.

2. Give that person 20% of their week back. If you cannot fund one day a week out of an operational team, you cannot fund the project either.

3. Get 30 real production traces annotated by that person this week. Binary, pass or fail, one line of reason on every fail. Reach 100 within a month.

4. Move the evaluation set into the same repository as the code, dated and versioned, and report its pass rate to the steering committee instead of adoption or licence counts.

5. Cancel any pilot that cannot state its correct output in one sentence. It gets cancelled in 2027 anyway, and it costs more then.

The number that did not move

30% in 2020. 42% in 2025. The failure rate held because the failure held. All that changed was the name of the document nobody would own.

Write the definition of correct. Put a name against it. The rest is engineering.

I run AI transformation programs through PADISO. If you are trying to work out what actually changes in your operating model, book a call.

So when a founder asks me in week one what I think is wrong with his engineering organisation, I tell him I do not have a view yet.

That answer has cost me work. I keep giving it, because 43 hours is the entire budget and I will not spend it confirming what the room already believes.

The thesis

The first 30 days of a fractional engagement is not diagnosis. It is instrumentation.

You cannot find a delivery constraint by asking the people inside it. They will report the constraint they personally feel, which is a real thing and a different thing. My job in month one is to leave four instruments running and a dated record of what everyone said before the instruments existed. The diagnosis is what the gap between those two says on day 31.

Why the interviews will lie to you, politely

In July 2025 METR ran the study that should have ended this argument. Sixteen experienced open source developers, 246 real issues on repositories they already maintained, averaging over 22,000 stars and a million lines of code. Screen recorded. Paid $150 an hour. Before starting, the developers forecast that AI tooling would make them 24% faster.

They were 19% slower.

The part that matters for month one is what happened afterwards. Having just been measured, on their own codebases, doing their own work, the same developers still estimated that AI had sped them up by about 20%. That is a 39 point gap between what a room of expert practitioners believed about their own delivery time and what a stopwatch recorded.

Nobody in that study was lying. Self report measures effort. It does not measure duration. Those two came apart in 2025 and they have not come back together.

Now put that against what the industry actually reports. DORA surveyed nearly 5,000 technology professionals for the 2025 State of DevOps report, with more than 100 hours of qualitative work behind it. 90% use AI at work. More than 80% believe it has made them more productive. 30% have little or no confidence in the code it produces. DORA found AI positively related to delivery throughput and still negatively related to delivery stability.

Both of those are true at once, which is precisely why an interview cannot resolve them.

What the telemetry says instead

The 2026 AI Engineering Report from Faros is the closest thing we have to an answer, because it is not a survey. It is two years of telemetry across 22,000 developers and more than 4,000 teams.

At the top of the pipe, the story people tell is correct. Merge rate per developer is up 16.2%. Task throughput per developer is up 33.7%. Epics per developer are up 66%.

At the bottom of the pipe it inverts. Median time in review is up 441.5%. Time to first review is up 156.6%. Merges shipped with no review at all are up 31.3%. Code churn is up 861%. Monthly incidents are up 57.9%, and incidents per pull request are up 242.7%. Bugs per developer are up 54%, against 9% the year before.

Read those two paragraphs again as one sentence. Everything a person can feel got faster. Everything only a system can see got worse. An interview picks up the first list and cannot see the second, and that is the entire reason I refuse to give an opinion in week one.

The four instruments

None of these need a vendor, a budget line, or a steering committee. All four come out of git, the deploy log and the incident channel, and I ask for read only access to all three on day one, before the kickoff deck.

One. Lead time from first commit to production. Not from ticket creation, which measures how a team fills in Jira. First commit to live measures the system. I want the distribution and the long tail, never the average, because the average is where a two week outlier goes to hide.

Two. Review latency and the unreviewed merge rate. This is the surface that broke in 2026 and almost nobody watches it. Two numbers: median hours in review, and the percentage of merges that reached production with no human review at all.

Three. Rework. Churn, restarts, and items stalled more than seven days. This separates shipped from finished. A team can be shipping 33% more and finishing less, and the roadmap will show only the first half.

Four. Incidents per merged change. Not incidents per month. A team reporting incidents up a bit is reporting the numerator while the denominator moved underneath it. In the Faros data the monthly count moved 57.9% and the ratio moved 242.7%. Those are the same organisation described two ways, and only one of them is a measurement.

Three things the instruments say that the room never does

”We are much faster now.” Usually true, and usually true only at merge. The change is real and it stops at the review queue. I have never once heard a team volunteer their unreviewed merge rate, because nobody computes it.

”Quality is holding.” Held against what. Flat incidents against flat volume is stability. Flat incidents against a 16.2% higher merge rate is an improvement worth celebrating. Rising incidents against rising volume is the normal case and it is not a crisis, but it is also not what holding means.

”The bottleneck is the platform team.” Sometimes. It is also the single most reported answer I get, from every seat, in every engagement, and it is exactly the shape of answer METR showed practitioners get wrong about themselves.

I learned this the expensive way on my own product rather than a client’s. I built the extraction engine for D30 first and the articulation gates second, which is the wrong order. The gates went in and immediately caught a share count that was out by 31 units against the store, on a workbook I had already read and believed. I would have signed that. Now the instrument goes in before the opinion, in my own tooling and in other people’s companies.

Where this breaks

Three ways, and I have hit all of them.

The first: not every engagement is diagnostic. If the brief is ship the migration by 30 November, spending 30 days instrumenting is a sophisticated way to miss the date. This rule applies when the brief is we are slow or we do not know why this hurts. When the brief names a deliverable, go and deliver it.

The second: instruments need events. In an organisation deploying quarterly, by hand, with incidents tracked in somebody’s inbox, 30 days of measurement produces almost no data points. There you are back to interviews and a stopwatch, and the honest move is to say so out loud rather than dress up a thin sample as evidence.

The third, and the one that actually bites: a number that lands on day 31 with no relationship behind it reads as an audit. Audited teams optimise the number, and then the instrument is worthless. So the 30 days is also 30 days of earning the right to publish what the instruments found. Skip that and the measurement survives while the mandate does not.

One more limit worth naming. The METR result is 16 developers on mature open source codebases with early 2025 tooling. The coefficient does not transfer to your company. The direction does, and the direction is the only part I use.

What I would do on Monday

1. Ask for read only access to git, the deploy or CI log, and the incident channel. If that takes more than five working days to arrive, you have your first finding, and it is about the organisation rather than the tooling.

2. Pull lead time from first commit to production for the last 90 days. Plot the distribution. Look at the slowest decile only.

3. Compute two numbers nobody has: median hours in review, and the share of merges that shipped unreviewed.

4. Compute incidents per merged change for the last two quarters. Compare it to incidents per month and see whether they tell the same story.

5. On day one, write down what the room says the constraint is. Date it. Do not share it. On day 31 put it beside the instruments. That comparison is the deliverable, and it is worth more than either half on its own.

Close

Forty three hours is not enough to fix an engineering organisation. It is exactly enough to stop guessing about one.

The question I refuse in week one is the same question I can answer on day 31 with a number instead of a view. Clients think they are paying for my opinion. What they are actually paying for is the 30 days in which I do not have one.

Most of what I write about here started as a client problem. If you have one, bring it to me.

Seven more emails. Twenty five more meetings.

Both groups did roughly the same amount of outreach. One group’s messages reached a human being and the other group’s did not. The thing that separated them is not effort and it is not deck quality. It is the warm introduction, and nobody in venture has ever put a price on it.

The thesis

The warm intro is not a courtesy. It is a sorting mechanism, and it sorts on affinity rather than on quality. Founders pay for it in meetings they never get. Investors pay for it in returns, and the second half of that sentence is the part the industry has never accepted.

I have a stake in this. I co-run Capitaly.vc with Houman, which exists because we thought this market clears badly. Read the rest knowing that.

What the sourcing week actually looks like

Paul Gompers, Will Gornall, Steven Kaplan and Ilya Strebulaev surveyed 885 institutional venture capitalists at 681 firms. It remains the largest structured look inside the job.

Their reported week runs 55 hours. Of that, 22 hours go to networking and sourcing and 18 go to working with portfolio companies. Sourcing is the single largest block of the week.

Where the deals come from is more revealing. Over 30% are generated through professional networks. Another 20% are referred by other investors. 8% come from a portfolio company. That is 58% of deal flow arriving through a relationship. Only 10% comes inbound from company management. Almost 30% is proactively self generated.

The funnel underneath: roughly 100 opportunities considered for every investment closed. One in four leads to a management meeting. One third of those reach a partners meeting. About half of those proceed to diligence. Firms offer 1.7 term sheets for each deal they close, and the median firm closes about four investments a year.

Now the number that should be uncomfortable. Asked which of the three things they do contributes most, 49% of these investors said deal selection, 27% said post investment value add, and 23% said deal flow. Forty percent of the working week goes into the activity they themselves rank last of three.

That is only irrational if you believe the network is a sourcing tool. It is not. It is a screening tool wearing a sourcing costume. An introduction carries something a cold deck cannot carry: a named person spending their own reputation on your behalf. It performs diligence before diligence, at zero marginal cost to the investor, using a credential the founder did not earn and cannot buy.

That is why it survives. It is genuinely useful to the person holding the cheque. The cost sits with people who are not in the room.

What it costs the people collecting it

The affinity part of this has been measured, and it was not measured on founders. It was measured on investors introducing each other.

Gompers, Vladimir Mukharlyamov and Yuhai Xuan studied 3,510 individual venture capitalists across 11,895 portfolio companies from 1975 to 2003. They asked a simple question: when two investors share a background, are they more likely to work together, and does the deal do better.

The answer to the first half is yes, strongly. Two VCs who worked at the same firm previously are 64% more likely to co invest. Two who went to the same undergraduate school are 42.5% more likely. Two from the same ethnic minority group are 22.8% more likely.

The answer to the second half is the interesting one. Success, defined narrowly as the portfolio company reaching an IPO, falls. Same previous employer costs 18 percentage points. Same undergraduate school costs 22 points. Same ethnic minority group costs 25 points.

The split inside that paper is the whole argument. Similarity based on ability, such as both partners holding degrees from top universities, improves outcomes by 9 to 11%. Similarity based on affinity destroys them. The network sorts on the second kind and pays for it in the first.

PitchBook surveyed 391 venture investors across the US, Europe and Asia and found 82% naming personal networks as their most valuable sourcing resource, against 44% for inbound and 36% for financial databases. Only 38% used data to source all of their opportunities. That survey ran in Winter 2018 and I would expect the data number to be higher now. I would not expect the 82% to have moved much, because the underlying incentive has not moved at all.

I built D30 for the listed version of this problem. It pulls three statement fact files out of ASX annual reports and runs articulation gates over them, so a company reaches a shortlist because its numbers tie, not because somebody vouched for it. Private markets have no equivalent instrument. They have a phone.

Australia makes the geometry worse

Cut Through Venture reported $5.1bn across 390 deals for Australian startups in 2025, published 3 February 2026. That is a 24% lift on the prior year and the third largest funding year on record. It is also 390 deals. A market that size has one degree of separation inside it, not six.

In the same data, female founders took 24% of deals, down from 28% in 2024. Series A is worse. That is what an affinity sort looks like when it runs at national scale for a decade: not a policy, not a conspiracy, just the accumulated output of a filter that rewards proximity to people who already have capital.

66% of 2025 deals included an international funder. Australian founders are increasingly raising from people who are structurally outside the local network. That is the tell. When the local sort is thin, founders route around it, and the routing costs them 25 meetings.

Where this breaks

Three places, and I want to be precise about them.

The Cost of Friendship measures co investment between investors, not introductions to founders. It also ends in 2003. I am transferring a mechanism, not a coefficient. Anyone who quotes 18 percentage points as the cost of a warm intro to a founder is misusing the paper, including me if I did it.

The intro is a real signal, not only an affinity artefact. A person who introduces you has read enough of your business to risk being wrong in front of someone whose opinion they need next quarter. That is information. A filter that is 60% accurate and free beats no filter when you are reading 100 opportunities to make four investments a year.

And the counterfactual is not open access, it is a different filter. Remove intros and the volume does not vanish, it lands somewhere. Every investor who has opened submissions has closed them again within two years. The honest version of my argument is not that the intro should go. It is that it should be one input among several, and that right now it is the gate.

What I would do on Monday

If you are raising:

1. Count your ratio, not your outreach. Contacts to first meetings is the only number that tells you whether you have an access problem or a business problem. Below 30% and the deck is not the issue.

2. Build the intro asset before you need it. Operators inside the portfolio companies of your target funds are the 8% referral channel, and they answer.

3. Publish the thing only you know. Proactive sourcing is 30% of deal flow. Being findable by a partner running a thesis search is the one channel that does not require permission.

If you are investing:

1. Instrument your own funnel by source. Split closed deals by professional network, other investors, portfolio referral, inbound and self generated, then look at outcomes by source three years later. Most firms have never run this and it takes an afternoon.

2. Cap the affinity channel deliberately. Not on principle. Because the published evidence says the correlation between how a deal reached you and how well it does is negative in exactly the channel you use most.

Close

77 investors and 40 meetings. 70 investors and 15 meetings.

The second group did the work. They just did it into a system that was never reading.

Capitaly connects founders and investors without the warm intro tax. See it here.

Those two numbers describe the same 62 engineers. The capacity can only be spent once.

The thesis

Headcount is not a result. It is an input you happen to control, which is exactly why it gets managed as if it were an outcome. AI frees one pool of capacity, and you convert that pool into a smaller payroll or into more change shipped. Both are defensible. Doing both, in the same year, on the same pool, is a double count, and it is the most common accounting error in enterprise AI right now.

The only figure that exposes it is cost per shipped unit of change. Almost nobody computes it.

What the metric actually is

Take everything it costs to move change into production over a quarter. Fully loaded engineering payroll, contractors, tooling, cloud, and the AI line: seats, tokens, and the API keys somebody expensed. That is the numerator. Then count the units of change that reached production and were still there thirty days later. That is the denominator. Divide.

The numerator is the easy half and most finance teams already have it, scattered. The AI component is now large enough to matter. Gartner reported in June 2026 that nearly a quarter of technology leaders spend between $200 and $500 per developer per month on AI coding tokens alone, and about 6% spend more than $2,000. Jellyfish published a worked example of a 40 developer organisation: $1,560 a month in licences, $2,100 in overages, $480 in extra tools, $1,400 on raw API keys and $300 in personal subscriptions that went through on cards. Total $5,840 a month, or $146 a developer. Inside that same company the platform team ran at $556 per developer and the frontend team at $61. That is a nine times spread, and nobody who has not built a denominator can tell you which of those two numbers is the good one.

The denominator is where the work is, because you have to decide what a unit is and then defend it. A merged pull request is too small and too gameable. A deployment is closer. A change that a customer or an internal user could describe is better.

Look at what happens when the unit is chosen badly. DORA’s own model books its value as time saved, 12.5% per developer, then reports the delivery outcome as deployments rising from 50 to 56 a year against a first year investment of $8.4 million. That is $1.4 million per additional deployment. The model is not wrong. It is measuring the return in one unit and the outcome in another, and the arithmetic only looks absurd because I forced the two units into the same fraction. That is the whole point. When the unit you book value in differs from the unit you measure delivery in, a double count can sit between them for a year and never show up on a slide.

Run the numbers on your own team

DX studied more than 400 organisations and found a median throughput gain of 7.76% from AI assisted development, a mean of 13.1%, and 43.9% at the ninetieth percentile. Take the median and a hundred engineers. Assume a fully loaded cost of $200,000 each, and adjust that to your own market. The AI spend at $350 a developer a month is $420,000 a year. The capacity gain is 7.76 engineers, worth $1.55 million. Close to four to one.

That ratio holds if you take the capacity as output. It also holds if you take it as payroll: cut 7.76 roles, save $1.55 million, ship the same volume, and the cost per shipped change still falls. Both paths work. The failure mode is the third one, where the payroll saving is banked in the January budget and the output increase is promised in the same board pack. Two quarters later the volume is down, because the 62 engineers you modelled were the same 62 you let go, and the ratio is worse than before you started.

Gartner’s finding is the tell. Workforce reduction rates were close to identical between the organisations reporting strong returns and the ones reporting nothing or worse. Helen Poitevin put it plainly: workforce reductions may create budget room, but they do not create return. If cutting correlated with returns you would see it in 350 companies with a billion dollars of revenue each. You do not.

What I count

I run this test on my own ventures before I take it into anyone else’s company.

D30 pulls a three statement fact file out of an ASX annual report and runs eight articulation gates over it. The unit is one completed fact file that passes all eight. I can tell you what a fact file costs to produce, including model spend, and I can tell you how that number has moved. I have never managed the business to analyst hours saved, because hours saved is a number you can claim twice and a fact file is a number you can count.

D23 sells managed Apache Superset. The unit is a dashboard running in production that somebody opened this month. Not a deploy. A deploy that nobody looks at is cost with no denominator.

SearchFIT counts one tracked prompt scanned across the answer engines. When a model price drops, that unit cost drops, and I can see it in a week rather than infer it from a vendor’s slide.

None of those units are obvious. Each took an argument to settle. That is the actual work, and it is why the metric is rare.

Where this breaks

Any denominator you publish becomes a target. Count merged pull requests and you will get more of them, smaller, split across branches, and your ratio will improve while nothing ships. The thirty day survival test slows that down. It does not stop it. If you put this number in front of a board you have to expect the number to be gamed, and the honest position is that this metric is a diagnostic for the people running delivery, not a compensation input.

It also does not travel outside software delivery. If your AI value is sitting in a claims queue or a contact centre, the unit is a resolved case, not a merged change, and forcing a delivery frame onto it will mislead you.

The hardest objection is timing. Cost per shipped change is noisy for two or three quarters, and a CFO under pressure this quarter cannot wait that long. Headcount is measurable today, it is unambiguous, and it moves the P&L in the period. That is not stupidity. That is a real constraint, and it is exactly why the wrong metric keeps winning.

What I would do on Monday

1. Write the unit down in one sentence and get the CTO and the CFO to sign the same sentence. If they cannot agree what a shipped change is, stop there, because that disagreement is the finding.

2. Total the AI line properly. Seats, token overages, API keys on personal cards, and the two tools nobody put through procurement. Split it by team. Expect a spread like the nine times gap in the Jellyfish example.

3. Instrument the denominator with a thirty day survival window. Count changes that reached production and stayed. Reversals do not count.

4. Compute the ratio for the four quarters before AI landed and every quarter since. You need the baseline more than you need the current number.

5. Put a freeze on any headcount decision justified by AI capacity until you have two quarters of the ratio. If the capacity is real it will still be there in six months.

Sixty two engineers is a real number inside a real model published in July. It is either coming off your payroll or going into your output. Decide which. Then check, in two quarters, whether the ratio agrees with you.

Brightlume does this work with enterprise teams. If the gap between the AI pilot and the P&L is the problem you have, talk to me.

A financial report is not a document. It is three statements welded together by about eight pieces of arithmetic that have to close to the dollar, and almost nobody in Australian private capital runs them. A number that has not been tied is not evidence. It is a quote.

What the ties actually are

The gates are not sophisticated. That is the point.

A1 is the balance sheet: total assets equal total liabilities plus total equity. A2 is component summation, run six ways, because a subtotal that does not equal the lines above it means either the extraction is wrong or something is sitting in a bucket nobody named. A3 walks the income statement: EBIT less finance costs plus finance income equals pretax, pretax less tax plus discontinued equals NPAT. A4 is the cash flow: opening cash plus operating plus investing plus financing plus FX equals closing, and closing equals the balance sheet. A5 rolls retained earnings forward: prior year plus profit attributable to members less dividends paid. A7 rolls the share count.

Each one is a subtraction. All of them together are the difference between a model built on numbers and a model built on typing.

The mechanical reason this is not already standard practice in Australia is that our filings are not machine readable. ASIC has offered voluntary digital lodgement since 2010 and, as at 2026, not one company has taken it up. XBRL is in active use across 65 countries. The EU, the UK and the US all mandate digital financial reporting. Australia does not. The Productivity Commission’s interim report recommends mandatory iXBRL using the IFRS Accounting Taxonomy for disclosing entities and a phased end to PDF submission. Until that lands, every ASX annual report reaches an analyst as pixels, gets keyed into a spreadsheet, and the spreadsheet inherits whatever the analyst read.

AASB 18 takes effect for periods beginning 1 January 2027 and rebuilds the face of the income statement. Every model keyed by hand off a PDF will need to be rekeyed.

The errors are not rare and they are not small

ASIC published REP 819 on 31 October 2025 covering the 2024 to 2025 cycle. It reviewed 254 company financial reports, 220 of them ASX listed and 34 large proprietary, plus 60 superannuation entity reports. Twenty two entities went to detailed surveillance. Eighteen entities made or agreed to make changes across 19 areas of concern. Energy World Corporation impaired assets by US$793.8 million. Bell Group Holdings restated to consolidate a subsidiary it had previously accounted for incorrectly. Vulcan Energy Resources restated its employee benefits presentation. Two entities corrected how they presented non-IFRS profit measures.

ASIC’s own enforcement in the same period ran to 21 infringement notices and more than $4 million for FY24 financial reporting breaches, including $792,000 across four Canva Group entities and $594,000 across three Mecca entities at $198,000 each. In its later update ASIC recorded Viva Energy taking $558.8 million of retail site impairment in FY25, of which $25 million, 4.5 per cent, came from a revised impairment testing methodology rather than a change in the assets. Pure Foods Tasmania reversed $4.5 million of deferred tax asset recognition, equal to 31 per cent of its total assets.

The cash flow statement is the softest target of the three. In the United States, where a machine reads every filing, the SEC’s then Chief Accountant Paul Munter noted on 4 December 2023 that cash flows had been the fourth most common accounting issue cited in restatements from 2003 through 2022, and the single most frequently cited issue among large accelerated filers. His point was blunter than the statistic: he rejected the argument that an error which only moves a number between operating, investing and financing is immaterial. Restatements rose 7 per cent in 2024 and Big R restatements hit a nine year high, on Audit Analytics data.

Then there is the lever that sits right on the operating line. Amendments to IAS 7 and IFRS 7 on supplier finance arrangements took effect for periods beginning on or after 1 January 2024, and they exist because the classification choice is worth real money. Call the balance a trade payable and operating cash flow and free cash flow improve. Call it a financial liability and the fees drop below EBITDA. Same cash, two different stories, and which story you get told depends on which metric the seller thinks you underwrite.

Where this breaks

Gates test arithmetic, not judgement, and judgement is where most value gets destroyed. Energy World’s balance sheet almost certainly tied to the dollar in the year before that US$793.8 million impairment landed. Impairment timing, revenue recognition policy, capitalisation of development spend and provision releases all pass every gate I have described. If you run the ties and conclude the numbers are clean, you have confirmed the report is internally consistent and nothing else.

The second problem is signal to noise. On a first pass, most gate failures are my extraction, not the company’s accounting. A residual bucket that swallows 59.7 per cent of current assets is a tagging failure, not fraud. You have to fix the parser before the output means anything, and that work is unglamorous and takes longer than building the gates did.

Third, for a large cap audited by a big four firm, the arithmetic is usually right and the gates earn nothing. They pay for themselves in small and mid caps, in recently listed companies, and above all in the unaudited management accounts that private capital actually spends most of its diligence on. That is the population where I would run them.

What I would do on Monday

1. Take the last three diligence packs you signed off and check A1 and A4 by hand on each. Two subtractions per pack. If any of the six fails, you have your answer about the process.

2. Stop accepting the PDF as the deliverable. Ask for the trial balance and the model that produced the summary. If nobody can produce the workbook, that is the finding.

3. Add one line to the information request list: disclose all supplier finance arrangements, the carrying amounts by balance sheet line, and the range of payment due dates against comparable trade payables. IAS 7 already requires it.

4. Put the gate results in the investment committee paper as a page, with the tolerance you used stated on it. A tolerance you did not write down is a tolerance you will argue about later.

5. Pick one company you already own and rebuild its last three years from the filings rather than from your own model. Compare. That exercise is where the tooling pays for itself or does not.

The line that started it

I wrote A4 BSCASH expecting a plumbing check. It is not a plumbing check. It is the question of whether the document you are underwriting agrees with itself, and until you have asked it, every number downstream is something you read rather than something you know. Thirty one units on a share count is nothing. Not knowing it was there is the problem.

Run the subtraction.

I built D30 to pull three-statement fact files out of ASX annual reports and flag where the numbers stop articulating. If you run diligence on listed or pre-IPO assets, have a look.

I have priced this work three ways: by the hour, by the retained day, and by the decision. Two of those are wrong and I used both. Both price my attendance, and attendance is the input that is deflating fastest right now. The decision is the only unit that held its value, because the cost of getting a decision wrong did not fall at all.

The entire market is denominated in time

Go and read the published benchmarks. Every one of them prices a calendar.

Go Fractional’s rate page puts the median fractional CTO ask at $220 an hour, with the middle half of the market between $175 and $250. Employers post $136. Talent asks $221. That $85 gap is the whole negotiation. The typical engagement is 16 hours a week, roughly 40% of a full-time week, which lands at about $14,000 a month with retainers starting near $11,200.

Tristella’s guide, published 1 July 2026, tiers it the same way: light advisory 10 to 15 hours at $4,000 to $8,000, standard fractional 20 to 40 hours at $8,000 to $15,000, deep fractional 40 to 60 hours at $15,000 to $25,000 and up. Kompella’s 2026 guide tiers by days instead of hours: advisory at one day a week for $8,000 to $10,000, fractional at two days for $15,000 to $18,000, embedded at three or more days for $25,000 to $30,000. It notes that most B2B SaaS engagements settle at $15,000 a month for two days a week.

Read those tiers again. Not one of them describes a result. They describe a diary.

What each model does to the conversation

Hourly billing punishes the thing you are selling. I am hired because I have seen the failure mode before. Recognition is instant. Under hourly, instant recognition is a small invoice, so the honest expert is paid least for the moment they were most useful. Every efficiency gain, every tool, every year of pattern library, converts directly into a smaller bill. You cannot fix that with a higher rate, because the rate has a ceiling the market publishes and the hours do not have a floor.

The retainer is better and it fails differently. You sell two days a week for $15,000 and the first month is fine. Then the finance lead asks what they got for the money. The truthful answer is eight days. Eight days is not a result, so you start manufacturing evidence of presence. Standups you did not need to be in. A weekly deck. Slack responsiveness as a performance. The retainer quietly converts a senior operator into an attendance record, and the moment the client’s budget tightens, an attendance record is the easiest line to cut.

Both models have the same defect. They price the input. In 2026 the input is the part collapsing in cost, and the client knows it.

The third model

The market already has the shape and misnames it. Kompella’s smallest tier is project pricing: a tech debt audit at $15,000 to $25,000, a 90 day plan at $30,000 to $50,000, pre-fundraise preparation at $40,000 to $75,000, M&A integration at $50,000 to $100,000 and up. That is closer, but a project is still a scope of work. A decision is different. A decision has a date, one or two viable options, and a cost of being wrong that somebody can name.

Four decisions make up most of what I actually get hired for. Build, buy, or agency. The platform migration go or no go. The pre-raise architecture answer, which in 2026 is really the question of what happens to gross margin when the model gets cheaper. And the diligence verdict on somebody else’s technology.

Each one has a number attached to being wrong, and the number is not $15,000 a month. That is what the fee attaches to, along with the artefact that outlives the engagement: the one page scope, the model, the gate list, the thing the client still has after I leave.

This is not a theory I applied to consulting and nowhere else. D30 is forensic extraction over ASX filings, and the fee is the fact file and the eight articulation gates, not the hours spent reading the PDF. That is deliberate: the model that reads the document is replaceable and getting cheaper, and pricing the reading would have been pricing the part that goes to zero. D23 sells managed Apache Superset, where nobody pays for the software because the software is free. They pay for it to be run correctly. Same logic, applied to me.

The largest firms in the world made the same move this year

McKinsey now ties about 25% of its global fees to outcomes rather than time, reported by the Wall Street Journal on 29 June 2026. In the same period its internal assistant, Lilli, runs over 500,000 prompts a month and its consultants report time savings on knowledge work of up to 30%. BCG puts AI and tech-enabled work at roughly 20% of 2024 revenue heading toward 40% this year. Bain has it near 30% and climbing toward half.

Treat those as directional. They come from firm media events and investor briefings, not audited disclosure, and every one of them is a marketing number as much as an operating one. The direction still matters. The firms with the most to lose from abandoning the billable hour moved a quarter of their fee base off it in the same year their own tooling cut a third off the work. That is not two unrelated events.

Where this breaks

Decision pricing needs a decision. Plenty of engagements are honest capability rental: the team is competent and simply has no senior person in the room, and they need one every week for a year. There is no dated call to attach a fee to. The retainer is the correct instrument there, and pretending otherwise is a pricing model looking for a problem. Cap it and give it an exit date so it does not become tenure.

It also requires deal flow you may not have. Quoting a fee that is unanchored from your cost only works if you can absorb a no. If one client is more than a third of your revenue, you will not hold the line, and a published day rate is the more honest thing to sell.

The hardest problem is attribution. An hourly invoice settles in 30 days and nobody argues about whether the hours happened. A decision proves itself 14 months later, by which point the client remembers the outcome and not who made the call. So the fee has to land at the moment of the decision, not at the moment of the result. Charge for the outcome and you have written the client a free option on your own judgement.

What I would do on Monday

1. Take your last three invoices and divide each by the hours behind it. Then write down, in dollars, what the client’s cost of being wrong was on the largest call in that same period. The ratio is the argument.

2. Change one line in the proposal template. Delete “days per week” and put in the name of the decision and the date it has to be made by.

3. Name the artefact. If nothing survives your last day, you sold attendance and the invoice was correct.

4. Put a cap and an exit date on every retainer you currently run. Not to end them. To make renewal a decision instead of a default.

5. Stop answering the day rate question first. Ask what decision is waiting on you, and quote the answer to that.

The question still arrives in the first ten minutes. What is my day rate. I answer with a number now, and it is not per day.

I write this from the PADISO seat. If you need a CTO who has shipped, raised, and cleaned up after both, book a call.

For most of last year it was. Which model, what context window, what the token bill looks like at volume. I would spend the first hour of a review on that page, because it was the line with the biggest number next to it, and a big number feels like a decision.

On 30 July 2026 OpenAI repriced GPT-5.6 Luna by 80%. Input went from $1.00 per million tokens to $0.20. Output went from $6.00 to $1.20. Terra came down 20%, from $2.50 and $15.00 to $2.00 and $12.00. Sol, the prestige tier, did not move at all.

Every hour anyone spent last quarter optimising a model choice on price was deleted by one update to a pricing page.

The thesis

Most enterprise AI budget is going into the layer that will be a utility bill inside 18 months. The two things that will still be yours after that happens are your data contracts and your evaluation sets, and almost nobody is funding either.

That is not a call to spend less. It is a call to spend the same money one layer down.

The numbers behind the claim

Menlo Ventures surveyed 495 US enterprise AI decision makers between 7 and 25 November 2025. Total enterprise AI spend for the year came to $37 billion, up from $11.5 billion in 2024 and $1.7 billion in 2023.

Split that $37 billion. Applications took $19 billion. Infrastructure took $18 billion. Inside infrastructure, foundation model APIs took $12.5 billion, model training infrastructure took $4.0 billion, and storage, retrieval and orchestration took $1.5 billion.

Read that ratio again. Enterprises spent 8.3 times more renting model capability than building the layer that feeds it.

Now put that next to the price curve. Andreessen Horowitz measured the cost of a fixed level of model performance falling roughly 10x per year: GPT-3 level quality cost $60 per million tokens in November 2021 and $0.06 three years later, a 1,000x collapse. GPT-4 level quality fell about 62x from its March 2023 launch. The 80% cut on 30 July 2026 is not an event. It is one visible step on a curve that has not broken once in five years.

You cannot build an advantage on a line item that falls 10x a year. Everyone else gets the same cut on the same day.

The switching data says nobody is locked in either

Perplexity published enterprise usage across January to December 2025. The leading model’s share of queries fell from 47.5% to roughly 23% inside twelve months. Early in the year two models held 91.5% of queries. By the end, four models each held more than 10%. Across organisations, 43.6% used more than one model at some point in the year, and 53% of users who pick a model switched between models at least once inside a single working day. The top 50 enterprise accounts averaged 30 models each, against seven for a typical account.

Menlo’s share numbers land in the same place: Anthropic 40%, OpenAI 27%, Google 21%. OpenAI held 50% in 2023.

A market where the leader halves its share in a year, where half of power users change model before lunch, and where the price of the thing drops 80% overnight, is a market with no defensible position in it. That is the definition of a commodity input. It is a fine thing to buy. It is a terrible thing to build a strategy on.

What does not commoditise

Two things. Both boring. Both underfunded.

The first is the data contract: an explicit agreement between the team that produces a table and the team that consumes it, covering schema, ownership, freshness and how a breaking change gets announced. Without it, someone renames a column upstream, your retrieval layer quietly returns worse context, your answers degrade, and your AI team spends three weeks debugging a model that never changed.

The second is the evaluation set: your own labelled examples of what a correct answer looks like for your business, run automatically against every model, prompt and retrieval change.

Here is the part people miss. Evaluation is filed under governance, so it gets treated as a brake. It is the opposite. The eval set is the mechanism that converts a price cut into cash.

When Luna drops 80%, you can only take that money if you can prove the cheaper model still does your job. With a golden set of a few hundred labelled cases you run it in an afternoon and migrate. Without one, you have a meeting, then a pilot, then a quarter of drift, and you keep paying the old price on the old model because nobody can sign off that the new one is safe. The company with evals harvests every price cut in the industry automatically. The company without them watches the curve go past.

The evidence that this layer is genuinely missing

Gartner surveyed 1,203 data management leaders in July 2024 and concluded that through 2026 organisations will abandon 60% of AI projects that are not supported by AI ready data. A separate Gartner survey of 248 data management leaders found 63% either lack appropriate data management practices for AI or are not sure whether they have them.

On the evaluation side, Gartner reported on 30 March 2026 that 15% of generative AI deployments currently include LLM observability, and projected 50% by 2028. Eighty five percent of deployments running today cannot tell you why an answer came out the way it did.

Meanwhile the build and buy ratio flipped hard. In 2024 enterprises built 47% of their AI use cases in house. In 2025 they built 24% and purchased 76%. That is a rational response to falling model costs and improving vendor products, and it has a side effect nobody priced: when you buy the application and rent the model, the only part of the stack you still own outright is your data and your definition of correct. Those are exactly the two lines that got $1.5 billion out of $37 billion.

I run this pattern in my own products. D30 pulls three statement fact files out of ASX annual reports, and the model that reads the PDF is not the asset. The articulation gates are. Eight of them, checking that the balance sheet balances, that the cash flow ties to the movement in cash, that the tagged store reconciles to the statements. If the numbers do not articulate, the fact file fails, whatever model produced it. That gate lets me change the model underneath without changing my confidence in the output. Same logic at D23, where clients pay for Superset to be run correctly rather than for the software. Same at SearchFIT, which has to query answer engines it does not control and would be worthless without a stable definition of what counts as a citation.

Where this breaks

The frontier is not commoditised, and my thesis does not cover it. Sol held at $5.00 and $30.00 on the same day Luna fell 80%. That gap is the market telling you that hard, long horizon reasoning still has scarcity value. If your use case genuinely sits there, model selection decides whether the thing works at all, and no eval set rescues a model that cannot do the task.

The thesis also over-fires for small companies. If you have three AI use cases and no data platform, building formal data contracts is over-engineering. Buy the application, use the vendor’s evaluation tooling, revisit at scale.

And evaluation sets rot. A golden set built on last year’s task distribution will happily approve a model that fails on what your customers ask today. An eval set is a living asset with an owner, not a compliance artefact you build once. If you are not editing it monthly, it is already lying to you.

What I would do on Monday

1. Print the AI budget. Mark every line by whether it survives a model swap. If more than half the spend dies when the model changes, you are funding the commodity.

2. Build one golden set this week. One hundred to three hundred labelled examples for your single highest volume task. Not a platform, not a vendor selection. A spreadsheet and a script are enough to start.

3. Put a contract on the three tables that feed retrieval. Named owner, schema, freshness target, and a rule that breaking changes get announced before they ship.

4. Re-run last quarter’s most expensive workload on the cheapest current model against that golden set. If it passes, take the 80% now. That single exercise usually pays for the eval work in one billing cycle.

5. Change the metric in the monthly pack from tokens consumed to cost per accepted output. Tokens are a price you do not control. Acceptance is a quality you do.

Close

The first thing I check now is the eval set. If there is one, I know the team can move when the price moves, and the model on the architecture diagram is a detail. If there is not, I know the exact conversation we will have in nine months, because the price will have fallen again and they will still be paying the old rate.

The model is rented. The definition of correct is owned.

Brightlume does this work with enterprise teams. If the gap between the AI pilot and the P&L is the problem you have, talk to me.

Read the sources it cites under the answer.

Now open Google, search the same words, and read the top ten.

Compare the two lists. Ahrefs ran exactly that comparison at scale: 15,000 long-tail queries across ChatGPT, Gemini, Copilot and Perplexity. On average 12% of the URLs the models cited appear anywhere in Google’s top ten for the query the user actually typed. ChatGPT scored 8.0% on in-text citations and 6.1% on its reference list. Gemini 8.6%. Copilot 8.2%. Four out of five cited URLs do not rank for the question at all.

The thesis

AEO is not SEO with new vocabulary. The unit of optimisation changed.

Search ranked pages against a query. Answer engines score passages against sub-queries the user never typed, then fuse the winners. What competes is a single verifiable claim. The page is just the container it arrived in.

If you are still running a page-level roadmap, you are optimising the box and not the thing inside it.

What happens between the question and the answer

The step everyone skips is query fan-out.

You type one question. The engine does not run it. It decomposes it into a set of narrower queries, runs those, and merges the result sets using Reciprocal Rank Fusion, a method that combines several ordered lists into one. Ahrefs identified fan-out as the structural reason the overlap is so low. The engine and the buyer are not searching for the same thing, so the results page you rank on is not the results page that fed the answer.

Then the model fills citation slots, and the slot count is not the same everywhere. Semrush analysed 126 million US AI search prompts between January and April 2026 across ChatGPT, Gemini, Google AI Mode and AI Overviews. ChatGPT averages 15 sources per response. Gemini averages 3. That is not a rounding difference. On Gemini you are fighting for one of three positions against Wikipedia and Reddit. On ChatGPT there is room for a specialist.

Semrush found something sharper still. On Gemini, the overlap between the brands mentioned in an answer and the domains cited underneath it runs as low as 30%. Being talked about and being cited are two different outcomes with two different mechanics.

The number that settles it

Everything above could be dismissed as third-party engines behaving oddly. So take Google’s own surface, where ranking should transfer most directly of all.

Ahrefs measured AI Overview citations twice. In July 2025, across 1.9 million citations, about 76% came from pages ranking in the top ten. In January 2026, across 863,000 results pages and 4 million AI Overview URLs, that figure was 37.9%.

It halved in six months.

The rest did not come from page eleven either. 31.2% came from positions 11 to 100. A further 31.0% came from pages that do not rank in the top 100 at all. YouTube alone supplied 5.6% of AI Overview citations while ranking nowhere in classic search.

Google is now sourcing nearly a third of its cited answers from documents its own ranking system does not put on the first ten pages. Fan-out is why.

The tactic that does nothing

If the page were still the unit, marking it up would help. It does not.

On 11 May 2026 Ahrefs published a controlled study covering August 2025 to March 2026. They took 1,885 pages that added JSON-LD schema, matched them against 4,000 control pages, and measured citations for 30 days before and 30 days after, using difference-in-differences to strip out platform-wide trends.

Google AI Overviews fell 4.6%, and that was the only statistically significant result. Google AI Mode rose 2.4% and ChatGPT rose 2.2%, neither significant. Adding schema produced no citation uplift on any platform, and on the largest one it went slightly the wrong way.

Retrieval reads visible text. The correlation everybody quotes exists because sites that implement JSON-LD also write better and earn more links. The most recommended AEO tactic of the last two years is decoration.

Why the stakes moved with it

SparkToro, using Similarweb clickstream data from January to April 2026, found 68.01% of US Google searches ended without a click. In 2024 it was 60.45%. Searches that produced a click fell 9.51 points, a 22.9% decline in two years. AI Overviews now appear on more than 20% of searches, and when one appears the click-through rate drops by nearly 60%.

The page used to be the destination. It is now a source the buyer never opens.

I built SearchFIT because I could not answer a simple question for a client: when a buyer asks the model, does the brand come up. The design decision that mattered was the atomic unit. SearchFIT tracks prompts, not keywords, and scores each engine separately, because a keyword ranking tells you nothing about a fan-out you cannot observe, and an engine average hides the fact that three slots and fifteen slots are different games.

It is the same instinct I applied at D30. D30 pulls ASX annual reports apart into tagged line items and runs articulation gates across the three statements, because a summary sentence that cannot be traced back to a number is not evidence. Both products refuse to treat the document as the unit. In forensic screening the unit is the tagged number. In answer engines the unit is the extractable claim. The document is packaging in both cases.

Where this breaks

Perplexity broke the pattern. Its overlap with Google’s top ten was 28.6%, more than three times ChatGPT’s. On one major engine classic ranking still transfers well, and if Perplexity is where your buyers are, the old playbook is largely intact.

The 15,000-query Ahrefs sample was long tail. Long tail is precisely where overlap should be lowest, because head terms have settled authority and fewer plausible sources. Run the same test on head terms and 12% would almost certainly rise. I would not quote that figure as though it covered all search.

The volume is also still in blue links. Google AI Mode accounted for 0.34% of searches between January and April 2026. Organic search remains the largest channel for most B2B companies by a wide margin. Anyone telling you to stop doing SEO is selling something, and 37.9% of AI Overview citations still come from the top ten, which is a lot of reason to keep ranking.

Last caveat, and it is about the category. Most AEO research is a press release. One widely circulated study this year claimed the overlap between top rankings and AI-cited sources collapsed from 70% to under 20%. Chase the citation and it attributes the finding to a third party with no disclosed sample size, no study period and no method. The real version of that collapse exists and I have used it above, because Ahrefs published the sample, the window and the test. Insist on all three before you move a budget.

What I would do on Monday

1. Replace the keyword list with a prompt list. Write the 20 questions a buyer asks in the four weeks before they shortlist. Track those weekly, with ChatGPT and Gemini scored separately.

2. Audit your top ten pages for extractable claims. One sentence that answers one question completely, carrying a number, a date and a source, sitting in visible HTML above any tab, accordion or click. Most pages have none. Aim for three per page.

3. Take schema out of the AEO budget line. A 1,885 page controlled study moved nothing anywhere and moved backwards on AI Overviews. Keep JSON-LD for rich results and stop paying for it as a citation tactic.

4. Go and win third-party mentions. With mention and citation overlap as low as 30% on Gemini, and 31% of AI Overview citations coming from outside the top 100, the review site, the comparison page and the forum thread are separate assets from your own domain.

5. Change the reporting unit. Report citations per claim per engine, not sessions per page. If your dashboard cannot answer which sentence of yours got cited last week, it is measuring the old thing.

Close

Go back to the tab you opened at the start.

Look at the sources under that answer one more time. Roughly a third of them are there without ranking in the top hundred for anything the buyer typed. Each one is present because a passage inside it answered a question the buyer never asked out loud, well enough that a fusion function put it in a shortlist the buyer will never see.

That is the whole game now. Not the page. The sentence.

SearchFIT tracks whether AI answer engines mention your brand when buyers ask. Most companies have never checked. Check yours.

Three vendors. Three different units of account. It is Intercom’s own comparison page, so read the framing with the suspicion it deserves. The prices are still the prices.

I read it twice. Then I opened the build versus buy model I have used for a decade and realised there is no cell to put any of that in.

The thesis

Cost is no longer the deciding variable in build versus buy. Build got cheap enough that the number stopped being decisive. Buy stopped producing a number you can forecast at all. The variable that replaced cost is reversibility: how many days it takes to undo the choice you just made.

What actually changed

Two things moved at once, in opposite directions.

Build got cheap at the front and expensive at the back. New Relic surveyed 200 US technology decision makers, manager level and above, published 10 June 2026.

67% said AI now generates or significantly refactors between 51% and 75% of their weekly code output. Google has publicly put its own figure near 75%, Microsoft around 30%, GitHub Copilot 46%. Whatever the real number inside your organisation, the first working version of an internal tool is no longer a two-quarter project with a business case attached.

The same survey carries the other half. 78% reported a measurable spike in production incidents tied to AI-written code. 86% saw senior engineers spending more time firefighting. 74% said at least a quarter of AI-written code needed significant rework after deployment. The report puts AI-generated code at roughly 1.7 times more critical runtime issues.

The build got cheap. The run got expensive. That is a different shape of decision, not a smaller one.

Buy stopped being a fixed price. Zylo’s 2026 SaaS Management Index covers 40 million licences and $75 billion in spend under management. Median SaaS spend per employee: $9,455. Licences sitting unused: 36%. AI-native application spend in organisations above 10,000 people: up 393% year on year. Large enterprises are adding 21 applications a month.

The figure that matters most sits in their survey of 218 IT leaders. 78% reported unexpected charges from consumption-based or AI pricing models. 61% were forced to cut projects because of unplanned SaaS cost increases.

Read that second number again. Three in five technology organisations killed work they had already committed to, because a vendor bill landed above forecast. That is not a procurement problem. That is a budget that has stopped being a budget.

For scale: Gartner put worldwide software spend at $1,468 billion for 2026, growing 15.5%, against IT services at $1,570 billion growing 5.3%. The money is moving into the category that just became unforecastable.

Three cases

D23.io. I run a managed Apache Superset service. Superset is Apache-licensed and costs nothing to acquire. Nobody has ever paid me for the software. They pay for version upgrades that do not break their dashboards, for someone answering the phone when a query melts a warehouse, for the security posture. The decision there was never about build cost, because build cost was zero. It was about who carries the run. That is the question the cost comparison never asks.

D30. I built forensic extraction over ASX annual reports myself rather than buying a data feed. Not because I could not buy one. Because the extraction path and the articulation gates are the product. Buying that layer means renting the only part a customer cannot get somewhere else, from a supplier who can reprice it annually. When a capability sits directly on your differentiated data, buying it hands someone else pricing power over your margin.

The support agent, priced out. Take 40,000 support conversations a year. At Agentforce’s $2 per conversation that is $80,000 before platform fees and before implementation. At Fin’s 99 cents per resolved outcome your cost depends entirely on resolution rate, which you do not know until you are live. At Zendesk’s committed $1.20 it is $48,000, if your volume matches the commitment you signed. Same capability, three cost curves, none of them modellable over three years without traffic data you do not have yet. Zendesk also absorbed its Advanced AI add-on into all Suite plans in May 2026, which moved the line again mid-year.

That is the cell that does not exist in the spreadsheet.

Where this breaks

The reversibility test is a luxury of small commitments.

If the capability is your system of record, nothing is reversible. Moving a general ledger, a core banking platform or a policy administration system is a two-year programme whichever way you originally decided, and for those, cost and vendor viability come straight back to the top of the list. Do not apply my test to a core system.

The bigger problem is the assumption underneath all of it: that build actually did get cheap for your team. METR ran a randomised controlled trial with 16 experienced open-source developers across 246 real issues, on repositories they had contributed to for years, averaging over a million lines of code and 22,000 stars. With AI tools available, they were 19% slower. They had expected to be 24% faster. After finishing, they still believed AI had made them 20% faster.

That result should sit badly with anyone quoting the 67% figure, including me. On a mature codebase, with senior people who already hold the context in their heads, build cost may not have fallen at all. It may have risen while everybody felt quicker. If that describes your team, this thesis weakens a lot, and the honest move is to measure your own cycle time before you rearrange policy around somebody else’s survey.

What I would do on Monday

1. Pull twelve months of vendor invoices and compute variance, not average. Any line above 20% month-on-month variance has become a risk decision rather than a cost decision. Those are your first candidates to cap or bring in-house.

2. Write the exit paragraph before you sign. Ninety days, where the data goes, in what format, who does the work, what it costs. If nobody in the room can write that paragraph, you are not buying a tool. You are merging with a vendor.

3. Put a hard ceiling on every usage-priced contract, with a stop and not an alert. An alert tells you after the money has gone. Ask for the ceiling in the contract, in writing, and expect resistance.

4. For anything you build, name the person who owns it in eighteen months. No name, no build. What you have otherwise is a prototype and a future problem, and the New Relic firefighting numbers tell you who inherits it.

5. Run a licence utilisation report this week. If 36% is anywhere near right for you, you are already paying monthly for a buy decision that went wrong. That money is the budget for whatever you decide next.

Close

I went back to the model and deleted the cost comparison tab.

What replaced it is one column: days to undo this. Under 90, buy it and cap the term at twelve months. Over 90, it either touches the data that makes you money, in which case build it and own the path, or it does not, in which case put an agency on it under a six month cap and keep the repository in your own organisation.

The spreadsheet is smaller now. It is also the first version of it that survives contact with a pricing page.

Most of what I write about here started as a client problem. If you have one, bring it to me.

Those reports run two to four weeks and cover five things: architecture and scalability, the team, security and compliance, infrastructure spend, and roadmap risk. I have been on both sides of them. The operator being audited, and the person an investor calls three months after close when the plan is already behind.

Not one standard scope measures how long it takes the company to turn a decision into a shipped, safe change.

That number is the deal.

The thesis

Technical diligence audits the artefact. The value leaks out of the system.

You are not buying a codebase. You are buying a rate: the rate at which this business converts capital into shipped change without breaking the part that makes money. Nobody measures that rate before the wire clears. Then the value creation plan assumes a rate nobody has ever observed.

The arithmetic changed and the diligence did not

For roughly a decade, a buyout needed about 5% annual EBITDA growth to reach a 2.5x multiple on invested capital. Multiple expansion and cheap debt carried the rest. Bain’s 2026 report puts the requirement now at 10% to 12% annual EBITDA growth for the same outcome, with borrowing costs sitting at 8% to 9% and leverage at 30% to 40% of the capital structure.

Double the operating growth, from the same assets, under more expensive debt.

The rest of the picture makes it worse. There are 32,000 unsold portfolio companies carrying $3.8 trillion of value. Average holding periods at exit have stretched to around 7 years, up from the 5 to 6 that was normal between 2010 and 2021. Distributions to LPs came in at 14% of NAV in 2025, the fourth consecutive year below 15%.

So returns have to come from operations. In a software or software-enabled asset, operations means one thing: how fast and how safely the company can change its own product. That is the engine. Diligence inspects the paint.

The code audit stopped being a signal

Here is what broke the old method.

CloudBees surveyed more than 200 enterprise technology leaders for its 2026 State of Code Abundance report. AI now generates or assists 61% of the average enterprise codebase. In the same survey, 81% of leaders report an increase in production issues tied to AI-generated code, while 92% say they are confident in that code’s production readiness. Organisations could attribute only about one third of their AI spend to a specific business outcome.

Read those four numbers together. The majority of what a code audit now reads was written by a model. It is stylistically uniform, cheap to produce, and syntactically clean. A static scan of it comes back green. And the same leaders sitting on top of it report more incidents, not fewer.

The artefact and the risk have come apart. SonarQube can tell you the code is tidy. It cannot tell you whether this company can safely change it on a Tuesday afternoon with two engineers on leave.

Three things the standard scope misses

One: absorption capacity. The value creation plan lands with a dozen or more initiatives in the first year. ERP consolidation, pricing rebuild, a data platform, two integrations, a security remediation. The relevant question is not whether each is a good idea. It is how many concurrent initiatives this delivery system has ever finished in a single year. That number exists. It is in the last three years of shipped work. Diligence almost never asks for it.

Two: the review and approval path. Writing changes got cheap. Approving them did not. In most mid-market software businesses there are three or four people who can sign off a change to billing, entitlements or customer data. Their names are not in the diligence report. Their retention risk is the single largest technical risk in the deal, and it is usually filed under key person dependency with no measurement attached.

Three: the gap between the process document and the deploy log. Every data room contains a document describing how the company ships software. It is aspirational. The deploy history, the incident records and the pull request timestamps describe what actually happens. The distance between those two artefacts is the most predictive thing in the whole room, and reading it takes an afternoon.

I built D30 to pull three-statement fact files out of ASX annual reports and run articulation gates over them, because I do not trust a summary figure I cannot trace back to the filing that produced it. The instinct is identical here. A process document is a summary figure. The deploy log is the filing.

Where I am wrong

This thesis has real limits and I would rather name them than have a reader find them.

For asset-light businesses where software is a thin wrapper on a services model, the codebase genuinely is the risk, and licence contamination or a single hard-coded customer integration can be the whole finding. For a carve-out, the delivery system you measure belongs to the seller and will not survive separation, so measuring it tells you less than modelling what replaces it. And there are deals where the data simply is not available: a competitive process, a two-week window, no repository access, a seller who will not open the incident history. In that situation the code audit is not the wrong tool. It is the only tool you are allowed to use, and a good one done honestly beats a throughput analysis you invented.

The failure I am pointing at is not doing a code audit. It is doing a code audit and believing you have assessed delivery risk.

What I would do on Monday

1. Add one line to the diligence request list. The last 90 days of production deployments with timestamps, and the last 12 months of incidents with time to restore. Not the process document. The records.

2. Count the approvers. Ask who can approve a change to the revenue-critical paths. If the answer is fewer than four people, that is a retention clause in the SPA, not a footnote.

3. Divide the plan by the observed rate. Take the number of year-one initiatives in the value creation plan and compare it against the largest number of concurrent initiatives the company has actually completed in a year. If the plan is more than double, the plan is fiction and the EBITDA bridge is built on it.

4. Instrument in the first 30 days post-close. Jellyfish, DX and Swarmia all read from Jira and GitHub and give you a baseline inside a fortnight. Set that baseline before the operating partner starts changing things, or you will never know whether anything you did worked.

5. Re-underwrite once, at day 90. With real throughput data in hand, restate the operating case. Investors hate this. Doing it at month 18 instead is worse.

Back to the report

That two to four week technical diligence report will still get written on every one of the next $900 billion of deals. It is not useless. It is scoped for a market where multiple expansion did the heavy lifting and 5% growth was enough.

That market is gone. The number that has to double is produced by a system nobody in the room measured.

Buy the engine, not the paint.

I built D30 to pull three-statement fact files out of ASX annual reports and flag where the numbers stop articulating. If you run diligence on listed or pre-IPO assets, have a look.

That assumption died about eighteen months ago. Almost nobody has redesigned around its absence.

Here is my claim, and you are welcome to disagree with it: your engineering organisation is not slow because your people are slow. It is slow because it was optimised for a constraint that no longer binds, and the real constraint moved somewhere nobody is measuring.

The constraint moved to review

Faros AI tracked 22,000 developers across roughly 4,000 teams. The productivity numbers are real. Epics completed per developer rose 66%. Task throughput per developer rose 33.7%. The share of AI-generated code accepted without editing went from 20% to 60%.

Then look at what happened downstream in the same dataset. Median code review time rose 441.5%. Median time to first review rose 156.6%. Code churn rose 861%. Bugs per developer rose 54%. The ratio of production incidents to pull requests rose 242.7%. Pull requests merged with no review at all rose 31.3%.

LinearB looked at 8.1 million pull requests across 4,800 teams in 42 countries and found the mechanism. An unassisted pull request at the 75th percentile is 157 lines. An AI-assisted one is over 400. Reviewer pickup time goes from roughly 200 minutes to more than 16 hours. And the number that should stop you: the 30-day merge rate for unassisted pull requests is 84.5%. For AI-assisted pull requests it is 32.7%.

Two thirds of the AI-assisted work does not merge within a month. It was generated. It was not delivered. Your throughput metric counted it. Your customers never saw it.

What is actually happening

The mechanism is simple. Adding an agent to the writing step and nothing to the review step does not make the system faster. It makes the queue longer. This is not a novel insight about software. It is the oldest result in operations research, and every CTO who has read about a factory floor already knows it. We are just failing to apply it to ourselves.

The reason we fail to apply it is that the writing step is where the visible cost sits. Engineers are expensive, so tooling that makes engineers produce more looks like an obvious win. Review capacity is invisible on a budget line. It is a byproduct of having senior people with context, and it does not appear anywhere in a procurement process.

So the org buys more production and inherits more queue.

The three shapes it takes

I want to be careful here and describe patterns rather than claim outcomes I have not measured. What I see across the engagements I run falls into three shapes.

The first is the large organisation with real seniority on the bench. Team-level velocity improves and looks convincing in a steering committee. The number that does not move is time from commit to customer, because the gain is absorbed in the gap between a pull request opening and a senior engineer having enough uninterrupted time to reason about four hundred lines they did not write. The work exists. It is queued.

The second is the mid-sized team where the senior engineers quietly become a bottleneck they were never staffed to be. Their week used to be roughly half building and half reviewing. It inverts. Nobody decides this and nobody announces it. The input rate changed and the roles did not, so the system rebalanced itself in the only place it could.

The third shape is the small product team with no senior reviewer at all. There, the 31.3% rise in unreviewed merges is not a statistic, it is the operating model. Those teams genuinely are shipping faster this quarter. They are also the population where the incident-to-pull-request ratio, up 242.7% in the Faros data, is going to show up as a customer-visible event rather than a dashboard.

GitHub has now run over 60 million automated code reviews, and roughly one in five reviews involves an agent. That helps with the mechanical layer. It does nothing for the judgement layer, which is the layer that is actually saturated.

Where this argument is weak

I should be honest about two things.

First, these are aggregate numbers across thousands of teams at a moment of rapid adoption. Some of the review-time increase is a learning curve, not a structural fact. Teams that adopted agents 18 months ago look different from teams that adopted them last quarter, and I would expect some of this to compress as review tooling catches up.

Second, the argument does not apply evenly. If your codebase is small, your team is three people, and everyone has full context, the review step was never a real queue and adding an agent genuinely does just make you faster. The constraint I am describing shows up when context is distributed across people, which is a function of headcount and codebase age, not of AI.

What I do not accept is the version of this argument that says the numbers will fix themselves. Queues do not self-correct. They get worse until somebody changes the capacity or the arrival rate.

What I would do on Monday

1. Measure time from pull request opened to merged, and split it by whether an agent was involved. If you measure one thing from this post, measure that. Most organisations report throughput and have never looked at this number.

2. Cap pull request size. The 400-line AI-assisted pull request is the specific object that breaks review. A hard cap forces decomposition at the point of generation, where it is cheap, instead of at the point of review, where it is not.

3. Make review capacity an explicit, staffed role rather than a tax on whoever has the most context. If two thirds of generated work is not merging, the reviewer is your production line, not your overhead.

4. Stop reporting throughput per developer to your board without the merge rate beside it. One of those numbers is activity. The other is delivery.

5. Move at least one senior engineer out of writing entirely for a quarter and watch what happens to flow. In every case where I have seen this tried, the organisation discovers the constraint was never where the budget was pointed.

The part I keep coming back to

In 1995 the scarce thing was someone who could make the machine do what you wanted. That scarcity built our entire profession, our salary bands, our org charts and our hiring funnels.

The scarcity is gone. What replaced it is the ability to look at four hundred lines of plausible-looking code and know which thirty are wrong. We did not build any of our institutions around that skill, and right now we are not staffing for it either.

The code was never the bottleneck. It just looked like one for thirty years.

I run AI transformation programs through PADISO. If the gap between your throughput metric and what your customers actually received is the problem you have, book a call at padiso.co.

Both models offer alternatives to hiring a full-time Chief Technology Officer, but they operate under distinctly different premises. Understanding the nuances between these two approaches—and when to deploy each—is essential for leaders making strategic technology decisions. Understanding the trade-offs in the fractional vs interim CTO comparison helps align leadership to business goals.

In this comprehensive guide, we'll break down the fractional vs interim CTO comparison, explore the real-world implications of each model, and help you determine which leadership approach aligns with your organization's current stage, budget, and strategic priorities.

Understanding the Core Distinction: Fractional vs Interim CTO

The fundamental difference between a fractional CTO and an interim CTO lies in duration, intensity, and strategic intent. While both models bring senior technical leadership without the cost and commitment of a full-time hire, they serve different organizational needs. A careful fractional vs interim CTO analysis will consider duration, intensity, and long-term strategic intent.

A fractional CTO is a long-term, ongoing engagement where a senior technologist dedicates a portion of their time—typically 10–40 hours per week—to your organization over an extended period (often 6–24+ months or indefinitely). The fractional model emphasizes strategic continuity, ongoing mentorship, and building sustainable technical practices. It's designed for organizations that need consistent leadership presence but don't require a full-time executive commitment.

An interim CTO, by contrast, is a temporary, intensive engagement typically lasting 3–12 months. An interim CTO is brought in to handle a specific transition, crisis, or project—such as standing up a new technology platform, leading through an acquisition, stabilizing a failing engineering organization, or bridging a leadership gap during a permanent hire search. The interim model emphasizes rapid execution, hands-on problem-solving, and transition planning.

As explained in resources like Fractional CTO vs Interim CTO: Which One Do You Actually Need?, the choice hinges on whether your organization needs ongoing strategic guidance (fractional) or time-bound operational intervention (interim).

Time Commitment and Engagement Duration

Photo by Dylan Gillis on Unsplash

One of the most visible differences between these two models is how much time the executive dedicates to your organization and for how long. Any board evaluating fractional vs interim CTO options should map hours and duration to desired outcomes.

Fractional CTO Time Commitment:

Fractional CTOs typically work 10–40 hours per week, though some arrangements flex based on seasonal needs or project intensity. The engagement is open-ended and renewable, often spanning 6 months to several years. Many fractional relationships become semi-permanent, evolving as the organization's needs change.

This part-time structure means the fractional CTO is simultaneously serving other clients or maintaining a portfolio of responsibilities. This isn't a limitation—it's often a feature. A fractional CTO brings cross-industry insights, exposure to multiple technology stacks, and battle-tested patterns from other organizations.

The fractional model works particularly well for organizations that need consistent guidance but don't have the budget or workload to justify a full-time executive. As detailed in Fractional CTO vs Full Time CTO: Which One 10M Company Actually Needs, many companies in the $5M–$50M revenue range find fractional engagement the optimal balance.

Interim CTO Time Commitment:

Interim CTOs typically operate at full-time intensity (40–60+ hours per week) for a defined duration. The engagement is time-bound and mission-focused, with clear start and end dates or trigger events (e.g., "until the new platform launches" or "until a permanent CTO is hired").

Because the interim role is temporary and intensive, the interim CTO is often fully dedicated to your organization during the engagement. This allows for deep immersion in your challenges, faster decision-making, and the ability to implement significant changes within a compressed timeframe.

Interim engagements are ideal when you need someone to "own the room," make tough technical decisions, and drive execution without the distraction of other commitments. Interim CTO vs Fractional CTO (2026): Which Do You Need? emphasizes that interim CTOs excel in crisis stabilization and major transitions.

Cost Structure and Financial Implications

Photo by Christian Velitchkov on Unsplash

Cost is often the primary driver of the fractional vs interim CTO decision, but the financial picture is more nuanced than simple hourly rates. When evaluating budgets, compare total cost and impact in a fractional vs interim CTO analysis rather than focusing solely on hourly rates.

Fractional CTO Costs:

Fractional CTOs typically charge via retainer-based models, often ranging from $5,000–$20,000+ per month depending on seniority, location, and scope. Some fractional arrangements use hourly rates ($150–$400+ per hour) or equity arrangements for early-stage startups.

Because fractional engagement is part-time and ongoing, the total investment is spread over a longer period. However, the cumulative cost over 12–24 months can be substantial. The advantage is predictability and flexibility—you know the monthly cost, and you can adjust hours or scope as needs evolve.

As explored in Fractional CTO Economics: Hours, Retainers, Equity, fractional arrangements often include equity components for early-stage companies, aligning incentives and reducing cash outlay.

Interim CTO Costs:

Interim CTOs typically command higher daily or weekly rates than fractional CTOs—often $3,000–$10,000+ per day or $15,000–$50,000+ per week—reflecting the intensity, temporary nature, and specialized expertise required.

However, because the engagement is time-bound (typically 3–12 months), the total cost is front-loaded and finite. You know upfront that you're committing to a 6-month engagement at $X per week, for a total investment of $Y. There's no open-ended commitment.

Interim engagements are often more expensive per unit of time but less expensive in total than a full-time hire (which includes salary, benefits, equity, and severance). For a specific, bounded problem, the interim model can be highly cost-effective.

As detailed in Pricing Fractional CTO Engagement: Day Rates, Retainers, Equity, organizations should evaluate total cost of engagement, not just hourly rates.

Strategic Continuity vs. Rapid Execution

Photo by Luke Chesser on Unsplash

Beyond time and cost, fractional and interim CTOs differ fundamentally in their strategic posture. Your product roadmap often drives whether you need fractional vs interim CTO guidance.

Fractional CTO: Strategic Continuity

The fractional model is built for long-term strategic thinking and sustainable change. Because the fractional CTO remains engaged over months or years, they:

• Build institutional knowledge about your technology, team, and business strategy

• Mentor your internal engineering leaders over time, raising organizational capability

• Implement sustainable practices (architecture patterns, security controls, development processes) that outlast the engagement

• Evolve strategy as the business grows, pivoting technical direction as needed

• Serve as a trusted advisor to the board, CEO, and executive team on technology decisions

The fractional model assumes that your organization benefits from consistent, evolving guidance. This is ideal for companies scaling engineering teams, modernizing technology stacks, or embedding AI and analytics capabilities. As outlined in The Fractional CTO Engagement Model: How to Structure the First 90 Days, fractional engagements thrive when structured with clear 90-day milestones that feed into longer-term strategy.

Interim CTO: Rapid Execution

The interim model is optimized for fast, decisive action on a bounded problem. An interim CTO excels at:

• Crisis stabilization: Stopping the bleeding when engineering is in chaos

• Rapid implementation: Standing up new platforms, migrating systems, or launching new capabilities in compressed timeframes

• Leadership transitions: Bridging the gap between departing and incoming permanent CTOs

• Specific projects: Leading a major initiative (e.g., cloud migration, AI integration) to completion

• Tough decisions: Making unpopular but necessary choices (e.g., sunsetting legacy systems, restructuring teams)

Interim CTOs can move faster because they're not managing the long-term consequences—they're focused on solving the immediate problem and transitioning the solution to permanent leadership. Interim CTO Carve-Outs: Standing Up Technology highlights how interim CTOs excel at well-defined technical carve-outs.

Depth of Involvement and Hands-On Leadership

Another critical distinction is the depth of hands-on involvement and the breadth of responsibilities each model typically assumes. Decide early in a fractional vs interim CTO discussion how much operational ownership you're willing to transfer.

Fractional CTO Involvement:

Fractional CTOs are often strategic advisors with selective hands-on involvement. They might spend 60% of their time on strategy, architecture, and mentorship, and 40% on hands-on coding, technical reviews, or specific problem-solving.

Because fractional CTOs are part-time, they're not typically managing day-to-day operations or attending every meeting. Instead, they focus on:

• High-level technical strategy and roadmap

• Architecture decisions and technical debt management

• Hiring and team development

• Board-level technology updates

• Specific technical challenges or mentoring sessions

This selective involvement means the fractional CTO is a force multiplier for your existing team, not a replacement for operational leadership. Organizations with fractional CTOs still need strong internal engineering leadership (VP Engineering, Engineering Managers) to handle day-to-day execution.

Interim CTO Involvement:

Interim CTOs are typically fully embedded and hands-on. They attend all relevant meetings, make day-to-day technical decisions, and often code or directly oversee critical work.

Because the interim engagement is temporary and intensive, interim CTOs often:

• Own the full scope of technology leadership during their tenure

• Make and implement major decisions without extensive consensus-building

• Directly execute on critical technical work, not just oversee it

• Establish new processes, tools, and standards that the permanent team will inherit

• Document and transition their work to ensure continuity after departure

The interim model works because the organization knows it's temporary—they can tolerate a more autocratic, directive leadership style if it means solving the crisis or completing the transition.

Organizational Readiness and Internal Team Dynamics

The choice between fractional and interim also depends on the maturity and readiness of your existing team. Leadership should run a fractional vs interim CTO readiness assessment to determine internal team capability and governance gaps.

Fractional CTO Fit:

The fractional model works best when your organization has:

• A capable internal engineering team that can execute day-to-day

• Clear strategic direction (even if technical strategy needs refinement)

• Stable operations (not in crisis mode)

• Willingness to invest in long-term capability building

Fractional CTOs amplify existing strengths. If your team is already functional but needs strategic direction, fractional engagement is ideal. As discussed in Building Engineering Team Fractional CTO, fractional CTOs excel at scaling teams and establishing sustainable engineering cultures.

Interim CTO Fit:

The interim model is appropriate when:

• Your organization is in crisis (engineering chaos, failed projects, departing CTO)

• You need rapid, decisive action on a bounded problem

• Your internal team needs external authority to implement hard changes

• You have a clear transition plan (hiring a permanent CTO, promoting from within, or shifting to fractional)

Interim CTOs are often brought in precisely because the internal team can't or won't solve the problem alone. The interim leader brings external authority and fresh perspective.

Scope and Responsibilities

The scope of responsibilities also differs significantly between the two models.

Fractional CTO Scope:

Fractional engagements typically focus on strategic and architectural domains, such as:

• Technology strategy and roadmap

• Architecture and systems design

• Engineering culture and hiring

• Vendor and tooling decisions

• Board-level technology guidance

• Specific technical mentoring or code reviews

Fractional CTOs often have a well-defined scope document that clarifies what's in and out of the engagement. As detailed in Fractional CTO Scope Document: Padiso Template, clear scope prevents scope creep and ensures alignment on expectations.

Interim CTO Scope:

Interim engagements often have a broader, more operational scope, including:

• Full technology leadership and decision-making

• Day-to-day team management and performance

• Project execution and delivery

• Crisis stabilization and operational fixes

• Hiring and team restructuring

• Vendor management and procurement

• Board reporting and stakeholder communication

Interim CTOs often have a mission statement rather than a detailed scope—e.g., "Stabilize engineering and launch the new platform by Q3." The interim leader has more autonomy to define and redefine scope as conditions change.

Transition and Exit Planning

How each model ends is also fundamentally different. Exit plans differ significantly in any fractional vs interim CTO engagement, so document handoff processes accordingly.

Fractional CTO Transition:

Fractional engagements can transition smoothly to:

• Continued fractional relationship (ongoing advisory)

• Full-time CTO hire (fractional CTO mentors the new permanent hire)

• Reduced fractional engagement (shifting to office hours or quarterly check-ins)

• Graduation (the organization is ready to operate independently)

Because fractional relationships are built on strategic mentorship and capability building, the transition is often gradual and planned. As outlined in When Fractional CTO Engagements Fail: How to Fix Them, successful fractional engagements include clear milestones and transition criteria.

Interim CTO Transition:

Interim engagements have a predetermined end state, such as:

• Permanent CTO hire (interim CTO onboards the new permanent leader)

• Promotion from within (interim CTO mentors and transitions to internal leader)

• Return to fractional or advisory model (if the crisis is resolved)

• Engagement conclusion (problem solved, transition complete)

Interim transitions are typically structured and documented. The interim CTO is responsible for ensuring that their work, decisions, and institutional knowledge are transferred to the permanent team. As discussed in Interim CTO Carve-Outs: Standing Up Technology, successful interim engagements include explicit transition planning from day one.

Use Cases: When to Choose Fractional

Fractional CTO engagements are ideal for:

Scaling Startups and Growth-Stage Companies

Companies in the $5M–$50M revenue range often lack the budget for a full-time CTO but need consistent technical leadership as they scale. A fractional CTO can provide 15–25 hours per week of strategic guidance, hiring support, and architecture decisions without the $250K+ annual cost of a full-time executive. If you can't staff a full-time executive, a fractional vs interim CTO decision often resolves in favor of fractional for growth and mentorship. As explored in Fractional CTO vs Full Time CTO: Which One 10M Company Actually Needs, the fractional model aligns perfectly with this stage.

Non-Technical Founders

Founders without technical backgrounds benefit enormously from fractional CTOs who can translate between engineering and business, mentor the VP Engineering, and help the founder understand technology trade-offs. As detailed in Fractional CTO or Technical Co-Founder: Which Fits a Non-Technical Founder, fractional CTOs are often the right choice for non-technical founders scaling beyond the initial product phase.

AI and Analytics Integration

Organizations embedding AI capabilities, autonomous agents, or embedded analytics (e.g., Apache Superset + ClickHouse) benefit from fractional CTO guidance on architecture, vendor selection, and team structure. The fractional model allows for ongoing mentorship as the organization learns and evolves its AI strategy.

Technology Modernization

Companies modernizing legacy systems, migrating to cloud, or adopting new architectural patterns benefit from fractional CTO guidance on strategy and approach. The long-term engagement allows for phased implementation and course correction.

Security and Compliance

Organizations preparing for SOC 2 or ISO 27001 audits benefit from fractional CTO involvement in architecture reviews, security strategy, and compliance roadmapping. As mentioned in Padiso's focus on SOC 2 / ISO 27001 security audits, fractional engagement allows for ongoing security mentorship and governance.

Lighter-Touch Advisory

Some organizations need only occasional guidance—perhaps monthly office hours, quarterly strategy reviews, or ad-hoc technical mentoring. Fractional CTO Office Hours: Lighter Engagement Model describes how fractional CTOs can serve in this lighter capacity.

Use Cases: When to Choose Interim

Interim CTO engagements are ideal for:

Crisis Stabilization

When engineering is in chaos—missed deadlines, high turnover, failed projects, or departing CTO—an interim CTO brings external authority and fresh perspective to stabilize operations. The interim model works because the organization knows it's temporary and can tolerate directive leadership. When time-bound delivery or crisis response is required, a fractional vs interim CTO analysis will often recommend interim leadership.

Leadership Transitions

When a CTO departs and you need coverage while recruiting a permanent replacement, an interim CTO ensures continuity and prevents leadership vacuum. The interim leader can also participate in recruiting and onboarding the permanent CTO.

Major Platform Launches

When launching a new platform, migrating to a new architecture, or executing a major technical initiative with a tight deadline, an interim CTO can lead the effort with full-time focus and accountability. Once the launch is complete, the organization can transition to fractional advisory or permanent hire.

Acquisition and Integration

During M&A activity, an interim CTO can lead technology integration, rationalize systems, and establish new technical standards. The temporary nature of the role allows for decisive action without long-term commitment.

Board-Mandated Change

When a board or investor mandates significant technology changes, an interim CTO can implement those changes with authority and urgency. The interim leader can make tough decisions (e.g., sunsetting legacy systems, restructuring teams) that internal leaders might struggle with.

Government and Regulated Environments

Government agencies and highly regulated organizations often use interim CTOs to lead specific initiatives (e.g., modernization programs, security upgrades, compliance projects) with defined timelines and deliverables. As relevant to government modernization efforts, interim CTOs bring specialized expertise and can move quickly within bureaucratic constraints.

Hybrid and Blended Approaches

Many organizations use a hybrid model that combines fractional and interim elements. Hybrid strategies let you test fractional vs interim CTO combinations without committing to one model exclusively.

Fractional-to-Interim Transition:

An organization might start with fractional CTO guidance (e.g., 20 hours/week for 3 months) to assess the situation and develop a plan. If a crisis emerges, the engagement can shift to interim (e.g., 40 hours/week for 6 months) to execute the plan, then revert to fractional for ongoing guidance.

Interim-to-Fractional Transition:

An interim CTO might stabilize a crisis and then transition to fractional advisory (e.g., 10 hours/week) to mentor the permanent team and ensure sustainability of changes.

Parallel Fractional and Interim:

Some organizations engage a fractional CTO for ongoing strategy while bringing in an interim CTO for a specific project or crisis. The two work in parallel, with the interim leader handling the bounded problem and the fractional leader providing strategic oversight.

As discussed in Fractional CTO Engagement Models 2026 Buyers Guide, modern organizations increasingly use blended approaches to optimize for flexibility and cost-effectiveness.

Key Comparison: Side-by-Side Feature Matrix

To help clarify the differences, here's a detailed comparison:

Factor Fractional CTO Interim CTO Duration 6 months–indefinite 3–12 months (bounded) Time Commitment 10–40 hours/week (part-time) 40–60+ hours/week (full-time) Cost Model Monthly retainer ($5K–$20K+) or hourly Daily/weekly rate ($3K–$10K+/day) Total Investment Spread over long term Front-loaded, finite Strategic Focus Long-term capability building Rapid execution on bounded problem Hands-On Involvement Selective (60% strategy, 40% execution) Intensive (hands-on across all domains) Scope Well-defined, strategic Broad, operational, mission-driven Team Fit Requires capable internal team Works in crisis or leadership vacuum Decision-Making Collaborative, mentoring-focused Directive, authority-based Transition Gradual, planned Structured, documented Ideal For Scaling, modernization, advisory Crisis, launches, transitions Risk Scope creep, unclear ROI Incomplete transition, dependency

Pros and Cons: Fractional CTO

Pros:

• Cost-effective for organizations that can't justify full-time hire

• Flexibility to adjust hours and scope as needs evolve

• Cross-industry insights from fractional CTO's other engagements

• Long-term relationship builds institutional knowledge and mentorship

• Lower risk than permanent hire (easier to adjust or end)

• Equity alignment available for early-stage companies

• Sustainability through capability building and team development

Cons:

• Limited availability (part-time means less immediate responsiveness)

• Less operational ownership (requires strong internal leadership)

• Potential scope creep without clear boundaries

• Dependency risk (what happens if fractional CTO leaves?)

• Slower crisis response (not available full-time)

• Cumulative cost can be high over 24+ months

• Requires clear internal structure to avoid confusion about authority

Pros and Cons: Interim CTO

Pros:

• Full-time focus on immediate problem or project

• External authority to make tough decisions

• Rapid execution and crisis stabilization

• Defined timeline and cost (predictable investment)

• Fresh perspective on entrenched problems

• Intensive mentorship for internal team

• Clear transition plan from day one

Cons:

• Higher cost per unit of time than fractional

• Limited long-term strategy (focused on immediate problem)

• Potential institutional knowledge loss at end of engagement

• Disruption if internal team resists external leadership

• Transition risk if permanent leader isn't ready to take over

• Less sustainable if changes aren't embedded in culture

• May create dependency on external leadership

The Verdict: How to Choose

Here's a practical framework for deciding between fractional and interim CTO:

Choose Fractional CTO If:

1. Your organization is growing but stable (not in crisis)

2. You have a capable internal engineering team

3. You need strategic guidance and mentorship over time

4. You want to build sustainable technical practices

5. You're scaling to $10M–$100M+ revenue range

6. You need flexibility to adjust engagement as you grow

7. You're embedding AI, analytics, or modernizing technology

8. You want to mentor your VP Engineering or internal leaders

Choose Interim CTO If:

1. Your organization is in crisis or facing urgent technical challenge

2. You need full-time, intensive leadership for a bounded problem

3. You're launching a major platform or initiative with tight deadline

4. You're transitioning between CTOs or leaders

5. You need external authority to implement difficult changes

6. You have a clear end-state or success criteria

7. You're going through M&A or major organizational change

8. You need rapid execution over long-term strategy

Consider Hybrid/Blended If:

1. You need both strategic guidance and tactical execution

2. You want to start with fractional assessment, then shift to interim if needed

3. You're planning a multi-phase transformation (fractional for strategy, interim for execution)

4. You want fractional oversight with interim project leadership

As detailed in Fractional CTO vs Tech Advisor vs Head of Engineering, the right choice depends on your specific needs, team maturity, and organizational stage.

Preparing Your Organization for Either Model

Regardless of which model you choose, preparation is essential for success. Before any retained engagement, run a checklist comparing the fractional vs interim CTO expectations against your operating rhythm.

For Fractional CTO Engagement:

1. Define clear scope using a Fractional CTO Scope Document to prevent scope creep

2. Establish governance (decision-making authority, meeting cadence, communication channels)

3. Identify internal champion who owns day-to-day execution

4. Set 90-day milestones (as outlined in The Fractional CTO Engagement Model: How to Structure the First 90 Days)

5. Prepare your team for external leadership and mentorship

6. Align on success metrics and how you'll measure ROI

For Interim CTO Engagement:

1. Define mission statement and success criteria clearly

2. Establish end-state (when does the engagement end? what does success look like?)

3. Prepare for change (internal team may resist external leadership)

4. Plan for transition from day one (who takes over when interim leader departs?)

5. Document decisions and rationale for continuity

6. Allocate time for knowledge transfer in final 30 days

7. Identify permanent leadership (hire, promote, or shift to fractional)

Real-World Considerations for Enterprise and Government

For enterprise and government organizations, the fractional vs interim choice has additional nuances.

Enterprise Considerations:

Large enterprises often use fractional CTOs for strategic advisory on technology modernization, AI integration, and cloud migration. The fractional model allows enterprises to tap specialized expertise without full-time commitment. Fractional CTOs can also provide governance and security oversight aligned with SOC 2 and ISO 27001 requirements.

Enterprises use interim CTOs for crisis stabilization, major platform launches, or leadership transitions. The interim model is particularly valuable during acquisitions or when implementing board-mandated technology changes.

Government Considerations:

Government agencies increasingly use interim CTOs for modernization initiatives with defined timelines and deliverables. The interim model aligns well with government procurement cycles and project-based funding.

Fractional CTOs are valuable for ongoing security and compliance advisory, particularly for SOC 2 and ISO 27001 audits. Fractional engagement also supports government agencies in building sustainable engineering practices and mentoring internal teams.

As relevant to government technology modernization, both models offer flexibility and cost-effectiveness compared to permanent hires.

Common Pitfalls and How to Avoid Them

Fractional CTO Pitfalls:

• Unclear scope leading to scope creep and misaligned expectations

• Insufficient internal leadership leaving no one to execute fractional guidance

• Treating fractional CTO as full-time replacement (they're not)

• Lack of decision-making authority limiting fractional CTO's effectiveness

• Not measuring progress or defining success criteria

Interim CTO Pitfalls:

• No clear end-state or success criteria (engagement drifts)

• Inadequate transition planning (knowledge and decisions don't transfer)

• Internal team resistance to external leadership

• Over-reliance on interim leader without building internal capability

• Hiring permanent CTO without interim input (new leader doesn't understand context)

As discussed in When Fractional CTO Engagements Fail: How to Fix Them, clarity, governance, and transition planning are essential to success.

Questions to Ask Before Committing

Before engaging either a fractional or interim CTO, ask these critical questions:

For Fractional CTO:

1. What is the expected duration, and how will we know when to transition or end the engagement?

2. How many hours per week can the fractional CTO commit, and how flexible is that?

3. What decisions does the fractional CTO have authority to make unilaterally?

4. How will we measure success and ROI?

5. What happens if the fractional CTO becomes unavailable?

6. How will we handle scope creep or changing needs?

7. What is the process for onboarding and first 30 days? (Reference Fractional CTO Onboarding: First 30 Days)

For Interim CTO:

1. What is the specific mission and success criteria?

2. What is the expected duration and end-state?

3. How will the interim CTO transition their work to permanent leadership?

4. What authority does the interim CTO have to make decisions and implement changes?

5. Who is responsible for documentation and knowledge transfer?

6. How will we identify and prepare permanent leadership to take over?

7. What is the communication plan for the organization during the interim period?

As outlined in What to Ask Fractional CTO Before Signing Retainer, asking the right questions upfront prevents misalignment and ensures successful engagement.

Conclusion: Making the Right Choice for Your Organization

The fractional vs interim CTO decision is not binary—it's contextual. The right choice depends on your organization's stage, challenges, team maturity, and strategic priorities. Ultimately, a pragmatic fractional vs interim CTO decision balances urgency, budget, and the ability of your team to absorb change.

Fractional CTOs are ideal for organizations that need consistent, long-term strategic guidance from experienced technical leadership. They're cost-effective, flexible, and build sustainable capability. Fractional engagement works best when your organization is stable but growing, and you have internal leadership to execute on guidance.

Interim CTOs are ideal for organizations facing urgent, bounded challenges that require full-time, intensive leadership. They're effective for crisis stabilization, major launches, and leadership transitions. Interim engagement works best when you have a clear end-state and a plan for permanent leadership transition.

Many organizations use both models at different times or in parallel, depending on their evolving needs. The key is clarity about what you need, clear governance and scope, and intentional transition planning.

Padiso specializes in both fractional and interim CTO engagements, with deep expertise in AI-native development, autonomous agents, embedded analytics, and security audits (SOC 2 / ISO 27001). Whether you need ongoing strategic advisory or intensive crisis leadership, Padiso can help you evaluate which model fits your organization and deliver results.

Ready to explore fractional or interim CTO options for your organization? Contact Padiso to discuss your needs and find the right leadership model for your technology challenges.

As you evaluate your options, also consider reading When to Hire Fractional CTO vs Full Time CTO and CTO as a Service vs Full Time CTO: Making the Right Choice for Your Business for additional perspective on technology leadership options. Additionally, Fractional CTO vs Interim CTO: Which Do You Need in the US provides independent industry perspective on these models.

For organizations exploring whether a fractional CTO is right for their size, When Is a Business Too Small or Too Big for a Fractional CTO offers practical guidance on fit and stage. And if you're building an engineering team, Building Engineering Team Fractional CTO details how fractional leadership accelerates team development.

The choice between fractional and interim CTO is ultimately about matching your organization's needs with the right leadership model. With clarity, preparation, and the right partner, either model can drive significant value and accelerate your technology transformation.

This article breaks down the real differences between seed and Series A, moving beyond superficial funding metrics to examine the operational, strategic, and technical transformations that must occur. Whether you're a CTO at a government agency evaluating an AI vendor, an enterprise technology leader building internal platforms, or a founder preparing for Series A, this guide will help you understand what's truly at stake.

The Funding Landscape: Size, Structure, and Investor Profile

Seed Funding: Proving the Concept

Seed funding typically ranges from $500K to $2M, though in AI-driven startups, seed rounds have inflated to $3–5M in competitive markets. According to CRV's analysis of seed funding versus Series A, seed investors are primarily angels, early-stage venture firms, accelerators, and sometimes founder networks (friends and family). These investors are betting on you—the founding team—and the problem you're solving, not necessarily on a proven market or revenue traction.

Seed funding is designed to answer one fundamental question: Does the market want this? You're building a prototype, validating assumptions, and proving that customers will pay (or at least engage meaningfully). The capital is meant to last 12–18 months, giving you runway to iterate, test channels, and gather early customer feedback.

At the seed stage, your technology stack is often scrappy. You might be using off-the-shelf tools, monolithic architectures, or even no-code solutions. The goal is speed and learning, not scalability or enterprise-grade compliance. This is the phase where many founders are still asking: "Should we build this in-house, or should we use existing platforms?"

Series A Funding: Scaling the Proven Model

Series A funding typically ranges from $2M to $15M, with AI-native startups often raising $10–25M in 2024–2025. Series A investors are institutional venture capital firms with deep sector expertise, board seats, and multi-year investment horizons. These are firms like Sequoia, Accel, Andreessen Horowitz, or industry-focused funds.

Series A investors are not betting on the team alone—they're betting on product-market fit (PMF). By the time you raise Series A, you need to demonstrate:

• Customer traction: Paying customers, or at minimum, strong product engagement and clear path to revenue

• Repeatable unit economics: Evidence that your go-to-market motion can scale

• Market validation: Proof that the problem is real and the market is addressable

• Competitive differentiation: Why you'll win, not just why the problem matters

Series A capital is meant to scale what works. You're hiring aggressively (often tripling your team), entering new markets, building enterprise-grade infrastructure, and preparing for the next growth phase. As Hustle Fund explains in their comparison of pre-seed, seed, and Series A, the Series A stage is fundamentally about proving you can execute at scale, not just prove the concept.

Governance, Control, and Decision-Making Authority

Photo by Austin Distel on Unsplash

Seed Stage: Founder Autonomy

At seed stage, you retain significant autonomy. Yes, you have investors, but they're typically hands-off or supportive rather than directive. Board meetings might be quarterly or semi-annual. Decisions about product direction, hiring, technology choices, and go-to-market strategy rest primarily with you and your co-founders.

This autonomy is a double-edged sword. It enables rapid iteration and bold pivots, but it also means you're fully accountable for every decision. There's no institutional safety net telling you to slow down or be more cautious. Seed investors expect you to move fast and break things—within reason.

Series A: Institutional Governance

Series A fundamentally changes governance. Your Series A investor typically gets a board seat. They participate in quarterly board meetings with detailed metrics reviews. They have information rights, anti-dilution provisions, and sometimes protective provisions (the ability to block certain decisions like hiring a new CEO, raising debt, or selling the company).

This shift from founder autonomy to shared governance is profound. You now have a fiduciary obligation to your investors to maximize their returns. This changes decision-making calculus: you can't just pivot on a whim anymore. Major strategic decisions require board alignment. Hiring becomes subject to budget scrutiny. Technology choices must be defensible to institutional investors who understand risk and compliance.

For CTOs specifically, this means your technology strategy now has to be communicated and aligned with board-level stakeholders. Decisions about architecture, infrastructure, and security posture are no longer purely technical—they're business decisions that affect investor confidence and company valuation.

Technology Architecture and Infrastructure

Photo by Christina @ wocintechchat.com M on Unsplash

Seed Stage: Iterate Fast, Scale Later

At seed stage, your technology choices should prioritize speed and learning over scalability. Many successful seed-stage startups use:

• Monolithic architectures or simple microservices (not over-engineered)

• Off-the-shelf platforms for non-differentiating functions (authentication, payments, analytics)

• Managed services over self-hosted infrastructure (AWS Lambda, Stripe, Supabase, etc.)

• Single-region deployment with basic disaster recovery

• Manual processes for deployment, monitoring, and incident response

The reason is simple: you're still learning what customers want. Investing heavily in scalable architecture before you have product-market fit is premature optimization. Your goal is to get something in front of customers quickly and iterate based on feedback.

At seed stage, you might not even have embedded analytics or sophisticated monitoring. You're probably using basic dashboards and direct customer conversations to understand usage patterns. Security is important, but enterprise-grade SOC 2 compliance might not be a priority yet—your customers are early adopters who understand the risk.

Series A: Build for Scale and Enterprise Requirements

Once you've raised Series A and proven product-market fit, your technology strategy must shift. You're now building for:

• Scalability: Your current architecture needs to support 10x growth without major rewrites

• Reliability: 99.5% uptime SLAs become table stakes; customers are now paying significant money and expecting enterprise-grade reliability

• Security and compliance: If you're selling to enterprises or government agencies, SOC 2 Type II certification becomes essential. Understanding what SOC 2 and ISO 27001 audits entail is critical for Series A startups targeting enterprise buyers

• Embedded analytics and observability: You need sophisticated monitoring, logging, and analytics to understand system behavior at scale

• Multi-region deployment: Enterprise customers often require data residency and geographic redundancy

• API-first architecture: You're now integrating with enterprise systems, not just standalone applications

This is the phase where building scalable AI platforms with proper platform engineering becomes critical. If you're an AI-native startup, you need to think about how your models will be served at scale, how you'll handle model versioning and monitoring, and how you'll ensure compliance with enterprise governance requirements.

Many Series A startups also adopt embedded analytics solutions like Apache Superset combined with ClickHouse to provide customers with real-time insights into their data. This requires a different infrastructure approach than seed-stage analytics.

Hiring, Organizational Structure, and Talent Strategy

Photo by Deng Xiang on Unsplash

Seed Stage: Hire Generalists, Move Fast

At seed stage, you typically have a small team—maybe 5–15 people. Your engineering team is lean and generalist. You hire people who can wear multiple hats: full-stack engineers who can build frontend, backend, and DevOps; product people who can also do user research; marketers who can also do sales.

Your hiring criteria emphasize:

• Adaptability: Can they handle ambiguity and change direction quickly?

• Ownership: Do they take initiative without waiting for permission?

• Technical depth in one area: You need some specialization, but generalist capability is more valuable

• Startup experience: Prior experience in high-uncertainty environments is a plus

Compensation is typically lower than Series A, but equity is a larger percentage of total comp. You're asking people to take a risk on an unproven company in exchange for potentially significant upside.

Series A: Build Specialized Teams and Infrastructure

Series A hiring is fundamentally different. You're likely tripling your team from 15 to 45+ people. You now need:

• Specialized engineers: ML engineers, infrastructure engineers, security engineers, data engineers

• Product managers: Dedicated PMs for each product area or customer segment

• Sales and customer success teams: You can't scale revenue with founder-led sales anymore

• Finance and operations: CFO, controller, HR, legal

• Customer success and support: Dedicated teams to ensure customers succeed (and renew)

Your hiring criteria shift toward:

• Specialized expertise: You need people who have solved these problems before at scale

• Leadership capability: As you grow, you need people who can build and lead teams

• Enterprise experience: If you're selling to enterprises, you need people who understand enterprise buying, implementation, and support

• Compliance and security mindset: Especially important if you're targeting regulated industries

Compensation also increases significantly. Series A startups typically offer 50–70% of FAANG salaries (depending on market and role), plus meaningful equity. You're now competing with established companies for talent in ways you weren't at seed stage.

For CTOs specifically, this is the phase where you might bring in a fractional CTO or program leadership to help scale your technology organization if your founding CTO doesn't have experience managing large engineering teams or enterprise sales cycles. Many Series A startups benefit from understanding what a fractional CTO actually does in the first 90 days to accelerate organizational build-out.

Go-to-Market Strategy and Sales Motion

Seed Stage: Product-Led or Founder-Led Sales

At seed stage, your go-to-market motion is typically one of:

• Product-led growth (PLG): Customers self-serve, sign up, and use the product without talking to sales

• Founder-led sales: You (the founder) are doing most of the selling, often to personal networks or warm introductions

• Land-and-expand: Get in with a small initial use case, then expand within the customer

Your target customers are typically early adopters: startups, innovative teams within larger organizations, or forward-thinking smaller companies. You're not yet selling to enterprise procurement teams or government agencies. Your sales cycle is measured in weeks, not months.

Marketing at seed stage is often organic: content, community, word-of-mouth, and maybe some paid acquisition if you have clear unit economics.

Series A: Enterprise Sales and Multi-Channel Go-to-Market

Once you've raised Series A, your go-to-market strategy must evolve to support faster growth. This typically means:

• Building a sales team: You hire a VP of Sales and start building an enterprise sales motion

• Longer sales cycles: Enterprise customers need to evaluate security, compliance, integration, and ROI—this takes 3–6 months

• Sales enablement: You need tools, processes, and training to help your sales team close deals

• Channel partnerships: You might work with resellers, integrators, or consulting firms to reach new markets

• Customer success infrastructure: You need dedicated teams to ensure customers succeed, reduce churn, and expand accounts

This is also the phase where you might start targeting government agencies and regulated industries. These customers have strict requirements around security, compliance, and data residency. Understanding how to structure engagements for government and enterprise buyers becomes critical.

Compliance, Security, and Risk Management

Seed Stage: Security Basics, Minimal Compliance

At seed stage, security is important, but it's not your primary focus. You're likely implementing:

• Basic authentication and authorization: Password management, two-factor authentication

• Encrypted data in transit and at rest: Standard HTTPS and database encryption

• Basic access controls: Role-based access, principle of least privilege

• Incident response procedures: Basic runbooks for common security incidents

Compliance is minimal. You might have a privacy policy and terms of service, but you're not pursuing SOC 2 certification or conducting formal security audits. Your customers are early adopters who accept higher risk in exchange for innovation.

Series A: Enterprise-Grade Security and Compliance

Series A is where security and compliance become non-negotiable. If you're selling to enterprises or government agencies, you need:

• SOC 2 Type II certification: This requires 6+ months of audit evidence, so you need to start immediately

• ISO 27001 certification: Increasingly required for enterprise and government sales

• Data residency and sovereignty: Ability to keep customer data in specific geographic regions

• Audit logging and monitoring: Comprehensive logging of all access and changes

• Incident response and breach notification: Formal procedures and legal compliance

• Vendor risk management: Assessment of your own vendors and third-party dependencies

This is not a nice-to-have; it's a blocker for enterprise deals. Many Series A startups find that 20–30% of their Series A capital goes toward building out security and compliance infrastructure. Understanding the full scope of SOC 2 and ISO 27001 requirements is essential for Series A CTOs.

If you're building AI products, you also need to think about AI governance, model monitoring, and explainability—especially if you're selling to regulated industries or government agencies.

Metrics, KPIs, and Investor Reporting

Seed Stage: Learning and Validation Metrics

At seed stage, your metrics focus on learning and validation:

• Customer acquisition cost (CAC): How much does it cost to acquire a customer?

• Retention and churn: Are customers sticking around? Are they renewing?

• Product engagement: Are customers actually using the product?

• Net Promoter Score (NPS): Are customers happy enough to recommend you?

• Revenue or ARR: If you're monetized, what's your annual recurring revenue?

These metrics help you understand whether you have product-market fit. You're looking for signals that customers want what you're building. Investor reporting might be quarterly, but it's relatively lightweight—a few slides showing progress toward key milestones.

Series A: Investor-Grade Metrics and Financial Reporting

Series A completely changes your metrics and reporting rigor. You now need:

• Monthly recurring revenue (MRR) and annual recurring revenue (ARR): Tracked precisely with cohort analysis

• Customer acquisition cost (CAC) and lifetime value (LTV): Detailed unit economics by customer segment

• Magic number: (Quarter revenue growth ÷ prior quarter sales and marketing spend) to assess go-to-market efficiency

• Churn rate: Both logo churn (% of customers lost) and revenue churn (net revenue retention)

• Burn rate and runway: Monthly cash burn and how many months of runway you have

• Headcount and hiring plan: Detailed org structure and hiring roadmap

You'll also need formal financial statements, board packages, and quarterly investor updates. Many Series A startups hire a CFO or finance person to manage this rigor. Your board will scrutinize these metrics monthly, and they'll inform strategic decisions about hiring, spending, and go-to-market investment.

Technology Debt and Technical Decisions

Seed Stage: Accept Technical Debt for Speed

At seed stage, you should actively embrace technical debt if it gets you to market faster. This means:

• Choosing speed over elegance: Using frameworks and libraries that get you to market quickly, even if they're not perfect

• Minimal documentation: Your team is small enough that knowledge sharing is verbal

• Scripted deployments: Manual processes that work but aren't fully automated

• Single database: Monolithic data storage rather than complex distributed systems

• Minimal testing: Focused testing on critical paths, not comprehensive test coverage

The rationale is simple: at seed stage, the biggest risk is not learning what customers want. Technical debt is acceptable as long as it doesn't prevent you from learning or iterating quickly.

Series A: Begin Paying Down Technical Debt

Once you've raised Series A, you need to start paying down technical debt systematically. This means:

• Investing in testing and CI/CD: Automated testing, continuous integration, and deployment pipelines

• Documentation: Formal documentation of architecture, APIs, and operational procedures

• Monitoring and observability: Comprehensive logging, metrics, and alerting

• Refactoring: Allocating engineering time to improve code quality and reduce complexity

• Infrastructure automation: Infrastructure-as-code, configuration management, and automated deployment

You typically allocate 20–30% of engineering effort to technical debt paydown in Series A. This is the phase where you might also adopt AI-native development practices if you're building AI products, ensuring your development process is optimized for rapid iteration with AI models.

The Role of External Expertise and Advisory

Seed Stage: Occasional Advisory

At seed stage, many founders rely on informal advisory networks: mentors, other founders, and angel investors who provide occasional guidance. You might hire a fractional CFO to help with financial modeling, but you're primarily self-sufficient.

Series A: Structured Advisory and Leadership

Series A is where many startups bring in external expertise systematically. This might include:

• Fractional CFO or controller: To manage financial planning and reporting

• General counsel or outside counsel: To handle legal, compliance, and contracts

• VP of Sales or sales consultant: To build out enterprise sales motion

• CTO or engineering advisor: To help scale the engineering organization and navigate enterprise requirements

Many Series A startups benefit from understanding the role of a fractional CTO in scaling technical organizations. A fractional CTO can help you navigate enterprise sales requirements, build SOC 2 compliance, and scale your engineering team without the cost of a full-time executive. Learning what to look for when hiring a fractional CTO is increasingly important for Series A startups targeting enterprise and government customers.

If you're building AI products, you might also consider working with a venture studio or co-build partner to accelerate product development and navigate enterprise AI requirements. Understanding the difference between building vs buying autonomous agents becomes a critical Series A decision if you're in the AI space.

Customer Profile and Market Positioning

Seed Stage: Early Adopters and Innovators

Your seed-stage customers are typically:

• Startups and scaleups: Companies that are also taking risks and moving fast

• Innovative teams within larger organizations: Forward-thinking departments willing to try new solutions

• Smaller companies: Typically under $100M in revenue, willing to work with immature vendors

• Price-sensitive: They're looking for value, but they're not willing to pay enterprise prices

These customers accept that your product is evolving, your support might be limited, and you might pivot. They're willing to work closely with you to shape the product.

Series A: Enterprise and Government Focus

Once you've raised Series A, your customer profile typically shifts upmarket:

• Mid-market and enterprise: Companies with $100M+ in revenue, formal procurement processes

• Government agencies: Federal, state, and local government, with strict compliance and security requirements

• Regulated industries: Financial services, healthcare, energy, defense—where compliance is non-negotiable

• Price-insensitive (relatively): These customers are willing to pay for reliability, security, and support

These customers have different expectations:

• Formal contracts and legal review: Not simple terms of service

• Security and compliance audits: They'll audit your systems and processes

• SLAs and support: They expect 24/7 support and guaranteed uptime

• Integration and customization: They need to integrate with existing systems

• Multi-year commitments: They want stability and long-term partnerships

This shift in customer profile is profound. It changes everything about how you operate: your sales process, your support model, your product roadmap, and your technology infrastructure.

The Verdict: What Actually Changes

For Founders

If you're a founder navigating the seed-to-Series A transition, here's what you need to understand:

Autonomy decreases, but resources increase. You'll have less freedom to pivot on a whim, but you'll have significantly more capital and talent to execute your vision. This trade-off is generally worth it if you've truly found product-market fit.

Complexity increases dramatically. You're no longer just building a product; you're building a company. You need financial discipline, compliance rigor, and formal processes. Many founders struggle with this transition because it feels bureaucratic, but it's essential for scaling.

Your role changes. If you were doing product, sales, and support at seed stage, Series A requires you to focus. Most successful Series A founders focus on product and strategy, hiring specialists for everything else.

Enterprise and government customers become viable. Series A is when you can realistically target large enterprises and government agencies. These are high-value customers, but they require investment in security, compliance, and support.

For Enterprise CTOs and Technology Leaders

If you're evaluating a Series A startup as a potential vendor or partner:

Series A is a maturity inflection point. A Series A startup has proven product-market fit and has invested in the infrastructure to support enterprise customers. This is fundamentally different from a seed-stage startup.

Look for security and compliance investment. A well-run Series A startup will have SOC 2 on the roadmap (or achieved). They'll have formal security and compliance processes. If they don't, that's a red flag.

Evaluate their technical depth. Series A startups should have specialized engineers (ML, infrastructure, security). If they're still relying on generalists, they're not ready for enterprise scale.

Assess their go-to-market maturity. Do they have a sales team? Customer success? Or are they still doing founder-led sales? Series A startups should have formal sales and CS processes.

Consider bringing in advisory support. If you're evaluating a Series A startup for a critical use case, working with a fractional CTO or technical advisor can help you assess technical risk and ensure the vendor can scale with your needs.

For Government and Regulated Industry Buyers

If you're a government agency or work in a regulated industry:

Series A is the earliest you should consider a startup vendor. Seed-stage startups are too risky for mission-critical systems or regulated use cases. Series A startups have invested in compliance and security, making them viable partners.

Require SOC 2 Type II certification. Don't accept promises of future compliance. If they don't have SOC 2, they're not ready.

Evaluate their ability to meet data residency requirements. Government customers often require data to stay in the US (or specific regions). Series A startups should be able to support this.

Consider multi-region deployment and disaster recovery. Government systems need redundancy and failover capabilities. Evaluate whether the vendor can support this.

Engage a technical advisor early. Working with a fractional CTO or program leadership can help you navigate vendor selection, implementation, and ongoing governance for startup partners.

Conclusion: The Inflection Point

The transition from seed to Series A is not just a funding milestone—it's a fundamental shift in how a startup operates. The capital increases, the team grows, the customers change, and the complexity multiplies. For some founders, this transition is exciting and energizing. For others, it feels like losing the scrappy, autonomous culture that made the seed stage fun.

The reality is both: Series A requires more discipline, more process, and more complexity. But it also enables you to build something truly meaningful at scale. You can hire the best engineers, invest in enterprise-grade infrastructure, and serve customers who have real, mission-critical problems.

For enterprise CTOs and government leaders, understanding this transition helps you evaluate startup vendors and partners more effectively. A Series A startup is fundamentally different from a seed-stage startup. They've invested in compliance, security, and scalability. They've proven product-market fit. They're ready to be a serious partner.

The key is knowing what to look for: security and compliance investment, technical depth, go-to-market maturity, and the ability to scale with your needs. If you're considering a startup for a critical use case, engaging a technical advisor or fractional CTO can help you navigate the evaluation and ensure you're making a sound decision.

Seed versus Series A is not just about funding—it's about maturity, capability, and readiness to scale. Understanding that difference is essential for everyone involved in the startup ecosystem.

If you're running a marketing agency, freelancing as a growth marketer, or leading a marketing team, you're facing a challenge: how do you stay competitive when your clients are asking about AI visibility, but you don't have the tools to track it? How do you justify your fees when traditional SEO platforms don't capture the full picture of where your clients are actually being discovered?

This is where SearchFIT changes the game. SearchFIT is an automated Answer Engine Optimization platform that tracks brand visibility and recommendations across multiple AI assistants in real-time. Unlike traditional SEO tools, SearchFIT gives you visibility into how AI systems are recommending your clients' brands, products, and services—and it provides the data and optimization strategies you need to win more AI recommendations.

In this comprehensive guide, we'll walk you through 12 actionable strategies to grow your marketing business using SearchFIT. Whether you're looking to win new clients, deliver measurable ROI, automate your workflows, or scale your operations, these tactics will help you leverage AEO as a competitive advantage.

1. Position AEO as a New Service Line to Win Premium Clients

The first step to growing your business with SearchFIT is recognizing that Answer Engine Optimization is a distinct, high-value service that commands premium pricing. Most agencies are still selling traditional SEO, which has become commoditized. AEO is different—it's newer, more technical, and directly addresses a gap that clients didn't even know they had.

When you audit your current client base using SearchFIT, you'll likely discover something shocking: many of your clients have zero visibility across ChatGPT, Perplexity, Gemini, and other AI assistants. Their competitors might already be getting recommended. This creates an immediate opportunity.

Start by running a free AEO audit for 5–10 prospective clients in your target verticals. Use SearchFIT to pull their current AI visibility metrics across all major platforms. Show them how often their brand is mentioned, which AI assistants are recommending competitors, and what content gaps exist. This audit becomes a powerful sales tool—suddenly, you're not just talking about SEO rankings; you're showing them a completely untapped channel where they could be winning business.

Position AEO as a premium add-on service for existing clients or as the anchor offering in a new "AI-First Growth" package. According to McKinsey's research on growth strategy, businesses that adopt new channels early capture disproportionate market share. AEO is that channel right now.

In your sales conversations, reference how a B2B SaaS company tripled AI recommendations across ChatGPT, Perplexity, and Gemini using a structured AEO approach. This social proof is invaluable when closing deals.

2. Use SearchFIT's Real-Time Dashboards to Deliver Transparent Client Reporting

Photo by Dylan Gillis on Unsplash

One of the biggest pain points for agencies is client reporting. Clients want to see ROI, but traditional reports are often delayed, generic, and don't clearly connect activity to business outcomes. SearchFIT solves this by providing real-time dashboards that show exactly what's happening across AI assistants.

Instead of waiting for monthly reports, your clients can log into SearchFIT and see live data on their AI visibility. How many times has ChatGPT recommended them this week? What's their citation trend on Perplexity? Which of their pages are getting pulled into Gemini responses? This transparency builds trust and justifies your fees.

Set up SearchFIT dashboard templates for agency client reporting on AI visibility tailored to each client segment. For e-commerce brands, emphasize product recommendation rates. For B2B SaaS, highlight thought-leadership citations and lead-generation opportunities. For agencies themselves, focus on competitive win rates.

When you hand off a dashboard to a client, you're giving them a window into a marketing channel they never had visibility into before. Suddenly, your work becomes tangible and measurable. This transforms your value proposition from "we're doing SEO work" to "we're driving measurable AI visibility and recommendations that generate qualified traffic."

Include a custom dashboard section that tracks 7 essential AEO KPIs that directly impact client retention. These KPIs—citation growth, recommendation frequency, competitive share-of-voice, and conversion attribution—become the metrics you use in every client conversation.

3. Implement SearchFIT's Competitor Monitoring to Upsell Competitive Intelligence

Photo by Carlos Muza on Unsplash

Competitor monitoring is a high-margin service that agencies can offer at a premium. With SearchFIT, you're not just tracking where competitors rank on Google; you're tracking where they're getting recommended by AI assistants. This is a completely different—and often more valuable—data set.

Use SearchFIT to monitor competitor mentions across ChatGPT, Perplexity, Gemini, and other AI assistants in real-time. Set up alerts so you and your clients know immediately when a competitor appears in a high-value AI recommendation or when a new competitive threat emerges.

This competitive intelligence becomes a standalone service you can sell. Imagine telling a prospect: "We'll monitor your competitors' AI visibility across six different AI assistants and alert you weekly when they gain new recommendations or lose ground. We'll also show you the exact content they're using to win those recommendations so you can optimize faster."

This is something traditional SEO tools don't offer. Semrush, Ahrefs, and Moz can track search rankings, but they don't track AI assistant recommendations. By offering this through SearchFIT, you're providing unique value that competitors can't easily replicate.

Bundle this as a "Competitive AEO Monitoring" add-on for $500–$1,500/month per client, depending on your market and the number of competitors you're tracking. For agencies in competitive verticals (SaaS, e-commerce, financial services), this is an easy upsell.

4. Leverage SearchFIT's AI-Optimized Content Generation to Scale Production

Photo by Microsoft 365 on Unsplash

Content is the fuel of AEO, but creating AI-optimized content at scale is challenging. SearchFIT includes AI-optimized content generation capabilities that help you produce content specifically designed to be recommended by AI assistants. This is different from SEO-optimized content—it's written to answer the types of questions that trigger AI recommendations.

Use SearchFIT's content generation tools to analyze what types of content your clients' competitors are using to win AI recommendations. Are they using structured Q&A formats? Comprehensive guides? Data-driven research? Once you identify the pattern, you can generate similar content for your clients at scale.

This capability lets you offer a "Content for AEO" service that's faster and more cost-effective than hiring freelance writers. You can produce 4–8 optimized pieces per week per client, which compounds into significant AI visibility gains over time.

For clients who already have existing content, use SearchFIT to audit and optimize it for AI visibility. The platform will show you which content is currently getting pulled into AI responses and which content has gaps. This optimization work becomes a retainer service that justifies ongoing monthly fees.

When you combine content generation with real-time tracking of how that content performs across ChatGPT, Gemini, and Perplexity, you create a feedback loop. Clients see exactly which pieces of content you created are driving AI recommendations. This accountability is powerful for retention.

5. Set Up SearchFIT Real-Time Alerts for Competitive Wins and Losses

Proactive monitoring is what separates great agencies from mediocre ones. Use SearchFIT's real-time alert system to set up alerts for competitor AI recommendations and your own clients' wins and losses.

When a competitor gets a major AI recommendation, you'll know immediately. This allows you to react quickly—either by optimizing your own content to compete or by identifying a new opportunity to pitch to a prospect. When your client gets a new recommendation, you'll know immediately and can celebrate the win and use it in your reporting.

Set up alerts for specific keywords, competitor brands, and industry trends. The goal is to be the first person in the room who understands what's happening in the AI visibility landscape. This makes you invaluable to your clients and gives you a competitive edge in sales conversations.

For agencies serving multiple clients in the same vertical, competitive alerts become a source of ongoing strategic insights. You can identify industry trends before they're obvious and position your clients ahead of the curve.

6. Integrate SearchFIT with Your Existing Tech Stack (Shopify, WordPress, CRM)

One of the biggest barriers to adoption is friction. If SearchFIT requires your team to log into yet another platform, adoption suffers. That's why SearchFIT offers integrations with the tools your clients already use.

For e-commerce clients, integrate SearchFIT with Shopify to see how product recommendations are flowing through AI assistants. For content-heavy clients, integrate with WordPress to track content performance directly from your publishing workflow. For agencies managing multiple clients, integrate with your CRM or project management tool so that AEO data flows into your existing systems.

These integrations reduce friction and make AEO a natural part of your existing workflow rather than an add-on. When your team is already in Shopify or WordPress, having AI visibility data right there makes optimization decisions faster and easier.

Set up these integrations during onboarding so your clients experience SearchFIT as an extension of their existing tools, not a separate platform. This dramatically improves adoption and stickiness.

7. Master the AEO Onboarding Process to Reduce Time-to-Value

The faster your clients see value from SearchFIT, the faster they'll become advocates and the less likely they'll churn. This means perfecting your onboarding process.

Create a structured onboarding workflow that takes clients from zero to generating their first AI recommendations in 14 days. Start with a competitive audit using SearchFIT to establish a baseline. Then, identify the top 3–5 keywords where AI visibility would have the highest business impact. Finally, create and optimize content for those keywords using SearchFIT's recommendations.

Reference the ultimate guide to Answer Engine Optimization for agencies as your playbook. This guide covers the full AEO strategy from research through optimization to measurement. Use it as your internal training material and as a client-facing resource.

Create an AEO launch checklist for product and marketing teams that you can hand off to clients. This checklist ensures nothing falls through the cracks and gives clients a clear sense of progress as they move through the onboarding process.

The faster clients see their first AI recommendation, the more confident they become in the channel and the more willing they are to invest in scaling it.

8. Build AEO Playbooks for In-House Teams and Resellers

As your agency grows, you'll want to scale beyond just direct client work. One way to do this is by creating AEO playbooks that in-house teams can use to manage their own AI visibility. You can sell these playbooks as standalone products or bundle them with SearchFIT access.

A playbook should include:

• A step-by-step guide to conducting an AEO audit using SearchFIT

• Templates for identifying high-impact AI visibility opportunities

• Content optimization checklists specific to each AI assistant

• Measurement frameworks and KPI definitions

• Monthly review processes and optimization cycles

• Troubleshooting guides for common AEO challenges

Reference the guide to creating AEO playbooks with SearchFIT for in-house SEO teams as your template. This resource walks through the exact structure and content that works best.

You can package these playbooks as a $2,000–$5,000 one-time product sold to companies that want to manage AEO internally but need guidance. Alternatively, bundle them with a lite version of SearchFIT access as a lower-price-point offering for smaller companies that can't afford full agency services.

This creates a new revenue stream that scales without requiring your team's time on every engagement.

9. Measure and Report AEO ROI to Justify Ongoing Investment

Clients care about one thing above all else: ROI. If you can't connect AEO activity to business outcomes (traffic, leads, revenue), clients will eventually cut the budget. This is why measuring and reporting ROI is critical.

Use SearchFIT to track not just AI visibility metrics but also the business outcomes that result from those recommendations. How many clicks are coming from ChatGPT recommendations? How many of those clicks convert to leads? What's the revenue impact?

For B2B SaaS clients, reference the guide to measuring ROI from AEO using SearchFIT. This guide walks through the exact methodology for connecting AI visibility to pipeline and revenue.

For e-commerce clients, focus on metrics like attributed sales, average order value, and customer acquisition cost from AI recommendations. For content-heavy clients, focus on traffic, engagement, and lead generation.

Create a monthly ROI report template that shows:

• AI visibility metrics (citations, recommendations, share-of-voice)

• Traffic attributed to AI recommendations

• Conversion rate from AI traffic

• Revenue attributed to AI recommendations

• Cost per acquisition via AI recommendations vs. other channels

• Month-over-month and year-over-year trends

When clients see that their AEO investment is generating measurable revenue, they don't just renew—they expand. They ask for more budget and more optimization.

10. Use SearchFIT to Identify and Pitch AEO Opportunities to Prospects

SearchFIT isn't just a tool for existing clients; it's a powerful sales tool for winning new business. Before you pitch a prospect, run an AEO audit using SearchFIT to see exactly where they're losing to competitors in the AI visibility space.

Show the prospect:

• Their current AI visibility across ChatGPT, Perplexity, Gemini, Grok, and Claude

• How often competitors are being recommended vs. them

• Which keywords are driving AI recommendations for competitors

• The content gaps that are costing them visibility

• A conservative estimate of the traffic and revenue they're leaving on the table

This audit becomes your discovery meeting. You're not asking the prospect to believe you; you're showing them data that proves the opportunity exists.

When you combine this with case studies showing how other companies increased AI recommendations 3x, you have a compelling sales narrative. The prospect can see themselves in the case study and understand exactly how you'll help them achieve similar results.

Price this audit service at $500–$1,000 depending on your market. Some prospects will buy the audit and hire you to implement the recommendations. Others will implement it themselves, which is fine—you've still built a relationship and demonstrated value.

11. Create Tiered Service Packages Aligned with SearchFIT Features and Pricing

Not every client needs the same level of AEO service. By creating tiered packages aligned with SearchFIT's capabilities, you can serve a broader market and capture more revenue.

Consider a three-tier structure:

Tier 1: AEO Essentials ($1,500–$2,500/month)

• AI visibility tracking across 3 major platforms (ChatGPT, Perplexity, Gemini)

• Monthly AEO audit and optimization recommendations

• Competitor monitoring for top 3 competitors

• Monthly reporting and strategy call

• Best for: Smaller companies, startups, and agencies testing AEO

Tier 2: AEO Growth ($3,500–$5,500/month)

• AI visibility tracking across all 6 platforms (ChatGPT, Perplexity, Gemini, Grok, Claude, Google)

• Bi-weekly optimization cycles with AI-generated content

• Competitor monitoring for top 5 competitors with real-time alerts

• Weekly reporting and strategy calls

• Custom dashboard and KPI tracking

• Best for: Mid-market companies, growth-stage SaaS, and established e-commerce brands

Tier 3: AEO Enterprise ($7,500–$15,000+/month)

• Everything in Tier 2, plus:

• Dedicated AEO strategist and content team

• Custom content creation (8–12 pieces/month)

• Advanced competitor intelligence and market research

• Integration with CRM and marketing automation tools

• Quarterly business reviews and strategic planning

• Best for: Enterprise companies, competitive verticals, and high-revenue clients

Each tier maps directly to SearchFIT's capabilities, so you can clearly explain what clients get at each level. This also makes it easy to upsell clients as they grow—they simply move up a tier.

12. Build a 30/90-Day Growth Plan for New Clients and Your Own Business

Structured planning is what separates agencies that grow from agencies that stagnate. Create a 30/90-day growth plan template that you use with every new client and that you apply to your own business.

30-Day Plan (Foundation Phase):

• Week 1: Complete AEO audit using SearchFIT; identify top 10 keywords with AI visibility potential

• Week 2: Analyze competitor content; identify content gaps and optimization opportunities

• Week 3: Create and publish 4 AI-optimized pieces of content

• Week 4: Measure initial AI visibility changes; refine strategy based on data

• Deliverable: First month of AI visibility data showing baseline and initial gains

90-Day Plan (Acceleration Phase):

• Month 2: Expand to 8–12 optimized pieces of content; implement technical SEO improvements; begin link-building for top-priority content

• Month 3: Launch advanced optimization cycles; begin testing different content formats; scale what's working

• Deliverable: 30–50% increase in AI visibility; first attributed traffic and leads from AI recommendations

This structure gives clients a clear roadmap and sets expectations. It also creates natural checkpoints where you can upsell additional services or move clients to higher-tier packages based on results.

For your own business, apply the same framework. In the first 30 days, focus on launching SearchFIT as a service, onboarding your first 3–5 clients, and creating case studies. In the first 90 days, focus on scaling to 10–15 active clients, refining your playbooks based on real results, and building a sales pipeline for the next quarter.

Conclusion: The AEO Opportunity is Now

Answer Engine Optimization is no longer a "nice to have" or a "future opportunity." It's happening now. AI assistants are actively recommending brands, products, and services to millions of users every day. Companies that optimize for AI visibility are capturing market share from companies that don't.

As a marketing agency owner, freelancer, or growth leader, you have a choice: you can continue operating with traditional SEO tools and hope clients don't notice the gap, or you can embrace AEO and become the expert your market needs.

SearchFIT gives you the platform to do this. It provides real-time visibility into where your clients are being recommended by AI assistants, the tools to optimize that visibility, and the data to prove ROI. More importantly, it gives you a competitive advantage in your market. While your competitors are still talking about Google rankings, you'll be talking about ChatGPT recommendations, Perplexity citations, and Gemini visibility.

Start by running AEO audits for your top 5 prospects using SearchFIT. Show them the opportunity. Then, implement the 12 strategies in this guide: position AEO as a premium service, use real-time dashboards for transparent reporting, monitor competitors, generate AI-optimized content, set up alerts, integrate with existing tools, perfect your onboarding, create playbooks, measure ROI, use SearchFIT as a sales tool, build tiered packages, and execute a structured growth plan.

The agencies and consultants who move first will capture the most market share. Those who wait will find themselves explaining to prospects why they didn't invest in AEO sooner. The time to grow your business with SearchFIT is now.

For more specific tactics and strategies, explore how to optimize for answer engines with SearchFIT, review the comprehensive AEO FAQ covering 25 essential questions, and dive into everything you need to know about AI visibility platforms. These resources will deepen your understanding and accelerate your success.

Your growth starts today.

For enterprises and government agencies, the fractional CTO engagement is particularly valuable during periods of digital transformation, AI integration, or when you need specialized expertise in areas like embedded analytics, autonomous agents, or security compliance. Organizations like yours often face the challenge of finding senior technical leadership that can move quickly while maintaining compliance standards such as SOC 2 and ISO 27001. The fractional model allows you to access this expertise without the long-term commitment or the complexity of building an entire C-suite.

Understanding when to hire a fractional CTO versus a full-time CTO is essential before you begin your search. Many enterprises discover that a fractional engagement during a specific transformation initiative or technology buildout phase delivers faster results and lower risk than hiring a permanent executive. The key is recognizing that fractional CTOs excel in outcomes-driven, time-bound engagements where you need strategic direction combined with hands-on delivery capability.

Step 1: Define Your Business Outcomes and Technical Needs

Photo by Christina @ wocintechchat.com M on Unsplash

The first and most critical step in hiring a fractional CTO is crystallizing what you actually need. This isn't about job descriptions—it's about defining the business outcomes you're trying to achieve. Are you building an AI-native product? Do you need to modernize legacy systems? Are you preparing for a security audit? Do you need to scale your engineering team? Your answer determines the type of fractional CTO expertise you should pursue.

Start by documenting your current state: What technology challenges are blocking your business? What are your revenue or operational goals for the next 12 months? What specific gaps exist in your current leadership or engineering capability? For enterprises, this often includes questions around digital transformation, cloud migration, AI integration, or security compliance. For government agencies, the focus might be on modernization, data governance, or meeting federal compliance requirements.

Next, identify the scope of work. Will your fractional CTO be responsible for strategy only, or do you need hands-on technical leadership and shipping capability? Do you need them to build and mentor an engineering team? Will they be responsible for vendor selection, architecture decisions, or managing external contractors? The scope directly influences the type of candidate you hire and the engagement structure you establish.

Document your timeline and constraints. How long do you anticipate needing this engagement? Is this a 90-day intensive push, or a 12-month transformation? Do you have budget constraints? Are there compliance or security requirements that will shape the engagement? Understanding engagement models and how to structure the first 90 days will help you communicate your needs clearly to potential candidates.

Create a simple one-page outcomes document. Include your top three business objectives, the technical initiatives required to achieve them, the current gaps in your team or capability, and your timeline. This document becomes your north star throughout the hiring process and ensures every candidate understands what success looks like.

Step 2: Assess Your Organization's Readiness

Photo by James Harrison on Unsplash

Before you hire a fractional CTO, you need to honestly assess whether your organization is ready to work with one effectively. A fractional CTO is most effective when there's clear executive sponsorship, defined decision-making authority, and a willingness to move quickly. If your organization is still debating whether to pursue digital transformation or lacks alignment on technical priorities, a fractional CTO will struggle to deliver impact.

Evaluate your current engineering team and structure. Do you have an existing team that the fractional CTO will lead, mentor, and scale? Or are you asking them to build from scratch? Understanding how to build an engineering team with a fractional CTO will help you determine the right profile. If you're starting from zero, you need a fractional CTO with strong hiring and team-building experience. If you have a team in place, you need someone skilled at mentorship, architecture, and scaling.

Assess your budget and commitment level. Fractional CTOs typically range from $8,000 to $25,000+ per month depending on experience, engagement model, and geography. Some work on retainers, others on day rates or equity arrangements. Understanding fractional CTO economics—hours, retainers, and equity will help you set realistic expectations. Enterprises often underestimate the commitment required. A fractional CTO needs access to your key stakeholders, decision-making authority, and the ability to move quickly without bureaucratic delays.

Review your governance and compliance requirements. If you're a regulated organization or government contractor, you need a fractional CTO with deep experience in compliance frameworks. Ask yourself: Do we need SOC 2 certification? ISO 27001? Federal compliance (FISMA, FedRAMP)? A fractional CTO with hands-on audit and compliance experience is invaluable here. Organizations often discover that compliance expertise prevents costly mistakes and accelerates security certifications.

Finally, determine the level of hands-on involvement you need from your executive team. A fractional CTO requires regular access to your CEO, CIO, or board. If your leadership team is unavailable or unable to make quick decisions, the engagement will stall. Ensure that whoever is sponsoring this hire understands the time commitment and decision-making authority required.

Step 3: Source Qualified Fractional CTO Candidates

Photo by Christina @ wocintechchat.com M on Unsplash

Once you've defined your needs and assessed your readiness, it's time to source candidates. The fractional CTO market has evolved significantly, and there are now multiple channels to find qualified talent. The key is using a combination of approaches to build a strong candidate pipeline.

Network and Referrals: Your best source of fractional CTO candidates is often your own network. Reach out to board members, investors, advisors, and peers in your industry. Ask: "Who is the best fractional CTO you've worked with or know?" Personal referrals come with built-in credibility and often lead to faster, higher-quality hires. For enterprises and government agencies, this network-based approach is particularly effective because fractional CTOs at the senior level often work through trusted relationships.

Specialized Platforms and Agencies: Platforms like Upwork, Toptal, Gun.io, and specialized fractional CTO networks have emerged to connect companies with experienced leaders. However, enterprise-grade platforms tend to produce better results than general freelance marketplaces. Look for platforms that specialize in C-level fractional roles and have vetting processes in place. When evaluating candidates on these platforms, focus on case studies, references, and specific experience with your industry or technology stack.

Executive Search Firms: For enterprises and government agencies, engaging a retained executive search firm that specializes in fractional or interim CTO placements can be worthwhile. These firms have deep networks, conduct thorough vetting, and often provide guarantees. The cost is higher (typically 20-30% of first-year fees), but for critical hires, the investment often pays off.

Venture Studios and Consulting Firms: If you're looking for a fractional CTO with hands-on delivery capability and access to a broader team, consider delivery-focused venture studios like Padiso that combine fractional leadership with co-build and execution capability. These firms bring not just the CTO but also access to engineers, architects, and specialists who can accelerate your initiatives. This is particularly valuable for government and enterprise clients who need compliance expertise, AI integration, or rapid shipping of complex systems.

Industry Events and Communities: Attend technology conferences, government contractor forums, and industry meetups where senior technologists gather. Many fractional CTOs are active in communities like YCombinator, Founders, or government technology groups. Building relationships in these spaces often yields qualified candidates.

As you source candidates, create a simple scorecard to evaluate each prospect. Include criteria like: relevant industry experience, track record with your technology stack, experience with your compliance requirements (SOC 2, ISO 27001, etc.), team leadership experience, and availability. This scorecard helps you compare candidates objectively and avoid hiring bias.

Step 4: Vet Candidates Thoroughly

Vetting a fractional CTO is different from hiring a full-time executive. You need to move quickly, but you also need to validate that the candidate can deliver on your specific outcomes. A thorough vetting process typically takes 2-4 weeks and includes multiple stages.

Initial Screening Call: Start with a 30-minute screening call focused on your outcomes and their relevant experience. Ask: "Tell me about a similar engagement you've led. What were the business outcomes? What was the technical approach? What challenges did you encounter?" Listen for specificity and evidence of hands-on delivery. Red flags include vague answers, a focus on process over outcomes, or lack of relevant experience.

Detailed Technical Discussion: Conduct a 60-minute technical discussion where you dive deep into your specific challenges. If you're building autonomous agents, ask about their experience with LLMs, prompt engineering, and deployment. If you need embedded analytics, ask about their hands-on experience with Apache Superset and ClickHouse. If compliance is critical, ask them to walk you through a SOC 2 audit they've led. A strong fractional CTO should be able to discuss technical details confidently and ask intelligent questions about your architecture and constraints.

Reference Checks: Always conduct reference checks with at least three previous clients. Ask specific questions: "What were the agreed-upon outcomes? Did this CTO deliver on them? How was their communication and responsiveness? Would you hire them again?" For enterprise and government clients, ask specifically about compliance experience, security practices, and how they handled complex stakeholder management.

Case Study or Work Sample: Ask the candidate to walk you through a specific case study or project they've led. Request details on the business problem, their approach, the team structure, the timeline, and the outcomes. If possible, ask for metrics: Did they reduce deployment time? Improve security posture? Accelerate revenue? A strong candidate should have concrete examples.

Compliance and Security Verification: For regulated organizations, verify that the candidate has the certifications and experience you need. If you require SOC 2 compliance, ask about their audit experience. If you need ISO 27001, ask about their security practices. For government contractors, verify their security clearance eligibility or prior government experience. This verification step is often overlooked but is critical for enterprise and government clients.

Trial or Discovery Engagement: Before committing to a long-term retainer, consider running a paid trial or discovery engagement. This might be a 1-2 week engagement focused on a specific deliverable: an architecture review, a security assessment, or a technology roadmap. A trial engagement costs $5,000-$15,000 but provides invaluable insight into how the candidate works, communicates, and delivers. It's one of the best ways to validate fit before committing to a larger engagement.

Step 5: Define the Scope and Engagement Structure

Once you've selected your fractional CTO, the next critical step is defining the scope and engagement structure clearly. Ambiguity here is the #1 cause of fractional CTO engagement failures. You need a detailed scope document that outlines expectations, deliverables, timelines, and success metrics.

Create a Scope Document: Your scope document should include: (1) Business outcomes and success metrics, (2) Specific responsibilities and areas of authority, (3) Time commitment and availability expectations, (4) Key deliverables and timeline, (5) Team structure and who reports to the fractional CTO, (6) Decision-making authority and escalation paths, (7) Compliance and security requirements, (8) Communication cadence and stakeholder management. Padiso provides a fractional CTO scope document template that you can adapt to your needs. This template ensures you cover all critical elements and reduce misalignment.

Establish the Engagement Model: Decide whether you're using a retainer model (fixed hours per week), a day-rate model (pay per day of work), or a hybrid model. For enterprises, retainers typically work better because they provide predictability and allow for ongoing strategic engagement. Most fractional CTOs charge between $8,000-$25,000+ per month for a part-time retainer, depending on experience and scope. Some also negotiate equity stakes in your company, particularly for startups or high-growth ventures.

Define the First 90 Days: Create a detailed 90-day plan that breaks down what you expect to accomplish in each phase. Understanding how to structure the first 90 days is critical. Typically, the first 30 days focus on assessment and relationship building, the next 30 days on strategy and planning, and the final 30 days on execution and team building. This structure provides clarity and allows you to evaluate whether the engagement is working before committing to a longer term.

Set Clear Success Metrics: Define what success looks like. If you're modernizing infrastructure, success might be "migrate 80% of workloads to cloud by Q2." If you're building an AI capability, success might be "deploy first autonomous agent to production by end of Q1." If you're pursuing compliance, success might be "achieve SOC 2 Type II certification by Q3." These metrics should be specific, measurable, and tied to business outcomes.

Establish Communication Norms: Define how often you'll communicate, who participates in what meetings, and how decisions get made. Most fractional CTOs work best with weekly strategy sessions, daily standups with the engineering team, and monthly business reviews with leadership. Establish clear escalation paths for critical decisions.

Step 6: Onboard Your Fractional CTO Effectively

The first 30 days of your fractional CTO engagement are critical. Poor onboarding leads to wasted time, misalignment, and failed engagements. A structured onboarding process accelerates time-to-value and sets the tone for the entire engagement.

Week One Priorities: During the first week, your fractional CTO should focus on understanding your business, meeting key stakeholders, and assessing your current technology landscape. This includes meeting with your CEO or executive sponsor, reviewing your product and business model, understanding your go-to-market strategy, assessing your engineering team and current technology stack, and identifying immediate risks or blockers. Understanding what a fractional CTO does in week one will help you prepare your team and provide the right access and information.

Access and Credentials: Ensure your fractional CTO has immediate access to all necessary systems: GitHub repositories, cloud infrastructure, security tools, compliance documentation, financial data, and customer feedback. Delays in access slow down the assessment phase significantly. For government and regulated organizations, ensure they understand your security protocols and get any necessary clearances or background checks completed.

Team Introductions and Stakeholder Mapping: Schedule meetings with your engineering team, product leadership, operations, and any external partners or vendors. Your fractional CTO needs to understand the team dynamics, current capabilities, and political landscape. This stakeholder mapping is particularly important in large enterprises where alignment across multiple departments is critical.

Assessment Phase: During the first 2-3 weeks, your fractional CTO should conduct a thorough assessment of your technology, team, processes, and compliance posture. This might include code reviews, architecture assessments, security audits, team capability assessments, and process reviews. The assessment should identify gaps, risks, and opportunities. Understanding the fractional CTO onboarding process for the first 30 days will help you prepare your team for this assessment.

Initial Recommendations and 90-Day Plan: By the end of week three, your fractional CTO should present initial findings and recommendations. This includes a prioritized list of technical initiatives, team changes, process improvements, and compliance actions. Together, you'll refine this into your 90-day plan with specific deliverables and milestones.

Establish Rhythm and Cadence: Lock in your regular meetings: weekly 1-on-1s with your CEO or executive sponsor, weekly team standups, monthly business reviews, and quarterly strategy sessions. This cadence keeps everyone aligned and creates accountability.

Step 7: Monitor Progress and Adjust as Needed

Once your fractional CTO is engaged and working, you need a system to monitor progress, identify issues early, and adjust as needed. Regular check-ins and transparency are critical.

Weekly Check-Ins: Have a 30-minute weekly check-in with your fractional CTO focused on: What was accomplished this week? What are the blockers? What's the priority for next week? Are we on track to meet our 90-day outcomes? These check-ins surface issues early and keep everyone aligned.

Monthly Business Reviews: Conduct a monthly business review where your fractional CTO presents progress against your agreed-upon outcomes. Include your CEO, CFO, and any other key stakeholders. Review metrics, celebrate wins, identify challenges, and adjust the plan if needed. This transparency builds confidence and ensures alignment.

Red Flags and Course Correction: Watch for red flags that indicate the engagement isn't working: the fractional CTO isn't available when promised, they're not engaging with your team, they're not making progress on agreed-upon deliverables, or there's misalignment on priorities. If you notice these issues, address them immediately. Have a direct conversation about expectations and whether adjustments are needed. Understanding when fractional CTO engagements fail and how to fix them will help you diagnose and address problems before they derail the engagement.

Quarterly Evaluations: Every 90 days, conduct a comprehensive evaluation of the engagement. Did you achieve your agreed-upon outcomes? Is the fractional CTO delivering value? Are there new priorities that have emerged? Should you extend the engagement, adjust the scope, or make a change? This evaluation point is critical for making intentional decisions about the future of the engagement.

Step 8: Plan for Transition and Long-Term Success

As your fractional CTO engagement progresses, you need to think about the long-term arc. Will this be a one-time engagement, or an ongoing relationship? If you're building a full-time engineering organization, how does the fractional CTO transition to a permanent role or to an advisory capacity?

Build Institutional Knowledge: Ensure that your fractional CTO documents their decisions, architecture choices, and strategic recommendations. This creates institutional knowledge that survives beyond the engagement. Create architecture decision records, process documentation, and strategy playbooks that your team can reference.

Develop Your Team: A great fractional CTO should be mentoring and developing your team. By the end of the engagement, your engineering team should have grown in capability and independence. If the fractional CTO has been effective, your team should be able to execute on the strategy they've outlined with less hands-on involvement.

Plan for Transition: If your engagement has a defined end date, plan the transition 4-6 weeks before completion. This includes: documenting all decisions and recommendations, training your team on ongoing execution, establishing success metrics for the next phase, and deciding on any ongoing advisory or fractional engagement. Some organizations transition their fractional CTO to a part-time advisory role or quarterly check-in cadence.

Consider Ongoing Engagement: For many enterprises, the fractional CTO model transitions to an ongoing relationship. Rather than a full-time hire, you maintain a fractional engagement (5-10 hours per week) for ongoing strategic guidance, vendor selection, architecture decisions, and mentorship. This model provides continuity and access to senior expertise without the overhead of a full-time executive.

Understanding when to transition from fractional to full-time CTO will help you make the right decision for your organization's stage and needs.

Key Considerations for Enterprise and Government Organizations

If you're an enterprise or government agency, there are specific considerations that apply to your fractional CTO hiring process.

Compliance and Security Expertise: Your fractional CTO must have hands-on experience with your compliance requirements. If you need SOC 2 certification, they should have led multiple SOC 2 audits. If you need ISO 27001, they should understand the framework deeply. For government contractors, they should understand federal compliance requirements (FISMA, FedRAMP, etc.). This expertise prevents costly mistakes and accelerates compliance timelines.

Vendor and Contractor Management: Enterprise and government organizations often work with multiple vendors and contractors. Your fractional CTO should have experience managing these relationships, evaluating vendors, negotiating contracts, and ensuring compliance across the vendor ecosystem.

Stakeholder Management: Enterprise organizations have complex stakeholder landscapes. Your fractional CTO needs to be skilled at managing relationships across multiple departments, board members, and external partners. They should be comfortable presenting to executive leadership and government officials.

Data Governance and AI Ethics: For organizations implementing AI and analytics, your fractional CTO should have expertise in data governance, responsible AI practices, and embedded analytics platforms like Apache Superset and ClickHouse. This expertise is increasingly critical for regulated organizations.

Multi-Team Coordination: Enterprise organizations often have multiple engineering teams and geographic locations. Your fractional CTO should have experience coordinating across these teams, establishing shared standards, and scaling processes.

Prerequisites Before You Start the Hiring Process

Before you begin hiring a fractional CTO, ensure you have these prerequisites in place:

• Executive Alignment: Your CEO, board, and key stakeholders must be aligned on the need for a fractional CTO and committed to the engagement.

• Budget Approval: You need approved budget for the engagement, including contingency for extended scope or additional resources.

• Clear Outcomes: You must have defined business outcomes and success metrics for the engagement.

• Decision-Making Authority: Your fractional CTO needs clear decision-making authority and access to key stakeholders.

• Team Readiness: Your existing team (if any) should be prepared for the arrival of a fractional CTO and understand how they'll work together.

• Infrastructure Access: You need to be able to provide immediate access to systems, repositories, documentation, and stakeholders.

• Compliance Documentation: If you're a regulated organization, you should have your compliance requirements and existing audit results documented.

Pro Tips for Success

Run a Paid Trial First: Before committing to a long-term retainer, run a 1-2 week paid trial engagement. This allows you to evaluate fit, communication style, and delivery capability with minimal risk. Many organizations find this $5,000-$15,000 investment saves them from expensive hiring mistakes.

Check References Thoroughly: Don't just ask generic questions. Ask previous clients about specific outcomes, communication style, and whether they'd hire again. For enterprise and government clients, ask about compliance and security expertise.

Define Success Metrics Upfront: Ambiguity about success is the #1 cause of failed fractional CTO engagements. Define specific, measurable outcomes before you hire. Understanding what questions to ask a fractional CTO before signing a retainer will help you ensure alignment.

Look for Hands-On Delivery: The best fractional CTOs aren't just strategists—they ship code, lead architecture decisions, and roll up their sleeves. Look for candidates with recent hands-on experience, not just consulting background.

Consider Venture Studio Models: For complex initiatives like AI integration or compliance transformation, consider engaging a delivery-focused venture studio that combines fractional CTO leadership with access to engineers and specialists. This model accelerates execution and reduces risk for enterprise digital transformation initiatives.

Invest in Onboarding: Don't skip the onboarding process. Spend time upfront ensuring your fractional CTO understands your business, team, and constraints. This investment pays dividends in faster time-to-value and stronger relationships.

Maintain Regular Communication: Weekly check-ins, monthly business reviews, and transparent reporting keep the engagement on track. Don't go dark for months and expect great outcomes.

Common Mistakes to Avoid

Hiring Without Clear Outcomes: The #1 mistake is hiring a fractional CTO without defining what you actually need. Vague job descriptions lead to misaligned expectations and failed engagements.

Underestimating the Commitment Required: Fractional CTOs need access to leadership, quick decision-making, and active engagement. If your organization can't provide this, the engagement will stall.

Skipping the Vetting Process: Don't hire based on a resume or one conversation. Conduct thorough reference checks, technical discussions, and ideally a trial engagement.

Lack of Scope Definition: Without a detailed scope document, both you and the fractional CTO will have different expectations. Invest time upfront in a clear scope.

Not Planning for Transition: Think about the long-term arc from day one. How will this engagement transition to ongoing work or a permanent hire? Planning this upfront prevents surprises later.

Ignoring Red Flags: If the fractional CTO isn't available, isn't engaging with your team, or isn't making progress, address it immediately. Don't hope it improves.

Summary and Key Takeaways

Hiring a fractional CTO is a significant decision that can accelerate your technology transformation and business outcomes. The key to success is following a structured process: define your outcomes, assess your readiness, source qualified candidates, vet thoroughly, define scope clearly, onboard effectively, monitor progress, and plan for the long term.

The fractional CTO model is particularly valuable for enterprises and government agencies pursuing digital transformation, AI integration, or compliance initiatives. By following this step-by-step guide, you'll avoid common pitfalls and set yourself up for a successful engagement that delivers measurable business outcomes.

Remember: the best fractional CTOs combine strategic thinking with hands-on delivery capability. They're not just advisors—they ship outcomes. Look for candidates with proven track records, relevant expertise, strong communication skills, and a commitment to your success. And don't skip the trial engagement; it's one of the best ways to validate fit before committing to a long-term relationship.

If you're ready to explore fractional CTO options for your enterprise, Padiso specializes in fractional CTO, AI-native development, and program leadership for enterprise and government clients. We combine senior technical leadership with hands-on delivery capability to accelerate your technology transformation. Whether you need strategic guidance, hands-on execution, or a combination of both, we can help you navigate the fractional CTO hiring process and structure an engagement that drives results.

A CEO asked me this last month over coffee in Sydney.

Manufacturing business, around 60 staff, profitable, no CTO. He’d been quoted $180K by a systems integrator, $2,400 a month by a SaaS vendor, and had a very keen 26-year-old on his team volunteering to “just build it with Cursor.”

He wanted me to tell him which one to pick.

I told him he was asking the wrong question, which is a rude thing to say to someone who has just bought you a coffee. But he was. All three quotes were answers to a question he hadn’t defined yet, and the gap between those numbers — $2,400 a month versus $180K — wasn’t a pricing difference. It was three vendors guessing at three completely different scopes.

Here’s the framework I use, across PADISO’s client work and inside my own companies. It starts by throwing out the assumption underneath the question.

This Substack is reader-supported. To receive new posts and support my work, consider becoming a free or paid subscriber.

The old logic is inverted

For twenty years, the buy-versus-build decision ran on one dominant variable: construction cost. Building software was expensive and slow, so you built only what was strategically essential and bought everything else. That was correct advice. I gave it myself for most of my career.

That variable has collapsed.

Roughly 25% of the SearchFit codebase is written by agents — Claude Code and Codex, running against a spec I write and a review I do. Features that would have required three or four engineers now require me and an afternoon of supervision. I’m running three companies from Sydney with a technical team you could fit in a small lift.

So building is cheap now. Which means, counterintuitively, build is no longer the expensive option — and buy is no longer the safe one.

What hasn’t got cheaper is everything around the code:

• Integrating with the booking system that hasn’t been updated since 2019

• Cleaning the data in the CRM that four different sales managers have used differently

• Deciding what the thing should actually do

• Owning it when it breaks on a Tuesday

That’s where the money goes now. Every AI project I’ve seen fail — and I’ve been called in to rescue several — failed at integration, data quality, or ownership. Not one failed because the model wasn’t smart enough.

So stop asking “what’s cheapest to build.” Ask “who owns this in eighteen months, and what happens the first time it’s wrong?”

Question one: is it a differentiator or a utility?

The cleanest cut in the whole decision.

Utilities are the things every business in your category needs and none of them win on. Transcription. Email drafting. Meeting notes. Document search. Support ticket deflection. Basic forecasting.

Buy these. Always. Do not let anyone build them for you, in-house or otherwise. There are funded companies with fifty engineers competing to make these cheaper and better every quarter, and you will never out-run them. If someone quotes you $80K to build an internal meeting-notes tool, that’s not an AI project, that’s a hobby with an invoice attached.

Differentiators are the things that encode how your business specifically makes money. The pricing logic your ops director keeps in her head. The way you triage inbound leads because you know which postcodes convert. The compliance workflow that’s specific to your licence. The quoting process that takes your estimator three days.

Nobody sells this. It doesn’t exist as a product, because the market for it is exactly one company. If you try to buy it, you’ll buy a generic platform and spend nine months and a change-request budget bending it into a shape it was never designed to hold.

Most executives get this backwards. They buy a big platform to handle the differentiated work and then build a scrappy internal tool for a utility, because the platform vendor had better sales collateral.

Question two: does it touch your mess?

This is the question that decides more outcomes than any other, and it never appears on a vendor comparison matrix.

Every real business runs on a substrate of legacy systems, half-documented processes, and data that’s technically wrong in ways everyone has quietly agreed to work around. At PADISO we wire agents into that reality — revenue tracking across booking platforms, self-updating Power BI dashboards, email pipelines, orchestration through N8N and custom agent architectures. The AI part is genuinely the easy part now. The hard part is that your “customer” table has three spellings of the same company name and a field called notes2.

If a proposed solution has to touch that mess, you cannot buy your way out of it. No vendor is going to reconcile your data model for a monthly subscription. They’ll give you an API and a Zapier connector and a smile.

If it doesn’t touch the mess — if it’s a standalone tool sitting at the edge of your operation — buying is almost always right.

Ask any vendor one question: “Show me exactly what happens when this reads from our systems and the data is wrong.” Their answer tells you whether they’ve deployed into a business like yours or only into slide decks.

Question three: who gets paged?

An AI system isn’t a purchase. It’s a dependency, and dependencies need owners.

Answer this before you sign anything:

• When the agent makes a wrong decision, who finds out — and how fast?

• When your CRM vendor changes an API in six months, who fixes it?

• When the person who understood the workflow leaves, what’s left behind?

Build in-house only if you have — or are willing to hire — someone who can hold that ownership. Not someone who can write code. Agents write the code. Someone who can specify clearly, evaluate whether the output is correct, and architect systems that don’t collapse under load. That’s a different profile from the one you’re used to hiring for, and it’s rarer than a good developer, not more common.

If you don’t have that person and you’re not ready to hire them, in-house build is how you acquire an unmaintained system with your logo on it.

Buy when the vendor owns the pager, and price the subscription as what it actually is: rent for not having to think about it.

Hire an agency when you need the capability faster than you can hire it, and you have a specific outcome in mind rather than a general desire to “do something with AI.”

The fourth option nobody quotes you for

Most businesses I work with don’t land on any of the three. They land on the combination, which is:

Buy the platform. Build the workflow. Hire someone to wire it together and then leave.

You buy the model access and the infrastructure — you are not training a foundation model, please do not let anyone tell you that you should. You build the thin, specific layer that encodes how your business works, because that layer is the whole point. And you bring in outside help for the twelve weeks it takes to get it into production, with a hard requirement that they hand you documentation, tests, and a runbook on the way out.

That last part is the bit to negotiate hard on, because the agency incentive runs directly against it.

How to buy an agency without getting burned

Since I run one, treat this as a confession rather than a sales pitch.

Buy outcomes, not hours. “Reduce quote turnaround from three days to four hours” is an outcome. “Two senior engineers for six months” is a staffing arrangement with extra steps, and it transfers all the risk to you.

Get IP assignment in writing. Not a licence. Assignment. If the workflow encodes how your business makes money, you own it — including prompts, agent definitions, and configuration, not just source code.

Demand a handover artefact. Documentation, tests, and a written runbook for what to do when it misbehaves, delivered as a milestone, not a favour at the end.

Ask what they run internally. Any agency selling AI transformation should be visibly running on it. If they can’t show you their own agents, their own automations, their own numbers, you’re buying a deck. We fund product bets at SearchFit and Capitaly off PADISO’s consulting revenue, and increasingly the consulting itself is delivered by agents — I’m using AI to build the AI consultancy that funds the AI products. That’s the standard I’d hold any agency to, including mine.

Start with one workflow. Anyone who wants to sell you an eighteen-month transformation programme before proving a single process in production is selling you optionality on their own revenue.

The ninety-day test

Before committing capital in any direction, run this:

1. Pick one workflow with a number attached to it — hours, error rate, turnaround time, cost per unit.

2. Measure the baseline for two weeks. If you can’t measure it, you’ve picked the wrong workflow, and you also can’t prove ROI later.

3. Ship something narrow into production in six weeks. Production, not a demo. A demo proves the model works. Production proves your business works.

4. Run it for six weeks with a human checking every output.

5. Then decide buy, build, or agency — with actual evidence about where the difficulty lives.

Ninety days and a contained budget buys you a real answer to a question that no vendor comparison, analyst report, or LinkedIn framework can give you: where in your specific business the friction actually is.

Almost every organisation is wrong about this before they test. They think the problem is the AI. The problem is nearly always the data, the integration, or the fact that nobody wrote down how the process really works.

The one-line version

If it’s a utility, buy it. If it’s how you make money, build it. If you need it faster than you can hire for it, bring in help — but own the output and take the pager back at the end.

And if you genuinely can’t tell which category something falls into, that’s not a procurement problem. That’s a strategy problem, and no amount of spend will fix it.

The company that spends $50K on the right workflow will beat the one that spends $500K on the wrong platform. Every time. I’ve watched it happen from both sides of the invoice.

I’m Kevin — CEO of PADISO and SearchFit, running three companies from Sydney with a two-person engineering team. I write about what the AI-native operating model actually takes, and what breaks. If this was useful, subscribe.

The digital landscape has fundamentally shifted. Traditional search engine optimization, while still critical, no longer captures the complete picture of how customers discover your brand. Today's enterprises must contend with a new reality: artificial intelligence assistants like ChatGPT, Perplexity, Gemini, Claude, and Grok are becoming primary discovery channels for information, recommendations, and purchasing decisions.

Multi-platform AI monitoring refers to the systematic tracking and measurement of your brand's visibility, citations, and recommendations across multiple AI assistant platforms simultaneously. Unlike traditional SEO, which focuses on search engine rankings, multi-platform AI monitoring captures where your brand appears in AI-generated responses, how frequently it's recommended, and how competitive your positioning is within each AI ecosystem.

For enterprises, this shift represents both a challenge and an opportunity. Organizations that understand how to monitor and optimize their presence across multiple AI platforms gain a significant competitive advantage. They can identify gaps in their AI visibility, understand which platforms drive the most relevant traffic, and develop targeted strategies to improve recommendations across each channel.

The stakes are higher than ever. When a prospect asks ChatGPT for a solution recommendation and your competitor appears in the response while you don't, you've lost that opportunity. When Perplexity users research your industry and your thought leadership content isn't cited, your market authority diminishes. Multi-platform AI monitoring transforms this blind spot into actionable intelligence.

Why Enterprise Organizations Need Multi-Platform AI Monitoring

Enterprise organizations operate in complex, multi-channel environments where visibility fragmentation is a constant challenge. The emergence of multiple AI assistants has created a new layer of complexity that traditional monitoring tools were never designed to address.

Consider the scale of the opportunity. According to recent industry analysis, AI assistants are being used by millions of professionals and consumers daily for research, decision-making, and recommendations. A comprehensive guide to AI visibility tracking tools reveals that enterprises monitoring 10+ AI engines simultaneously are capturing visibility opportunities that competitors relying on traditional SEO metrics completely miss.

The business impact is measurable and significant. When enterprises implement proper multi-platform AI monitoring, they typically discover:

Visibility Gaps: Many brands have strong traditional SEO rankings but minimal presence in AI assistant responses. This gap represents lost revenue and market share.

Competitor Insights: Understanding where competitors are cited, how frequently, and in what context provides strategic advantages for content and positioning decisions.

Content Opportunities: AI monitoring reveals which topics, formats, and angles resonate with AI training data and recommendation algorithms, guiding content strategy more effectively than traditional keyword research alone.

Attribution Challenges: Without proper monitoring, enterprises cannot accurately attribute website traffic, leads, and conversions to AI-driven discovery, making ROI calculations impossible.

For B2B SaaS companies, the implications are particularly significant. When a prospect asks Claude about project management tools or Gemini for marketing automation recommendations, your solution needs to be cited. For e-commerce brands on Shopify, Perplexity users researching product categories need to see your brand recommended. For agencies managing multiple client accounts, the ability to track and report on AI visibility across platforms is essential for demonstrating value and justifying marketing spend.

The Multi-Platform AI Landscape: Understanding Each Major Platform

Successful multi-platform AI monitoring requires understanding the unique characteristics, user bases, and recommendation patterns of each major AI assistant. They are not interchangeable; each platform has distinct strengths, training data recency, and user behavior patterns.

ChatGPT: The Market Leader

OpenAI's ChatGPT remains the most widely adopted AI assistant, commanding the largest user base and the most frequent business queries. ChatGPT's recommendation patterns are influenced by its training data (with a knowledge cutoff in April 2024), web browsing capabilities, and the platform's emphasis on providing comprehensive, detailed responses.

For enterprises, ChatGPT visibility is often the highest priority because of its market dominance. However, ChatGPT's responses are not ranked in traditional ways; instead, it provides contextual citations and recommendations based on relevance and authority signals. Understanding how your brand appears in ChatGPT responses requires different monitoring approaches than traditional search.

Perplexity: The Research-Focused Platform

Perplexity has emerged as the go-to platform for detailed research and comparative analysis. Its user base skews toward professionals, researchers, and knowledge workers seeking comprehensive, cited information. Perplexity's strength lies in its transparency—it clearly shows sources and citations, making it easier for users to verify information and explore recommendations.

For B2B companies and thought leaders, Perplexity visibility is increasingly critical. When Perplexity users research industry topics, best practices, or vendor comparisons, your brand's appearance in the sources and recommendations directly influences consideration. A detailed comparison of AI visibility monitoring tools highlights that Perplexity-specific monitoring has become essential for many enterprises.

Google Gemini: The Integrated Powerhouse

Google's Gemini integration into Search represents a fundamental shift in how Google delivers information. With hundreds of millions of users accessing Gemini through Google Search, its impact on visibility cannot be overstated. Gemini's responses are influenced by Google's Knowledge Graph, traditional ranking signals, and its own training data.

For enterprises already investing in traditional SEO, understanding how your content appears in Gemini responses is crucial. The platform's integration with Google's search ecosystem means that strong SEO performance often correlates with Gemini visibility, but not always. Specific optimization for Gemini's response patterns may be necessary.

Claude, Grok, and Emerging Platforms

While ChatGPT and Perplexity dominate, Claude (Anthropic), Grok (X/Twitter's platform), and other emerging AI assistants are gaining traction in specific niches and user communities. Claude particularly appeals to technical audiences and professionals seeking detailed, nuanced responses. Grok attracts users interested in real-time information and contrarian perspectives.

For comprehensive multi-platform monitoring, these emerging platforms cannot be ignored. A brand that appears in ChatGPT and Perplexity but is absent from Claude and Grok is leaving visibility opportunities on the table, particularly in technical and specialized markets.

Building Your Multi-Platform AI Monitoring Strategy

Successful multi-platform AI monitoring isn't simply about tracking mentions across platforms. It requires a strategic framework that aligns monitoring efforts with business objectives, integrates data across platforms, and drives actionable optimization.

Define Your Monitoring Objectives and KPIs

Before implementing any monitoring system, enterprises must clearly define what success looks like. Different organizations will have different priorities.

For SaaS companies, primary KPIs might include:

• Citation frequency in solution recommendation queries

• Competitive share of voice in relevant AI responses

• Traffic attribution from AI assistant referrals

• Lead quality and conversion rates from AI-sourced traffic

For e-commerce brands, KPIs might focus on:

• Product recommendation frequency in shopping-related queries

• Category visibility in comparative product searches

• Review and rating citations in AI responses

• Direct traffic and conversion attribution

For agencies, KPIs should address:

• Client visibility across multiple AI platforms

• Competitive positioning relative to direct competitors

• Content performance in AI training and recommendations

• ROI demonstration for client reporting

The framework for measuring AEO success through KPI metrics provides guidance on establishing enterprise-level metrics that connect AI visibility to business outcomes.

Select and Integrate Monitoring Tools

Not all monitoring platforms are created equal. When selecting a multi-platform AI monitoring solution, enterprises should evaluate:

Platform Coverage: Does the tool monitor all relevant AI assistants for your industry and audience? A tool that covers ChatGPT and Perplexity but not Gemini has blind spots.

Real-Time Capability: AI responses change frequently. Can the tool provide real-time or near-real-time visibility data, or is it limited to periodic checks?

Competitor Tracking: Can you monitor not just your own brand but also your direct competitors across all platforms?

Integration Capabilities: Does the tool integrate with your existing martech stack (Google Analytics, CRM, content management systems)? A review of AI visibility optimization platforms emphasizes that integration capabilities significantly impact implementation success.

Actionable Insights: Does the tool simply report data, or does it provide strategic recommendations for improvement?

SearchFIT stands out in this landscape by providing comprehensive multi-platform AI visibility tracking across ChatGPT, Perplexity, Gemini, Claude, Grok, and other emerging platforms. The platform's real-time monitoring capabilities and integration with existing workflows make it particularly valuable for enterprises managing complex visibility strategies.

Establish Baseline Metrics and Benchmarking

Before optimization can begin, enterprises need to establish baseline metrics for their current AI visibility. This involves:

Comprehensive Audits: Conduct thorough audits of how your brand currently appears across all monitored AI platforms. What percentage of relevant queries include your brand? How does your visibility compare to competitors?

Competitive Benchmarking: Understand your competitive position. Where do direct competitors appear that you don't? What topics do competitors dominate in AI responses?

Content Analysis: Identify which of your content pieces are most frequently cited in AI responses. What characteristics do highly-cited pieces share?

Topic Mapping: Create a map of topics relevant to your business and track your visibility for each. This reveals opportunities and gaps in your AI presence.

A competitor citation gap analysis framework helps enterprises systematically identify visibility gaps where competitors are cited but your brand is absent.

Optimizing Content and Strategy for Multi-Platform AI Visibility

Once monitoring is in place and baselines are established, the real work of optimization begins. Multi-platform AI visibility isn't achieved through gaming algorithms; it requires creating genuinely valuable, well-structured content that AI assistants recognize as authoritative and relevant.

Answer Engine Optimization (AEO) Fundamentals

Answer Engine Optimization represents a fundamental shift from traditional SEO. While SEO optimizes for ranking in search results, AEO optimizes for appearing in AI-generated responses and recommendations.

The complete guide to Answer Engine Optimization outlines the core principles:

Comprehensiveness: AI assistants favor comprehensive, well-structured content that thoroughly addresses questions. Thin, surface-level content rarely appears in AI responses.

Authority Signals: Content from recognized authorities, institutions, and brands with strong domain authority is more likely to be cited. Building authority through quality content, backlinks, and media mentions is essential.

Structured Data: Proper implementation of schema markup, heading hierarchies, and content organization helps AI assistants understand and cite your content more effectively.

Citation-Worthiness: Content must be genuinely valuable and citation-worthy. AI assistants cite sources that provide unique insights, data, or perspectives that add value to their responses.

Topical Authority: Demonstrating deep expertise across related topics increases the likelihood of citations across multiple queries and platforms.

Platform-Specific Optimization Strategies

While core AEO principles apply across platforms, each AI assistant has unique characteristics that warrant tailored optimization approaches.

ChatGPT Optimization: ChatGPT values comprehensive, well-structured responses. Content with clear sections, logical flow, and practical examples performs well. Since ChatGPT has a knowledge cutoff, maintaining fresh content and building authority through current media mentions helps. Detailed guides, case studies, and original research are frequently cited.

Perplexity Optimization: Perplexity's emphasis on transparency and source attribution means that content with clear citations, data attribution, and verifiable claims performs better. Content that directly answers specific questions and provides comparative analysis is particularly valuable. Perplexity users appreciate primary sources and original research.

Gemini Optimization: As a Google product, Gemini's recommendations are influenced by traditional SEO signals, but also by content structure and comprehensiveness. Content that ranks well in Google Search often appears in Gemini responses, but optimization specifically for Gemini's response patterns (clear topic coverage, structured data, authoritative sources) can improve visibility.

Claude and Emerging Platforms: These platforms often favor nuanced, well-reasoned content. Technical accuracy, thoughtful analysis, and content that acknowledges complexity and nuance performs well. For technical audiences, detailed documentation and expert-level content is particularly valuable.

A detailed comparison of optimization strategies for ChatGPT, Perplexity, and Gemini provides platform-specific tactics for maximizing visibility on each major platform.

Content Development and Topic Clustering

Multi-platform AI monitoring reveals topic gaps and opportunities. Enterprises should use this intelligence to guide content development.

Identify High-Value Topics: Which topics are frequently queried in AI assistants but your brand rarely appears in responses? These represent immediate content opportunities.

Develop Comprehensive Content: Create in-depth, authoritative content that thoroughly covers high-value topics. This content should be significantly more comprehensive than competitor content.

Build Topic Clusters: Organize content around core topics with supporting subtopics. This topical authority signals expertise to AI assistants and increases citation likelihood.

Prioritize Original Research: AI assistants frequently cite original research, data, and unique insights. Developing original research, surveys, and proprietary data increases citation potential.

Optimize for Different Query Types: Different AI assistants receive different query types. Ensure your content addresses comparison queries, how-to questions, research queries, and recommendation requests.

Technical Implementation and Integration

For enterprises with complex technical environments, implementing multi-platform AI monitoring requires careful integration planning. This is where platforms like SearchFIT provide significant value through APIs, webhooks, and native integrations.

API-Driven Monitoring and Automation

SearchFIT's API enables enterprises to build custom monitoring workflows that integrate with existing systems. The real-time citation monitoring through SearchFIT's API allows organizations to:

• Automatically track brand mentions across all platforms

• Trigger alerts when visibility changes significantly

• Feed AI visibility data into existing dashboards and reporting systems

• Build custom workflows that integrate with marketing automation platforms

Building custom AEO workflows with SearchFIT's API provides detailed guidance on implementing sophisticated monitoring and optimization workflows.

Integration with Existing Martech Stacks

Most enterprises use multiple marketing technology platforms. Effective multi-platform AI monitoring requires integration with these existing systems.

Google Analytics Integration: Understanding how AI-sourced traffic performs compared to traditional search traffic is critical. SearchFIT's Google Analytics integration enables seamless tracking of AI visibility impact on website traffic and conversions.

CRM and Sales Integration: For B2B companies, connecting AI visibility data to CRM systems helps sales teams understand which prospects discovered the company through AI assistants.

Content Management System Integration: Direct integration with WordPress, Shopify, and other platforms enables content optimization recommendations without manual data transfer.

Workflow Automation: Platforms like n8n enable enterprises to build sophisticated automation workflows. Integration with n8n for self-hosted teams demonstrates how enterprises can automate multi-platform monitoring and reporting.

Dashboard Development and Reporting

Data is only valuable if it's accessible and actionable. Enterprises should develop comprehensive dashboards that provide visibility into multi-platform AI performance.

Executive Dashboards: High-level KPI summaries showing overall AI visibility trends, competitive position, and business impact.

Platform-Specific Dashboards: Detailed views of performance on each AI platform, with platform-specific metrics and optimization recommendations.

Competitor Dashboards: Side-by-side comparisons of your visibility versus direct competitors across all platforms.

Content Performance Dashboards: Tracking which content pieces drive citations, recommendations, and traffic from AI assistants.

Multi-source analytics dashboards provide guidance on consolidating data from multiple sources into actionable dashboards.

Measuring ROI and Business Impact

For multi-platform AI monitoring to gain enterprise buy-in and sustained investment, organizations must clearly demonstrate ROI and business impact.

Establishing Attribution Models

Traditional attribution models often miss AI-driven traffic because it doesn't follow standard referral patterns. Enterprises need to implement sophisticated attribution approaches:

First-Click Attribution: When did prospects first encounter your brand through an AI assistant? This reveals awareness-building impact.

Multi-Touch Attribution: How do AI-sourced interactions contribute to the overall customer journey alongside traditional search, paid, and organic channels?

Incrementality Testing: What additional revenue would be lost if your brand disappeared from AI recommendations? This incremental impact is the true ROI of AI visibility.

A comprehensive framework for correlating AI citations with revenue provides detailed guidance on establishing these attribution connections.

Calculating Business Impact

Once attribution is established, enterprises can calculate concrete business impact:

Revenue Attribution: How much revenue can be attributed to AI-sourced traffic and recommendations?

Cost Per Acquisition: How does the cost to acquire customers from AI sources compare to other channels?

Lifetime Value: Do customers acquired through AI recommendations have higher lifetime value than those from other sources?

Market Share Impact: How much market share is influenced by visibility in AI recommendations?

A detailed guide for measuring AEO ROI for CFOs provides frameworks for presenting AI visibility impact in financial terms that resonate with executive leadership.

Developing Comprehensive KPI Frameworks

Enterprise organizations need comprehensive KPI frameworks that connect AI visibility to business outcomes. The AEO scorecard with 12 key metrics outlines metrics that should be tracked:

• Brand mention frequency across platforms

• Competitive share of voice

• Citation growth trends

• Traffic attribution from AI sources

• Lead quality and conversion rates

• Customer acquisition cost

• Market share trends

• Content performance metrics

• Platform-specific performance indicators

• Competitive benchmarking metrics

Advanced Strategies for Enterprise Organizations

Once foundational multi-platform AI monitoring is in place, enterprises can implement advanced strategies that provide competitive advantages.

Competitive Intelligence and Benchmarking

Beyond tracking your own visibility, enterprises should systematically monitor competitors' AI presence. This intelligence informs strategic decisions about content, positioning, and resource allocation.

Competitive Share of Voice: What percentage of relevant AI responses mention your brand versus competitors? Where are you losing visibility?

Topic Dominance: Which topics do competitors dominate in AI responses? Where can you build authority?

Content Strategy Analysis: What content types and topics do competitors publish that drive citations? What gaps exist?

Recommendation Patterns: How do different AI platforms recommend competitors? What positioning and messaging do they emphasize?

Competitor citation gap analysis provides systematic approaches to competitive AI monitoring.

Generative Engine Optimization (GEO)

As AI assistants become more sophisticated, Generative Engine Optimization—optimizing for AI-generated content and recommendations—becomes increasingly important. This goes beyond traditional AEO.

Generative Engine Optimization explained for CMOs covers advanced strategies for optimizing for AI-generated content, including positioning strategies, content approaches, and measurement frameworks.

Multi-Agent Orchestration and AI Teams

For enterprises with sophisticated AI implementation, multi-agent orchestration—coordinating multiple AI systems to work together—becomes relevant. Understanding how different AI agents interact and recommend can inform strategy.

Multi-agent orchestration in the SearchFIT foundation explores how enterprises can leverage multiple AI systems strategically.

Implementation Roadmap for Enterprise Organizations

Implementing comprehensive multi-platform AI monitoring doesn't happen overnight. Enterprises should follow a structured roadmap.

Phase 1: Assessment and Planning (Weeks 1-4)

Conduct Current State Analysis: Audit existing AI visibility across major platforms. Identify baseline metrics and competitive position.

Define Objectives and KPIs: Align multi-platform AI monitoring strategy with business objectives. Establish success metrics.

Evaluate Tools and Platforms: Research and select monitoring tools that meet enterprise requirements. SearchFIT's comprehensive platform coverage and integration capabilities make it a strong choice for enterprises.

Develop Governance Framework: Establish processes for managing multi-platform AI optimization, reporting, and decision-making.

Phase 2: Foundation Building (Weeks 5-12)

Implement Monitoring Infrastructure: Deploy selected monitoring tools and establish baseline data collection across all platforms.

Integrate with Existing Systems: Connect monitoring data to existing dashboards, analytics platforms, and reporting systems.

Establish Reporting Cadence: Develop weekly, monthly, and quarterly reporting processes. Setting up weekly AI visibility reports for clients provides guidance on establishing effective reporting.

Train Teams: Ensure marketing, content, and analytics teams understand multi-platform AI monitoring concepts and how to interpret data.

Phase 3: Optimization and Scale (Weeks 13-26)

Identify Content Opportunities: Use monitoring data to identify high-value topics where you're underrepresented in AI responses.

Develop Content Strategy: Create comprehensive content that addresses identified gaps and builds topical authority.

Implement Platform-Specific Optimizations: Apply platform-specific optimization strategies for ChatGPT, Perplexity, Gemini, and other platforms.

Build Competitive Intelligence: Establish ongoing competitive monitoring and benchmarking processes.

Phase 4: Maturity and Advanced Strategies (Month 7+)

Implement Advanced Monitoring: Deploy API-driven monitoring, custom workflows, and sophisticated automation.

Develop Attribution Models: Establish connections between AI visibility and business outcomes.

Implement Generative Engine Optimization: Move beyond basic AEO to advanced GEO strategies.

Continuous Optimization: Establish ongoing optimization cycles based on performance data and competitive intelligence.

Common Challenges and Solutions

Enterprise organizations implementing multi-platform AI monitoring often encounter predictable challenges. Understanding these challenges and their solutions accelerates successful implementation.

Challenge 1: Fragmented Data and Reporting

Problem: Visibility data exists in multiple tools and systems, making it difficult to get a unified view of AI performance.

Solution: Implement a centralized analytics platform that consolidates data from all monitoring sources. SearchFIT's API and integration capabilities enable this consolidation.

Challenge 2: Attribution Complexity

Problem: Connecting AI visibility to business outcomes is difficult because AI-sourced traffic doesn't follow traditional attribution patterns.

Solution: Implement sophisticated attribution modeling that accounts for AI-sourced interactions. Use UTM parameters, direct tracking, and incremental testing to establish causation.

Challenge 3: Platform Proliferation

Problem: New AI platforms emerge constantly, making it difficult to maintain comprehensive monitoring.

Solution: Select monitoring platforms that regularly add support for emerging AI assistants. SearchFIT's commitment to tracking new platforms ensures you're not caught off-guard by emerging competitors.

Challenge 4: Content at Scale

Problem: Developing comprehensive content to address all identified gaps is resource-intensive.

Solution: Prioritize based on business impact. Focus first on topics with high search volume, high commercial intent, and significant visibility gaps. Use AI-assisted content generation tools to scale content development.

Challenge 5: Team Alignment

Problem: Marketing, content, SEO, and product teams may have different priorities and perspectives on AI optimization.

Solution: Establish clear governance, shared KPIs, and regular communication. Make AI visibility metrics visible to all teams through dashboards and reporting.

Future-Proofing Your Multi-Platform AI Monitoring Strategy

The AI landscape is rapidly evolving. Enterprises need strategies that remain effective as AI assistants become more sophisticated and new platforms emerge.

Staying Ahead of Platform Evolution

AI assistants are constantly improving their recommendation algorithms, expanding their capabilities, and changing how they cite sources. Enterprises should:

• Monitor platform updates and changes regularly

• Test how changes affect your visibility and recommendations

• Adjust optimization strategies as platforms evolve

• Maintain relationships with platform providers

Adapting to Changing User Behavior

As AI assistants become more prevalent, user behavior evolves. Query types change, user expectations shift, and the competitive landscape transforms. Successful enterprises:

• Regularly analyze query patterns and user behavior

• Adjust content strategy based on emerging user needs

• Test new content formats and approaches

• Monitor emerging use cases for AI assistants

Building Organizational Capability

Multi-platform AI monitoring requires new skills and expertise. Enterprises should invest in:

• Training for marketing and content teams on AEO principles

• Hiring or developing expertise in AI visibility optimization

• Building internal capabilities for data analysis and interpretation

• Establishing partnerships with agencies or consultants who specialize in AEO

Conclusion: The Enterprise Imperative for Multi-Platform AI Monitoring

Multi-platform AI monitoring has moved from optional to essential for enterprise organizations. The emergence of multiple AI assistants as discovery channels, combined with their growing influence on purchasing decisions, makes AI visibility as important as traditional search visibility.

Enterprises that implement comprehensive multi-platform AI monitoring gain significant competitive advantages. They understand where their brand appears in AI responses, identify gaps in visibility, develop targeted strategies to improve recommendations, and ultimately drive more traffic, leads, and revenue from AI sources.

The implementation journey requires strategic planning, tool selection, content development, and ongoing optimization. But the payoff is substantial: enterprises that master multi-platform AI monitoring position themselves as leaders in their markets and capture visibility opportunities that competitors miss.

SearchFIT's comprehensive platform for tracking brand visibility across ChatGPT, Perplexity, and Gemini combined with its real-time monitoring, competitor tracking, and integration capabilities, provides the foundation for enterprise-scale multi-platform AI monitoring. By leveraging these tools and following the strategies outlined in this playbook, enterprises can build sustainable competitive advantages in the AI-driven discovery landscape.

The question is no longer whether your enterprise should implement multi-platform AI monitoring—it's how quickly you can get started. The competitive window for capturing AI visibility advantage is open now, but it won't remain open indefinitely. Organizations that act today will build the expertise, data, and competitive advantages that will define market leadership for years to come.