On an estimate you build in Leads 2 Build, a version is a checkpoint: it freezes the building, every material line, every service and the prices exactly as they stand. Save one when a round of changes is ready — the porch, the pad, the gutters — and keep going. Go back puts any earlier version back in one click, after saving where you are. Compare puts two side by side: the difference in the total, where it moved, what changed in the building, and the line items behind it, written out ready to send. Leads 2 Build is made only for post-frame and barndominium builders, so the changes it reads back are the ones your customers actually ask for — porches, lean-tos, wainscot, a concrete pad. Estimates synced from SmartBuild keep their own version list, with one version live on the customer's link.
Also called: see versions · revision history · what was in the last quote · previous version of the estimate · estimate checkpoints · go back to the original quote · revert an estimate · compare two quotes · why did the price go up · undo changes to an estimate
Save a version when a round of changes is ready
Try itOn an estimate you build in Leads 2 Build, Versions keeps checkpoints. Name the round — with porch + gutters — and press Save version. The building, every material line, every service and the prices are frozen exactly as they stand, stamped with when and who. Autosave keeps your working draft; a version is only made when you make one, and pressing Save again with nothing changed doesn't make a copy.
The customer adds a porch, then a pad, then gutters, and by the third round nobody can say what the first quote was — it got typed over.
People change their minds out loud. When every round is saved and named, a rep can say yes to what would that add? without worrying about losing the last price — and the office always has the quote the customer actually saw.
A version keeps the prices it was saved with
Try itOpen any version and it reads back the building in one line — 40′×60′ · 14′ eave · 3 doors, 4 windows · 1 porch/lean-to — then its materials, labour, services and markup, and the services it carried. Nothing is recalculated, so a catalogue price change next month cannot rewrite what version 2 cost.
Mid-call the customer asks what was in the quote before the pad went on, and the spreadsheet you priced it in has been changed since.
A record only settles a question if it can't drift. A rep who reads the old quote straight off the screen, mid-call, sounds sure of himself — and the customer hears that.
Go back to an earlier one in one click
Try itCustomers change their minds back. Open the version they want and press Go back to this version: the building, the services, the pricing and the quantity edits return to how they were. Where you were is saved first, so going back can be undone too. If catalogue prices have moved since, the window says what that version comes to today — $61,384 now, $60,726 then — so an old number never goes out by accident.
The customer can't stretch to the version with the pad and wants the original back — and rebuilding it means remembering every post and gutter run you took off.
Being able to go back to any version takes the fear out of trying a change in front of the customer. Reps try more options when nothing can be lost, and a customer who hears let's look at it with the pad instead of I'll get back to you decides sooner.
Compare any two versions, side by side
Try itPress Compare, tick two versions, and the older one becomes the starting point. You get the difference in the total — +$28,206 from version 1 to version 3 — then where it moved: materials, labour, services and markup, each with its own change. Under that, what changed in the building in plain sentences: Added: Porch 40′×12′ on the front, Wainscot: no wainscot → 3′ wainscot. Any pair works, not just the last two.
Why is it twenty-eight thousand more? gets answered from memory, and the customer decides the price moves depending on who picks up the phone.
A price that goes up with no reason feels like a trick; the same increase with its reasons feels fair. Showing the customer the porch, the pad, the wainscot keeps the talk on their building instead of on whether they can trust you — and that keeps the deal alive.
Down to the line items that moved
Try itEvery service that was added, removed or changed is listed with its dollars — 4″ Concrete Pad +$15,000, Seamless Gutters & Downspouts +$1,880. Materials are grouped by category, biggest change first, and each category opens to its lines: 6×6 treated post · 14′ · 5 ea +$700, 2×6 purlin · 12′ · 48 → 66 ea +$486.
A category total says framing went up; it doesn't say whether that was the porch posts or a purlin count somebody typed wrong.
Detail is what lets a rep defend a number without guessing, and lets an estimator catch a mistake before the customer does. Confidence on the phone comes from knowing you can point at the line.
The explanation, written for you
Try itCopy for the customer turns the comparison into plain words — the two totals, what changed in the building, the services, the materials by category and the labour — ready to paste into a text or an email. Version 3 is $88,932 — $28,206 more than Version 1 ($60,726).
Writing out why a price changed takes longer than making the change, so it never gets written and the customer gets a number with no reasons.
Most reps won't write a long explanation at the end of a day, so it has to write itself. A customer who can read where the money went argues about the porch, not about the price — and the deal keeps moving.
Synced from SmartBuild: every revision kept, one of them live
An estimate synced from SmartBuild keeps its own version list — version 1 through version 7, all retrievable, exactly one published. Which one the customer sees is a decision, not an accident of which email they opened, and any two can be compared in two colours: older in blue, newer in amber.
It is eight at night and you are scrolling your sent folder trying to work out whether the customer is holding the eighty-eight thousand quote or the ninety-three.
When exactly one version is marked live, nobody has to remember which price is out there — they read it off the list. That quiet certainty lets a rep pick up a call cold and quote the right number, and it ends the signed-the-wrong-PDF problem for good.
The customer's link never changes
Try itSame address for the life of the deal. On an estimate synced from SmartBuild, make a different version live and that link now shows it — nothing to resend, nothing for them to lose.
Every revision means another email, and the customer quotes the price back to you from whichever one happens to be nearest the top of their inbox.
Customers lose emails, and they hate being told to dig out the newer one. One link that always shows the current price means they never feel caught out — and an internal draft still has to go through Send first, so labour and markup are on it before anyone outside sees it.
Try it without sending it
Try itOn an estimate synced from SmartBuild, model the cheaper roof, the smaller slab, the porch removed — as a what-if that nobody but you can see. The alternative is sending options you have not thought through.
You float the cheaper option off the top of your head on the phone, then find at the desk that pulling the porch also pulled markup you were counting on.
Reps float options on the phone because the customer asks right then. When the number they float is the real one — services, markup and change orders included — they say it with confidence and never have to walk it back.
An approved version is locked, and unlocking is on the record
Try itOn an estimate synced from SmartBuild, approval locks every field that made up the price — colours, markup, labour, the payment schedule — with a padlock beside each. Unlocking asks you to confirm, says plainly that the customer has to approve again, and writes an entry with your name on it. The lock closes itself again the moment they approve the revision.
Someone nudges the markup on a quote that already carries a signature, and nobody notices until the contract and the signed page disagree.
Nobody means to edit a signed price — it happens at the end of a long day. A lock that has to be opened on purpose, with your name on it, protects the rep from his own tired click and the business from a contract that doesn't match what was signed.
The customer only ever sees one price
On an estimate synced from SmartBuild, the live figure and your unsent working draft sit on one card, each labelled. The customer can only reach what is live, which means they cannot sign an old version.
You spend the afternoon reworking the quote and the approval lands on the number from before lunch.
Builders rework quotes all afternoon. Seeing what they see now beside what you are working on ends the did that just go out? panic — moving the price takes a send, and the send makes the next version.
The live version is what becomes the contract
The agreement is generated from the version they approved — not from whichever spreadsheet was open — so the contract cannot disagree with the quote.
Someone retypes the agreed price into the agreement and out goes a contract whose payment schedule does not add up to the quote.
Customers read a contract looking for the catch. When every number matches the quote they approved, there is no catch to find — they sign faster, and nobody retypes a price by hand and gets it wrong.
…and what they actually approved
The approval is recorded against a specific version, with its total. Six months later the question what did they agree to has one answer.
Six months into the build the customer says that was never the number, and all you have is an email thread.
Memory is kind to whoever is doing the remembering. A figure and a moment, written into the box they ticked, settles that was never the number before it starts — and keeps a good customer from turning into an angry one.
The customer's copy cannot be quietly rewritten either
Automatic refreshes skip an approved link outright, refused where the writing happens rather than trusted to each screen that might trigger one. From that point the document is the record of what was agreed, and a price change becomes a change order.
A refresh after approval quietly rewrites the page the customer agreed to, and now their copy and yours disagree.
Once a customer has agreed, the page they agreed to should never move under them — that is what makes them trust the next document you send. From then on a price change is a change order, which is how it gets paid for.
A gap between the approved amount and the live one announces itself
The figure the customer approved is compared against what the estimate says now, and a difference of five cents or more is reported with both numbers and the version each came from. A customer approving from an old email is caught on the estimate — not at invoicing, with the customer holding the old number in writing.
The customer approves from a March email, the job is booked at the April figure, and nobody finds out until the first invoice doesn't match.
The worst surprise is the one at invoicing, when the customer is holding the old number in writing. Catching a five-cent gap on the estimate turns a fight into a two-minute conversation.
- 1Open an estimate and press Versions
- 2Name the round and press Save version — the building, materials, services and prices are frozen as they are
- 3Keep changing the estimate: autosave keeps the working draft, and a version is only made when you save one
- 4Open any version to read its building, its totals and the services it carried
- 5Go back to this version restores the building, pricing and quantity edits — and saves where you were first
- 6If catalogue prices have moved since, it tells you what that version comes to today
- 7Compare any two: the price difference, where it moved, the building changes, and every service and material line behind it
- 8Copy for the customer turns the comparison into a message you can paste
- 9On an estimate synced from SmartBuild, one version is live on the customer's link and an approved version is locked
Quoting a post-frame building is a conversation, not a document. The customer asks what a porch would add, then a concrete pad, then gutters — and by the third round the first price is gone, typed over by the second. Then they sleep on it and say the original was the one they could afford. Rebuilding that first quote from memory is how a porch post goes missing from the takeoff. Explaining why the new number is twenty-eight thousand more, from memory, is how a customer starts to think the price moves depending on who answers the phone. So a version is a checkpoint you can stand on: save it, change freely, go straight back, and put any two side by side with the reasons written out. Being able to undo takes the fear out of trying a change in front of the customer — and a price difference that arrives with its reasons is one the customer believes.
- The first quote lost under later changes
- Price differences explained from memory
- Rebuilding an earlier quote by hand
- Multiple live versions of one price
- No record of what was quoted when
- Editing a signed document without noticing
Every send captures the exact document the customer got
Two separate histories, on purpose. Internal snapshots are before markup and stay inside the building. Sent versions carry the customer's actual document — markup applied, total quoted — and they start out visible, because they were just sent.
Pin the version the customer sees
By default they see the newest. Make this the live version holds them on an earlier one instead. Nothing newer is deleted to do it, so the choice is always reversible.
Show or hide a version from the customer
Sent versions start out visible. Internal snapshots are never eligible — the customer's page will not show a version that was never sent to them.
Compare two versions side by side
The older one is blue, the newer is amber, and the difference reads green or red. The colours are deliberately distinct, so every number is unmistakably tied to its version — including the ticks back on the list rows.
What-if toggles on a version's total
Every version's total breaks into parts, and each part has a checkbox. The figure recalculates on your screen only. It answers what would the total be without this, and it is not a save.
What the customer sees now, versus your latest draft
It settles three different numbers a rep can be looking at — the working draft, the raw materials figure, and what was actually sent. It names the live one and its total, then flags the gap: either a newer version you never sent, or edits made after the last send that live in no version at all.
Version checkpoints on a Leads 2 Build estimate
Drafts save continuously, so nothing is lost. A version is a deliberate act, never an autosave, and it freezes what the estimate shows at that moment, so a catalogue change later cannot rewrite it. Go back to any version in one click, or compare two to see where the price moved.
