Skip to content
Mock demo · simulated data

A mock demo for marketing and revenue teams

Why did this contact get that message? Replay the run.

NurtureRun follows one contact through an automation flow, step by step. See which condition sent them left or right, how long each wait lasted, and where a run stopped, without asking an engineer to dig through logs.

All data on this site is simulated. Nothing is sent to anyone.

StartOpenedit?Yes: task forthe ownerNo: reminder,wait 3 days

One flow, two contacts, two stories

A welcome series with a wait, three conditions, a webhook and two goals. Flip what the contact did and the path changes.

Try it: the same flow, two different contacts

  1. Trigger
  2. Update field
  3. Add tag
  4. Send message
  5. Wait
  6. Condition
  7. Condition
  8. Webhook
  9. Notification
  10. Goal

This contact opened the welcome message and works at a team of 50 or more, so the owner gets a task and a lead alert is posted.

What the demo shows

  • Triggers and branches

    A form, a tag or a stage change starts a run. Conditions read the contact record and its activity, then pick a branch.

  • Waits and messages

    Pause for hours or days, send a message, notify the owner, add a tag, update a field, or call a webhook you control.

  • A log for every run

    Each step records when it ran, what it decided and how it ended. A failed step is marked as failed, not silently skipped.

  • Drop-off at a glance

    See how many runs reached each step, then open the ones that stalled and read what happened.

The last three weeks, simulated

Running
27
meeting booked
40
marked engaged
43
no engagement
32
Failed at a step
2

144 runs of the same flow. Open the run log to see who stalled and why.