A system for agency founders who want to get paid for outcomes — without the retainer blowing up the moment results get close to the line.
Each S maps to a phase of the outcome-retainer lifecycle. Every time you start a new client engagement, run through the 7S in order.
Every step has a gate condition. You don’t move to the next S until the gate is cleared. The most common failure point: skipping from S1 straight to S4 without properly completing S2 and S3. Stuck on what to do next? Find your S. That’s your answer.
| Step | Name | What it means in practice |
|---|---|---|
| S1 | Set the Baseline | Lock the numbers before you agree to anything |
| S2 | Structure the Offer | Design for bad months, not great ones |
| S3 | Screen the Client | Filter ruthlessly — the wrong client breaks the model |
| S4 | Secure the Contract | Specific language prevents disputes |
| S5 | Start the Clock Right | 90 days of calibration before performance begins |
| S6 | Show the Results | Consistent reporting makes fees defensible |
| S7 | Stay or Scale | Renewal is a process, not a last-minute call |
Pin this somewhere visible during every client kick-off. Each S has a gate condition, and the gate is the whole point — it keeps you honest about what’s actually been completed before you commit to the next phase. If you can’t clear the gate, you’re not ready to move on.
Most agencies lose outcome retainers not because they underperformed — but because they never defined what performance meant in the first place.
Outcome-based pricing makes sense in theory. You get paid when results happen. The client has a reason to trust you. Everyone wins.
The problem isn’t the concept. The problem is execution. Most agencies implement it badly and then blame the model. They start without a clean baseline. They leave ‘results’ undefined in the contract. They start the performance clock before the reporting infrastructure is ready.
Six months later there’s a dispute, a tense call, and a retainer that doesn’t renew. This playbook covers the execution layer. The 7S Framework gives you a mental shortcut for the whole system. Each section goes deep on one S.
This model doesn’t work for every client. S3 covers the qualifying filter. If a client is pushing you into pure outcome pricing before you’ve established a baseline, that’s a red flag, not a green light.
You need a number you and your client both agree on before any work starts. Not a rough estimate. A specific, documented figure from real data.
Most agencies skip this or rush it. They take the client’s word for what ‘average performance’ looks like. That’s where the trouble starts.
Here’s a common scenario: client says their average is 40 leads a month. You build your targets around that. Month three you deliver 31 leads. You pull the historical data and find out 40 was their best month in 18 months. Their actual average was 22. You overperformed by 40% and the relationship is damaged.
A baseline isn’t paperwork. It’s the single number every performance fee, every invoice dispute, and every renewal conversation will come back to.
We made this mistake on our second client. Took their word on the numbers. Spent six months in a dispute that could have been avoided with a 30-minute audit. Never again.
Pull 6 to 12 months of data and use the median. If there’s a genuine outlier month — a product launch, a PR spike — note it and exclude it. Agree on the attribution model in writing before the contract is signed. If the client’s data is too patchy to build a defensible baseline, say so: fix the tracking first or restructure the engagement.
Most agencies build the fee structure around the upside scenario. The math looks good when results are strong. They don’t stress-test what happens when results are average or below.
Your base retainer has to cover your costs. Full stop. The performance fee is upside. It’s not the part that pays your team.
Price the floor, not the ceiling. If your model only works when everything goes right, it’s not a model — it’s a bet.
| Model | When it works |
|---|---|
| Pure outcome 100% performance-based | Rare. Only viable with 12+ months of clean data, sales cycles under 60 days, and a client you’ve already worked with. Most agencies shouldn’t start here. |
| Hybrid base + performance fee | The default. Base covers your costs. Performance fee is the margin. Start here with most clients. |
| Tiered bonus flat + milestones | Good for new clients or new service lines where the baseline is thin. Predictable for both sides. |
Most hybrid retainers run 60/40 to 70/30 — base to performance. The base should be at least 110% of your cost of delivery. That buffer matters when a month underperforms.
If the bad-month scenario puts you underwater, the model isn’t ready. Fix the base before you sign anything.
Outcome-based retainers have structural requirements. If the client doesn’t meet them, the model breaks — usually around month four, when results are near the threshold and both sides read the numbers differently.
Qualifying a client isn’t about being picky. It’s about not setting yourself up for a relationship that ends badly.
The hardest thing to learn was saying no to revenue. A client who can’t support this model isn’t a client — they’re a future dispute.
| What to check | What you need to see |
|---|---|
| Data maturity | 12+ months of clean, consistent data for the metrics you’ll own |
| Attribution clarity | They can agree on one source of truth for measurement |
| Sales cycle length | Under 90 days. Longer cycles make attribution arguments almost guaranteed. |
| Internal dependencies | Marketing controls — or directly influences — the metrics in scope |
| Budget stability | The marketing budget isn’t getting reforecast quarterly |
| Team stability | No major leadership changes expected in the next 6 months |
| Channel track record | Some history in the channels you’ll work in. Not starting from zero. |
| Decision clarity | You know who signs off on disputes and renewals |
If you’re unsure, start smaller. A 3-month project to build the baseline and set up reporting is a better entry point than jumping straight into a 12-month outcome retainer.
Most outcome-retainer blowups don’t start in month five. They start in the contract, when both sides were too optimistic to define what ‘results’ actually meant.
You don’t need a 40-page legal document. You need precise language on a handful of specific things. The rest is standard.
Every disputed invoice we’ve ever had came down to one thing: we didn’t define the metric clearly enough in the contract. Now we spend more time on the definition clause than anything else.
The measurement methodology clause is the one that matters most. HubSpot says 60 leads. Salesforce shows 44. Without a pre-agreed answer for which number is on the invoice, you’ll be having that argument on a Friday afternoon.
Starting the performance clock too early is the most common operational mistake in outcome retainers.
The client wants results fast. You want to show momentum. So you skip the infrastructure work and launch campaigns before the reporting is solid. By month three, the data is inconsistent, the baseline is being questioned, and nobody knows what’s actually working.
The first 90 days are a calibration period. You’re not being measured on performance yet. You’re building the system that makes performance measurable.
We used to start running ads in week one. Looked like momentum. What it actually did was corrupt the baseline before we had a clean line to measure against. Now we don’t touch campaign spend until the tracking is verified.
| Phase | What you’re doing |
|---|---|
| Days 1–14 Sprint 0 | Validate data access. Confirm baseline matches the signed document. Set up reporting. Align on metric definitions. |
| Days 15–45 Sprint 1 | First campaigns live. Reporting running. Weekly check-ins start. Flag blockers early. |
| Days 46–75 Sprint 2 | Optimize from early data. Confirm baseline is stable. Deliver a proof-of-direction update at day 45. |
| Days 76–90 Gate review | Confirm reporting is clean. Agree the performance clock starts in month 4. Document any baseline adjustments in writing. |
The performance clock start date needs to be a specific date. Agreed. Written down. Not implied.
In a fixed retainer, a late report is inconvenient. In an outcome retainer, it’s a credibility problem.
Your invoices are tied to performance. That means your reporting needs to be tight, consistent, and documented from the start of the performance period. When a client questions a result — and eventually one will — you want a clean paper trail going back to day one.
The monthly narrative is the most underrated part of this model. Numbers without context get misread. One paragraph of interpretation saves three emails of back-and-forth.
| Report | What it does |
|---|---|
| Weekly snapshot | 3 metrics. Automated. No narrative. Keeps the client informed without creating work. Send every Monday. |
| Monthly performance report | Full metrics review plus a narrative layer — what changed, why, what’s next. Goes out with the invoice. |
| Quarterly business review | Results vs. targets, learnings, next-quarter plan. Live call, 60–90 minutes. Schedule these at the start of the engagement. |
The monthly narrative is the most important thing you write. Numbers without context invite the wrong interpretation. If results are below target, the narrative explains what happened and what you’re doing about it.
Most retainer renewals get negotiated under pressure. The contract is expiring, both sides are scrambling, and whoever is more anxious to close it loses ground.
Renewal isn’t an event. It’s a process that starts at the first QBR and builds from there. By month nine, you should already know which of three paths you’re heading toward.
We start the renewal conversation in QBR2. Not as a pitch — as a ‘here’s what I’m thinking for year two.’ By the time the contract expires, it’s not a negotiation. It’s a formality.
| Path | When to take it |
|---|---|
| Stay & Scale bigger scope, higher targets | Results consistently exceeded baseline. Client sees direct business impact. Use QBR data to propose elevated targets and a higher performance ceiling. |
| Stay & Maintain renew on adjusted terms | Results were solid, relationship is good. Renew with a new baseline that reflects current performance and carry learnings forward. |
| Restructure or Exit change the model | Results were inconsistent. Attribution disputes came up. Go back to a hybrid or project model before the relationship gets worse. |
60 days before the contract expires, do an honest internal review. Not for the client — for you.
Be willing to walk away from a renewal that doesn’t make sense. A broken outcome retainer doesn’t fix itself in year two. The structural problems compound.
Don’t wait for month 12. If you’re in month six and results are consistently below target, address it now.
Every S maps to a project phase. Build the whole retainer lifecycle as a reusable project template — baseline audit, offer design, 90-day onboarding, reporting, renewal — and run it the same way for every client.
Outcome-based retainers aren’t for every client. Some don’t have clean enough data. Some have sales cycles too long to show impact. Some have internal teams that’ll make attribution a permanent argument. But when the fit is right — baseline solid, contract specific, reporting consistent — this is the strongest model available.
The model isn’t the hard part. The execution is. That’s what the 7S is for.
Trellis Digital is a fictional B2B demand-generation agency. This scenario is constructed to show how the 7S plays out end-to-end. Client: Meridian Software, a 120-person B2B SaaS company selling to mid-market finance teams. Engagement: a 12-month outcome-based retainer. Primary metric: qualified pipeline generated.
Trellis had run a traditional fixed-fee retainer for Meridian for eight months. The relationship was fine, but the client kept asking the same question: ‘What are we actually getting for this?’
Maya, the founder, had wanted to shift to outcome-based pricing for a year. Meridian felt right — reasonably clean data, a clear ICP, a ~45-day sales cycle. She proposed converting to a 12-month outcome retainer. The client said yes — but wanted to start the performance clock immediately. Maya ran the 7S instead.
| Step | What Trellis did |
|---|---|
| S1 · Baseline | Maya requested 12 months of Meridian’s HubSpot data. Their contact said average MQL volume was 80/month. Actual median: 54. She flagged this before the contract conversation. Baseline locked at 54 MQLs/month, multi-touch attribution, HubSpot as source of truth. |
| S2 · Offer | Hybrid model: $8,000 base (110% of delivery cost) + $75 per MQL above 54, capped at $12,000 in performance fees in year one. Three scenarios modelled — bad month (45 MQLs, $8k), average (65 MQLs, $8,825), strong (90 MQLs, $11,550). |
| S3 · Screen | Meridian cleared 7 of 8 criteria. The concern: the VP of Sales had been in role only 3 months. Maya flagged it in the dependency clause — if the sales follow-up SLA changed materially, targets could be reviewed. Client signed off. |
| S4 · Contract | HubSpot as source of truth, multi-touch attribution defined in full, 14-day dispute window, dependency clause naming sales and RevOps, and a force majeure clause covering algorithm changes. Legal reviewed the performance definition before signing. |
| S5 · Onboard | Full Sprint 0. Week one: confirmed HubSpot access, pulled a test report. Week two: validated the 54 MQL baseline. Dashboard built and confirmed on day 11. Performance clock set to month 4, day one — no exceptions, even when the client asked to start early. |
| S6 · Report | Automated weekly snapshot: MQLs, SQL conversion, pipeline value. Monthly narrative sent with invoice. First QBR at month 3 — 67 MQLs, above baseline. Maya presented what drove the improvement, what was next, and a risk flag on a coming algorithm update. |
| S7 · Renew | By month nine: a monthly average of 72 MQLs against a 54 baseline — a sustained 33% uplift. Renewal scorecard: zero disputes, stable team, stronger relationship. Proposed expanding to content and nurture at month ten. New contract signed at month eleven. |
| Metric | Result |
|---|---|
| Engagement length | 12 months |
| Baseline MQLs / month | 54 |
| Avg MQLs / month delivered | 72 |
| Performance uplift | +33% |
| Attribution disputes | 0 |
| Year-one revenue (Trellis) | $118,400 |
| Year-two contract value | $144,000 |
| Client NPS at renewal | 87 |
The model didn’t save us from problems. What saved us was having the contract language and the data to handle the problems quickly. The 7S gave us the infrastructure to do that.
Trellis didn’t succeed because results were always above target. They succeeded because they had a system that handled the moments when results weren’t. That’s what the 7S is designed to do.
This playbook is published by 5day.io for informational and educational purposes only. The frameworks, systems, and recommendations represent general guidance based on industry research and operational experience; they do not constitute professional legal, commercial, or contractual advice. All third-party statistics and research citations are attributed to their original sources and reproduced in summary form for illustrative purposes. The Trellis Digital case study is fictional and constructed for illustration. 5day.io makes no warranty, express or implied, regarding accuracy, completeness, or fitness for purpose. Results vary based on agency size, client category, team structure, and implementation discipline. © 2026 5day.io. All rights reserved.
Build the entire 7S lifecycle as a reusable project template — baseline to renewal — and run every outcome retainer the same disciplined way.
Try 5day.io free →Let's get your team onboarded
Try all the premium 5day.io features free for 30 days. No credit card needed.
Built for Marketing Operations
Product
Features
Industries
Teams
Compare
Resources
Company