A per-user, per-org demo lead with a story attached (notes included) that appears on the real pipeline board so tours can point at a real card. It is created before step one, removed on completion and on exit, and is fenced off from every system that could turn it into real activity.
Also called: demo lead · practice data · fake lead to learn on · sandbox lead
- 1The card appears instantly: its id is a pure function of (org, user), so an optimistic card is injected client-side and the server seed heals it in place
- 2Leak guards, one per trap: `demo-` id prefix keeps it out of lead distribution; assigned to you so it doesn't hit the Leads Manager backlog hold; email on the reserved @demo.invalid domain; GoHighLevel ids never stamped; no stage-transition log rows so analytics, leaderboard and Rep Score never see it; no opportunity row so the follow-up cron ignores it
- 3Cleanup deletes only rows where is_demo = true AND demo_owner_user_id = you AND org = your org
- 4A flag is set before seeding and cleared only after a successful cleanup, so a crashed session's rows get swept next time
Learning the pipeline with nothing on it teaches nothing; the whole point is dragging a card between columns and seeing what that sets off. Practising on a real customer's card is worse — one mis-drag on a live job and somebody's client gets an automatic 'your project has started' message. Walkthroughs that need a lead put a single clearly badged practice lead on the real board, shaped so it can't be counted in reports or routed to a rep, and take it away at the end. It works on live accounts on purpose: this is for the builder, not for testing.
- Nothing to point at on a brand-new board
- Practice data polluting analytics, leaderboards and lead routing
- Fake leads left behind after a training session
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →