What it does
Use when a user mentions "post-demo nurture", "post-demo cadence", "after demo follow-up", or asks for related help. After a demo meeting completes, fire a multi-touch nurture cadence over 90 days — value content at Day 7, case study at Day 14, ROI calculator at Day 30, customer story at Day 60, decision-stage check-in at Day 90 — branching on engagement signals.
You get
Segment
Segment produced by this recipe.
Content Asset
Asset produced by this recipe.
Journey
Journey produced by this recipe.
Dashboard
Dashboard produced by this recipe.
How it works
Identify Recent Demo Attendees
Create SegmentBuild a segment
Build Cadence Content
Generate ContentGenerate 5-touch post-demo content. Touch 1 (Day 7): value content - a playbook or guide directly relevant to use case discussed in demo. Touch 2 (Day 14): case study matching the prospect
Build Nurture Journey
Create JourneyBuild a 5-touch journey wired to the post-demo segment: touch 1 at Day 7, touch 2 at Day 14, touch 3 at Day 30, touch 4 at Day 60, touch 5 at Day 90, all relative to meeting_completed. Add a high-engagement branch: if the prospect clicks on touch 1 or 2, route to a dedicated AE-outreach task instead of continuing the automated cadence (signal of buying intent). Exit conditions: deal_created, meeting_scheduled (re-engagement), or unsubscribe.
Build Post-Demo Performance Dashboard
Build DashboardCompose a dashboard tracking post-demo nurture conversion: demo-to-deal conversion rate (60d, 90d), drop-off by touch (which touches lose the most attention), AE-outreach handoffs triggered (count of high-engagement branches), and deal-velocity comparison between demos that went through the cadence vs not. Flag touches with reply rate below 1% (content failure signal).
Ready to run this recipe?
Tell Blu what you need. It builds the segment, content, journey, and dashboard in minutes.
Sign up free