Let's Talk
Spend Is Not an Outcome
AI Strategy

Spend Is Not an Outcome

Pablo Cruz Pou

· October 26, 2026 · 4 min read

Most leadership teams can state their AI spend to the dollar. Few can state what it changed in the business. AWSM LABS built three self-guided assessments that show where your program stands and where the gap to results is widest, each in about two minutes, none requiring a call.

Ask any leadership team what they spent on AI last year and you'll get a number within a minute. Ask what changed in the business because of it and the room goes quiet. Someone mentions a pilot. Someone else mentions adoption. Nobody mentions a result they would put in front of a board.

Spend, licenses, logins and pilots are output. They show what the program produced. They don't show what the business got. The outcome is the shorter cycle, the cost taken out, the revenue brought in, the risk reduced. It is the only return anyone is accountable for, and it is the one most teams can't state.

Why the debate stalls

The usual response is a review. It takes weeks, costs real money, and returns a deck that restarts the argument it was meant to end, because the COO, the CFO and the head of product still measure progress three different ways. One counts adoption. One counts savings. One counts speed. Nobody agreed on a baseline for the outcome.

Without a baseline, every number is a vote.

A baseline needs no verdict and no long engagement. It needs honest answers to a short list of well-built questions, scored against something outside your own building. Get that first and the argument gets shorter, because people are arguing about where the program stands instead of whose impression to trust.

Three reads on the same question

We publish our thinking on AI value. The Analysis Tools page lets you run it on your own organization. We built each assessment from the frameworks, benchmarks and failure modes we keep running into in the field. Each one scores you against how the rest of the market is doing and returns a report you can forward. Nothing you answer is stored in the report itself.

There are three, and each points at a different outcome question.

AI ROI Assessment (The AI Accountability Gap). Nine questions, about two minutes. It shows where your program really stands and where the need is greatest, so you know where to look first. Forward the report to the CFO or an operating partner and both sides argue from the same page. Start here if your question is “is any of this working?”

Agentic GTM Field Guide. Twelve questions, about two minutes. It places your revenue engine on an agentic maturity scale and names the one move to make next, so the next dollar goes to one move instead of ten. A revenue team usually carries ten priorities. This gives it one.

AI-Native Gap (CRFT agentic candidate assessment). Sixteen questions, about three minutes. It asks which of your systems is a real candidate to become agentic, and whether you can rebuild it while it keeps running. You get back a ranked shortlist and a capacity verdict. The second half matters most. A system can be an ideal candidate and still be one your team has no room to touch, and a rebuild that stalls produces a demo, not a result.

What a score can and can't do

We'd rather say this plainly than let you find it out. The number is a starting point, not a verdict. It can't account for your stack, the state of your data, or who owns the outcome. It also doesn't measure the outcome itself. That takes your own numbers. Anyone selling certainty from nine questions is selling something other than analysis.

What the score can do is more modest and more useful. It names where your program is thinnest. It gives a skeptical colleague something concrete to challenge. It turns “I think we're behind” into a statement someone can test. And it moves the conversation from what the program produced to what the business got.

Consider a common version. A COO believes adoption is strong because licenses are active and the usage dashboards look healthy. A CFO believes the program is a cost center because nothing has shown up in the numbers. Both are reading real data. The COO is reading output. The CFO is looking for outcome. Neither is wrong, and the two have never been lined up.

Run the same assessment independently and the gap between their answers becomes the first honest map of the program. The conversation that follows stops being about whose instinct is right. It becomes about one question: which result is this program supposed to deliver, and whose name is on it?


Start with the question you can't answer today. Is any of this working?

All three sit on the Analysis Tools page.

Then bring the result to a session with us. We'll go through the report line by line and tell you which result to go after first.

AWSM DSPTCH

Get the dispatch.

Perspectives on AI activation — ROI, frameworks, and lessons from the frontier — sent when we publish. No noise.

How often?

We respect your inbox. Unsubscribe anytime.