If you ever want the option to sell your agency, buyers won’t pay you for effort. They’ll pay you for reliable EBITDA. One of the fastest ways EBITDA gets quietly eroded in agencies is simple: you deliver more than you priced, more often than you notice.
A Work Breakout (WBO) is a lightweight habit that helps you catch that margin drift early, fix it, and prove it’s fixed. Not as an “ops overhaul,” but as a repeatable check your ops leader or outsourced CFO can run so you can make smarter scope and pricing decisions without becoming the spreadsheet person.
Why this matters for exit value
Most agency owners understand the basic math: more EBITDA is better. The part people miss is the timeline.
- If you improve EBITDA once, you get a better year.
- If you improve EBITDA and sustain it, you get a better trend, better predictability, and a stronger story.
- If you improve EBITDA earlier, you get more time for the improvement to compound and become normal, not a one-off.
Work Breakouts help with that third point. They’re not glamorous—but they’re effective.
The hidden risk to your EBITDA: unpriced overdelivery
Agencies lose money when they do more work than planned and fail to convert that reality into one of three outcomes:
- Tighter scope
- Higher fees
- Better operating rules to prevent a repeat
That gap between “what we planned” and “what we did” is where EBITDA disappears.
A WBO gives you a consistent way to measure that gap and decide what changes next.
This article is intentionally narrow. A Work Breakout targets one of the most common margin leaks: unpriced overdelivery on projects and retainers.
What a work breakout is and what it is not
A Work Breakout is a structured comparison between:
- Planned work: What you sold and what you assumed
- Actual work: What your team delivered, including the hidden time
- Variance: Where the overage happened and why
- Decision: What you will change going forward
A WBO is not:
- A new time-tracking initiative
- A performance management tool
- A weeks-long operational deep dive
It’s a decision tool. If a WBO analysis doesn’t produce actionable insights you can use in the future, it didn’t do its job.
When to run a work breakout
You don’t need to run these on everything. Use them where they protect EBITDA and reduce surprises.
Run a WBO when any of these happen:
- A project hits 60–70% of planned effort and still looks half done.
- A retainer’s meeting load or revision cycles spike compared to the first 60–90 days.
- Stakeholders multiply and approvals slow down.
- You are scoping Phase 2 or renewing a retainer and want a reality check.
If you’re exit-minded, add one more trigger:
- You want to improve margins now and be able to show the improvement is repeatable, not heroic.
The Work Breakout (WBO) method
A strong WBO takes 30–60 minutes the first time, and gets faster as the habit forms. As the owner or CEO, you’ll likely delegate this work to your team—your CFO, operations director, or a senior PM.
Step 1: List the work in client language
Break the project or retainer into meaningful components: deliverables, phases, or workstreams.
Examples:
- Discovery and stakeholder interviews
- Information architecture
- Design concepts and revisions
- Implementation
- Analytics and tagging
- QA and launch support
Avoid micro-tasks. You’re trying to locate where overdelivery happened, not reconstruct every hour. Aim for 8–20 line items.
Step 2: Capture the baseline
You need a benchmark. Use the best available baseline:
- The original estimate by phase
- Statement of Work (SoW) assumptions, especially revision rounds and client responsibilities
- Sprint plan or resourcing plan
- Retainer level of effort and what is included
If the baseline is imperfect, proceed anyway. Write a best-available baseline and note the assumptions. Directional truth beats “precise but not accurate.”
Step 3: Capture actual effort, including hidden work
Pull actual hours by the same categories.
Then correct the most common understatement: Ensure your team adds 25–35% for project management and administrative load unless it was explicitly tracked and already included.
What drives the AM/PM range?
- Assume ~25% when scope is tight, approvals are clear, and meetings are predictable
- Assume more like ~35% when stakeholders multiply, decisions churn, meetings expand, and “quick asks” become normal
The goal is not to inflate numbers. It’s to stop pretending the coordination work is free.
Step 4: Calculate variance
Compare planned versus actual for each line item, then total it. Focus on two outputs:
- Overall variance as a percentage
- Specific areas that went over budget
Percentages stay useful over time and make comparisons easier across different account sizes.
Step 5: Require a diagnosis and a decision
End every WBO process with two statements:
- Diagnosis: “We went over because ___.”
- Decision: “Next time, we will ___.”
Your WBO is incomplete without a diagnosis and a decision.
A simple example using hours and variance
You can use WBOs for projects and retainers. Let’s look at a project-based example.
Assume you planned a fixed-fee project with 120 hours of delivery effort:
- Discovery: 20 hours
- Design: 40
- Implementation: 40
- QA and launch: 20
Actual delivery effort comes in as:
- Discovery: 28 hours
- Design: 55
- Implementation: 46
- QA and launch: 26
That totals 155 hours.
Your ops lead notices that the team didn’t track AM and PM time cleanly, so they add 30% (within my 25–35% guidance range).
- 155 × 0.30 = 46.5 hours
- All-in actual effort = 155 + 46.5 = 201.5 hours
Variance:
- Planned: 120 hours
- Actual: 201.5
- Overage: 81.5 hours
- Percent over plan: 81.5 ÷ 120 = 0.679166… which is about 68% over plan
That level of variance is not a “project hiccup.” It’s an EBITDA issue.
If it happens repeatedly across a handful of accounts, it becomes a negative pattern for your profit margins. And margin patterns are exactly what a buyer will scrutinize when they’re deciding what you’re worth.
The five most common overage causes
Keep the diagnosis high-level. In most agencies, overages fall into one of these buckets:
- Scope expansion: New deliverables, extra rounds, “can you also” requests.
- Client drag: Late feedback, unclear ownership, too many stakeholders, decisions revisited.
- Incorrect assumptions: You assumed approvals would be clean, inputs would arrive on time, or revision rounds would be limited.
- Delivery rework: Unclear definition of “done,” QA failures, internal handoff churn.
- Intentional overdelivery: You chose to do extra to preserve a relationship or win Phase 2. That can be a strategy if you recognize it and price for it next time.
The point is not to litigate the past. The point is to pick the right future delivery levers.
Building momentum: How to make WBOs a habit
Ideally, PMs do WBOs after every engagement—and mid-engagement for long-term projects or retainers. But to get big results—and grow your EBITDA—you need to make WBOs an agency-wide habit.
Work with your operations team to ensure they analyze WBOs across clients and PMs. They might find that certain clients need more budget than others (something your AMs have likely been saying all along). They may also find that certain services aren’t profitable—and now you can make changes to fix that.
The exact solution will depend on how your agency approaches operations. But for the best results, make WBOs part of your culture rather than a one-off activity.
The three decision paths that protect EBITDA
A Work Breakout earns its keep when it leads to one of these outcomes.
Path 1: Reset scope
Use the WBO to specify what is included, what is not, and what triggers a change order. Common takeaways:
- Cap revision rounds
- Limit stakeholder review paths
- Define turnaround expectations
- Push “nice-to-haves” into Phase 2
- Shift to more productized services
Path 2: Reset pricing
Sometimes the work is legitimately bigger than the price. In that case, the fix is pricing and packaging, not persuasion. Consider:
- Price add-ons instead of absorbing them
- Create retainer tiers based on complexity
- Separate strategy from production so it doesn’t become free
Path 3: Reset operating rules to prevent repeats
You’re not trying to become a strident ops enforcer—you’re trying to stop recurring causes. Keep it small:
- Tighten the definition of “done”
- Add an approval rule and a decision owner
- Create a single change-control step everyone follows
One fix per recurring pattern beats a grand transformation plan that never ships.
How to delegate WBOs without becoming the bottleneck
This is where WBOs become a habit instead of a burden.
What you do as owner or CEO
Once you’ve delegated, allot 10–15 minutes to:
- Read a one-page summary
- Confirm which bucket caused the variance
- Make one decision: reset scope, reset pricing, or reset operating rules
Your job is not to rework the spreadsheet. Your job is to protect EBITDA.
What your ops leader or outsourced CFO does
As the owner or CEO, ensure your team produces these outcomes:
- Runs the WBO across multiple engagements
- Brings a recommendation, not a data dump
- Maintains an estimate library that improves future scoping and pricing, including the assumptions involved
What project managers do
PMs can run project-specific WBO debriefs after delivery to improve future estimates and reduce repeat mistakes. At larger agencies, PMs will use WBOs to make better short-term decisions—while ops and finance will use aggregate feedback from WBOs to improve pricing and scoping.
Three reasons work breakouts fail
Watch out for these issues, which keep WBOs from becoming a habit:
- They become paperwork. Fix that by requiring a decision every time.
- They become overly detailed. Fix that by capping the breakout at ~8–20 line items and timeboxing the work.
- They become blame. Fix it by treating WBOs as scope and pricing governance, not performance management.
Be careful: If you use WBOs to punish people, your data quality will collapse. People will stop reporting honestly, and you’ll lose the accuracy that protects your margin.
Work breakouts detect the problem. Scope systems prevent it.
A WBO is an early warning habit. Routine use reveals margin leaks while you still have time to do something about it.
If you want that EBITDA improvement to last and to strengthen your exit story, you need consistent scope controls: how you set expectations, handle changes, manage approvals, and prevent “included work” from expanding by default. And that needs to happen at all levels of the agency.
That’s exactly what my on-demand How to Stop Scope Creep training teaches. It’s built to help you protect margin—and your valuation—without turning your agency into a bureaucracy. There’s even a group discount, so you can align your entire team in making better decisions.
Question: What’s your next step to adopt—or upgrade—Work Breakouts (WBOs) at your agency?
