The 14-Day Agency Reset

Fourteen days, one system per day. Each day is self-contained — a goal, a handful of steps, and a deliverables checklist to tick off before you move on.

The order matters. Days 1–2 make the problem visible, Days 3–5 put structure and hard capacity limits around the team, Days 6–9 make delivery consistent regardless of who is working, and Days 10–14 take you out of the critical path for good. Skipping ahead to delegation before you have SOPs and capacity numbers is how most founders end up delegating chaos.

Budget 30–60 minutes per day. You do not need to finish all fourteen in fourteen consecutive days, but you do need to finish them in order.

Phase 1 — See What's Actually Happening

Day 1 — Audit

Goal: figure out where your time actually goes.

Step 1: Track the last 7 days

Write down every single thing you did, sorted into these categories:

• 🚚 Delivery — client work, reviews, QA
• 🫂 Team — questions, problems, 1:1s
• 💰 Sales — calls, proposals, follow-ups
• ⚙️ Admin — invoicing, tools, random tasks
• 🔥 Fires — unplanned chaos

Step 2: Tag each item

For everything you listed, rate it:

• 🔥 Fire — reactive, unplanned
• 📌 Important — but could be delegated
• 💤 Low-value — shouldn't exist
• 👑 CEO-only — actually needs you

Step 3: Build your chaos map

Draw this out:

[YOU]
   ↓
[Delivery] → Who reviews work? You? That's a problem.
   ↓
[Team] → Who answers questions? You? Problem.
   ↓
[Clients] → Who handles fires? You? Problem.
   ↓
[Sales] → Who closes deals? Just you? Problem.

Step 4: Define your "Founder Only Zone"

Write down the 3–5 things that genuinely only you can do:

• Vision and strategy
• Key partnerships
• Senior hires
• Offer positioning

Day 1 deliverables

• 7-day time audit completed
• Every task tagged (🔥/📌/💤/👑)
• Chaos map drawn
• "Founder Only Zone" defined

Day 2 — Weekly Reporting System

Goal: know exactly what's happening without asking "any updates?"

Step 1: Set up the Friday Report template

Every pod lead fills this out by Friday 4pm:

Section	What to include
✅ Completed	What shipped this week
🔄 In Progress	What's being worked on + % complete
⚠️ Risks/Blockers	Anything stuck or at risk
💚 Client Health	🟢🟡🔴 for each client + 1-line reason
📊 Capacity	Team utilization %
⏭️ Next Week	Top 3 priorities

Example report:

✅ COMPLETED THIS WEEK

• [Client A] Website mockups v2 delivered
• [Client B] Monthly report sent

🔄 IN PROGRESS

• [Client A] Dev build — 60% complete
• [Client B] SEO audit — due Tuesday

⚠️ RISKS / BLOCKERS

• [Client C] Waiting on brand assets since Monday

💚 CLIENT HEALTH

• Client A: 🟢 Happy, engaged
• Client B: 🟡 Slow responses
• Client C: 🔴 Frustrated about timeline

📊 CAPACITY

• Team at 85% utilization

⏭️ NEXT WEEK

1. Client A site launch
2. Client B strategy presentation
3. Client C recovery call

Step 2: Automate the reminder

Set a Slack reminder or Notion automation:

• Friday 2pm — "Weekly report due in 2 hours"
• Friday 4pm — check submissions
• Monday 9am — review all reports (block 15 mins)

Step 3: Train the "no surprises" rule

Make this clear to pod leads:

• 🟢 Bad news in the report = good
• 🔴 Bad news as a surprise = very bad

If it's not in the report, it didn't happen.

Day 2 deliverables

• Weekly report template created
• Automated reminder set (Slack/Notion)
• 15-min review block in your calendar
• Team briefed on submission expectations

Phase 2 — Structure the Team and Its Capacity

Day 3 — Team Structure

Goal: build self-managing teams that ship without you.

Step 1: Understand the shift

Old Model	New Model
Departments (design, dev, strategy)	Pods (cross-functional teams)
Founder coordinates everything	Pod Lead owns end-to-end
Handoffs between teams	One team, one client set
Quality varies by person	Consistent pod standards

