I don't have a team. It's me, a laptop, and a publishing schedule that would collapse inside a week if it lived in my head.
I run a small niche content site solo — research, writing, editing, publishing, promotion, all of it. After a few years of doing this the loud way (bursts of motivation, then silence), I rebuilt the whole operation around one idea: the system should be boring, so the work doesn't have to be.
Here's what actually stuck.
1. One calendar, not five apps
Everything I publish — articles, updates, guest posts, social posts — goes on a single calendar. Not a project board, not a notes app, a calendar with dates on it.
The rule that made it work: drafting and publishing are separate events, on separate days. I write things when I have the energy, then schedule them to go out spaced like a person actually lives — one or two a day, never a burst of nine. A queue of finished work sitting between me and the publish button is the whole trick. Motivation fills the queue; the calendar empties it.
2. Two queues, brutally labelled
Every piece of content is in exactly one of two states:
- Ready — finished, checked, could go live today.
- In draft — everything else, no matter how "almost done" it feels.
"Almost done" is where solo operations go to die. If it's not ready, it doesn't get a date. This one distinction killed the Sunday-night scramble completely.
3. Batch by type of energy, not by topic
Research days, writing days, editing days. Switching between them is where my hours used to leak. A research session produces raw material for four or five pieces, not one. A writing session is only allowed to open drafts, never a blank page and a search engine at the same time.
4. One spreadsheet for what happened
I track every piece I publish in one plain spreadsheet: where it went, when, and what it links to. Once a week, ten minutes, I update it and look at what's actually moving. Not daily — daily metrics-watching is just anxiety with charts.
The spreadsheet has saved me more than once. Duplicate content, forgotten follow-ups, a pitch I sent twice to the same editor (once — never again).
5. A weekly review that takes 20 minutes
Same time every week:
- What's in the ready queue? (Less than a week of runway = writing becomes the priority.)
- What's waiting on someone else? (One polite follow-up, then I move on.)
- What did last week's numbers quietly tell me?
That's it. No quarterly planning theatre. The review is small enough that I never skip it, which matters more than it being thorough.
What I'd tell another solo operator
Your system doesn't need to be impressive. It needs to survive your worst week, not showcase your best one. Mine is a calendar, two queues, and a spreadsheet — and it has carried the whole business for years now.
If you run something solo, I'd genuinely like to hear what your version looks like. Especially if it's weirder than mine.
Top comments (0)