Win-loss report

Same vault as the ICP report

What we did

Win-loss here is not a survey. Bloom tagged closed-won, closed-lost, and stalled opportunities in the same archive used for ICP (about 3,347 meetings). We listened for the moment a champion could or could not sell upstairs, and for the objections that repeated across R1 to R5.

Named accounts and people are stripped. HubSpot and Salesforce stay as stack words when the quote needs them.

Why deals actually closed

Won patterns

Deals that moved shared a forcing function. The buyer hired a third party who made the black box speak, then handed the champion a page the CEO could read.

• Inherited CRM, fast trust. New in-seat leaders (R1) closed when the partner showed up as the person who bangs the drum. Continuity when the expert left beat another documentation project.
• Visibility, not more campaigns. Operators (R2) closed when the offer named the Direct bucket and forensic reporting. “You do not have a content problem. You have a visibility problem” is the line that re-frames the work.
• Stop waiting on the backlog. Revenue execs (R3) closed when pipeline reviews stopped using X-day-old data and the spreadsheet stopped being the real CRM.
• Ammo for upstairs. Wins included an executive summary the champion could forward. Feature menus did not survive that handoff.

“People show up when there’s a third party. Someone else is banging the drum to make shit happen.”

“We actually believe and understand what’s in our pipeline now.”

Where champions stall upstairs

Lost and stalled patterns

Losses clustered on clarity and sequencing, not on whether the champion liked the team.

• Unclear get. “Didn’t come away with a clear understanding of what they’d be getting.” The champion cannot repeat the offer in a hallway.
• Cheaper alternative. Skepticism that a more experienced, lower-cost shop exists. Without a sharper case, they say they will call around.
• No push to the decision maker. Champion stays open and will not escalate without stronger justification.
• Headcount before systems. Board wants sellers now. The RevOps case never gets a slide. The deal waits, then dies in a hiring plan.
• Operator without a sponsor. Highest-research persona still stalls as a standalone contact. Ask “Who signs off above you?” inside the first two conversations.

“He remains open… but won’t push it to the decision maker without stronger justification.”

“Board approval is the blocker, not internal alignment.”

“Adding headcount without fixing top-of-funnel infrastructure will repeat burning through reps.”

Objections by who is in the room

Objection clusters

What Sales Enablement works first

Implications for the sales team

Sales Enablement inherits this vault the same way Customer Intelligence does. Call query in Slack is the daily surface. Win-loss, battlecards, and coaching are the artifacts.

1. Coach to buyer words: inherited mess, Direct bucket, shadow spreadsheet, prove ROI to the CEO. Drop “attribution modeling” on a first call.
2. Build the upstairs one-pager as a standard output, not a favor. Lost deals die in that gap.
3. Qualify the operator path with a named exec sponsor early. Technical love without a signer is a stall.
4. Productize the headcount-before-systems objection. If the board is hiring sellers into a broken funnel, say so.
5. Keep revenue-exec proof in referral packs. They will not find you on a keyword.

Pair this with the ICP findings report when both teams share the vault. Then map the 90-day install for the starter team you actually hire.