Step 2: Design your teams

Each pod needs:

• A Pod Lead who owns outcomes
• All skills required to deliver (design + dev + strategy, etc.)
• A set of clients they fully own
• Their own KPIs

Example structure:

Pod	Lead	Team	Clients
Pod A	Sarah	Mike (Paid), Emma (Creative)	Company X, Y, Z
Pod B	James	Lisa (SEO), Tom (Dev)	Company A, B

Step 3: Define Pod Lead responsibilities

A Pod Lead isn't a senior person who manages. They're a mini-CEO who owns:

• Client outcomes, not just deliverables
• Team performance
• Weekly reporting
• Decisions without asking you

The test: can they handle a client issue without pinging you?

• ✅ Yes — Pod Lead material
• ❌ No — not ready yet

Step 4: Set Pod KPIs

Metric	Target	Who tracks
Client retention	90%+	Pod Lead
On-time delivery	95%+	Pod Lead
Client NPS	8+	Monthly survey
Utilization	75–85%	Capacity calculator

Step 5: Communicate the change

Send a Loom or hold a 15-minute call:

We're moving to pods. Here's why: faster delivery, more ownership, better work.

[Pod Lead] now owns [these clients]. They make decisions. They escalate when needed.

Questions?

Day 3 deliverables

• Pod structure designed
• Pod Leads identified and briefed
• Clients assigned to pods
• KPIs defined
• Team communication sent

Day 4 — Capacity Calculator

Goal: know exactly how much work your team can handle.

Step 1: Map available hours

For every delivery team member, calculate actual available hours. Delivery % is time on client work — not meetings, admin, or Slack.

Role	Name	Weekly Hours	Delivery %	Available
Designer	Emma	40h	70%	28h
Developer	Tom	40h	80%	32h
Strategist	Sarah	40h	50%	20h
PM	James	40h	60%	24h

Step 2: Calculate hours per client

Pick your most common service and estimate hours per role per week.

Example — monthly retainer:

Role	Hours/client/week
Strategy/PM	5h
Design	6h
Dev	4h
Content	3h

Step 3: Do the math

Formula: available hours ÷ hours per client = max clients

Example:

• Design available: 28h
• Design per client: 6h
• Max clients: 28 ÷ 6 = 4.6 clients

Your bottleneck is whoever maxes out first.

Step 4: Build the tracker

Role	Available	Used	Free	Utilization
Design	28h	24h	4h	86% 🟡
Dev	32h	20h	12h	63% 🟢
Strategy	20h	22h	-2h	110% 🔴

Colour coding:

• 🟢 Under 75% — room to grow
• 🟡 75–90% — getting tight
• 🔴 Over 90% — (almost) maxed out

Step 5: Set hiring triggers

Rule: when any role hits 85% for 2 consecutive weeks, start hiring.

Hiring takes 4–8 weeks. Don't wait until 100%.

Day 4 deliverables

• Available hours mapped for all team
• Hours per client calculated
• Capacity tracker built with RAG status
• Hiring triggers defined
• Monthly review scheduled

Day 5 — Hiring Calculator

Goal: predict exactly when to hire and for what role.

Step 1: Connect to your pipeline

What's coming in the next 30-60-90 days?

Expected Client	Close Date	Type	Hours Needed
Company X	Jan 15	Retainer	Design 6h, Dev 4h
Company Y	Feb 1	Project	Design 10h, Dev 8h
Company Z	Feb 15	Retainer	Strategy 5h, Design 6h

Step 2: Forecast capacity impact

Add expected hours to current utilization:

Timeline	Design Utilization	Status
Now (Jan 1)	86%	🟡
After Company X (Jan 15)	107%	🔴
After Company Y (Feb 1)	143%	🚨🚨

Example conclusion: you need to hire a designer before Jan 15.

Step 3: Build the 30/60/90 plan

