Your cost book is not somebody else's training data.
I am a licensed general contractor. I built this for my own company first. When I say the bid book stays in the building, it is because mine does.
Why a contractor should care where the model runs
Nobody is going to fine you for putting a bid into a cloud tool. That is not the risk. The risk is that your unit costs, your subcontractor pricing, your markup structure and your win-loss history are the only durable advantage a mid-size GC has, and you are being asked to upload all of it to a platform that also serves the people you bid against.
A system on hardware you own solves that the boring way. The cost book, the estimates, the change orders and the job files are read by a model sitting in your own office. Nothing about your pricing leaves, because there is nowhere for it to go.
Before the job
- Lead intake
- Missed-call recovery
- Qualification
- Follow-up
- Estimating
- Proposals
Preconstruction is where this pays first, because preconstruction is where the unpaid hours live. You bid work you do not win, and every one of those bids cost somebody two days.
Construction estimating with AI support does not mean a model that prices your job. It means the specification gets read and summarized, the scope gaps get flagged, the quantities you have taken off get carried into your own estimate template without retyping, prior similar jobs get surfaced with what they actually cost you, and the proposal gets assembled from your own language instead of rebuilt from the last one.
Your estimator still sets the numbers. The system removes the retyping, the hunting and the re-reading, which is most of the two days.
Bid and submittal handling
The invitation-to-bid inbox is a mess at most GCs I have seen, including mine before I fixed it. Bids arrive as email attachments, addenda arrive late, and the one that mattered is under forty that did not.
- Incoming invitations sorted by owner, architect, due date and trade scope
- Addenda matched to the right bid package
- Sub coverage tracked by scope, so you know what is uncovered before bid day
- Submittals and product data checked against the specification section they answer
- Missing submittals chased with the sub directly
None of this replaces a project engineer. It makes the project engineer stop being a filing clerk.
During the job
- Project emails
- Document search
- RFIs
- Sub coordination
- Customer updates
- Cost tracking
Document search across the job files is the one superintendents notice first. Plans, specs, RFIs, submittals, daily reports and the email thread from March all become searchable in plain language, so the answer to "did we ever get an answer on the curtain wall detail" takes a minute instead of an afternoon.
RFI drafting works the same way: the question gets written against the actual spec section and drawing reference, and a person sends it. Cost tracking pulls the committed versus actual picture out of the systems you already run, so the number in the owner meeting is current.
After the job
- Invoices
- Collections
- Review requests
- Referral requests
- Project archive
The project archive is the underrated one. A closed job that is properly indexed becomes estimating data for the next bid, warranty evidence if something goes wrong, and the reference package for the next owner who asks whether you have done this building type before.
If you came here looking for general contractor software
I do not sell one, and if you have no project management system at all, buy one before you call me. The established products are good at what they do.
What none of them do is work the way your office specifically works. You already have a PM platform, an accounting system, an estimating tool and a shared drive, and the work still falls through the seams between them, usually onto whoever is least able to say no. Construction automation, as I mean it here, is closing those seams: connecting what you own, and automating the handoffs nobody wrote down.
If the audit finds that the honest answer is a product purchase rather than a build, that goes in the readout.
Why the construction page is the proof page
The other pages on this site describe work in businesses I serve. This one describes work in businesses I run. I hold a general contractor's license and I run a construction company and an electrical company, and the lead intake, follow-up, email triage, document search and review engine described here run on my own box, on my own jobs, today.
That is also the honest reason a contractor should be a little skeptical of the other pages and less skeptical of this one. I have been the customer here for longer than I have been the consultant.
What I will not claim
No win-rate promise and no hours-saved number. Your win rate depends on your market, your bonding capacity and who you are bidding against, and any figure I put on a page would be marketing rather than measurement. The audit instruments what you have now so the comparison is yours to read.
The other limit worth saying: local models are strong at reading specs, sorting documents, extracting quantities and drafting. The hardest reasoning still tends to go to a frontier model, on your own account, with the minimum approved context for that task. Your cost book is not in that category.
How it goes
- Twenty minute call, free.
- The audit: half a day walking your office and a job, the workflow map, and one thing installed that same week.
- The proposal, handed to you inside the audit readout.
- The install, four to six weeks, then go live.
The Operator's AI Audit: $3,500. Credited in full against the Private AI System if you go ahead within 30 days.
Who this is for
Trades and home services get their own page too.