Flooring and concrete contractor
≈ $25M revenue (approx.) · 12 years of job history · Zoho CRM · Azure tenant
Estimation benchmarks from twelve years of costing sheets
Twelve years of costing sheets and work orders become a governed knowledge base; every new estimate is benchmarked by technology and size band against what past jobs actually cost, QA'd before approval, and driven from inside the CRM the sales team already lives in.
- Organization
- Specialty flooring and concrete contractor
- History
- About twelve years of costing sheets, work orders and job outcomes in spreadsheets
- Runs on
- The contractor's own Azure tenant, driven from Zoho CRM
- Scope
- Historical benchmarks, estimate calculation, QA/QC before approval, learning loop
Where they started.
The company had years of project history and no way to use it. Costing sheets, work orders and estimating files lived in individual spreadsheets, so nobody could quickly say what an epoxy job really costs per square foot, which technologies are most profitable, how estimates compared with actuals, or whether a new number was too low, too high or missing a cost line. The brief was explicit: not another calculator, an estimation support system that combines the company's costing logic with its own performance history.
What was built.
- Historical costing sheets and work orders are normalized into a governed knowledge base: technology, square footage, price per square foot, labor hours, material, transport, equipment, consumables, per diem, estimated versus actual value, profitability, crew size, duration, change orders.
- Benchmarks by technology and project-size band: epoxy coatings, urethane cement, polished concrete, self-leveling systems, sealers, with the realistic ranges for every cost category.
- A new estimate is calculated on the company's own cost logic, then compared with the closest historical jobs and their outcomes, and the gaps are flagged before an estimation manager approves it.
- The whole loop runs from inside the CRM the sales team already uses, and completed jobs feed their actuals back into the benchmarks.
What changed.
- Estimates grounded in what the company's own jobs actually cost, by technology.
- Too-low, too-high and missing-cost estimates caught before they leave the building.
- Profitability visible by technology and market segment for the first time.
- Spreadsheet dependence replaced with a knowledge base that improves with every job.
A contractor's cost structure and margins by technology are the business. Benchmarking against them on private inference keeps that history inside the company's own tenant.
Microsoft Azure
Components involved.
More like this.
Multi-brand industrial manufacturer
≈ $200M revenue across five brands (approx.) · 5 brands · 4 ERPs · 1 CRM
- Use Case:
- Consolidation, forecast and pricing intelligence across four ERPs
- Results:
- One governed lakehouse behind an AI agent: audit-grade consolidated financials that trace to the source transaction, forecast and pipeline by business unit, large-job margin watch, and plain-English inquiry over all of it, inside the company's own Azure tenant.
European logistics group
≈ $2B revenue · 6,000+ employees · 50+ countries
- Use Case:
- Quote control tower over forwarding systems
- Results:
- Quotes that track fuel prices, routing and political risk across the group's forwarding systems, assembled by agents over the company's own data lake and handed to the desk with the reasoning attached.
Sleep-therapy provider
≈ $60M revenue (approx.) · 40 clinics · one clinical reporting app
- Use Case:
- Natural-language clinical reports
- Results:
- Clinicians ask for patient cohorts in plain English and a constrained pipeline turns the question into validated filters, never free-form database queries, on a private GPU that costs a fraction of the hosted model it replaced.
Have one like it?
Every spotlight started as a conversation about a process nobody liked doing, under a data-locality constraint.