Founder’s Note
Last week we talked about the decision bottleneck — the founder as the human routing system — and I got a lot of replies.
The most common one: "I know I'm the bottleneck. But I also can't let go because when I do, the work costs me more than it should."
That's the reply I want to talk about today.
Because that feeling — the one where delegation feels risky and saying yes to everything feels necessary — is often rooted in something that has nothing to do with your team's competence.
It has to do with your scope.
🗓️ THIS WEEK: The Scope Creep Tax
Here's the thing about scope creep that no one says directly:
Most of the time, it's not your clients' fault. It's your proposal's fault.
Scope creep happens when a proposal is vague enough that a client's interpretation and your interpretation can diverge — and both of you are technically right.
"Monthly social media management" means something different to you and to your client. "Ongoing PR support" is a blank check if it's not defined. "Content strategy" covers anything from a one-page document to a full quarterly production calendar.
When scope is undefined, the path of least resistance is always to do more. Because saying no to a client request mid-engagement is uncomfortable, and delivering short feels worse than delivering over.
So you deliver over. Again and again. And you call it "going the extra mile" when really it's margin erosion.
Here's what this costs you over a year:
→ The average agency team member spends 4–6 hours per week on out-of-scope work that was never billed
→ At even a $100/hr blended rate, that's $400–$600 per team member per week going unbilled
→ For a 5-person team, that's $100K–$150K in invisible write-offs annually
→ And none of it shows up in your P&L as a cost — it just shows up as exhaustion
This is the scope creep tax. And almost every agency I work with is paying it.
THE SYSTEM: The Scope Guardrail Stack
The fix isn't a longer contract. It's a tighter proposal structure. Here's the three-part Scope Guardrail Stack I install with every Agency OS Core (and above) client:
GUARDRAIL 1 — Define the deliverable, not the effort
Stop writing proposals that describe how much work you'll do. Write proposals that describe exactly what the client will receive.
Bad: "Ongoing social media management, including content creation, scheduling, and engagement."
Good: "12 posts per month across [specified channels], formatted to [spec], delivered in [tool] for approval by [date]. Engagement monitoring excluded unless specified as an add-on."
One is a promise of effort. The other is a deliverable. Clients request additions to deliverables much less freely than they request additional effort.
GUARDRAIL 2 — Name what's not included
Every proposal should contain an "Out of Scope" section. Not buried in a contract appendix — in the proposal itself, before they sign.
This does two things: it protects you legally, and it resets the client's expectations before the engagement starts. Clients who are going to be scope-pushers will often self-select out at this point, which is a feature, not a bug.
Example out-of-scope items for a PR retainer: reactive media response outside business hours, any coverage outside the agreed target outlet list, additional spokesperson prep beyond the monthly allotment, earned media for product lines not listed in this agreement.
Make the fence visible. Clients respect fences they can see.
GUARDRAIL 3 — Install a change order trigger
Define the threshold at which something becomes a change order conversation — and put it in writing.
Simple version: "Any request that falls outside the deliverables listed above will be scoped and quoted separately before work begins. We'll respond to out-of-scope requests within 48 hours with a proposal."
This isn't adversarial. Frame it as a professional service standard. "We scope everything so we can do it properly." Clients who respect your work respect this. The ones who don't were going to cost you money anyway.
THE ACTION: Do This Before Next Week
Pull up your last 3 proposals. Open them and ask one question for each:
"If a client asked for something adjacent to this, would I know instantly whether it's in scope or not?"
If the answer is "not really" — that proposal has a scope problem.
Pick the client you're renewing or pitching next. Before you write the proposal, write the out-of-scope list first. Then write the deliverables to match. You'll immediately see where your previous proposals were leaving space for interpretation.
That list is also your foundation for a Scope SOP — a template you and your team use for every engagement going forward. We'll build that out in a future issue.
🤖 AI CORNER: Let Claude Handle Your Tier 1 Decisions
Once you've pulled your existing proposals, here's a Claude prompt that will flag scope gaps faster than you can read through them yourself:
PROMPT:
"You are a scope risk analyst for a PR and marketing agency.
Review the following proposal and identify:
Any deliverables described in terms of effort rather than
output (flag the specific language)Any services mentioned without defined limits
(e.g. 'ongoing', 'as needed', 'support')The top 5 client requests this proposal could trigger
that aren't explicitly out of scopeSuggested rewrites for the vaguest 3 lines
Proposal text: [paste proposal here]"
Run every active client's proposal through this. The output will be uncomfortable. That's the point.
Members of the Agency OS Skool community get the full Scope Audit template and the Claude install file pre-built — including the change order email template and the out-of-scope conversation script. [Get on the waitlist →]
📊 BY THE NUMBERS
One number I keep coming back to from the agencies I work with:
Agencies that formalize their out-of-scope process report an average 18% increase in effective hourly rate within 60 days — without raising their prices.
They didn't charge more. They just stopped giving work away.
In Case You Missed It…
The $180k Question: When Should You Hire vs. Automate? 6 minute read
How to Calculate Your Agency's "Operational Debt" 5 minute read
📣 A QUICK NOTE
The Agency OS community on Skool opens on May 1st at founding member pricing — $97/month before it goes to $147.
Everything in this newsletter is the what. The community is the how — the SOPs, AI installs, workflow templates, and founder resources that make this practical instead of theoretical.
If you want to be in at the founding rate, the link is below. It closes when it closes.
See you next week.
Work smart. Enjoy life harder.
Erin James Murphy
Founder, Agency Owner Lab
When you're ready, here's how we can work together:
→ Agency OS Community (Skool) — SOPs, AI installs, tool stacks. $97/month. [Join here]
→ Agency OS Core — 12-week coaching for $8K–$50K/month agencies [Apply here]
→ Agency OS Accelerate — 12-month program for $50K–$150K/month agencies [Apply here]
→ The Boardroom — mastermind for founders at or approaching $1M/year [Apply here]
→ Implementation Sprints — done-for-you systems builds, $8K–$15K [Book a Systems Audit]

