Sales & CRM

How to run a win/loss analysis as Professional Services Founders

Sales & CRMFor Professional Services Founders3 apps12 steps~24 min to set up

You close a big retainer, onboard the client, then six months later you're wondering why three similar proposals lost in Q4. The answer is buried across HubSpot deal notes, a few Gmail threads, a Notion doc someone wrote once, and your own memory of the debrief call. You have no systematic win/loss view — just anecdotes. You know your win rate by feel, not by data. You can't tell if you lose more often on price, scope clarity, or competitor preference. And you definitely can't tell which partner or which service line is winning vs. bleeding. Every quarter you plan to build a proper analysis; every quarter client delivery gets in the way.

Build this on Starch → See the apps used

Sales & CRMFor Professional Services Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

A live win/loss analysis app that pulls closed and lost deals from HubSpot, tags them by service line, deal size, competitor mentioned, and loss reason, so you can see patterns without manually exporting anything

An automated weekly digest that surfaces your win rate trend, average deal cycle by service type, and the top three loss reasons from the past 90 days — emailed to you every Monday morning

A prompt-driven CRM layer on top of your existing HubSpot data where you can ask 'which proposals over $50k did we lose in Q1 and what reason did we log?' and get a real answer, not a filter exercise

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

CRM Sales Agent CRM Growth Analyst

Data sources & config

Starch syncs your HubSpot data on a schedule — contacts, companies, deals, and owners land in Starch automatically and refresh so your analysis stays current without manual exports. Gmail is also synced on a schedule, so deal-related email threads are attached to the right contact records. For any proposal docs stored in Google Drive, connect Google Drive from Starch's integration catalog; the agent queries it live when your app needs to pull in proposal context. Loss reasons and competitor tags you've been logging in HubSpot flow through as-is; if those fields are inconsistent, you can prompt Starch to normalize them on import.

Prompts to copy

Build me a win/loss analysis app that syncs my HubSpot deals, groups them by service line (strategy, implementation, fractional, training), and shows win rate, average deal size, average sales cycle, and top loss reasons for each group. Add a filter for deal size above $25k.

Every Monday at 7am, send me an email summarizing: deals closed and lost in the past 7 days, running win rate for the past 90 days by service line, and any deal where the close date slipped more than 30 days with the last note logged.

Build me a CRM view that shows every deal lost in the past 6 months, with the loss reason field, the competitor field, the proposal value, and the last Gmail thread snippet, sorted by deal value descending.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs your deals, contacts, companies, and owners on a schedule. If your deal stages, custom fields, or loss-reason dropdown are already configured in HubSpot, they come through automatically.

2 Connect Gmail — Starch syncs your messages on a schedule so every email thread tied to a contact is available when you ask questions about a deal's history.

3 Open the Sales Agent CRM app from the App Store as your starting point, then describe the customizations you need: 'Add fields for service line, loss reason category, and competitor mentioned. Group deals by service line on the pipeline view.'

4 Audit your loss-reason field hygiene. Prompt Starch: 'Show me all closed-lost deals in the past 12 months where the loss reason field is blank or says Other — list them with the deal owner and last activity date.' Go fill in the gaps in HubSpot or let Starch help you infer from email thread content.

5 Build the win/loss breakdown app. Prompt: 'Create a win/loss analysis view grouped by service line, showing deal count won, deal count lost, win rate percentage, average deal value, and median sales cycle in days for each group. Filter to the past 12 months by default with a date range selector.'

6 Add a competitor analysis layer. Prompt: 'Add a section showing which competitors appear most often in lost deals, sorted by frequency, with average deal size for each competitor row. Pull from the competitor field in HubSpot deals.'

7 Set up the Monday morning email digest using the Growth Analyst app as a base. Prompt: 'Every Monday at 7am, email me a digest that includes: win rate for the past 7 days, win rate for the past 90 days, top 3 loss reasons by frequency in the past quarter, and any deal that slipped its close date by more than 2 weeks with the last logged note.'

8 Build a 'deals to debrief' automation. Prompt: 'Every time a deal is marked closed-lost in HubSpot, create a task for me in Starch with the deal name, value, loss reason, and a link to the HubSpot record, so I have a debrief queue each week.'

9 Add a proposal-size cohort filter. Prompt: 'Add a filter to the win/loss view so I can toggle between deals under $25k, $25k–$75k, and over $75k. Show me win rate and average sales cycle for each band.' — Most consultancies find their win rate and loss reasons differ significantly by deal size.

10 Run your first quarterly review. Prompt Starch: 'Summarize the past quarter's pipeline. Which service line had the highest win rate? Which had the longest average sales cycle? Which competitor appeared most often in losses over $50k?' Review the output, identify one pricing or scoping change to test, and log it as a note.

11 Share the view with a senior. If a partner or practice lead should see the same analysis, describe a filtered version: 'Build a read-only win/loss view filtered to Strategy engagements only, showing the same metrics, and export it as a weekly PDF I can share with my co-founder.'

12 Revisit and refine the loss-reason taxonomy quarterly. As patterns emerge, prompt: 'Show me the most common loss reasons in plain language from deal notes and email threads for deals lost in Q1 2026, even if the structured field is blank — summarize the top themes.' Use this to improve how you tag deals going forward.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Q1 2026 Win/Loss Review — 12-person strategy consultancy

