Outcome. The 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 map
Enrollment, branches and actions at a glance
sales-ops-050
flowchart TD
A[Deal has Next meeting start, brief status pending] --> B[Delay until Next meeting start minus 1 day, 07:00]
B --> C{Next meeting start still known?}
C -->|No, meeting canceled| D[Set brief status = skipped]
C -->|Yes| E[Run an agent: Pre-call research brief, output to Pre-call brief]
E --> F{Brief written?}
F -->|No| G[Set status = failed]
G --> H[Create task for deal owner with manual checklist]
F -->|Yes| I[Set status = generated, stamp generated at]
I --> J[Internal email to deal owner: brief ready]
When to use it, when not to
- UseUse 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.
- UseUse 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.
- SkipDo 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)
- SkipDo 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.
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.8 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.10 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.6 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.4 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
