Debrief
Handoff intelligence for HubSpot CRM.
When a HubSpot user initiates a handoff from the Debrief CRM card, Debrief generates a structured brief for the incoming owner and drafts the message the outgoing owner sends to the contact.
Debrief is a HubSpot marketplace app from Dunamis Studios that generates structured handoff briefs and conversational handoff messages on demand, when a HubSpot user starts a handoff from the Debrief CRM card on a record. It reads the record's history, properties, and engagement to produce a concise brief for the new owner and a personalized message they can send to the contact, so handoffs preserve context instead of restarting it.
Handoffs are where CRM context goes to die.
When a HubSpot record changes hands, the outgoing owner's mental model goes with them: why the customer bought, who the real champion is, what was promised, and what is at risk. Most teams paper this over with a manual handoff note that nobody reads, or skip it entirely and hope the new owner figures it out from the record itself. The result is a quiet, recurring loss of context that shows up as missed renewals, slow ramps, and rework with the customer.
Every feature earns its weight.
Two-stage brief and message generation
Each handoff produces two artifacts. A structured brief for the new owner with sections for Why, People, Timeline, Next Steps, Risk Flags, and Promises, followed by a conversational message tuned to the handoff type (BDR to AE, AE to CS, CS to CS, rep to rep, or marketing to sales).
Coverage on every CRM object type
Debrief renders as a CRM card on contacts, companies, deals, tickets, and every custom object in the portal. One install puts a handoff surface on every record.
Draft Brief preview vs. atomic Handoff
Draft Brief generates a brief for the current owner without changing ownership, useful for prep before a call or internal review. Handoff is the atomic operation: it reassigns ownership to the recipient, attaches the brief as a Note on the record, and writes the event to the Handoff Log.
Pre-flight data-gap scanner
Before generation, Debrief scans the record for missing owner, low engagement signal, record staleness, and missing sender notes. Briefs are held back when the inputs are too thin to produce a useful one.
Handoff Log and per-rep brief inbox
Every Debrief handoff is logged with the previous owner, the new owner, the timestamp, and the reason. Each rep has a Briefs for me inbox of incoming handoffs, filterable by role and record type.
Admin-tunable depth and rollout controls
Per-object-type controls govern which associations to include, how many records per association, whether to fan out to engagements, and how the brief sections are labeled. A dry-run enforcement mode lets admins stage rollout safely without changing record ownership.
Debrief vs. AI meeting summary tools
Debrief is often grouped with meeting summary tools because both involve AI and CRM. The two solve different problems. Meeting summary tools turn one conversation into notes. Debrief turns a record's entire history into a handoff that the next owner can act on.
What triggers it
A user clicking Handoff or Draft Brief on the Debrief CRM card on a HubSpot record.
A meeting ending on Zoom, Google Meet, Teams, or a similar platform.
Input it reads
The full record: properties, change history, associations, engagement timeline, prior owner notes.
Audio or transcript of a single meeting.
What it produces
A structured brief for the new owner and a conversational message they can send to the contact.
A summary, action items, and sometimes a draft follow-up email tied to the meeting.
When it runs
On demand, when the outgoing owner is preparing to hand off the record. Generation is user-initiated, not automatic on every owner change.
After every meeting, regardless of whether handoff is involved.
Where it lives
Inside the HubSpot record. The brief and message are surfaced where handoffs actually happen.
Inside the meeting platform's interface or a separate notes app, often disconnected from the CRM.
Starter, Pro, Enterprise.
Transparent tiers. No hidden per-seat fees.
Answers to the questions we actually get.
What is Debrief?
Debrief is a HubSpot marketplace app from Dunamis Studios that generates structured handoff briefs and conversational handoff messages on demand, when a HubSpot user starts a handoff from the Debrief CRM card on a record. It reads the record's properties, history, associations, and engagement to produce a concise brief for the new owner and a personalized message the previous owner can send to the contact. Briefs are user-initiated, not automatically triggered by ownership changes. The goal is to preserve context across handoffs instead of restarting it from scratch.
How is Debrief different from AI meeting summary tools?
AI meeting summary tools (Otter, Fireflies, Gong, Fathom, and similar) turn a single recorded conversation into notes, action items, and sometimes a follow-up email. Debrief is triggered differently: a HubSpot user initiates a handoff from the Debrief CRM card on a record. It reads the entire record (properties, change history, associations, engagement timeline) rather than one meeting, and produces a brief for the incoming owner plus a draft message the outgoing owner can send to the contact. The two solve adjacent but different problems.
When does Debrief generate a handoff?
Debrief runs on demand, when a HubSpot user initiates one from the Debrief CRM card on a record. The Handoff operation is the atomic action: it reassigns ownership to the recipient, attaches the generated brief as a Note, and writes the event to the Handoff Log. Debrief also offers a Draft Brief mode that produces a brief without changing ownership, useful for call prep or internal review.
What's in a Debrief handoff brief?
Each brief is structured into six sections by default: Why (the strategic why behind the relationship), People (the contacts and stakeholders), Timeline (the relevant chronology), Next Steps (what the new owner should do first), Risk Flags (where the relationship is fragile), and Promises (commitments the previous owner made). Admins can rename the six section labels to match team vocabulary. Alongside the brief, Debrief drafts a conversational message tuned to the handoff type (for example, BDR to AE, AE to CS, or CS to CS).
How much does Debrief cost?
Debrief is a subscription billed per HubSpot portal per month, with three tiers: Starter at $19, Pro at $49, and Enterprise at $149. Each tier includes a monthly credit allotment (50, 250, and 1,000 respectively, doubled in the first month). Each brief consumes one to three credits depending on depth. Credit packs can be purchased on top of the subscription and stack in an addon bucket that does not expire.
Which HubSpot objects does Debrief work with?
Debrief renders as a CRM card on contacts, companies, deals, tickets, and every custom object in the portal. Each object type can be configured separately for which associations Debrief reads, how many records per association, whether to fan out to engagements, and how brief sections are labeled. Once Debrief is installed, every record across these object types has a handoff surface.
Does Debrief use AI, and where does the data go?
Debrief uses a large language model to generate the brief and the message; today the LLM provider is Anthropic, via the Claude API. Customer CRM data is read from HubSpot at handoff time, scoped to only the record context Debrief needs (properties, change history, associations, engagement timeline configured by admins), and sent to the LLM provider for generation. The resulting brief is written back to HubSpot as a Note on the record. Per our LLM provider agreement, your portal's data is not used to train the model. Dunamis Studios servers do not maintain a separate copy of customer CRM data.
Can we customize the brief and message Debrief generates?
Yes. Admins can rename the six brief section labels to match team vocabulary (Why, People, Timeline, Next Steps, Risk Flags, Promises by default). Per-object-type, admins control which associations Debrief reads, how many records per association, and whether to fan out to engagements. Per-handoff-type, admins can add AI instructions and message-template guidance so a BDR-to-AE brief reads differently from a CS-to-CS brief. The Enterprise tier adds portal-level custom prompt tuning.
Ready when you are.
Debrief is on the way. Drop your email and we'll send a single note when it ships.
Get notified when Debrief ships.
One email when the marketplace listing goes live. No newsletter, no drip.
See what's shipped, what's in progress, and what's next.
Debrief roadmap