A server-side engine mapping eight events (estimate synced, estimate sent, estimate approved, intake form submitted, contract sent, customer signed, counter-signed, project started) onto the canonical journey stages, advancing the local card and optionally mirroring the move to a connected CRM.
Also called: pipeline moves automatically · customer signed and the card moved · auto advance the deal
- 1Each event has a default target stage; a tenant can override the target per event or switch the automation off
- 2FORWARD-ONLY: rows are read first and only those ranked behind the target advance — 'A resend of an estimate can't pull a contract_signed deal back to estimate_sent'
- 3Any project-pipeline stage outranks every sales stage, so an automation can never yank a project card back into sales
- 4Advancing stamps entered_stage_at, clears the follow-up badge, and resets the per-visit SOP checklist after snapshotting it onto the audit row
- 5The CRM mirror is timeout-guarded and kill-switchable; every failure path warns and skips rather than breaking the customer's click
Automated deal progression had never once fired. It looked deals up by a column that does not exist, got nothing back, and advanced nothing — for every event, for every builder, for as long as it had been running. Hundreds of lifecycle records existed and not one had been written by automation, and the failure surfaced only as a warning in a log nobody reads. Deals advance off real customer actions now, and each stage's checklist resets on entry, because without that a later snapshot credited every earlier stage's work to whichever visit happened to close — eight estimate-stage steps filed under New Lead.
- Manual pipeline maintenance
- Re-sends regressing advanced deals
- Silent, invisible automation failure
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 →