An email ops runbook for a solo marketer is a single document that holds your repeatable process for every send, from brief through post-send review. It replaces the habit of keeping steps in your head with a written system that survives busy weeks, client fires, and the inevitable afternoon where you're running on fumes and still need to ship. If you're operating alone, the runbook is your team.
I run a lean operation myself. I've built and shipped email programs from 28 countries, often nine hours offset from the people reading what I sent. The runbook structure I'm sharing here is the one I actually use. It's the minimum viable process that holds under real production pressure without becoming a document you resent opening.
Key Takeaways
- A runbook is not documentation for its own sake. It's the operational backbone that lets you produce consistent sends without relying on memory or motivation.
- Solo marketers need fewer stages, not zero stages. The goal is a process lean enough to follow every time, not one you skip when things get busy.
- AI tools don't replace the runbook. They accelerate the steps inside it. Without a defined process, AI just helps you do undefined work faster.
- The runbook compounds. Every send that follows the process adds to your institutional memory, and that memory is what makes each subsequent send faster and better.
What Should an Email Ops Runbook Actually Include?
A runbook should include the minimum set of stages, checklists, and templates that make your email production repeatable without someone standing over your shoulder. From my experience, most solo marketers either have no documented process at all or have a 40-page SOP they copied from a larger team and never open. Both fail for the same reason: they don't match the way a single person actually works.
The core sections of a solo runbook are:
- Send brief template with pre-filled defaults for your most common email types
- Draft production checklist covering copy, subject line, and CTA requirements
- Build and QA checklist for platform assembly, link verification, and rendering
- Post-send review template for logging performance and one observation per send
- Escalation rules defining what happens when something breaks after you hit send
That's it. Five sections. The email production workflow SOP covers the full enterprise version of these stages. As a solo operator, your job is to compress that into something you'll actually follow when you're the only person accountable.
How Do You Compress a Full SOP Into a Solo Runbook?
Start by asking one question about every step in a traditional SOP: "If I skip this, what breaks?" Any step where the honest answer is "nothing, usually" gets cut. Any step where the answer is "a subscriber sees something broken" stays.
From what I've seen auditing solo email programs, the leak is almost always in the same two places. First, the brief stage gets skipped entirely because the person writing the email is also the person who decided what to write, so the brief feels redundant. Second, QA gets compressed into a quick visual scan because there's no second set of eyes and the send is due in twenty minutes.
Both of these shortcuts create compounding problems. A missing brief means every email starts from a blank page, which is slow and produces inconsistent quality. A skipped QA means errors reach subscribers, which erodes the sender reputation and subscriber trust you've spent months building. The email QA checklist before send gives you the structured pre-send review that catches these failures before they go live.
The compression principle is this: fewer stages, same quality gates. You can combine briefing and drafting into one sitting. You can build and schedule in the same session. But you cannot skip the QA pass, and you cannot skip the post-send log. Those two are load-bearing.
The Solo Email Ops Runbook Template
Here is the runbook structure I use. Adapt it to your platform and send cadence, but keep the stage logic intact.
Stage 1: Brief and Draft (Combined)
Open your brief template. Fill in: send date, email type, audience, core message in one sentence, primary CTA and destination URL, subject line options, preview text. Then write the draft directly below the brief in the same document. Having the brief visible while drafting keeps the email focused and prevents scope creep.
Time target: 45 to 90 minutes depending on complexity.
Stage 2: Build and Schedule
Move the approved draft into your email platform. Apply the correct template, enter all copy, upload images, set links with UTM parameters, configure audience, and schedule the send. Do a quick visual pass as you build. This is not QA. This is assembly.
Time target: 20 to 40 minutes.
Stage 3: QA Pass (Mandatory Gap)
Walk away for at least one hour. Come back and run the QA checklist with fresh eyes. Click every link. Preview on mobile. Check the subject line and preview text in the platform preview. Verify the audience segment. Confirm the send time. If anything fails, fix it and run the checklist again from the top.
Time target: 15 to 25 minutes, plus the gap.
Stage 4: Post-Send Review (Within 48 Hours)
Log open rate, click-through rate, unsubscribe rate, and any conversion data. Compare to your rolling baseline. Write one sentence about what you'd change next time. This is the step that makes the runbook compound over time. Without it, you're producing in a vacuum.
Time target: 10 minutes.
The entire cycle takes roughly two to three hours of working time, spread across two days. That's the real cost of a repeatable email operation for one person. If you're spending more than that on a standard send, something in the process is leaking time.
Where AI Fits Inside the Runbook
AI tools are useful inside the runbook, not as a replacement for it. The distinction matters because from what I've seen, solo marketers who adopt AI without a defined process just generate more unstructured output. You don't need more drafts. You need a system that turns a brief into a finished send with fewer decision points along the way.
Here's where AI actually helps:
- Brief to draft generation. Feed your completed brief template into an AI writing tool and you get a usable first draft in minutes instead of staring at a blank page. The brief is the context layer. Without it, the AI output is generic and costs you more time in editing than it saves.
- Subject line variations. Generate ten options in seconds, then apply your own judgement to pick the strongest two for testing. This is one of the highest-leverage uses of AI in email because subject lines are the variable that compounds across every send.
- QA assistance. Use AI to scan your draft for broken personalisation tags, inconsistent CTAs, or copy that doesn't match the brief. This doesn't replace clicking every link yourself, but it catches text-level errors faster than a manual read.
- Post-send analysis. Paste your performance data into an AI tool and ask it to compare against your baselines. It won't tell you why something worked or didn't, but it surfaces patterns you might miss when you're reviewing your own data alone.
The complete guide to email ops and AI workflows covers the full AI integration model, including the 3-Layer AI OS framework that makes these individual uses connect into a coherent system.
The Three Mistakes Solo Email Marketers Make With Runbooks
Mistake one: building the runbook but not using it. A runbook only works if you open it every time you produce an email. The fix is to make the runbook your production workspace, not a reference document you store somewhere else. I keep mine in the same tool where I write drafts, so opening the document is the first step of every send.
Mistake two: making the runbook too detailed. If your runbook takes longer to read than the email takes to write, you've over-engineered it. Every instruction should be at the level of "do this next," not "here is the philosophy behind why we do this." Save the philosophy for your strategy doc. The runbook is for production.
Mistake three: never updating the runbook. Your process will change. New platform features, new email types, new audience segments. Review the runbook once a quarter for fifteen minutes. Remove anything you never reference. Add anything you've been doing by habit that should be documented. The runbook should reflect how you actually work today, not how you worked six months ago.
Want a faster path to better conversions? Get a free Conversion Infrastructure Audit and we will review your email operation, identify the gaps in your process, and give you a prioritised plan to fix them.
Frequently Asked Questions
What should an email ops runbook include?
An email ops runbook should include a send brief template, a draft production checklist, a build and QA checklist, a post-send review template, and escalation rules for handling errors after deployment. The key is keeping it lean enough that you actually follow it every time. A runbook you skip under pressure is not a runbook. It's a wish list.
How do you run email marketing as a team of one?
You run it by building a documented, repeatable process and following it for every send. The biggest operational risk for solo email marketers is relying on memory instead of a system. A written runbook with defined stages, quality gates, and a post-send log gives you the consistency that larger teams get from role separation and peer review.
What AI tools help solo email marketers?
AI writing assistants, subject line generators, and QA scanning tools all help solo operators produce faster. But the tool matters less than the system underneath. An AI tool paired with a structured brief template and a defined QA checklist produces consistently strong output. The same tool without a process just produces more first drafts that still need heavy editing.
Want Help Applying This?
A runbook gives you the process. But the process runs on top of infrastructure: your audience segments, your template system, your analytics baselines, your deliverability health. If any of those layers are weak, the runbook will expose the gaps faster than it fills them.
Our free audit reviews your full email operation across workflow, platform, content, and analytics, and gives you a prioritised plan for building the foundation your runbook needs. We build it alongside you as your growth partner, not as a PDF you file and forget.
Here's the thing worth sitting with. If you took a week off tomorrow and someone handed your runbook to a freelancer or a VA, could they ship your next email without texting you? If the honest answer is no, the runbook isn't done yet. Keep refining it until the process can run without you in the room. That's the whole point.