Hire By	Role	Reason	Hours Gap
Jan 30	Designer	Pipeline + current capacity	12h/week
Mar 1	Developer	Q2 projects forecast	8h/week
TBD	PM	Depends on close rate	Watch

Step 4: Prioritise roles

Score each potential hire 1–5:

Factor	Designer	Developer	PM
Urgency (hitting cap soon?)	5	3	2
Revenue impact (unlocks deals?)	4	3	3
Quality risk (work suffering?)	4	2	2
Availability (can you find them?)	3	4	4
Total	16	12	11

Highest score gets hired first.

Step 5: Consider fractional first

Not sure you need full-time?

• Start with a freelancer or fractional hire
• Track their utilization for 8 weeks
• 80%+ utilization — convert to full-time
• Under 80% — you probably didn't need the hire

Day 5 deliverables

• Pipeline forecast built
• Capacity impact calculated
• 30/60/90 hiring plan created
• Roles prioritised
• First hire decision made (or freelancer sourced)

Phase 3 — Standardise Delivery and Quality

Day 6 — Delivery SOPs

Goal: turn "depends who's working" into "this is how we do it."

Step 1: Identify core deliverables

Pick the 3–5 things your team delivers most often. For example:

• Monthly performance report
• Website launch
• Ad creative set
• SEO audit
• Client onboarding

Step 2: Map the workflow

For each deliverable, document:

1. What triggers this work?
2. What inputs are needed?
3. What are the exact steps?
4. Who owns each step?
5. What does "done" look like?

Example — monthly performance report:

Step	Owner	Time	Input	Output
1. Pull data	Analyst	1h	GA4, ad platforms	Raw data
2. Update template	Analyst	30m	Raw data	Draft report
3. Add commentary	Strategist	1h	Draft report	Insights added
4. QA review	PM	30m	Report	Approved or feedback
5. Send to client	PM	15m	Approved report	Delivered

Step 3: Add "What Good Looks Like"

For every deliverable, create a good example with notes on why it works, and a bad example with notes on what's wrong. Use real work. Show, don't tell.

Good ✅	Bad ❌
Clean data viz	Wall of numbers
Insights, not just metrics	No context
Clear next steps	Generic recommendations
Client-specific commentary	Copy-paste from last month

Step 4: Record Loom walkthroughs

For each SOP, record 5–10 minutes covering:

• Why this process matters
• How to do each step
• Common mistakes
• What to do if something goes wrong

Keep it casual. You're not making a course.

Step 5: Organise the SOP hub

Create one central location in Notion:

📋 SOPs

• ✅ Client Deliverables — Monthly Report, Website Launch, Ad Creative
• ⚙️ Internal Processes — Client Onboarding, QA Process, Handoffs
• 📄 Templates — all templates linked

Day 6 deliverables

• 3–5 core deliverables identified
• Workflow documented for each
• "What Good Looks Like" examples created
• Loom walkthroughs recorded
• SOP hub organised

Day 7 — QA System

Goal: catch mistakes before clients do.

Step 1: Build QA checklists

For each core deliverable, create a checklist that must be completed before anything ships.

Example — ad creative QA:

• Copy matches approved messaging
• No spelling/grammar errors
• Brand colours correct
• Logo placement per guidelines
• CTA clear and aligned with campaign
• Sized for all required placements
• File naming correct
• Added to correct folder

If any box is unchecked, it doesn't ship.

Step 2: Define quality standards

Element	Good	Bad
Headlines	Under 40 chars, benefit-led	Vague, too long
Visuals	On-brand, high-res	Pixelated, off-brand
Copy	Clear CTA, no jargon	Wall of text
Data	Accurate, sourced	Estimated, unsourced

Step 3: Assign QA owners

Rules:

• The creator never QAs their own work
• The QA owner signs off before delivery
• The QA owner is accountable for quality issues

Deliverable	Creator	QA Owner
Ad creative	Designer	Pod Lead
Reports	Analyst	Strategist
Website pages	Developer	PM

Step 4: Track mistakes

Every mistake is data. Create a simple log:

