← Alvin Slate

EmpowerBuild · Fractional COO case study

One price, checked twice

Every estimate this company sends now traces back to one verified number, and gets checked at least twice before a client sees it. That discipline is what caught two pricing errors and closed a signature near-miss before any of them reached a client.

The result

2
Silent pricing errors caught and fixed before a client ever saw them
1
Document-control near-miss closed with a standing sign-off rule
300–400KB
Healthy PDF range the QC gate checks against, every render
0KB 100KB 200KB 300KB 400KB Healthy rendered PDF: 300-400KB Healthy range Corrupted render caught by the QC gate: 46KB 46KB — caught

How it works

A price only has to be right in exactly one place, and every step that could silently fail gets checked instead of assumed.

01

One underwrite per job

A single verified file drives every line. The client-facing rate is primary; internal cost derives from it, not the other way around.

02

Read the sketch, not just the scope

Hand-marked dimensions on a client's design sketch get read directly off the page, then cross-checked against what's actually verified versus approximate before any of it prices into an estimate.

03

Assessor-card takeoffs

For Indianapolis jobs without a usable sketch, wall heights and perimeters come off the county assessor's own property record card instead of a guess from a photo.

04

Byte-size QC gate

Every rendered estimate gets checked before delivery. A healthy PDF runs 300–400KB; a silently-overwritten one lands near 46KB, and now that's caught automatically.

05

EST → CA → CO

Estimate, contract, and change order each get their own numbering track. A revision is always a new file, never an overwrite of the last one.

06

Stage before signature

Nothing goes out for e-signature until it's staged and reviewed first, closing the exact gap that caused the double-send below.

Standing rules

What it replaced

Every estimate used to start from a blank copy of the same template, priced by hand, with no single place a number had to be right. That looked fine until it didn't:

Now caught by the underwrite file

One job's per-trade subtotals were silently wrong through two full revisions before anyone noticed. The grand total happened to be right, so nothing looked broken until someone added the trade lines by hand.

Now caught by the QC gate

A render silently overwrote a good, client-ready estimate PDF with a corrupted error page. Nothing in the workflow would have caught it without deliberately checking file size on every render.

Now caught by the change-order gate

A signed contract sat roughly $6,450 under its likely cost because scope changed after pricing and nobody re-priced it. The gap was found on review, not by the client.

Now caught by the sign-off rule

A revised contract went out for e-signature twice within the same hour. The e-signature platform has no cancel/void tool, so a premature send has to be killed by hand.