Founder & Business

7 Chapters Interactive Playbook

The Founder OS Playbook

For small-business owners who want a clearer operating plan. Work through seven 30-minute sessions using your own records. Build a service map, capacity check, unit economics sheet, delegation charter, operating review, management rhythm and scale stress test. This is planning support, not accounting, legal or investment advice; verify consequential decisions with suitable advisers.

Read the full workbook below

Create an account or log in, then choose your client.

Playbook Structure & Focus

An interactive digital playbook structured into digestible sequential chapters with multimedia modules and reflection prompts.

Read before you assign

Full workbook

Read every chapter and explore the exercises below. This is a read-only template preview. Use this workbook in your account to personalize it and collect your clients' responses.

Chapter 1 of 7

Chapter 1: Map how work gets delivered

How to use this workbook

Use it alone or with a coach. All responses are optional. Short notes are enough; skip anything that does not fit. Use additional paper for longer records, noting the chapter and question. Keep completed pages private and choose what to share.

Choose one offer and trace a recent job from enquiry to completion. Describe the actual process, including rework and waiting, before designing a better one.

What offer, customer need and delivery promise are you examining? What is inside and outside the agreed scope?

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Map enquiry → agreement → delivery → follow-up. For each stage record owner, input, output and typical delay.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Where did the last job stall or require rework? What evidence supports that observation?

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Choose one bottleneck to investigate in chapter 2. What customer or team outcome would improve?

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Next: Keep these notes available for chapter 2, “Check capacity before adding work”. Return to earlier answers when useful; revise your plan as circumstances change.

Back to chapter contents

Chapter 2 of 7

Chapter 2: Check capacity before adding work

Use the bottleneck from chapter 1. Compare demand with realistic available time over the same period. Delegation requires agreed authority, skills, resources and review, not just moving a task off your list.

For the coming week, record demand by task and estimated hours. State assumptions and uncertain items.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

List available people/hours after existing commitments and leave. Compare total demand with capacity; what gap remains?

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Choose a response: reduce scope, reschedule, improve a process or arrange supported help. What trade-off follows?

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Draft a handoff: result | owner’s agreement | authority | resources | deadline | check-in | escalation route.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Next: Keep these notes available for chapter 3, “Make financial assumptions explicit”. Return to earlier answers when useful; revise your plan as circumstances change.

Back to chapter contents

Chapter 3 of 7

Chapter 3: Make financial assumptions explicit

Use a single currency and period. Contribution per sale = price minus variable cost per sale. Illustrative example: 100 − 40 = 60; fixed costs of 600 would require 10 sales to cover those costs only. This is not a cash-flow forecast or a universal target.

Record currency/period, price, variable cost per sale and fixed costs. Identify source/date and uncertainty for each.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Calculate contribution and fixed costs ÷ contribution. If contribution is zero or negative, do not use the division; examine price/cost assumptions.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Compare low, expected and high sales scenarios. Record revenue, variable costs and remaining amount after fixed costs for each.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

What cash timing, tax, debt, owner pay or other obligations are missing from this simplified view? Who will verify them before a decision?

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Next: Keep these notes available for chapter 4, “Design standard operating procedures and delegation”. Return to earlier answers when useful; revise your plan as circumstances change.

Back to chapter contents

Chapter 4 of 7

Chapter 4: Design standard operating procedures and delegation

Scaling requires shifting from founder dependency to repeatable team processes. Document standard operating procedures (SOPs) for critical delivery paths and establish explicit delegation authority so team members execute with confidence.

Select one critical workflow: current owner | triggers | sequential steps | required tools | definition of done.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Document the SOP clearly so a team member can execute without ad-hoc verbal guidance. Where could confusion occur?

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Establish clear delegation boundaries: which decisions require founder sign-off versus autonomous team authority?

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Test the SOP with a team member. Record friction encountered, required clarifications and updates made to the procedure.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Next: Keep these notes available for chapter 5, “Run a weekly operating review”. Return to earlier answers when useful; revise your plan as circumstances change.

Back to chapter contents

Chapter 5 of 7

Chapter 5: Run a weekly operating review

Bring the process map, capacity plan and assumptions sheet. Choose a few measures with agreed definitions. Do not infer that one week’s movement was caused by your intervention.

Define up to three measures: name | calculation | source | owner | review frequency | useful decision.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Complete two dated review entries: result | comparison period | explanation or uncertainty | customer/team effect.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Choose one improvement: owner | first action | due date | expected signal | cost limit | stop condition.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

At the next review, what happened? Keep, adjust or stop the change, and record the next review date.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Next: Keep these notes available for chapter 6, “Build team autonomy and management rhythm”. Return to earlier answers when useful; revise your plan as circumstances change.

Back to chapter contents

Chapter 6 of 7

Chapter 6: Build team autonomy and management rhythm

High-performing operating rhythms replace ad-hoc firefighting with structured checkpoints. Design a consistent cadence of team synchronizations and one-on-one sessions that promote accountability, psychological safety and rapid roadblock removal.

Design your meeting cadence: weekly team sync | bi-weekly 1:1s | monthly financial check-in | quarterly strategic review.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Draft a standard 30-minute 1:1 agenda focused on coaching, roadblock removal and professional growth rather than status updates.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Identify where team members hesitate to make decisions. What reassurance or guardrails are needed to build autonomy?

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Run the new 1:1 and sync format for two weeks. Note feedback from the team and adjustments made to meeting frequency or length.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Next: Keep these notes available for chapter 7, “Stress-test the business for scale”. Return to earlier answers when useful; revise your plan as circumstances change.

Back to chapter contents

Chapter 7 of 7

Chapter 7: Stress-test the business for scale

Resilient enterprises withstand volatility and grow without breaking. Regularly audit operational vulnerabilities, customer concentrations and key-person dependencies to build a business that thrives independently of daily founder intervention.

Identify single points of failure: key person risk | revenue concentration | single supplier dependencies | critical tools.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Run a 2x capacity stress test: if sales doubled next month, where would operations, customer service or delivery break first?

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Simulate a 2-week complete founder absence: what emergencies cannot be handled without you? What protocol is needed?

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Create a quarterly resilience roadmap: 3 systemic upgrades to implement over the next 90 days and scheduled review date.

Short notes or several lines are welcome. For logs, use one line per entry.

{}

Finish: Keep your plan and dated observations together. Revisit the review date you chose; you can adapt or stop this practice.

Back to chapter contents

Bring this workbook into your practice

Choose your client and review delivery settings before assigning it.

Use this workbook