What we build
Most people arrive with something specific that isn't working. A process that eats a day a week. A document they rewrite every time. A system that made sense two years ago.
That's usually where we start. Below is a picture of what's possible. But each should be tailored specifically to you and how you work. Because real AI fluency isn't a product you purchase, it's a practice you develop.
The first conversation is free. Not a pitch, a conversation. If what you need isn't something we should build, we'll say so.
Where the time goes
| What's eating your time | What's possible |
|---|---|
| Explaining your business from scratch every time you open a chat | A working library it reads before it answers, so context builds instead of resetting |
| Writing the same proposal, report or outline in a slightly different shape each time | A builder that drafts in your structure and your language from your own past work |
| Recordings and call notes you'll never listen back to | Conversations turned into summaries, decisions and follow-ups — and into the deck or document they were meant to produce |
| Losing track of who you're talking to and what you owe them | A simple client and pipeline record you can keep current in minutes |
| Content taking a day a week you don't have | A workflow from idea to draft to published, with a record of what actually landed |
| Course and programme communications rebuilt every cohort | Enrolment, pre-course and follow-up sequences drafted from materials you already have |
| Client breakthroughs you can't recall when the renewal conversation comes | Insight captured as it happens rather than reconstructed months later |
| Video that never gets made because the process is too long | A production pipeline from script through to post |
| The follow-ups, reminders and small obligations that never end | The admin layer around your work, scoped carefully — some of it is worth automating and some of it isn't |
| Something not on this list | Most builds start as a description of a problem. Worth a conversation. |
Task-level, not job-level
In late 2025, MIT's Media Lab and Oak Ridge National Laboratory published Project Iceberg — a simulation of 151 million workers as individual agents, mapped across more than 32,000 skills and 3,000 counties.
Visible AI adoption accounts for about 2.2% of wage value, concentrated in computing and technology. Technical capability extends to roughly 11.7%, spread across administrative, financial and professional services. Fivefold larger than what's showing, and distributed across every state rather than a handful of coastal hubs. Hence the name: most of it is below the waterline.
The paper is careful about what that number means, and it's worth quoting the framing rather than the headline: the Index captures technical exposure — where AI can perform occupational tasks — not displacement outcomes or adoption timelines.
That distinction is the whole point, and it gets lost constantly. CNBC ran the finding as "AI can already replace 11.7% of the U.S. workforce," which is precisely the conflation the researchers refused to make. A task being technically exposed is not a person being replaceable. Jobs are bundles of tasks, and the bundles don't come apart evenly.
Which is why we work at task level. Not "can AI do your job," but: which parts of this specific process are mechanical, which parts are judgement, and where does the time actually go once you separate them?
Below is one example, broken down properly.
A worked example: producing a commissioned article
Producing a commissioned article: a stage-by-stage comparison of how the work was done before and how it is done with AI partnership.
Before, an idea sparks from somewhere — another story, a lateral connection, something subconscious. It gets developed by your own research, talking it through with a colleague, or in the morning meeting with the editor.
The meeting still happens. What changes is how far the idea has travelled before you walk in. Pressure-test it with AI first and you arrive with something substantial rather than a hunch.
A meeting between people, and it stays that way.
Two places where AI can help. When an editor pushes back and asks you to confirm figures or sources before green-lighting, that loop closes faster — unless you are waiting on others. And with the right setup and everyone's consent, the meeting itself can be captured and transcribed, with the agreed changes drafted for approval before the room has emptied.
This is where AI shows significant edge — from hours of searching and skimming through a large quantity of material online, to finding the right pieces of the puzzle.
What AI cannot do is taste the wine, talk to the artist at an exhibition, or walk into the LHC and feel its grand scale. Those hours are yours. And they matter the most because they are human — experiences that shape your taste and perspective.
What changes is what happens around them. You talk the experience through, and AI fills the gaps: historic context, what others have written, the detail you missed on the night.
This step is new. Before, gathering and judging happened together — you assessed each source as you came across it, and the verification was distributed through the slow process. But you might get tired and lose focus. The solution was more coffee.
Now the gathering is faster, with one degree of verification baked in. Which means you must reallocate the time you saved to the more important work. Full verification becomes its own deliberate act — this is where more of the time goes now. But instead of the old one-directional search and find, it's a faster, iterative learning process, because you don't know what the AI will come back with. With the right setup, you are usually pleasantly surprised.
Both sides bring bias. Yours comes from experience — the Cognitive Bias Codex maps 188 documented varieties. The model's comes from its training data and the context it has been given. A good partnership corrects for both. A bad one compounds them.
Governed by someone else's diary. But this is usually the meat of the pie.
This is uniquely human — knowing when to push, reading the facial expression before an answer arrives, and being present.
As more organisations adopt AI, these human capabilities will be the differentiator between quality content and AI slop. An intern writing with AI and a reporter with decades of experience will leave the same interview with entirely different stories.
In most cases you don't need to transcribe the whole interview — you mark the audio and extract the quotes you need. But if the editor asks for a full transcript, it could take hours depending on the interview.
Now the whole thing is transcribed before you've left the building, and you ask for a quote conversationally rather than scrubbing audio.
Like the research stage, AI saves you time in one place — so reallocate some of it to verification. Double-check names, titles and key facts. Just like an audio recorder in a noisy environment, AI can mishear too. This is no different from before: use your judgement, and when in doubt, double-check with the source.
Some writers structure the whole picture in their heads as each piece of the puzzle arrives; some do so once they've gathered enough material. Others move subheadings around in a Word document.
Sometimes the piece writes itself. Other times the hardest part is the blank page, or the empty space between subheadings.
Now, instead of starting from a blank canvas, AI structures all the pieces you have available. No procrastination, and no more rearranging subheadings as the clock ticks away.
The real change isn't only efficiency. It's momentum and a clear direction. With the right setup it's like talking it through with a friend or an editor during the coffee break — except there's almost no lag between a new idea and testing it out.
The first draft was usually the first big hurdle — a feedback loop between the piece and yourself.
With your AI partner, the structure and the first draft blend together. After one conversation you are already in the editing phase before you know it.
Writing is rewriting. At its best this was writer, editor, sub-editors and picture desk, each with their own filters — which is why a piece could pass through five or six people and come out transformed. For better or worse, that feedback loop could be smooth or arduous depending on the team and the culture.
With the right setup: you share the piece, everyone contributes in the same chat, and everything gets incorporated with your approval. No more keeping track of long email chains, multiple Word documents back and forth, or debating who should be in the CMS right now.
In SMEs, the editorial team is sometimes one junior staff member wearing every hat at once. AI restores some of what's missing — only if it's used with human judgement rather than replacing it.
Yes, we never put the word 'final' on anything without jinxing it. But you'll be surprised how quickly you can get to a place where you can use that word confidently. Sometimes it's a false sense of confidence — which is exactly why we keep stressing the importance of showing up and maintaining your agency.
If you have access to more powerful models, going through this process with a more advanced one might push the piece further still. Even if that opens another round of feedback, it will still be faster than before, given the right setup.
You or the editor read through everything again, raise anything outstanding, and double or triple-check depending on the piece and its sensitivity. Use alternative sources or methods for any fact-checking at this stage. Asking the same AI that drafted the piece to check its own work is not verification — it's asking for reassurance.
AI empowers you to 'write' less. It does not let you take less responsibility. Show up, read it properly, and check everything thoroughly, every single time. Don't be lazy.
You'd think we'd have this all automated by now. Unfortunately most content management systems are old, and every platform wants something different.
You could automate it, but to be reliable it would need a proper agentic architecture with multiple layers of guardrails — and human judgement may still be required, depending on your distribution platforms.
Between the time it takes to make it reliable, the token cost and the supervision, we don't recommend it. But it's doable.
This is how we work, and the timings are indicative ranges from our own experience across editorial and commercial content — excluding time spent waiting on interviewees and contributors. Every commission differs, and so will your version of this. That is what makes it a practice rather than a template.
The same breakdown, for your work
That's one task. The method is the same whatever the process: separate the mechanical from the judgement, find where the time actually goes, and be honest about the parts AI doesn't improve.
The first conversation is free.