How we work
Built to Fit: live on Sage Estimating in weeks, not months.
No two estimating departments work the same way, so no two implementations should either. Built to Fit starts with a cost database that reflects how your company builds work, and everything else is fitted around it. Six stages, in this order, for a reason.
- Step 1
Assess & design
How your team bids today, and the database structure agreed on paper.
- Step 2
Build
Installation, configuration, and your items, assemblies, crews, and pricing.
- Step 3
Prove
A parallel run on a real estimate, with any variance reconciled.
- Step 4
Train & go live
Role-based training on your own data, then the switch.
Internal tools we’ve built handle the slow parts of an implementation, so your team keeps bidding the whole time. The sixth stage, Sustain, carries on after go-live.
01
Assess
Find where the process breaks.
We sit with your estimators and watch how a bid really gets built — including the spreadsheet nobody mentions in the meeting. The output is a straight read on whether you have a configuration problem, a database problem, or a genuine software gap. Sometimes the fix costs you nothing, and we would rather tell you that than quote a build.
What you get
- Current-state map of how estimates move through your team
- A straight answer on configure vs. rebuild vs. build
- Scope and rough effort for whatever comes next
02
Design
Model the database before anyone builds anything.
This is where the long-term fit is decided. We design the cost structure — items, assemblies, crews, cost codes, WBS — around how your company estimates, and we agree on it in writing before a single record is created. Getting this wrong is expensive to unwind two years later.
What you get
- Cost database structure documented and signed off
- Assembly and crew logic defined for your trades
- Integration map: what connects to what, in which direction
- Milestone calendar for the rest of the engagement
03
Build
Configure, populate, and write what doesn’t exist.
Installation, SQL configuration, and the database itself — items, assemblies, pricing, reports. Where your workflow needs something beyond the standard setup, this is where we build the add-on or integration. The people who scoped your project are the people building it.
What you get
- Configured environment with multi-user access
- Populated cost database with your items, assemblies, and pricing
- Custom reports on your live data
- Any custom applications or integrations the design called for
04
Prove
Run it against a real bid, in parallel.
Before anyone depends on it, we pilot the setup on a live estimate alongside your existing process and compare the numbers. Discrepancies get resolved here, where they cost nothing, rather than on a bid day where they cost a job. Nothing goes live until an estimator you trust says the numbers hold up.
What you get
- Parallel run on a real estimate with variance reconciled
- Corrections fed back into the database
- Sign-off from the estimators who’ll use it
05
Adopt
Train on your data, not a demo set.
Training sticks when it happens on your own data. We train your estimators on your own database, with your own assemblies, building the kind of estimate they’ll be building on Monday. Different roles need different sessions — an estimator, a buyer, and a CFO want different things from the same system.
What you get
- Role-based training run on your live configuration
- Written procedures for the workflows specific to your team
- A named internal owner who knows the database, not just the software
06
Sustain
Keep it current as the business moves.
A cost database is a living thing. Pricing moves, crews change, Sage releases new versions, and the estimating team turns over. We stay on for upgrades, troubleshooting, database maintenance, and the periodic pricing updates that decide whether the system is still telling you the truth in three years.
What you get
- Scheduled pricing and database maintenance
- Version upgrades handled without a fire drill
- Support from people who already know your setup
Why design comes before the build.
A structural change is easy to make on paper. It’s much harder once a year of live estimates sits on top of it. Start with a conversation about how your team estimates.
- Response time
- One business day, usually the same day.
