Add or remove reps and leads in batches (or set a target count), press Distribute to route them through the real routing engine by county/state/zip, then Simulate to build realistic lifecycles — speed-to-lead timings, stage progressions and roughly 38% wins — so analytics, the leaderboard and rep scores populate.
Also called: fake leads for testing · test the routing · simulate conversions · fill the leaderboard
- 1The panel prints the intended order: +reps → +leads → Distribute → Simulate
- 2Seeded reps are also added as crew members so they appear in the pipeline assignment pickers
- 3Everything is prefixed (test-rep-, test-lead-, test-crew-) so 'clear seed' removes exactly what was created
- 4Gated to admins and disabled in production unless explicitly allowed
Demo data cannot test lead routing, because demo data is deliberately kept out of routing — that is what stops a pretend lead landing on a real rep's phone at nine at night. So 'will leads actually reach the right person when we switch this on' had no safe answer until the first real lead arrived and proved it either way. This mints reps and leads that the live distribution engine, the leaderboard, the analytics and the rep score all treat as real, then simulates a month of activity against them, with every row marked so the lot can be wiped in one go.
- Routing rules that can only be verified on real leads
- Empty dashboards that can't be evaluated before go-live
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 →