Date	Client	What went wrong	Root cause	Fix
Jan 5	Client A	Wrong logo	Old file in folder	Cleaned folder
Jan 12	Client B	Typo in headline	Skipped QA	Added checkpoint

Step 5: Make QA non-negotiable

Build this into the culture:

Nothing ships without QA. Ever. If we don't have time for QA, we don't have time to do the work.

If you're always rushing, it's a capacity problem — go back to Day 4.

Day 7 deliverables

• QA checklist for each deliverable
• Quality standards documented
• QA owners assigned
• Mistake log created
• Team briefed: QA is mandatory

Day 8 — Leadership Meetings

Goal: align your leadership team in 45 minutes per week.

Step 1: Lock the meeting

• When: Monday or Tuesday AM, same time every week
• Who: you + Pod Leads + Ops Lead
• Duration: 45 minutes max

Step 2: Use this agenda

Section	Time	Purpose
Wins	5 min	What went well? One each.
Metrics	5 min	Scorecard check. RAG status only.
Pod Updates	15 min	2–3 min per pod. Health, blockers, priorities.
Escalations	10 min	What needs discussion? Decisions needed?
Priorities	10 min	Top 3 for the business this week.

Step 3: Require pre-work

Pod leads submit this 24 hours before:

[POD NAME] — Week of [DATE]

Client health:

• Client A: 🟢
• Client B: 🟡 (slow responses)
• Client C: 🔴

Completed: [list]

This week: [top 3]

Blockers: [list or "None"]

Capacity: 🟢/🟡/🔴

No pre-work submitted means no airtime in the meeting.

Step 4: Apply the "no meeting discussion" rule

If it can be solved in Slack, a Loom, or a quick 1:1, it's not for the leadership meeting.

Leadership meetings are for:

• ✅ Cross-pod issues
• ✅ Resource allocation
• ✅ Strategic alignment

Not for:

• ❌ Status updates — that's pre-work
• ❌ 1:1 conversations
• ❌ Problems one person could solve

Step 5: Keep a rolling scorecard

Metric	Target	This Week	Trend
Client retention	90%	92%	🟢
On-time delivery	95%	88%	🔴 ↓
Team utilization	80%	85%	🟡
Clients at risk	0	2	🔴

Day 8 deliverables

• Meeting time locked (recurring)
• Agenda documented
• Pre-work template created
• Scorecard set up
• First meeting run

Day 9 — Client Health Scorecards

Goal: know which clients are about to churn before they tell you.

Step 1: Define health categories

Category	🟢 Green	🟡 Yellow	🔴 Red
Communication	Replies in 24–48h	Slow, brief	Ghosting, curt
Results	Hitting targets	Mixed	Missing targets
Engagement	Attends calls, gives feedback	Sometimes misses	Disengaged
Payment	On time	Occasional delays	Late, pushback

Step 2: Create the weekly scorecard

Each pod lead scores their clients weekly. Fill the category columns yourself:

Client	Comms	Results	Engagement	Payment	Overall
Company A					🟢
Company B					🟡
Company C					🔴

Step 3: Add to Friday reports

Client health becomes part of the weekly report from Day 2. Your five-minute review looks for:

• Any client that moved green → yellow
• Any client yellow for 2+ weeks
• Any client at red — action needed now

Step 4: Build the intervention playbook

When a client goes 🔴:

Timeline	Action
Same day	Pod lead identifies issue
Same day	Internal sync: what happened?
Within 24h	Reach out to client for a call
On the call	Listen first. Acknowledge. Propose solution.
Within 24h	Follow up in writing
After	Add to mistake log if relevant

Step 5: Track patterns

Monthly, review:

• Which clients have been yellow longest?
• What makes clients go red? (common causes)
• What recovered clients? (what worked)

Day 9 deliverables

• Health categories defined
• Scorecard created
• Added to weekly reports
• Intervention playbook documented
• Current clients scored (baseline)

Phase 4 — Get Yourself Out of the Machine

Day 10 — Delegation Mapping

Goal: stop doing things that aren't your job.

Step 1: List everything you still do

Be honest. Write down:

