Outcome. A qualified discovery call produces a deal in the AE's pipeline automatically, with the contact already associated, instead of an SDR manually creating and populating a deal after every call.
Workflow map
Enrollment, branches and actions at a glance
sales-ops-025
flowchart TD
A[Meeting outcome changes to Qualified] --> B{Existing open deal in target pipeline?}
B -->|Yes| C[Notify SDR: already has an open deal]
B -->|No| D[Create deal, associate contact, owner = AE]
D --> E[Create handoff call task for AE]
E --> F[Notify AE of new qualified handoff]

When to use it, when not to
- UseUse it when SDRs already log a consistent outcome value after each discovery call and that value reliably distinguishes qualified from not-qualified.
- UseUse it when there is a clear, single next pipeline stage for a freshly qualified deal (for example, "Discovery Scheduled"), so the created deal lands somewhere consistent.
- SkipDo not use it if outcome logging is inconsistent across SDRs; a workflow built on an unreliable property just automates the inconsistency instead of fixing it. Fix the logging habit first.
- SkipDo not use it if a contact can have more than one open deal created from repeat qualified meetings; add a check for an existing open deal first (see Known pitfalls) or duplicate deals will pile up.
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.3 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.3 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 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.3 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.





