The systems week kit: run your business on systems, not memory

Everything you need to run one week of your business on systems instead of memory, then test whether it holds when you're gone.

The operational playbook generator

Paste this into Claude:

Here are the 5-7 core processes I repeat in my business: [list them, e.g., client onboarding, project delivery, content creation]. For each process, create: a step-by-step checklist that ensures consistency; the decision points where things usually go wrong; the quality standards that define "done"; the tools/templates needed; the parts that could be automated or delegated within 6 months. Write this as if I'm training my future replacement, even though I'm not hiring anyone yet.

This is the document a $300K owner needs before the first hire. Most owners never write it because it feels too early. It isn't.

The productized service blueprint

Paste this into Claude:

I currently offer [service description] at [pricing model]. My ideal clients struggle with [specific problem] and the transformation they want is [desired outcome]. Redesign this as a productized offering: Create 3 different package tiers (entry/core/premium); define exactly what's included and excluded in each; identify the delivery process that's repeatable without customization; set scope boundaries that prevent scope creep; price based on value not hours. Make it something I could theoretically document so well that someone else could deliver it.

This turns "I do custom work for everyone" into a sellable, delegatable product.

The batching numbers

Grouping same-type tasks (all emails, all content, all client calls) into single blocks instead of interleaving them cuts context-switching from roughly 40 times a day down to 15, and saves about 5 hours a week. The mechanism is simple: your brain pays a tax every time it switches task types, and batching stops charging you that tax all day long.

Theme-day calendar template (copy this)

Pick one, put it on the calendar this week, and don't reorder your day around whatever feels urgent when you wake up.

The 4-hours-to-30-minutes note

The first time you do a task, it takes forever. One documented case: a single blog post took 4 hours, then 2, then 1, then landed at 3-4 posts in 2 hours once the process was systemized. The speed came from documenting the process instead of redoing the thinking every time.

The Week-Off Test

Before you book time off, check whether these three areas run without you.

Delivery: is there a written process for what you deliver, with the decision points marked, or does it live only in your head?

Sales: can a lead come in, get a response, and get a proposal without you touching it that week?

Client comms: does someone or something check in with active clients on a normal schedule even if you don't open your inbox?

If any answer is no, that's the gap. Fix it before the week off, not during it.

Appendix: two more generators

The elevator pitch generator:

Write 3 elevator pitches for [my business/offer]: one problem-led, one result-led, one story-led. No buzzwords, no jargon, speakable language a stranger would understand. For each, add a natural follow-up question I can ask to keep the conversation going.

The meeting brief generator:

Prepare a meeting brief for [person/company I'm meeting]: their likely priorities, 3 key points I should make, questions I should ask them, objections they might raise and how I'd respond, and my ideal outcome for the meeting.

This is the exact system WorkSmart teaches inside the Scale Plan: your answers become a personalized growth plan, then a 30-day plan with weekly check-ins. More free tools live at worksmartadvisor.com/resources.