Writing Statements of Work That Stop You From Underpricing
Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
Most agency underpricing doesn't happen in the pricing conversation. It happens in the statement of work — or rather, in everything the statement of work left vague. You quoted a website redesign. The client heard "a website redesign, plus the blog migration, plus five rounds of homepage revisions, plus the landing page that came up later." You did all of it, because saying no felt like bad service. The price stayed the same; the work tripled.
That gap is almost never a negotiation problem. It's a definition problem. When the SOW doesn't spell out exactly what's included, how many rounds, and where the work stops, the client's expectations expand to fill the silence — and every hour of that expansion comes straight out of your margin.
WHAT THE SOW DEFINES vs. WHAT GETS DELIVERED
vague SOW ("a brand refresh")
│
├─ deliverables unnamed → "isn't that included?" → done for free
├─ rounds uncapped → revise until they're happy → hours bleed
└─ boundaries unstated → "one more small thing" → scope creep
│
priced for X ──────────────────────────► delivered 2–3XOwner symptoms
Projects that felt profitable when you quoted them lose money by delivery.
Your team keeps saying "just do it, it's small" to requests nobody scoped.
Clients seem genuinely surprised when you say something is extra — and they're not wrong to be, because the SOW never said otherwise.
Why this happens
An SOW written to win the deal and an SOW written to govern the work are two different documents. The winning version is short, warm, and full of outcome language — "a modern, high-converting site." That language sells, but it defines nothing. When the project starts, every undefined word becomes the client's to interpret, and they'll interpret generously toward themselves. It isn't bad faith; it's the natural reading of a vague promise. The agency that never names its deliverables, caps its rounds, or states what's excluded has quietly agreed to whatever the client later imagines.
Common mistakes
Selling outcomes instead of deliverables. "A brand refresh" is a feeling; "logo, one color palette, one type system, a 12-page guideline PDF" is a scope.
Leaving revision rounds uncapped. "Until you're happy" has no floor, and some clients are never quite happy for free.
Listing what's included but never what's excluded. The boundary is invisible until you've drawn it.
Burying scope in prose. A paragraph nobody rereads is not a boundary; a numbered deliverables list is.
No mechanism for extra work. If there's no clean way to say "that's a change order," every add-on becomes a favor.
Business consequences
A vague SOW doesn't just cost you the extra hours on one project — it resets the client's baseline for every project after it. Once you've absorbed the "small" extras once, they're the expectation, and your effective rate quietly drops on everything that follows. Multiply that across a book of clients and you have an agency that's busy, well-reviewed, and barely profitable. The owner who writes tight statements of work isn't being rigid or unfriendly; they're making the price they quoted match the work they actually do — which is the only way the margin they planned for survives contact with the client.
How experienced operators think about it
They treat the SOW as the place where profitability is decided, not the invoice. By the time an over-scoped project reaches billing, the money is already gone; the only leverage was in defining the work up front. So they write the SOW to be read by a stranger: every deliverable named and countable, every round numbered, a short "not included" list that prevents the most common assumptions, and a plain sentence on how new requests become paid change orders. None of that is adversarial — a clear boundary is a kindness to the client, because it lets them plan and choose rather than guess. The tight SOW protects the relationship at least as much as the margin.
Practical actions
List deliverables as countable nouns. Not "social content" but "12 posts, 3 platforms, per month." If you can't count it, you can't price it or defend it.
Cap revision rounds explicitly. State the number ("two rounds per deliverable") and what a round is, so "one more tweak" has a defined home.
Write a short exclusions list. Three to six lines naming the things clients most often assume are included — hosting, copywriting, stock photos, extra pages.
Add a change-order line. One sentence: work beyond this SOW is quoted and approved separately before it starts. That gives your team a script for "small" asks.
Price from the real deliverables list, not the outcome pitch. Once the SOW is honest about the work, check that the number is honest about the hours.
Questions every owner should ask
If a stranger read this SOW, could they list exactly what we owe and what we don't?
Where in our last three projects did undefined scope eat the margin — and was it in the pitch language?
When a client asks for "one more small thing," does the team have a boundary to point to, or just their own goodwill?
Frequently asked questions
Won't a detailed, boundary-heavy SOW make us look rigid and cost us the deal?
It reads as rigid only when the boundaries feel like traps. Framed as clarity — here's exactly what you get, here's how extra work is handled — most serious clients prefer it, because it tells them what they're buying and protects them from surprise bills too. The clients a clear SOW scares off are usually the ones who were counting on the vagueness. Specificity signals a shop that runs real projects, not one that's hiding the real cost until later.
How do I handle scope creep on a project where the SOW was already vague?
You can't retroactively tighten a signed SOW, but you can draw the line at the next request. Name the original scope, note that the new ask sits outside it, and offer it as a small change order rather than a favor. Do it warmly and early, before the extras pile up. Then fix the template so the next SOW carries the boundary from the start — most scope-creep problems are really SOW-writing problems in disguise.
Related articles
Running a Profitable Marketing Agency — the pillar.
Cash Flow When Clients Pay in 60 and Payroll Comes Every Two Weeks — the timing side of agency money.
Collecting on Overdue Invoices Without Damaging the Client Relationship — getting paid for the work you scoped.
What Does a Job Actually Cost You? Real Job Costing — the cost side the SOW has to cover.
Am I Charging Enough? How to Know for Sure — the pricing question underneath the scope.
Every business has more decisions than time
Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.
Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.