A Note for May

Stop Announcing AI. Draw the Workflow.

Thirteen Reports, Same Conclusion.

Every fortnight, another report confirms it. Ninety-five percent of AI pilots fail to scale. Thirteen reports now, roughly 5,800 respondents across industries, same headline.

The pilots are not failing because the models are not capable enough. They are failing because nobody redesigned the operating model around them.

This is, we have come to believe, the only AI conversation worth having right now. Not which model. Not which agent. The redesign that should have happened in week two, before anyone touched an API key. We tested the argument against our own work this month. It kept landing. Four times.

The Award Was for the Operating Model, Not the Migration.

At Acquia Engage Denver, we picked up the Best Use of Asset Management and Content Workflow award. The client, a UAE consumer cooperative, came to us with two terabytes of legacy creative scattered across laptops, drives, and Magento exports. They did not ask us for a digital asset management tool. They asked us for a system.

Metadata taxonomy first. Role design first. A two-stage Trading-then-Marketing approval flow with the audit trail wired in. Acquia DAM and the Workflow App came after, to make the model real. The judges did not give us the award for moving two terabytes. They gave it to us for the operating model the two terabytes flowed through.

The Same Pattern Showed Up in Our Own Building. Three Times.

Donut, Replaced.

We swapped our Donut subscription on Slack this month for an in-house alternative. No external announcement. No press release. What we have is an alpha tool that pairs people on the same governance model we would propose to a client: who can do what, when, with what audit trail. Pairings live. Watercoolers live. Time off in testing. Projected saving around twelve thousand dollars a year, which is fine, but the saving was never the point. The model came before the build.

Friday Afternoon Stopped Being a Rebuild.

Every engineer here used to end the week the same way: thirty to forty-five minutes of reconstructing five days from memory in Mavenlink. The data already existed. Tickets had moved, PRs had been reviewed, meetings were on the calendar. We built something to read it back. A daily cron, a Claude Sonnet pass, a calendar-style grid that pre-fills the week. Five to fifteen minutes to confirm and sync. The point, though, is not the time saved. Each line item is grounded in a verifiable signal now: a real PR, a real ticket transition, a real attended meeting. Ambiguity is logged as a flag, not buried as a guess. The audit trail came first. The model did the reconciliation. The engineer kept the final say.

Marketing’s Plugin, in Revenue’s Hands.

An industry-campaign-engine plugin that ran inside marketing for two cycles went to the revenue team last week. It built a qualified UK lookalike list, the per-account deep dives that go with it, a full campaign plan, and the ad assets to launch. The first artefact we handed to revenue this month was not a deck. It was a working tool with the shape of the work already in it.

Which Brings Us to the Part Nobody Likes to Write About.

Most of what passes for “AI-native” in our industry right now is a wrapper. Existing workflows, renamed. Existing tooling, sold harder. The same agencies that were selling “digital transformation” two years ago are selling “AI transformation” now, with the same RFP templates and a different colour palette. We do not blame them. The market rewards the claim. We are not in that game.

The honest answer to the “are you AI-native?” question is not a slide. It is the operating model under the slide. The audit trail, the approval gate, the role design, the metadata taxonomy. The boring engineering work that scales the AI when the demo is over. The model is what scales. The technology is just where it lives.

What Booth 1 Looked Like at Engage London.

At Booth 1 last week, we did not run a demo of an agent. We ran a whiteboard, a CMS roster, and a pen. Twenty-minute sessions, both days, with whoever brought a site inventory. We mapped consolidation paths on Acquia MEO, live. No deck. No pitch.

The offer holds outside the conference. If you have an inventory, an asset roster, or an approval map that keeps you up at night, the same whiteboard runs on a call. If we are the right partner, you will know. If not, you will have the artefact anyway.

There will be more announcements next month. There always are. The work we are most proud of this month is the work nobody can announce.

The plugin nobody wrote a press release about. The audit trail that prevented a problem instead of cleaning one up. The approval gate that became an award category. The operating model that came before the rollout.

Until the next one, drink the tea while it is hot.

From the team at Axelerant