Outcome. Once an edition is delivered, every sponsor account gets stamped with the edition it just bought, and the next edition deal is created automatically for the ones who scored you nine or ten, while the unhappy ones get a phone call before anyone mentions a renewal price.
Workflow map
Enrollment, branches and actions at a glance
events-003
flowchart TD
A[Sponsorship deal reaches Delivered] --> B[Add edition to company history]
B --> C[Add contract value to lifetime value]
C --> D[Delay 2 days]
D --> E[Debrief task for the account owner]
E --> F{Score known within 21 days?}
F -->|no| G[Chase the survey, end]
F -->|yes| H{Score?}
H -->|9 or 10| I[Create next edition deal, first refusal task, notify manager]
H -->|7 or 8| J[Debrief first task, notify owner]
H -->|6 or below| K[Director call task in 2 days, no offer]
H -->|out of range| L[Alert marketing operations, survey scale wrong]
When to use it, when not to
- UseUse it when sponsors come back year after year and the first refusal window is the commercial moment that matters, which is most established events.
- UseUse it when you want the renewal pipeline to open in the fortnight after the doors close, while the team still remembers who was pleased and who was not.
- SkipDo not use it without a post event survey that sponsors actually answer. With no score the workflow correctly refuses to open anything, and you will have built a stamping machine.
- SkipDo not use it when renewal is negotiated centrally once a year for a portfolio of events. One deal per sponsor per event is the wrong shape for a framework agreement.
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.11 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.6 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.7 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, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
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.
