MSP Win/Loss Review Template: Debrief Lost Quotes and Fix Pricing and Scope
Most MSPs only talk about a lost quote when someone is mad. The deck gets blamed. Price gets blamed. The prospect "went dark." Then the next proposal repeats the same shape, the same discount habit, and the same unanswered risk.
A win/loss review is the boring fix. Ten minutes after every closed quote, won or lost, one person writes what actually happened. Once a month, the vCIO or sales lead looks at the pile and changes the offer, not the storytelling.
This template is for the account manager, vCIO, or senior operator who already owns the quote approval and proposal path. It feeds pricing and scope decisions. It is not a CRM science project.
What this review is for
Use it when:
- You lose on "price" and nobody can say whether the scope was fat, the tier was wrong, or the discount was panic.
- Wins feel random, so the team cannot copy what worked.
- Renewals and new logos share a pipeline, but loss reasons stay in Slack.
- The owner asks why margin slipped and the answer is a shrug.
Skip it when the "loss" was a tire-kicker who never saw a scoped proposal. If there was no real quote, there is nothing to debrief.
Loss-reason taxonomy
Tag every closed quote with one primary reason. Add one secondary note if needed. Do not invent seven overlapping labels.
| Code | Primary reason | What it means | Usual fix |
|---|---|---|---|
| PRICE | Price / margin | Buyer chose a lower number with comparable scope | Revisit tiers, discounts, or which labor is included |
| SCOPE | Scope fit | Offer missed required work, or padded work they refused | Tighten discovery and the scope of work |
| TIMING | Timing / budget cycle | Need was real, money or decision window was not | Park with a next-touch date; stop rewriting the same quote |
| INCUMBENT | Incumbent lock | Current MSP or internal IT kept the seat | Change the wedge (project, assessment, compliance) or walk |
| TRUST | Trust / proof | Buyer doubted delivery, references, or risk ownership | Fix proof pack, references, and QBR evidence |
| NOD | No decision | Stall with no competitor win | Kill or requalify; do not keep "updating the PDF" |
Rules that keep the taxonomy honest:
- "Price" is only primary when the buyer compared a similar scope. If they cut half the stack out, that is SCOPE.
- "Went with someone else" is not a reason. Name whether it was PRICE, SCOPE, INCUMBENT, or TRUST.
- Won quotes get a reason too. Tag the winning lever: tier clarity, assessment-backed scope, faster cycle, or relationship. Patterns on wins matter as much as losses.
10-minute debrief form
Fill this the same day the quote closes. Owner is the AM or vCIO who ran the deal. Keep it to one page.
| Field | Prompt | Example |
|---|---|---|
| Quote ID / client | Legal name + quote version sent | Acme / Q-2411-v3 |
| Outcome | Won / Lost / No decision | Lost |
| Primary reason code | One code from the table | PRICE |
| Secondary note | One sentence only | Discounted year one to match a thinner competitor stack |
| What the buyer compared | Named alternative or "unknown" | Local MSP + cheaper M365 SKU mix |
| Scope delta vs last version | What changed after first send | Removed vCIO hours; added after-hours block |
| Margin at send | Gross margin on the version they saw | 38% recurring / 22% project |
| Decision date | When they said yes/no/stall | 2026-11-04 |
| Asked for feedback? | Yes/No + channel | Yes, email to CFO |
| Next action | One concrete change or park | Review Good/Better/Best after-hours packaging |
Debrief questions that beat "why did we lose?":
- What did the buyer say was out of scope, overpriced, or unclear?
- Which line items did we discount, and who approved that?
- Did discovery miss a constraint that showed up late (compliance, locations, union hours, M365 SKU)?
- If we won, what proof or packaging made the yes easier?
If the seller wants a longer story, put it in the CRM note. The form stays short so people actually fill it.
How to ask a lost prospect for feedback
Ask once, within two business days, from the person who had the relationship. Do not send a survey with twelve boxes.
Suggested email:
Thanks for the clear decision. For our own cleanup, what was the main reason you went another direction: price for a similar scope, missing scope, timing, or confidence in delivery? One sentence is enough. It helps us stop guessing.
If they answer, paste the sentence into the secondary note. If they do not answer, leave the code as your best internal call and mark feedback "No."
Never argue the decision in the feedback ask. You are collecting a tag, not reopening the deal.
Monthly pattern review (45 minutes)
Once a month, the vCIO or sales lead reviews every closed quote from the last 30 days. Bring the forms, not the PDFs.
Agenda:
- Count outcomes: won, lost, no decision.
- Stack primary reason codes. Call out any code above 30% of losses.
- Pick one pattern to act on this month. Not five.
- Assign an owner and a due date.
- Note which open pipeline deals share the same risk.
Pattern to action
| Pattern you see | Likely root | Action this month |
|---|---|---|
| PRICE dominates losses | Tiers too fuzzy, or discounting is the close habit | Rebuild Good/Better/Best inclusions with the service tiers template; freeze ad-hoc discounts without owner approval |
| SCOPE dominates | Discovery is light or SOW language is soft | Require the discovery checklist before quote v1; rewrite two recurring scope blurbs |
| NOD dominates | Unqualified pipeline | Add a kill rule after two unanswered decision dates |
| TRUST shows on mid-market logos | Proof pack is weak | Attach one QBR scorecard or assessment excerpt to every proposal over a set ARR |
| Wins cluster on assessment-backed quotes | Live findings sell better than generic stacks | Prefer assessment-to-scope before big new logos |
Write the chosen action as a change to packaging, process, or qualification. "Sell harder" is not an action.
Where this sits in the quote path
- Discovery and standards check.
- Scope and quote build, then approval.
- Send, follow-up, close.
- Win/loss debrief the same day.
- On a win, run the quote-to-agreement handoff so the signed version does not leak margin.
- Monthly pattern review feeds next month's tiers, discounts, and discovery.
If quote history lives in email and versioned PDFs, the monthly review turns into archaeology. Keep the client, opportunity, line items, discounts, and outcome on one quote record so the debrief references the version the buyer saw.
Scopable's MSP quoting workflow keeps that quote history with the client and opportunity, so a win/loss tag sits on the same record as scope and margin instead of a separate spreadsheet.
When you want that path in one place, start Scopable for free.
Copy-paste checklist
Same-day debrief:
- Outcome tagged Won / Lost / No decision
- One primary reason code
- Margin and version ID recorded
- Feedback asked once (if lost)
- Next action written in one line
Monthly review:
- All closed quotes from the period in the stack
- Reason-code counts written down
- One pattern chosen
- Owner and due date assigned
- Open deals checked for the same pattern
Run the form for two weeks before you change pricing. The first month is for clean tags. The second month is for the fix.
