GTM

How Do You Run a Win-Loss Review With Only Five Deals?

Written by
Pravin Kumar
Published on
Oct 10, 2026

Can you learn anything from a win-loss review with only five deals?

Yes. A win-loss review with five deals will not give you statistics, but it can give you patterns, quotes, and hypotheses worth testing. With a small sample, you study each deal in depth instead of counting outcomes. The goal is to find the two or three reasons that keep showing up, then check them against the next ten deals.

Most win-loss advice assumes a sales team closing dozens of deals a month. That is not the reality for a seed-stage startup or a small services firm. You might close one deal a week, or one a month. Waiting for a big sample means waiting a year to learn things you need now.

This post is for founders and first sales hires who want to learn from every deal while the pipeline is still small.

Why does a small sample still matter?

A small sample matters because early deals carry the most information per deal. Each one tests your ICP, your message, your pricing, and your sales process at once. The patterns are rough, but they arrive while you can still change direction cheaply. Waiting for statistical confidence means making decisions too late to matter.

Early-stage GTM is mostly about reducing uncertainty. You do not know yet which segment buys fastest, which objection kills deals, or which competitor you lose to most. Five well-studied deals will not settle those questions, but they will tell you which ones to watch.

The trick is to treat findings as hypotheses, not conclusions. "Two of five lost deals mentioned onboarding time" is not proof that onboarding loses deals. It is a reason to ask about onboarding on every call for the next month.

Which five deals should you pick?

Pick a mix of wins and losses, ideally at least two of each, from the last few months. Include one deal you expected to win and lost, and one you expected to lose and won. Surprises teach the most. Skip deals that died for reasons outside anyone's control, like a company shutting down.

Recency matters. Buyers forget quickly, and your product and pitch change fast at this stage. A deal from a year ago reflects a different company. Stick to the last quarter if you can.

Fit matters too. If one deal was far outside your ICP, it can distort the review. Note it, but do not let it drive conclusions. The point is to learn about the buyers you want more of.

If you track loss reasons in your CRM, start there. My tutorial on building a lost deal reason report in HubSpot shows how to capture them. But remember that CRM loss reasons are usually written by the rep in a hurry. They are a starting point, not the answer.

How do you gather the evidence for each deal?

Gather evidence from three sources for each deal: the CRM record and emails, call recordings or notes, and a short conversation with the buyer. The buyer conversation is the most valuable and the most skipped. Ask for fifteen minutes, promise no sales pitch, and keep that promise.

Start with the paper trail. Read the deal history in HubSpot or your CRM, every email, and any proposal. Note the timeline. When did the deal stall, speed up, or change hands? Those moments usually explain the outcome better than the final note.

Then review calls. If you use Gong, Fathom, or another call recorder, listen to the first discovery call and the last call before the decision. If you only have notes, read them. Look for the buyer's own words about their problem and their concerns.

Finally, ask the buyer. Lost buyers often agree to a short call if you make it clear you want to learn, not to reopen the deal. Won buyers are usually happy to explain why they chose you. I have written more about running these conversations in my post on win-loss interviews that improve B2B marketing.

What questions should you ask buyers?

Ask buyers what triggered their search, what else they considered, what nearly stopped them, and what finally decided it. Keep the questions open and neutral. Avoid asking whether they liked your product. You want the story of their decision in their words, not a rating of your sales team.

The trigger question is often the most revealing. "What was happening in your business when you started looking?" tells you which events create demand. Those events become signals you can watch for in outbound.

The alternatives question shows your real competition. Sometimes it is another vendor. Often it is a spreadsheet, an internal team, or doing nothing. Knowing which one you lose to changes your messaging.

The "what nearly stopped you" question works for wins and losses. Winners will tell you about the risk they almost did not take. Losers will tell you the risk that won. Both are objections you need to handle earlier in the sales process.

How do you find patterns across so few deals?

Find patterns by putting every deal into the same simple grid: trigger, alternatives considered, main concern, deciding factor, and stage where momentum changed. Read across the rows. Anything that appears in three or more of the five deals is a strong hypothesis. Anything in two is worth watching. One-offs are noted and set aside.

A spreadsheet is enough. One row per deal, one column per question. Use the buyer's own words in the cells wherever you can. Paraphrasing too early hides the language that will later make great copy.

Look for differences between wins and losses, not just common themes. If every win involved a technical champion and every loss did not, that is a strong signal about who you need in the room. If wins came from one industry and losses from another, that is a segment signal.

Be honest about what you cannot know. Five deals cannot tell you your win rate against a competitor or the effect of a price change. Say so in your summary, so nobody treats a hypothesis as a fact.

What do you do with the findings?

Turn each strong hypothesis into one specific change and one way to test it. If buyers worry about onboarding, add an onboarding plan to proposals and track whether that concern comes up less. If a segment wins faster, tilt next month's outbound toward it. Small, testable changes beat a big strategy rewrite.

Share the findings in a short document with three parts: what you learned, what you will change, and what you will watch. Keep it to one page. Long reports from small samples invite overconfidence.

Update your sales process too. A recurring objection belongs in your discovery questions. A recurring deciding factor belongs in your homepage and pitch deck. A recurring trigger belongs in your lead scoring and outbound signals. This is where win-loss connects to the rest of your GTM system.

How often should you repeat the review?

Repeat the review every time you close another five to ten deals, or once a quarter, whichever comes first. Each round tests the last round's hypotheses and adds new ones. Over time, the small reviews add up to a reliable picture of why you win and lose, built while it was still useful.

Keep the grid going. Each new deal adds a row. After a few rounds, you will have a dataset that is large enough to show real patterns, and you will have built the habit of learning from every deal instead of only the big ones.

This is one of the habits I push hardest with early-stage founders. The teams that review every deal learn faster than the teams that wait for enough deals to review.

What should you do next?

Pick your last five closed deals, including at least two wins and two losses. Build a simple grid with trigger, alternatives, main concern, deciding factor, and turning point. Fill it from your CRM and calls, then ask each buyer for fifteen minutes. Write a one-page summary and pick one change to test.

Then set a reminder to repeat it after your next batch of deals. The second round is where hypotheses start turning into knowledge.

If you want help setting up a win-loss process or connecting its findings to your CRM and outbound system, reach out. I am happy to talk it through.

Get found, cited and the back office automated

Let's make your site the source AI engines quote and wire up the systems behind it.

Contact

Let's get your website found and cited by AI

Tell me what you're working on, whether AI search is skipping your product, your back office is buried in manual work, or you need a build that does both.

Got it, thanks. I read every message personally and reply within 1-2 business days.
Oops! Something went wrong while submitting the form.