The situation
He had the audience, the knowledge and the sense of humour. What he did not have was a spare evening every week to face a blank page. So nothing got published, which is the most expensive outcome there is.
← All work
TF Medical · Healthcare
How a working GP started publishing every week in about twenty minutes
TF Medical is run by a practising GP who wanted to write a weekly newsletter for trainees, covering the guidance and news that actually changes how they work.
- Sector
- Healthcare
- What we built
- Content systems
- Sends automatically
- Never
- Built on
- Claude, Kit, a written voice card
Before
A blank page, and no evening to face it
After
About 20 minutes, weekly
How it works
The system, step by step
A person stays in control here
- 1Automatic
Weekly sweep of approved sources
NICE, RCGP and others he chose
- 2Automatic
Recommends what to lead on
- 3A person
He picks and adds his take
- 4Automatic
Issue drafted in his voice
From a signed off voice card
- 5A person
He reviews and sends
Nothing sends on its own
What we built
Not a newsletter that writes itself. A system he runs. Once a week it sweeps his approved sources and recommends what to lead on. He picks, and gives his own take, because that is the part nobody can outsource. Then it drafts the issue in his voice. It never sends. He does.
The voice is not a guess
Built from his own writing. Two comedy sketches, a scoping call, a banned words list, and a signed off voice card covering tone, rhythm and exactly where the jokes stop.
What we found that they did not know
The first design ran on a schedule and waited for him. Obvious, and wrong. The moment a system needs a human opinion mid run, a timer is the enemy. Rebuilding it as something he drives made it simpler and deleted a pile of moving parts.
The thing that would have broken the handover
The generated HTML could not be pasted into his email platform. The template lives at account level; a broadcast holds only content. Found before delivery rather than three weeks after.
The result
- ✓About twenty minutes to produce an issue, weekly
- ✓Written in his own voice, from a signed off voice card built out of his own writing
- ✓Governance rules on anonymisation and disclaimers override voice and structure, always
- ✓Runs in his own account, on his own subscription
- ✓Nothing is ever sent automatically
He writes it. The system does everything around the writing.
What they own
The whole thing runs in his own account, on his own subscription. The reference files, the voice card, the source list and the governance rules are all plain documents he can read and change himself.
There is no server, no monthly fee to us, and nothing that stops working if we do.
This was FHAi’s first paid engagement.
More work
Document automationOutsourced HR
How People Matters HR turned hours of document branding into a 10 minute job
Before
3 to 4 hours per client
After
About 10 minutes
Event registrationsCommunity and events
How Active Inclusion Network stopped retyping every registration by hand
Before
Export, clean, retype, every event
After
Syncs every 4 hours
Free 30 minute call
Tell us what's eating your week.
You leave with two or three ways to save time, whether we work together or not.