What happens automatically when the contract is executed

Counter-signing advances the pipeline card, notifies the team, emails the customer a branded 'fully signed' message, and creates the QuickBooks customer and project — without auto-starting the build.

What it is

A server endpoint that runs after the counter-signature is recorded. It resolves the deal's specific job so it advances the exact pipeline card (multi-job safe), runs the tenant's configured stage automation for admin_counter_signed, creates an idempotent QuickBooks project marked 'not started', emits a team notification with a Build Schedule CTA, and sends the customer a tenant-branded portal-link email.

Also called: after the contract is signed · contract triggers · ready to start · quickbooks project created

See it
What happens automatically when the contract is executed
Prepared for
Ivy Brubaker
1140 Ridge Line Rd · Fair Play
Shell package$34,782
Concrete & site$10,098
Doors & windows$6,732
Trim & finish$4,488
Total
$56,100
Signature
A fan-out diagram from the counter-sign click: pipeline card advances, team notification, customer email, QuickBooks project — with 'Start Project' shown as a separate manual gate. Sample data — no customer information appears here.
How it works
  1. 1Re-asserts org scope on the contract as defense in depth, and refuses if the contract isn't fully_executed.
  2. 2Resolves the SmartBuild job id from the estimate link so 'the dashboard advances the EXACT pipeline card (multi-job-safe), not every card for this contact'.
  3. 3QuickBooks sync is fire-and-forget and idempotent: 'a double-fire can't duplicate (UNIQUE(org_id, smartbuild_job_id) + claim-row mutex)'.
  4. 4Team notification: 'Contract with <name> is fully executed — ready to start project'.
  5. 5Customer email uses the 'contract.fullySigned' message key with the tenant's email brand, and the same tokens compose the text version.
Why we built it

The protocol is recorded and deliberate: 'Per protocol locked 2026-counter-sign emits a notification + the "Ready to Start" pill flips on for this estimate; it does NOT auto-create a project.' The customer email exists for a stated goal — 'every time there is an update we want the client going to this dashboard' — so 'they train themselves to check the dashboard instead of texting the builder.'

The problem
  • Manual re-keying of a signed job into accounting
  • Pipeline stages that lag behind reality
  • Automations that start a build before the builder decides to
Sound familiar?
What you get
The right pipeline card moves, on a multi-job customer
QuickBooks customer and project created once, never duplicated
Customer is told it's official and pulled back to their dashboard
Starting the project stays a human decision

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 →