A grid of small circles on a navy field, most of them empty outlines, with a scattered minority filled in solid yellow

    August 1, 2026 · Julian Bowman

    You Probably Don't Need AI

    Strange thing for an AI company to say, we know. But we've now watched enough businesses buy this stuff before anyone worked out what it was actually for that we'd rather get it out of the way early. AI works. We use it every day, it's changed how we run, and that's a big part of why the way it's currently being sold gets on our nerves.

    Nearly all of it runs on fear. Move now or fall behind, your competitors are already ahead of you, the window's closing. It sells beautifully. What it mostly produces is a lot of expensive software wandering around a business looking for a job to do.

    Some businesses should just wait, and if yours is one of them we'd honestly rather say so than take the money. There are four reasonably reliable signs, which we'll get to. If none of them land, the second half of this is what's been working for us, and it's a good deal less complicated than you'd expect.

    Everyone has started. Almost nobody has finished.

    McKinsey put this to 1,993 people across 105 countries last November, and the drop-off between starting and getting anywhere is the whole story.

    Fig. 1
    Enthusiasm was never the bottleneck.
    Using AI somewhere in the business 88%
    Can point to any effect on enterprise EBIT 39%
    Reckon they have actually scaled it 7%

    Source: McKinsey & Company, The state of AI in 2025, November 2025. The 7% comes from their follow-up analysis in December.

    Bain arrives in the same place from another direction, with fewer than a fifth of organisations having scaled generative AI in any way they'd call meaningful. None of which says the technology is a dud. It says most attempts die somewhere between the demo that impressed everyone in the room and anything that changes how the work actually gets done.

    Hardly any of this is a technology failure. It is tools bought before anyone named the job.

    Which is worth sitting with for a second, because it changes what you think you're buying. AI isn't an answer, it's a tool, and a good one. It makes a team sharper at problems they already understand and quicker at work they already do. It won't hand you a strategy you haven't got, unbreak a process that's broken, or tell you which parts of the business are worth fixing in the first place. Aim it at something well understood and it's genuinely brilliant. Aim it at "we should be doing AI" and you'll end up in the 61% with nothing to show at enterprise level.

    Four signs it isn't your turn yet

    These are the ones where we'd tell you to go and spend the budget elsewhere. Not for ever. Just not this quarter.

    01
    You're short of customers, not hours
    If the team has slack in the week and what you're actually short of is demand, handing everybody eight hours back doesn't fix anything. Go and fix the pipeline. This will keep.
    02
    Nothing you do happens twice the same way
    Properly bespoke, low-volume work leaves it no pattern to get hold of. Plenty of good businesses are like this and there's nothing wrong with being one of them.
    03
    Nothing's written down, and nobody's going to start
    This is the big one, and most of the rest of this article is really about why. If your standards, pricing and methods only live in people's heads, there's nothing for any of it to stand on.
    04
    Nobody is going to own it
    Not a working group. One named person with real time in their week for it. If they don't exist and you're not willing to invent them, you already know how this ends.

    Two or more of those and we'd point you at whatever's genuinely holding the business back instead. That isn't us being coy about wanting the work. A decent slice of what we get asked to build shouldn't be built, and working that out in a first conversation is a lot cheaper for everybody than working it out in month four.

    What it looks like when it does stick

    We're an AI-native company so we're an easy case, and you should discount our numbers accordingly. The bit we didn't see coming was where the time came back.

    Fig. 2 · Our own team
    Hours back per week, and not one of them an engineer
    Illustrative. Our own team, self-reported, and we are still refining how we measure it.
    Developer ~10h
    Jira and Xray tests · scope pricer · sprint readiness · code and PR helper
    Project manager ~8h
    Meeting follow-up · sprint dashboards · retro logger · status packs
    Sales ~7h
    Proposal builder · branded decks · weekly leads plan
    Operations ~6h
    Meeting follow-up · retro logger · document generation
    HR ~4h
    One-to-one prep · job specs · candidate assessment

    That caveat stays attached, because anyone quoting you a tidy productivity percentage for something this new is telling you a story rather than a finding. What we're confident about is the shape of it. The gains landed hardest on the people who spend their days turning context into documents, which is most of a business and almost none of its engineering.

    So how do you get there

    We gave a version of this at the Civitas AI Conference recently, to a room full of local businesses who wanted to adopt AI and mostly weren't sure where to begin. Five things came out of it.

    1. The part everyone skips is context

    Your competitor can license the same model this afternoon, for the same money, and have it running by dinner. What they can't get hold of is your clients, your pricing, the reasoning behind decisions you made three years ago, or the way you actually win work, which isn't written down anywhere and certainly isn't what the website says. Take that away and you get generic output, which is exactly what people mean when they say the first month was underwhelming.

    The model is rented. Your context is owned.

    2. Your knowledge comes in two kinds

    Treating both halves the same way is the thing that quietly kills these projects about six months in. They want opposite handling.

    Static
    Barely changes
    Standards, methods, strategy, pricing.
    Curate it
    One small guarded place. A human approves every change. Every fact carries a date, because a confident stale answer does more damage than no answer at all.
    Dynamic
    Changes hourly
    Email, calls, transcripts, your CRM.
    Never copy it
    Leave it in the system that owns it and read it live. A copy is stale the moment you make it, and nobody trusts it again afterwards.
    Connect, don't copy. The source is always fresher than your snapshot.

    3. Two loops, and you can start the first one this week

    You don't need a finished knowledge base, you need a first one and some way for it to grow. That's loop one, and it's an afternoon's work. Loop two is the one that stops the whole thing rotting once real work starts moving through it.

    Loop one
    Getting it started
    01  Pick a store. Notion or Confluence will do.
    02  Let AI distil the documents you already have into it.
    03  Point a Project at it and do real work inside.
    04  Feed what you produce back in.
    ↻ It compounds from here
    Loop two
    Keeping it true
    01  Delivery captures context on its own.
    02  AI drafts it clean from the raw mess.
    03  A human blesses it, and dates it.
    04  It lands in the core as truth.
    Honest bit: the capture works fine. Step three is the one we're still tightening, and it isn't a technical problem.

    4. Build skills on skills

    Teach it your house style once and never explain it again. Everything built on top of that inherits it for free, so each workflow skill only has to do one actual job.

    Proposal builder
    Client proposal, from our knowledge
    Quoting
    Scope in, consistent price out
    Meeting follow-up
    Recording in, notes and actions out
    Monthly one-to-one
    A balanced view of the month
    ↑ all inherit from ↑
    Foundational skills, written once
    Word, house style PPTX, on brand HTML, built on both

    5. Why our team adopted it so fast

    This is the one that surprised the room, because it wasn't training and it wasn't enthusiasm. Nobody on our team has unlimited usage, and that turned out to be the whole trick.

    $25
    Standard seat, per month. Around three quarters of the team.
    $125
    Premium seat. Granted by role, and people motivate for it.
    Capped
    A small overage, so no surprise bills at month end.
    Because usage was finite, people learned to manage context windows, tokens and model choice. Hand everyone an unlimited licence on day one and none of that discipline ever forms.

    We didn't design it that way on purpose, which is a bit embarrassing given it turned out to be the cheapest training programme we've ever run. The other half was letting people mess about first, share whatever worked, and only then hardening the good ones into something everybody gets.

    The whole talk
    All five of these go quite a bit deeper than the version above, and we've written the lot up properly, along with the ecosystem diagram and the connector setup that sits underneath it.
    Getting the most out of Claude →
    riivo AI Blueprint
    Not sure whether you're one of the businesses that should wait?
    That's what a discovery call is for. We map how your processes actually run rather than how the manual says they run, work out where the time really goes, and only then look at whether AI earns a place in any of it. The four-week Blueprint after that only makes sense if it does.
    The call's free, and if the answer is that you'd be better off spending the money elsewhere this year, we'll say so.
    Book a free discovery call →

    References

    • McKinsey & Company. The state of AI in 2025: Agents, innovation, and transformation. November 2025. mckinsey.com
    • McKinsey & Company. AI at work but not at scale. Week in Charts, December 2025. Source of the 7% figure. mckinsey.com
    • Bain & Company. How Do Companies Create Value with AI? June 2026. bain.com
    • The 61% is our own arithmetic, being the share that did not report enterprise-level EBIT impact in the McKinsey survey.
    • Per-role time savings and licence mix: riivo internal, self-reported and illustrative. Seat prices are Anthropic's published monthly rates; annual billing is lower.