Use casesResearch
Turn lost deals into a pattern you can see
Mitra collects every deal lost this week into one running document, grouped by reason. The agent reads the closed-lost deals in HubSpot with their reason, value and notes. They are appended to a Notion page under themes like price or timing, and the tally goes to Slack.
Every Friday at 5pm, add this week's closed-lost HubSpot deals to my 'Why we lose' Notion page, grouped by theme. Post the tally to #gtm.
200 credits to start · no credit card
What the agent actually does.
Collect the week's losses
The agent reads the deals marked closed-lost since the last run, with their value, stage, owner and reason.
Read what was actually said
The notes and last emails carry the real reason, which is usually narrower than the dropdown a rep picked.
Group the losses by theme
Price, timing, a missing feature, a competitor, no decision: each deal goes under the theme it belongs to.
Append to the document
The week is added to your Notion page rather than replacing it, so three months read as a trend.
Post the tally
The count per theme and the value behind each go to Slack, so the largest reason reaches sales and product together.
Make it yours.
For sales leads and product managers who each know why deals are lost, separately, with no document ordering the reasons. Change any of this by saying so — there is nothing to rewire.
- Give the deals lost to a named competitor their own section.
- Include deals that went quiet without a formal loss.
- Post to a product channel too, so the feature gaps reach the roadmap.
Questions, answered.
How do I track why we lose deals without asking reps to write it up?
Can Mitra keep one running document instead of a new one each week?
Ready to
reclaim your day?
Build my first agent200 free credits · no credit card · nothing to install