July 21, 2026 · 5 min read · Patrick Keating, Founder
The $87K Cabinet Quote: Why Price Anomalies Slip Through
The short version: A price anomaly rarely looks wrong sitting alone on an invoice. It only looks wrong next to your own project history, and most GCs never put the two side by side before the number gets approved. SpecAlign's internal model puts price and quote anomalies at roughly 0.5% of hard costs on a typical build, worth $8,000 to $10,000 on a $2M job. Money that's recoverable if caught before the PO cuts, and mostly gone after.
A cabinet package comes in at $87,000. Eight-foot ceilings, an island, a mix of stock and semi-custom. Nothing unusual about the kitchen, and nothing wrong-looking about the number by itself. It's only next to the last three kitchens at that tier, averaging $74,000, that the gap shows up: 17% over, unexplained, sitting in a stack of forty other line items that also need approving this week.
Where do price anomalies actually hide?
Three places, mostly.
Quotes. A sub or supplier prices a scope higher than their last three jobs at the same tier, sometimes 10% high, sometimes 30%. Sometimes material costs genuinely moved. Sometimes nobody's checking. Both look identical on the page.
Purchase orders. The PO gets cut off a verbal number instead of the quote that actually came in, and the two don't get reconciled until an invoice shows up that matches neither one.
Invoices. A line item bills for more units than the PO called for, or the same SKU shows up at a different unit price than it did ninety days earlier on the same job.
None of this requires dishonesty to happen. A supplier's cost genuinely rises. A verbal change genuinely gets miscommunicated. The anomaly isn't proof of anything by itself. It's a signal that something needs a second look, and a second look requires a baseline sitting next to the number when the decision gets made. Most builders don't have one.
Why does an inflated quote get approved anyway?
Because review happens one document at a time, fast, against gut instinct instead of history.
A GC running two or three active builds is approving quotes, POs, and invoices in the gaps between site visits and client calls. FMI's Construction Disconnected research puts non-optimal admin time at 35% of a construction professional's week, roughly 14 hours, split across finding information, resolving conflicts, and fixing mistakes. Sage's research on small-business owners found 32% spend up to a quarter of their time on basic admin; another 24% spend up to half. Quote review sits inside that block, competing with everything else on the list.
Nobody sits down with the last three kitchen quotes before approving the fourth. The comparison would catch the gap in about a minute. It just never happens, because the prior numbers aren't in front of anyone when the decision gets made.
| Anomaly type | What it looks like | Where it normally gets caught (if ever) |
|---|---|---|
| Line-item markup above trade history | A quote priced well above your last several jobs at the same scope | Rarely, unless someone manually pulls the old quotes |
| PO/quote mismatch | The purchase order doesn't match the number the sub actually quoted | At reconciliation, sometimes weeks later |
| Quantity drift | Invoice bills more units than the PO authorized | At payment, if the invoice gets checked line by line |
| Unit price drift | Same SKU, higher price than the last order on the same job | Close-out, if there's a close-out review at all |
The same math as the escalation ladder
This is the escalation ladder from the rework numbers, priced in dollars instead of labor. A price anomaly caught at the quote stage costs a phone call: your number's 17% over your last three, walk me through it. Minutes, no damage. Caught after the PO cuts, it costs an awkward renegotiation and maybe a delay while a new quote comes in. Caught after the invoice is paid and the draw has closed, it's gone. The 17% is now baked into the budget line, and probably into next year's estimate too, because an unquestioned high number quietly resets the baseline upward.
That's detection-timing economics again. The dollar amount barely changes between stages. What changes is whether it's still yours.
What actually catches it
- Keep quote history somewhere it gets checked, not just stored. A folder of old PDFs doesn't compare itself to the new one.
- Compare every quote to your own trade history at intake, not to a general sense of "that feels high." A 17% gap against your own last three jobs is a specific, defensible number to raise with a sub.
- Reconcile the PO against the invoice before approving payment, not after. A three-way match (quote, PO, invoice) catches drift at the one point it's still cheap to fix.
- Flag it, don't block it. Most anomalies have a real explanation. The goal is a second look, not an automatic rejection.
Put plainly, here is the shift on this one job:
| What you do today | With SpecAlign | Enabler |
|---|---|---|
| Judge each quote on its own, against a gut sense that a number "feels high" | Every quote scored against your own last jobs at the same scope, the moment it lands | Read: past quotes become structured, comparable data |
| "Is $87K high?" answered from memory | "17% over your last three kitchens at this tier," computed for you | Compare: your own history is the baseline, and the delta is automatic |
| The bad number surfaces at reconciliation or close-out, after the draw | Flagged before the PO is cut, while it is still recoverable | Act: the check runs at intake, not at payment |
Those four steps are one instance of how the software works everywhere: read your documents into structured data, compare each new number against your own history, act before the money moves. The quote check is the same read-compare-act pattern that runs spec extraction, version compare, and takeoffs. See it across the platform.
SpecAlign checks every incoming quote and invoice against your own project history and flags what's off before the PO goes out: the same three-way match a document control team would run by hand, minus the team. Half a percent of hard costs doesn't sound like much until it's the $9,000 nobody would have caught otherwise.
Sources
- FMI / Autodesk, Construction Disconnected (35% non-optimal time, ~14 hr/week; conflict resolution and rework buckets)
- Sage, "The Cure To Your Admin Headaches" (32% of small-business owners spend up to a quarter of their time on admin; another 24% up to half)
- SpecAlign internal value model (price/quote anomaly pool modeled at ~0.5% of hard costs, ~$8-10K on a $2M build)
The $87K/$74K figures illustrate how the anomaly check reads a quote; they are a representative example, not a specific client's numbers. SpecAlign's cost-avoidance figures are modeled estimates with a stated methodology, not measured customer outcomes.
Frequently asked questions
- What is a price anomaly in a construction quote?
- A line item priced meaningfully above what the same scope has cost on your own recent jobs, without an obvious reason. A cabinet package running 17% over your last three kitchens at the same tier is a textbook example. It isn't proof of a bad actor. It's a number that needs a second look before it gets approved.
- How much do price anomalies actually cost on a custom home?
- SpecAlign's internal model puts price and quote anomalies at roughly half a percent of hard costs on a typical build, about $8,000 to $10,000 on a $2M job. That's a modeled estimate with a stated methodology, not a measured customer result, and it only counts what a systematic check catches before the money moves.
- Why does an inflated quote get approved instead of questioned?
- Because most quote review happens fast, one document at a time, without the builder's own project history sitting next to the new number. FMI's research puts non-optimal admin time at roughly 35% of a construction professional's week. Quote comparison competes with everything else in that block, and it usually loses.
- What is a three-way match, and does a small builder need one?
- It's reconciling the quote, the purchase order, and the invoice against each other before payment goes out, standard practice on commercial jobs and rare on residential ones. A small builder doesn't need a document-control department to run it. Software that checks the three automatically covers the same ground.
- How do I start catching price anomalies without hiring someone to track it?
- Keep quote history somewhere searchable instead of scattered across email, and compare every new quote to your last two or three jobs at the same scope before you approve it. That single habit catches most of what a full anomaly-detection system catches, just slower and only for the quotes you remember to check.
Patrick Keating, Founder
Patrick Keating is the founder of SpecAlign, building AI construction intelligence for custom home builders.