10 meditation scripts to a complete content engine, in 4 weeks.
How a London-based meditation teacher and former Buddhist monk turned a hard drive of unused content into an AI-powered business with corporate proposition, content engine, and competitive intelligence - all delivered as files he owns forever.
01The situation
David Butcher had a problem most experienced practitioners have. He'd been teaching mind management and meditation for over two decades - first as a Buddhist monk, more recently to corporate audiences and senior leaders through Positively Aware. The expertise was deep, the track record real. But the body of work - meditation scripts, talks, presentations - sat on his hard drive, mostly unused.
He'd tried ChatGPT. Got the same response most experienced people get when they try ChatGPT for the first time: generic mindfulness-influencer copy that sounded nothing like him. A few attempts later he stopped trying. The conclusion he'd drawn - and that most of his peers had drawn - was that AI “didn't work” for his kind of business.
What he actually needed was the layer underneath - voice captured properly, audiences mapped properly, competitors understood properly, a workspace configured to use all of it. Without that infrastructure, no AI tool can produce work specific enough to be useful.
02What we built
A four-week AI Blueprint engagement. Nine deliverables, plus a fully configured Claude Project ready to use on the day of handover.
The voice work was the linchpin
David has three distinct voice registers - the teaching voice, the personal-story voice, and the speaking voice. Each is used for different contexts, has a different tonal centre, and uses different language patterns. Capturing all three from the raw source material (meditation transcripts, talks, personal essays) took three days. The first version went to v1.1 after his feedback - the third register only emerged once he saw the first two written down and could feel the gap.
By handover, the voice doc was substantial enough that AI-generated content using it sounded like David to David. That's the bar.
The competitor research surfaced something useful
The 5-competitor Intel Report covered the obvious players in corporate mindfulness - Headspace for Work, Calm Business, and three smaller boutique practitioners. The most valuable finding was a near-identical language overlap with Ruby Wax - same phrasing for similar concepts, which would have caused accidental positioning collision if not surfaced and adjusted.
The PDF deliverable became a useful artifact in its own right. David has since used sections of it in conversations with potential corporate clients to demonstrate market understanding.
03The outcome
“I produced a month's worth of content in an afternoon. Felt like a different business overnight.”
David Butcher, Founder, Positively Aware
The real outcome is qualitative, not just quantitative. David has gone from “AI doesn't work for my business” to a workspace that produces on-brand content, corporate proposals, and content repurposing on demand. The system runs in his own Claude account - no platform lock-in, full ownership of all files.
- Content production unblocked.
LinkedIn drafts, talk outlines, podcast briefs - all produced from existing meditation script content. The hard drive of unused material became active raw material.
- Corporate proposition sharpened.
Audience personas distinguished four distinct buyer types. The corporate buyer persona in particular gave him language he hadn't been using - now used in proposals to senior teams.
- Competitive position clearer.
The Ruby Wax language overlap finding alone protected David from accidental positioning collision. Other competitor analysis informed how he frames Positively Aware vs Headspace for Work.
- Strategic direction documented.
The opportunity map surfaced 19 directions worth considering, ranked by feasibility. Six emerged during the build itself - including a "Mindful Thought of the Day API" concept now scoped for a future Sprint.
04What we'd do differently
The engagement landed well. The Blueprint product is now better calibrated for it. But there were three things worth flagging - both because future engagements benefit from them and because honest case studies should include them.
Voice v1.1 was expected. We should have planned for it.
The third voice register only emerged once David saw v1.0 written down. We treated it as iteration - it should have been a planned step. Future engagements explicitly schedule a v1.1 cycle after mid-engagement review.
Competitor research took longer than budgeted.
Five competitors at substance took 10+ hours rather than the 6-8 we'd estimated. We now budget a full week for competitor research and don't try to do other substantive work in parallel.
The Competitor Intel PDF layout iteration was significant.
Page numbering, page breaks, and layout polish on a 14-page branded PDF took 4-6 hours we hadn't fully accounted for. The Blueprint price now includes this work explicitly rather than absorbing it.
These are the kind of things you only learn by delivering the work. Worth being transparent about them - and worth knowing that future Blueprint engagements benefit from them being identified.
A visitor who's read this far is usually the right kind of visitor to book a call.
Book a 15-min call →15 minutes. Honest answer, even if it's “not yet” or “not us.”
This is our first published case study.
More are in progress and will be published as engagements complete and clients give permission.
See all work →Ready for your own Blueprint?
15 minutes to walk through your situation. Honest answer on whether the Blueprint is the right shape - or whether something smaller fits.