Skip to content

Pre-call research brief generated by a Breeze agent before every deal meeting

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Sales Hub Professional.

Deal10 stepsUpdated for HubSpot seat pricing
OutcomeThe day before a scheduled deal meeting, the deal owner gets a short written brief on the account, built from what the CRM already holds, without anyone opening five tabs to prepare.
Workflow mapsales-ops-050
Deal has Next meeting start, brief status pending leads to Delay until Next meeting start minus 1 day, 07:00. Delay until Next meeting start minus 1 day, 07:00 leads to Next meeting start still known?. Next meeting start still known? leads to No, meeting canceled: Set brief status = skipped; Yes: Run an agent: Pre-call research brief, output to Pre-call brief. Run an agent: Pre-call research brief, output to Pre-call brief leads to Brief written?. Brief written? leads to No: Set status = failed; Yes: Set status = generated, stamp generated at. Set status = failed leads to Create task for deal owner with manual checklist. Set status = generated, stamp generated at leads to Internal email to deal owner: brief ready. No, meeting canceled Yes No Yes Deal has Next meeting start, brief status pending Delay until Next meeting start minus 1 day, 07:00 Next meeting start still known? Set brief status = skipped Run an agent: Pre-call research brief, output to Pre-call brief Brief written? Set status = failed Set status = generated, stamp generated at Create task for deal owner with manual checklist Internal email to deal owner: brief ready
Deal has Next meeting start, brief status pending leads to Delay until Next meeting start minus 1 day, 07:00. Delay until Next meeting start minus 1 day, 07:00 leads to Next meeting start still known?. Next meeting start still known? leads to No, meeting canceled: Set brief status = skipped; Yes: Run an agent: Pre-call research brief, output to Pre-call brief. Run an agent: Pre-call research brief, output to Pre-call brief leads to Brief written?. Brief written? leads to No: Set status = failed; Yes: Set status = generated, stamp generated at. Set status = failed leads to Create task for deal owner with manual checklist. Set status = generated, stamp generated at leads to Internal email to deal owner: brief ready. No, meeting canceled Yes No Yes Deal has Next meeting start, brief status pending Delay until Next meeting start minus 1 day, 07:00 Next meeting start still known? Set brief status = skipped Run an agent: Pre-call research brief, output to Pre-call brief Brief written? Set status = failed Set status = generated, stamp generated at Create task for deal owner with manual checklist Internal email to deal owner: brief ready

When to use it, when not to

Use it

  • Use it when reps prepare meetings by hand and the prep quality depends on who is doing it and how much time they have that morning.
  • Use it when the deal record already carries substance: logged calls, emails, notes, company data. An agent reading an empty record writes an empty brief, and reps stop trusting the output after two of those.
Read more on when to use itShow less

Skip it

  • Do not run it on every meeting in a high-volume transactional pipeline. Each agent run consumes the portal's AI credit balance, and a 20-minute renewal call rarely justifies a generated brief. Filter by deal amount or pipeline instead. (check in your portal: whether the Run an agent workflow action draws on the portal's Breeze credit balance, and at what rate per run)
  • Do not treat the brief as customer-facing content. It is an internal prep note, it can be wrong, and it should never be pasted into an email to the buyer.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 8 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 10 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 6

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 5 cases, 4 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Sales ops spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library