What teams actually ship after a one-day AI workshop

An L&D lead asked me a fair question on a call last month: "If I book my team a one-day AI workshop, what do they actually have at 5pm? Be specific. I've sat through too many days that ended with a feedback form and nothing else."

So let me be specific.

This post is the honest version of what marketing, ops, sales, and leadership teams realistically ship after a single day with us — and how to think about whether it was worth it, without me waving made-up numbers at you.

First, what "ship" means here

When I say a team ships something, I mean there's an artefact at the end of the day that exists outside the workshop. Something you can open on Monday. A URL. A working tool. A documented automation that runs.

Not notes. Not a deck. Not "exposure to concepts."

That distinction is the whole game. A team that watched a day of AI content has a vocabulary. A team that built for a day has a skill they can repeat — and, crucially, an artefact their colleagues can see and ask about. The thing on the screen is what turns one day into a habit.

So here's what that artefact tends to look like, by team.

What marketing teams ship

Marketing is usually the easiest team to point at a quick win, because so much of the work is repeatable production with a human-judgement layer on top.

The common build is a draft-and-review workflow for something the team does every week — a campaign recap, a batch of social posts in the brand voice, a first-draft newsletter, a competitor scan. The team brings their actual brand guidelines and a real past example, and we build a workflow that produces a first draft in their tone, with the human firmly in the review seat.

The important word is draft. Nobody walks out having automated their judgement away. They walk out having removed the blank-page friction between an idea and a usable starting point.

What ops teams ship

Ops is where I most often see a small internal tool get built — the kind of thing that used to require a developer ticket and a three-week wait.

A simple intake form that sorts and routes requests. A checklist app that enforces a process everyone keeps skipping. A little dashboard that pulls a messy spreadsheet into something readable. A document that drafts itself from a few inputs.

These are unglamorous, and that's exactly why they matter. They're the small recurring annoyances that never make it onto a roadmap because they're not big enough to justify engineering time — but they quietly cost the team an hour here and an hour there, every week.

What sales teams ship

Sales teams usually leave with an assistant for the parts of the job that aren't selling.

Pre-call research pulled together from a few sources. A follow-up draft that's specific to the conversation instead of a template. A way to turn rough call notes into a clean CRM entry. A first pass at a proposal from a short brief.

Same principle as marketing: the human stays in the relationship. The build just removes the admin tax that eats into the hours reps would rather spend talking to people.

What leadership teams ship

Leadership sessions are a little different. Sometimes a leader builds a tool of their own — a board-update drafter, a quick way to summarise a long thread. But often the more valuable thing they ship is judgement: a grounded, first-hand sense of what this technology can and can't do for their org, built by actually doing it rather than reading a forecast about it.

A leader who has spent a day building is a much harder person to sell vapourware to. That alone has paid for a few of these workshops.

Why a build beats slideware

I'll keep this short, because I've made the longer case in what real AI training for teams looks like. But the core of it is three things.

Watching is not doing. Nobody learns to ride a bike from a deck about bikes. AI is the same. The understanding only arrives once you've sat with a real tool, given it real input, gotten something wrong, and fixed it.

Generic examples don't transfer. "Here's how AI could help with sales emails" lands as theory if the email isn't yours. The bridge from the example to the actual job gets left unbuilt, so people nod and then never act on it. We build on your work, with your data, so there's no bridge to cross.

No artefact, no momentum. A team that leaves with a certificate has nothing to point at next Monday. A team that leaves with a working tool has a thing their colleagues notice — and noticing is how the second build, and the third, get started.

How to think about ROI (without me inventing a number)

People ask me for the ROI figure. I'd rather not make one up, and you should be suspicious of anyone who does.

The honest framing isn't "how many dollars per training hour did we save?" It's "how much faster can the team move on things they already want to do?" Good AI training doesn't replace anyone's job — it removes the friction between an idea and the output. The unlocked velocity is the return. It's real, and it's genuinely hard to put a clean number on in a quarterly review.

What I can tell you is how to test it yourself.

The teams that get the most out of a workshop usually do one small thing afterward: they pick one of the things they built, give it an owner, and agree to actually use it for two weeks. That's it. The build creates the possibility; a named owner turns it into a habit.

Choosing a format

A rough guide, since this is the question that follows next:

• Half-day is a focused single build. Best for one team with one clear, shared pain point.
• Full-day lets a few small groups each build a different thing, then demo to the room. Best when a team has several recurring annoyances rather than one big one.
• Weekend intensive goes deeper — bigger prototypes, more iteration, more "what do we roll out across the company?" conversation. Best for leadership or a team treating this as a genuine kickoff.

We pre-scope every one of these with the team lead beforehand, so the room walks in pointed at a real outcome instead of "AI literacy in general." Prices vary by format and team size and are shown at booking — if you want market context on how this kind of training is priced in the region, the Singapore and Hong Kong price guides are a fair starting point.

So — what will your team ship?

I genuinely don't know yet, and that's the point. The answer depends on the recurring annoyance your team would most like to hand off, and we figure that out together before the day.

If you've got one in mind — the Monday report nobody wants to write, the intake process held together with copy-paste, the follow-ups that pile up — that's exactly the raw material for a workshop. Have a look at how we run these on the companies page, then book a free discovery call and tell me what your team would build. No slides on that call either.

— Mr. Brown