Sample numbers from a real run

Deals entered pipeline Q1 2026	34
Deals closed-won	11
Deals closed-lost	16
Deals still active (carried to Q2)	7
Win rate Q1 (won vs. decided)	41
Average deal value, won	68,000
Average deal value, lost	52,000
Deals lost where 'price' was loss reason	7
Deals lost where 'scope unclear' was loss reason	5
Deals lost to named competitor (Vendor A)	4

Before Starch, this analysis would have taken a senior consultant half a day in HubSpot reports and a spreadsheet. With Starch syncing HubSpot deals on a schedule, the founder prompted: 'Break down Q1 2026 closed deals by service line, win rate, and top loss reason.' The result: Implementation engagements won at 55% with an average deal of $82k; Strategy engagements won at only 28% with an average deal of $61k. Seven of the sixteen lost deals cited price, but five of those seven were Strategy engagements over $60k — suggesting the issue wasn't price sensitivity broadly, it was that the Strategy value prop wasn't landing at that size. Four losses mentioned the same competitor by name in HubSpot notes. The founder adjusted the Q2 proposal template for Strategy engagements to front-load ROI framing and tightened the scoping process for deals over $50k. None of this required a BI tool or a CRM admin — just a prompt, live HubSpot sync, and a Monday morning digest to track whether the win rate moved.

Measurement

How you'll know it's working

Win rate by service line (strategy vs. implementation vs. fractional vs. training)

Average sales cycle in days, segmented by deal size band (under $25k / $25k–$75k / over $75k)

Top 3 loss reasons by frequency, refreshed quarterly

Competitor appearance rate in closed-lost deals

Deal value won vs. deal value lost as a ratio (to catch systematic underpricing in won deals)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

HubSpot reports (native)

HubSpot's built-in reporting shows deal counts and stage conversion but doesn't let you cross-reference loss reasons against email thread context or ask freeform questions about your pipeline — you get fixed reports, not answers.

Manual spreadsheet (HubSpot CSV export + Excel)

This is what most 12-person consultancies actually do today — it works but takes two to three hours a quarter, goes stale immediately after export, and depends on whoever built the pivot table still being around.

Salesforce + Einstein Analytics

Powerful win/loss analytics at scale, but implementation time is measured in months, per-seat cost assumes a dedicated admin, and it's genuinely overbuilt for a sub-20-person firm.

Clari or Gong

Purpose-built for revenue intelligence and call analysis at quota-carrying sales teams — pricing and feature surface area assume you have a VP of Sales and a dedicated RevOps function, not a founder running the pipeline.

Notion + manual deal log

Flexible and free, but requires someone to maintain the schema, enter data manually after every deal closes, and still won't surface patterns automatically — you're the analyst, not Starch.

On Starch RECOMMENDED

One platform — crm, sales agent crm, growth analyst all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

My loss-reason field in HubSpot is a mess — half the deals have nothing in it. Can Starch still do a useful analysis?

Yes, with some upfront cleanup. Starch syncs your HubSpot deals and can show you exactly which closed-lost records have blank or generic loss-reason fields. You can fill those in directly in HubSpot (they'll resync), or you can prompt Starch to infer likely reasons from the last few Gmail thread snippets attached to those contacts — not a perfect substitute for structured data, but enough to identify obvious patterns you missed. The more you fill in going forward, the better the analysis gets quarter over quarter.

We don't use HubSpot — our pipeline lives in a Google Sheet. Can this still work?

Connect Google Sheets from Starch's integration catalog; the agent queries it live when your app runs. You'll lose the scheduled sync depth you'd get with HubSpot, but you can still build a win/loss analysis on top of your sheet data, ask freeform questions about your deals, and set up the Monday digest. If the sheet is the source of truth, Starch meets you there.

Can Starch automatically pull in notes from client debrief calls?

If your debrief notes live in Gmail, Notion, or Google Docs, yes — Gmail syncs on a schedule, and Notion syncs on a schedule too, so anything logged there is available for Starch to reference. If you record debrief calls, Starch doesn't transcribe audio natively today, but if you use a tool that produces transcripts as Google Docs or Notion pages, those flow through.

Is my deal data stored in Starch or just queried live?

HubSpot and Gmail are scheduled-sync providers, meaning data refreshes on a schedule and is stored in Starch's database — that's what makes the analysis fast and lets you ask historical questions without hitting HubSpot's API every time. Google Sheets or other apps connected from the integration catalog are queried live when your app runs, not stored. Honest caveat: Starch is not a long-horizon data warehouse. It's built for live operational surfaces, not archived analytics going back years.

Will this replace our HubSpot subscription?

No, and it's not designed to. Starch sits on top of HubSpot — your team keeps logging deals, updating stages, and using HubSpot however they already do. Starch pulls that data, lets you build analysis and automations on top of it, and answers questions your HubSpot reports can't. You'd keep HubSpot as the system of record for deal data entry.

Is Starch SOC 2 certified? Our clients are sensitive about data.

Not yet — Starch is not currently SOC 2 Type II certified. If that's a hard requirement for your firm's data policies, that's worth knowing upfront. It's on the roadmap.