The quote re-reads itself about every ten seconds. So does the dashboard. Waiting screens check even faster, so the dashboard appears within seconds of your click. A warning you resolved comes off their screen too — cleared items are pushed as cleared, not just left out. And a choice the customer just made — a colour, or an optional extra they added — is never undone by the next refresh. One system running both sides of the glass, built only for post-frame and barndominium builders, so what you change at your desk is what the customer reads at their kitchen table.
Also called: do I have to resend the quote · live updates · customer sees my edits
Fix a number and it reaches the tab they already have open
A customer sitting on their quote while you corrected a price over the phone kept reading the old figure until they thought to refresh — and talking somebody through a refresh mid-call is an awkward way to close. The quote re-reads its live fields about every ten seconds — payment stages, spec rows, colour picks and colour restrictions — so the correction lands on the page they already have open. No resend. No second link.
You fix the deposit percentage while the customer is on the phone, and they're still reading the old number because they never thought to refresh.
Talking a customer through a page refresh mid-call is an awkward way to close. The correction appears on the page they already have open, so the conversation stays on the building — and nobody gets a second link.
A warning you resolved comes off their screen too
When you withdraw a colour restriction or delete an override note, the page is told the entry is now empty rather than simply not told about it. Sending only what still exists left a resolved warning stranded on the customer's quote after the reason for it was gone. A stale warning on the document you are asking somebody to sign costs more than the problem it was about.
You lift a colour restriction, but the warning stays on the customer's quote — on the very document you're asking them to sign.
A stale warning makes a customer hesitate at the worst moment. Pushing cleared items as cleared means what they read always matches what you decided, so nothing old stands between them and the signature.
Waiting screens turn themselves into the real page
While a customer waits for you to start their build, the page checks every few seconds and swaps itself for the live dashboard within seconds of your click — same address, same bookmark, no second email to find. The agreement works the same way: while the contract is still with you they sit on a preparing-your-agreement screen that becomes the signing view the moment you send it.
You start the project on Monday, but the customer is still looking at the waiting screen until you email them to refresh.
A customer who sees the build appear the moment it starts feels looked after. Waiting screens check every few seconds and swap themselves for the real page — same address, no email to find.
Build progress is never served from a stale copy
The dashboard asks for project data with caching switched off, because a cached answer defeats the entire point of a live view. A customer checking at nine on a Sunday night sees the checkpoint your crew ticked at four that afternoon — not a copy of the page from Thursday.
The crew ticks off the trusses at four o'clock, and the customer checking at nine still sees Thursday's progress.
The customer checking at nine on a Sunday should see what happened at four. Asking for project data with caching off means the live view is actually live — and it saves you the Monday-morning 'is anything happening?' call.
The refresh cannot undo a choice they just made
A colour the customer picked seconds ago is held against the next refresh instead of being reverted to the value the server had before the pick landed; the following pass reconciles it. Without that guard the refresh took a fresh selection straight back off the page — which reads to the buyer as software that did not accept their answer. An optional extra they add on a SmartBuild-priced quote is protected the same way: the server totals every write as the base plus their picks, so neither your refresh nor theirs can erase the other.
The customer picks a colour, and two seconds later the page flips it back — so they pick it again, and wonder if it took.
People trust a page that accepts their answer the first time. Holding a fresh pick against the refresh — and totalling extras on the server — means the customer's choice always sticks.
- 1You correct a price and their open quote picks it up in seconds
- 2You clear a warning and it comes off their screen too
- 3You click Start Project and their waiting screen becomes the dashboard
- 4Build progress is never served from a cache
- 5A colour they just picked, or an extra they just added, is not undone by the next refresh
A customer sitting on their quote while you corrected a price over the phone kept looking at the old number until they thought to refresh — and talking somebody through a refresh mid-call is an awkward way to close. Cleared items are pushed as explicitly cleared, because otherwise a warning you had already resolved lingered on the customer's screen after it was gone.
- Resending a quote for every small correction
- Customers reading a stale document
- Cleared warnings and notes persisting on the customer's screen