• Recurring tasks (weekly/monthly)
• Decisions people ask you to make
• Reviews and approvals that route through you
• Problems you get pulled into
• Things you do "because it's faster"

Most founders have 30–50 items.

Step 2: Apply the E-A-D filter

Filter	Question	Example
Eliminate	Does this need to exist?	Weekly call nobody prepares for
Automate	Can a tool or template do this?	Client onboarding emails
Delegate	Can someone own this outcome?	Reviewing social posts

Step 3: Fill out the delegation matrix

Task	E / A / D	New Owner	Success Metric	SOP Exists?
Approve social posts	D	Pod Lead	Posts on brand	Yes
Send onboarding emails	A	Automated	Sent within 24h	Create
Weekly team call	E	-	-	-
Review all deliverables	D	QA owners	Error rate <2%	Yes
Client fire drills	D	Pod Lead	Resolved in 24h	Create

Step 4: Assign ownership, not tasks

Task delegation: "Can you send this email?"

Ownership delegation: "You own client communication. Here are the standards. Make decisions. Escalate if X."

For each delegation, be explicit about:

• Who owns it
• What success looks like
• When to escalate
• Where the SOP lives

Step 5: Update your Founder Only Zone

After this exercise, what's left?

Keep:

• Vision and strategy
• Major partnerships
• Senior hiring
• Final escalations

Remove — you've built systems for these:

• Reviewing reports
• Client fires
• Team questions
• Approving everything

Step 6: Tell people

Template message:

Hey hey team — moving forward, [Name] owns [Thing].

They'll make decisions on [scope]. Questions go to them first. They'll escalate to me if needed.

This gives them more ownership and frees me for [strategic work].

Day 10 deliverables

• Full task list created
• E-A-D filter applied
• Delegation matrix complete
• Ownership assigned, not just tasks
• Founder Only Zone updated
• Team notified

Day 11 — Client Communication

Goal: stop being a 24/7 Slack support desk.

Step 1: Define one channel per client

Option	Best for	Rules
Slack channel	Fast-moving projects	Shared channel, not DMs
Email	Traditional clients	Dedicated PM inbox
Client portal	Async-heavy	Notion, ClickUp, etc.

One channel means everything is searchable and visible to the team.

Step 2: Set expectations upfront

Send this during onboarding, or retroactively:

Hey [Name],

Quick note on how we work:

✅ Communication: everything through [channel]. Keeps the whole team in the loop, which means faster responses.

⏰ Response time: within 1 business day. Urgent? Tag with 🚨 and we'll prioritise.

📊 Updates: weekly update every Friday covering completed, in progress, and next steps.

👤 Main contact: [Pod Lead] owns your account. They can make decisions without waiting on me.

Step 3: Install weekly updates

Every Friday, each client gets:

✅ This week: [what was delivered]

