Stages Advance From Real Actions

The board advances when the estimate syncs, the customer approves, the form arrives or the contract is signed — a hand move is allowed but recorded as an override.

What it is

A server-side automation engine maps real events to stages: estimate synced to Create Estimate, estimate sent to Estimate Sent, customer approved to Estimate Approved, intake form submitted to Info Submitted, contract sent to Contract Sent, customer signed to Co-sign Pending, builder countersigned to Ready to Start. Every hand move except New Lead to Contacted asks for confirmation first and is stamped in the audit log as a manual override.

Also called: automatic stage movement · stage automation · pipeline moves itself · no fake progress

See it
Stages Advance From Real Actions
Prepared for
Ronan Petsch
1140 Ridge Line Rd · Fair Play
Shell package$26,040
Concrete & site$7,560
Doors & windows$5,040
Trim & finish$3,360
Total
$42,000
Signature
The manual-override confirm dialog quoting the doctrine, over a board where a card has just auto-advanced to Estimate Approved. Sample data — no customer information appears here.
How it works
  1. 1The engine runs after the customer-facing action already succeeded, so a failure never breaks the customer's experience
  2. 2Automations are forward-only: a resent estimate cannot pull a signed contract back to Estimate Sent
  3. 3The one free manual move is New Lead to Contacted, because contacting a lead has no system event to detect
  4. 4Every automated hop writes the same lifecycle row a hand drag would
Why we built it

A board moved by hand is a board that reflects what somebody remembered to drag, not what happened. Stages now advance from real events: the estimate syncing, the customer approving, the intake form arriving, the contract being signed. Hand moves are still allowed but are recorded as overrides in the audit timeline, and automation never drags a card backwards — resending an estimate cannot pull a signed deal back to Estimate Sent. When a sync fails the failure stays quiet on the customer's side, because by then the customer has already successfully signed and should not meet an error from a system they never touched.

The problem
  • A pipeline that only reflects what someone remembered to drag
  • Stage position as a claim rather than a fact
  • Automations dragging a signed deal backwards
Sound familiar?
What you get
The board reflects work, not clicks
A hand move is still possible but leaves a trace
Nothing an automation does can regress a deal
What's inside
Hand Moves Are Logged as Overrides
Every hand move writes who moved it, their role, the stage it came from, how long it sat there, and the reason 'manual override'.
Contract-Sent Gate
A deal with an estimate cannot cross into Contract Sent or beyond until a contract has actually gone to the customer.
Call the Lead, Don't Claim You Did
The New Lead card's button dials the lead; the stage moves when the call actually connects, not when someone clicks.
Draw the Building From the Card
A card in Contacted carries a Create Estimate button that opens the 3D builder for that lead — and turns into View Estimate once one exists.
Sold Deals Hand Off to the Build Board
Dragging a deal to Sold no longer creates a project — a countersigned deal becomes a project only through Start Project, and the sales card retires.

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 →