Most "no marketing team" advice still quietly assumes there's a team of some kind — a cofounder to nudge you, an assistant to schedule things, an intern to chase the calendar. We've written the full playbook for running content marketing without a marketing team, and it holds for any small company. But if you're genuinely solo, you already know the part it can't fully cover: there is no one to hand anything to. Not the scheduling, not the chasing, not the "can you just post this." Everything either fits inside your week or it doesn't happen.
This post is the solo adaptation. Same principles — keep the decisions, delegate the production — rebuilt around the constraints that only apply when the whole company is one calendar: marketing competes directly with revenue work, context-switching costs more than the hours do, and the failure mode isn't bad content. It's burnout.
The solo constraint, stated honestly
Start with what's actually different, because it isn't the hours. A five-person startup and a solo founder might both have three hours a week for marketing. The difference is what those hours displace and what they cost to access.
When you're solo, every marketing hour is subtracted directly from billable or buildable time. There's no abstraction between "time spent on content" and "revenue not earned" — it's the same hour, which is why solo founders abandon content faster than teams do. The opportunity cost sits right there, glaring at you.
The second tax is worse and mostly invisible: context-switching. Writing a LinkedIn post between two coding sessions doesn't cost thirty minutes — it costs thirty minutes plus the ramp back into deep work on either side. Sprinkle five small content tasks across a week and you've fractured five work sessions, not spent two hours. The real currency isn't hours; it's uninterrupted blocks, and naive content advice spends them recklessly.
Third: there's no redundancy. On a team, if you're sick or shipping a release, someone else keeps the cadence. Solo, a bad week for you is a bad week for the channel — and a string of them becomes the quiet abandonment that kills most founder content programs by month three. Any system you adopt has to be designed around those three facts, not around the fantasy version of your calendar.
What should a solo founder cut entirely?
Cut every channel except one home base plus one distribution feed, every format you can't repeat weekly, and every polishing pass beyond the second. That's the answer in one sentence; here's the reasoning behind each cut:
Extra channels
One blog you own, one feed where your buyers already are — for most B2B founders, LinkedIn. A third channel doesn't add a third of the results; it adds a third context to switch into. Kill it without ceremony.
Production-heavy formats
Video, podcasts, designed carousels — anything with a production chain longer than "write, review, publish." Unless the format is your natural medium, the setup cost eats the block of deep time you were protecting.
Perfectionism
Two passes, then publish. The bar is "clear and true," not "impressive." A third editing pass rarely changes what a reader takes away, but it reliably steals the hour that next week's post needed.
Measurement theater
No dashboards, no attribution tooling, no weekly analytics review. Check three signals monthly — branded search, "how did you hear about us," AI-assistant mentions — and spend the reclaimed time publishing.
Notice the pattern: everything cut is something that consumes founder attention without compounding. What survives — one home base, one feed, a repeatable format, a two-pass bar — is the minimum machine that still compounds. If you want the fuller architecture behind that machine, the guide on how to build a content engine walks through every moving part.
The three-hour loop for one person
The parent playbook budgets three founder-hours a week. Solo, the same three hours work only if you change when and how they're spent — the adaptation is batching, because the enemy is the switch, not the clock:
- Capture: 30 minutes, spread thin on purpose. Keep one running note. When a sales call, support thread, or build decision surfaces a question worth answering publicly, add a line. This is the one task that should be sprinkled — it takes seconds, needs no ramp-up, and by Friday the note is next month's topic list.
- Review: one 90-minute block, same slot every week. This is where you edit the drafts produced for you — sharpen the opinions, cut the generic, make it sound like you. Anchor it to a fixed calendar slot next to your other shallow work (admin day, invoice hour), never adjacent to deep build time. One block, one switch, done.
- Show up: two 15–30 minute passes. Reply to comments and DMs on the feed. This is phone-tier work — it fits the gaps you already have (the commute, the coffee) and costs no deep-work blocks at all.
Two things make this loop hold for one person. First, decisions are quarterly, not weekly: audience, topics, channel, and cadence get one revisit per quarter, so the weekly loop is pure execution with nothing to deliberate. Second — and this is non-negotiable — drafting, scheduling, and publishing are not in the loop. The moment they are, three hours becomes eight, the eight collide with a customer deadline, and the whole channel goes quiet.
How do you delegate when you can't hire?
Two realistic options: a freelancer who takes drafting off your plate, or a content engine that takes drafting, scheduling, and publishing off it. The difference matters more for a solo founder than for anyone else.
A freelancer removes the writing, not the operating. You still write the briefs, keep the calendar, chase the drafts, and manage the relationship — and management is precisely the kind of fragmented, interruption-shaped work the solo constraint can't absorb. Hiring a writer quietly makes you a part-time content manager, which is the second job you were trying to avoid.
An engine removes the operating too. A managed content engine takes your positioning and your captured topics, and handles strategy, calendar, drafting, and publishing as one loop — your role collapses to the 90-minute review block. That's the configuration that actually fits inside three batched hours, because everything outside those hours runs without you. It's also typically cheaper than the freelancer path once you price your own management time at anything above zero.
Neither option gets to own your point of view. The opinions, the takes you'd defend on a call with a customer — those stay yours, captured in the running note and enforced in the review block. If you're weighing whether the engine route fits your specific stage and setup, the honest self-assessment at is this for me is the fastest way to find out.
The burnout rule: build for your worst week
Here's the rule that decides whether any of the above survives past March: set your cadence for your worst week, not your best one.
The mechanism is simple. Content compounds through consistency, and consistency breaks at the weakest week — the launch crunch, the flu, the client fire. A cadence calibrated to your energized weeks will meet a bad week eventually; the miss becomes a broken streak, the streak becomes guilt, and the guilt becomes "pausing for now." Solo, there's no colleague to catch the drop, and the pause is usually permanent.
So run the test before you commit: picture your worst realistic week and ask what still ships. If the answer is "nothing, but I'll catch up," the cadence is wrong — cut it in half. One post a week you never miss beats three you abandon, because the compounding never restarts from zero.
Better still, design a system whose worst-week requirement is zero founder-hours. When production and publishing run outside your calendar, a week where you contribute nothing is a week where the channel coasts instead of stopping — drafts still publish, the cadence holds, and you come back to a live channel, not a cold one. Solo means the decisions are yours. It should never mean the machine stops when you do.