Always-on · Why deals move
Deal Enablement Director
Win-loss from the calls, not only from the CRM field. Battlecards and coaching from the same vault.
On the always-on team
You own the Mac mini. Bloom installs it in your office. Day to day you talk to the Orchestrator in Slack. A human from Bloom stays. This seat is one employee on that roster, not a project that ends at kickoff.
What this seat does
Owns why deals are actually won and lost, from the calls rather than the loss-reason field. Same vault as Customer Intelligence, different lens.
- Reconciles what the CRM says with what was said on the calls.
- Sample size stated on every rate. Directional when n is small.
- Coaching and battlecards the floor can use, between reports, in Slack.
The monthly report
Win-loss report. Delivered day 1. Eleven public sections. The evidence appendix stays internal.
- Executive synthesis: the dominant win, the dominant loss, and what changed
- Win rate by segment, using the same slices as the ICP pack, with sample size on every row
- Why deals were won, with the language from the calls
- Why deals were lost: loss taxonomy, ranked
- Competitor involvement: who showed up, in which deals, and what was said
- Objection ranking, and which objections travel with loss
- Stage drop: where deals stall, and what happened on the call before they did
- CRM reconciliation: where the recorded reason disagrees with the calls
- Expansion and referral signals
- Recommended messaging fixes for the rest of the team
- Decisions and next actions
See an example win-loss report.
Hire Deal Enablement.
Book a call. We look at where this seat fits on your team. Every new client gets a 90-day roadmap.