🔄 In progress: [what's being worked on]

⏭️ Coming up: [what's planned next week]

📝 Notes: [blockers, questions, things we need from them]

Takes 10 minutes to write. Saves hours of "any updates?" messages.

Step 4: Remove yourself from channels

• Current state: clients Slack you directly
• Target state: the Pod Lead is the primary contact

How to frame it: "[Pod Lead] owns your account. They know your business and can make decisions without waiting on me. If you ever need me, they'll loop me in."

Step 5: Handle the transition

If you've been responsive 24/7, clients will notice. Be proactive:

We're upgrading how we work with clients. You'll get more consistent updates and faster responses from the team. [Pod Lead] is your main contact — they have full authority.

Most clients prefer reliable systems over burned-out founders.

Day 11 deliverables

• Primary channel defined per client
• Expectations documented
• Weekly update template created
• Pod leads installed as main contacts
• Transition communicated

Day 12 — Delivery Rhythm

Goal: make your week predictable.

Step 1: Define the weekly cycle

Day	Focus	Activities
Monday	Planning	Review priorities, assign tasks, pod standup
Tuesday	Execution	Deep work, minimal meetings
Wednesday	Execution	Deep work, mid-week async check
Thursday	QA	Internal reviews, revisions, prep for delivery
Friday	Delivery	Ship to clients, send updates, submit reports

Step 2: Make it visible

Create a shared calendar showing:

• Monday — AM: pod planning (15 min). PM: execution starts.
• Tuesday — deep work day, no meetings
• Wednesday — deep work. PM: mid-week check (async).
• Thursday — AM: QA reviews. PM: final polish.
• Friday — AM: deliveries ship. PM: weekly updates sent. EOD: reports due.

Step 3: Protect deep work time

Rule: at least one meeting-free day per week.

• No internal meetings
• No client calls unless urgent
• Focus time for actual delivery

Teams are 2–3x more productive on protected days.

Step 4: Sync internal and client rhythms

Work backwards from client needs.

Client touchpoint	Internal deadline
Updates sent Friday	QA done Thursday
Deliverables Monday AM	Ship Friday EOD
Monthly report 5th	Data pulled 3rd

Day 12 deliverables

• Weekly rhythm defined
• Calendar blocked
• Meeting-free day implemented
• Internal deadlines synced to client touchpoints
• Team briefed and bought in

Day 13 — Founder Time System

Goal: get 10+ hours back per week for CEO work.

Step 1: Audit your current calendar

Look at the last 2 weeks:

Time Type	Hours	% of Week
CEO work (strategy, vision)	?	?
Operations	?	?
Meetings (could be async)	?	?
Reactive/fires	?	?

If CEO work is under 20%, you're operating, not leading.

Step 2: Design your default week

Block CEO time before anything else:

Day	AM	PM
Monday	Leadership meeting	1:1s if needed
Tuesday	CEO time (no meetings)	CEO time
Wednesday	External calls	Available for team
Thursday	CEO time	Client strategic calls
Friday	Review reports	Plan next week

Step 3: Set meeting rules

Type	Rule
Internal	Agenda required. 30 min default. Could this be async?
External	Batch on specific days. Buffer time after.
All	No back-to-back if possible.

Step 4: Install interrupt handling

Create an escalation path:

1. Check the SOP
2. Ask your pod lead
3. Post in Slack for async help
4. Only then: escalate to the founder

Then create office hours: "I'm available for quick questions Tuesday and Thursday 2–3pm. Outside that, Slack me or book time."

Step 5: Track weekly

Every Friday, two minutes:

• Did I protect CEO time?
• What pulled me out?
• One adjustment for next week?

Day 13 deliverables

• Calendar audited
• Default week designed
• CEO time blocked (10+ hours)
• Meeting rules documented
• Interrupt handling established
• Weekly reflection habit started

Day 14 — Handoff and Integration

Goal: make everything permanent without you maintaining it.

Step 1: Assign system owners

System	Owner	Check-in
Weekly reporting	Ops Lead	Weekly
Pod KPIs	Pod Leads	Weekly
Capacity calculator	Ops Lead	Monthly
SOPs	Pod Leads (their area)	Monthly
QA system	Pod Leads	Bi-weekly
Client health	Pod Leads	Weekly
Leadership meeting	Ops Lead	Weekly

Step 2: Run handoff conversations

Fifteen minutes with each owner:

You own [System]. Here's where it lives. Here's what success looks like. Here's when to escalate. Questions?

Get explicit agreement: "Are you good to own this?"

Step 3: Create the Operations Hub

Create one central location in Notion:

🏢 Agency Operations

• ⚙️ Systems — Reporting, Pods, Capacity, QA, Client Comms
• 📋 SOPs — organised by function
• 📄 Templates — all in one place
• 👤 System Owners — who owns what

New hires should find everything here.

Step 4: Set a monthly systems review

Thirty minutes monthly with leadership:

• Are systems still being used?
• What's breaking?
• What needs updating?
• 1–3 action items max

Step 5: Communicate to the team

Over the last 14 days, we've installed [systems].

Here's what changes. Here's what stays the same. Here's why this matters for you.

Questions?

Day 14 deliverables

• Every system has an owner
• Handoff conversations completed
• Operations hub organised
• Monthly review scheduled
• Team communication sent