How to run a win/loss analysis on Starch
Win/loss analysis is the practice of systematically figuring out why you're winning deals and why you're losing them — not based on gut feel, but based on patterns across your pipeline over time. Most operators know they should be doing it. Few are doing it well.
What it looks like in practice varies: a B2B SaaS founder combing through lost deal reasons in HubSpot, a services firm reviewing which proposal types convert, a product-led business correlating trial behavior to close rate. The inputs and the questions differ, but the core job is the same — turn your closed deals into a feedback loop that makes the next ones go better.
On Starch, you end up with a live view of your pipeline that actually answers the question. Your CRM data, email thread history, and deal outcomes sit in one place, and you can ask it things like 'what objections did we lose to most often last quarter?' or 'which deal source has the best close rate?' and get a real answer. If you're running structured win/loss interviews, those notes get captured and tagged against each deal. If you want a weekly digest of where deals are stalling, it shows up in your inbox. The dashboard you have at the end of setup reflects your actual sales process — not a generic template you're forced to work around.
Why it matters
Without a systematic win/loss process, you're making product decisions, pricing decisions, and hiring decisions based on the loudest recent anecdote, not the actual pattern. A lost deal you never examined is a lesson you paid for and didn't collect. Get this right and you'll spot the objections that keep repeating, the competitors you're consistently losing to, and the deal characteristics that predict a close — before your pipeline gets thin.
Common pitfalls
First, logging deal outcomes without logging the reason — 'lost' tells you nothing; 'lost to price after legal review' tells you something actionable. Second, only reviewing losses and ignoring wins, which means you don't know what to replicate. Third, running win/loss interviews weeks after a deal closes, when the contact has moved on mentally and the details are fuzzy — the interview should happen within a week. Fourth, keeping interview notes in a separate doc that never gets connected back to the deal record, so the learning stays siloed in someone's Google Drive.
Starch apps used
See this running on Starch
Connect your tools, describe what you want, and the agent builds it. Closed beta is free.
Choose your operator
A version of this guide tailored to your role — same recipe, different starting context.
The AI stack built for small RevOps teams.
The AI stack built for small marketing teams.
The AI stack built for boutique professional services firms.
The AI stack built for real estate operators.
The AI stack built for emerging fund managers.
The AI stack built for event planners and agencies.
The AI stack built for small contractors and builders.
The AI stack built for small customer success teams.
The AI stack built for the founder's office.
Related workflows in Sales & CRM
A strategic account plan is a documented, living view of a specific customer or prospect — their business goals, the stakeholders who matter, the gaps your product fills, the risks to the relationship, and the actions your team is taking.
Read guide →An outbound email sequence is a structured series of messages sent to prospects who haven't heard from you yet — or haven't responded.
Read guide →Stale deals are the quiet tax on a healthy pipeline.
Read guide →A sales enablement library is the collection of materials your team actually uses to move deals forward — battle cards, objection-handling guides, one-pagers, case studies, competitive comparisons, pricing sheets.
Read guide →