I help solopreneurs get organised. I help them build systems. I help them stop doing everything by hand and start letting their tools do the heavy lifting.
And for the better part of this year, my own content system was held together by good intentions and a half-finished Canva template.
Sound familiar?
The thing nobody tells you about content
The problem was never that I didn't know what to write. I had ideas constantly, in the shower, on a walk, mid-client meeting when I really should have been listening. The problem was that those ideas evaporated before I could do anything with them, and then two weeks would go by and I'd realise I hadn't posted anything, hadn't sent a newsletter, hadn't shown up anywhere at all.
That's not a motivation problem. That's a systems problem. And systems problems are, fortunately, my thing.
So I decided to build one.
Two sessions, two very different conversations
I built One Step Calmer across two working sessions with Claude, and they were nothing alike.
The first session was a conversation. I didn't come in with a brief. I came in with a feeling, something like "I want to create content that actually means something to the people who read it, not just stuff that fills a grid." We talked about what I wanted to say, who I was saying it to, and why any of it mattered. By the end, we had a writing skeleton: Mirror it. Name it. Shift it. Make it real. Hand it back. Five moves. Every edition follows them. That session produced the soul of the project.
The second session was structured. I came in knowing what I wanted to build, and we built it: the platform formats, the trigger words, the Airtable connection, the production rhythm. That session produced the bones.
Neither one would have worked without the other. The soul without the system is just vibes. The system without the soul is just output.
Soul first. System second. In that order, always.
Friction is information
Every time a solution we landed on felt clunky, I said so. Copy-pasting between tabs, pipe-separated fields I had to type on my phone, a form that didn't route where it was supposed to. Each time, we redesigned it.
If it was too fiddly for the person who builds automation systems for a living, it was absolutely too fiddly for my clients. That instinct to push back on anything that added steps turned out to be the most important design principle of the whole build. Friction is information. If something feels hard, it's telling you something.
And it turns out, not being a developer is its own kind of quality control. I caught every friction point because I experienced them as friction. I asked all the "but why can't it just..." questions. Those questions are exactly what produced a better system. That's not a limitation. It's calibrated exactly to the people I work with.
The pivot that made the rest of it unnecessary
We'd built the whole pipeline in Google Sheets. A form, an Apps Script, a tracker. It worked. And then I stopped and asked Claude to rethink the whole process, to look at what connections were already in place and work out whether there was a better way that didn't involve me copying and pasting anything.
Turns out, Airtable was already connected to Claude. Directly. Claude can write to my Airtable pipeline automatically, every time I capture an idea. No form. No script. No copy-paste. Just: idea captured, pipeline updated, done.
The whole Google Sheets setup became unnecessary in about 30 seconds. And I didn't feel bad about that for a single moment.
The lesson: always ask if there's a better way before you settle for what works.
What actually exists on the other side of this
When both sessions were done, here's what we had built.
- A Claude project with a full set of instructions covering my brand voice, how I write, what I'd never say, who I'm talking to, and a content engine that takes one blog post and turns it into platform-specific pieces for LinkedIn, Facebook, Instagram, and email. Not one post copy-pasted four times. Four different versions, each written for how people actually read on that platform.
- A live connection to Airtable that captures every idea I have directly into my content pipeline. The connection between Claude and Airtable was already there. What needed building was the table itself. So we worked out exactly what fields were needed and why, turned that into a prompt, handed it to Airtable's own AI, and it built the whole table. Every field, every option. No sitting there creating each one manually, no dropdown options typed out one by one. Described it once, and it was done.
- A set of trigger words that mean I can start any content task — capturing a raw idea on my phone, building a full month of content, writing a spontaneous post — with a single word and a sentence.
And then the question I know some people will ask: if Claude is writing the content, is it actually mine?
It is. Getting to a place where Claude writes in my voice didn't happen overnight. It happened over months of conversations, across dozens of chats, because I fed it content I'd already written, walked it through who I help and why, explained how I talk to clients and what I'd never say. My brand voice in Claude is built from real input. Real history, real business context, real personality. And it's ongoing. The more we work together, the more refined it gets.
Every piece of output gets reviewed by me before it goes anywhere. I read it, tweak it, fix the bits that don't quite land. If something sounds off, I change it. Claude produces the first draft at speed — I make sure it actually sounds like me before anyone else sees it.
There's one more step I've added that makes the whole thing smarter. At the end of longer working sessions, I ask: what did we learn, what needs to be updated, what could we do better next time? It's become one of the most useful things I do. It means the system doesn't just run — it improves.
It's not AI replacing my voice. It's AI helping me use it more consistently, more often, with a lot less friction.
One Step Calmer comes out monthly. One blog post, one newsletter, a month's worth of social content. All produced in roughly two hours once the system is running.
Before you build anything — a content system, a client process, a filing setup — ask yourself one question: what's the one thing that keeps breaking down in how you currently do this? Not what platform should I use, not what does everyone else do. Just: where does it fall apart?
Start there. Fix that. Soul first. System second.
Organise · Automate · Breathe.