Custom builders leave 3 to 8 percent of every project on the table because change orders never get signed.
Every custom home builder knows the pattern. Client walks the framing and asks for a bump-out in the master bath. Superintendent nods, tells the trade to make it happen, forgets to write the change order. Trade completes the work. Three months later at closing, the builder has $6,400 in extra labor and materials with no signed CO to bill against. That $6,400 gets absorbed as "the cost of doing business."
Multiply that across every project. The National Association of Home Builders has documented that unmanaged change orders represent 3 to 8 percent of gross revenue for the average custom builder. On a builder doing $8 million in annual revenue, that is $240,000 to $640,000 walking out the door every year.
Why change orders slip through the cracks
Change orders die between three moments. First, the field: superintendent hears the request, thinks he will handle it later, moves on to the next fire. Second, the office: bookkeeper does not know a CO happened until she sees the invoice from the trade, at which point pricing is guesswork. Third, the client: client does not sign because they were never presented with a clean CO document, or they sign but only after arguing about pricing that should have been agreed up front.
The traditional stack does not help. Buildertrend or CoConstruct track projects but require someone to enter the CO manually. QuickBooks handles the accounting but only after the CO is in the system. Email and text threads with the client are unstructured. Nobody has a single source of truth for scope changes.
How MiOpsAI catches every change order
Every project in MiOpsAI has a client record with baseline scope and pricing. When a scope change happens, it gets logged in one of three ways. Superintendent voice-dictates or texts the change from the field, and Lizzi turns it into a structured CO draft. Client emails or texts the request, and Lizzi flags it as a potential CO and drafts pricing. Trade partner submits a change proposal, and Milo files it against the project.
Once a CO is drafted, Mac prices it against the estimating database (materials markup, labor rates, subcontractor pricing). Julia reviews the CO document for the correct scope description, price, and change to timeline. The client gets a clean CO for signature via email with one-click e-sign integration. Once signed, the change is added to the project budget, the trade is authorized to proceed, and Mac queues the CO on the next progress invoice.
The Hive that runs on the job site
Lizzi handles inbox and messaging for every client (included free with every account). She drafts responses to homeowner questions, files photos and communications under the right project, and flags CO opportunities. Milo runs project delivery including schedule, task management, and trade coordination. Mac handles finance including project budget tracking, CO pricing, progress invoicing, and job-cost accounting. Marcus handles pipeline including prospective clients and lot inventory. Sally handles marketing including project galleries, testimonials, and referral outreach. Julia reviews contracts, waivers, and CO documents. Jerry handles integrations with Buildertrend, QuickBooks, and estimating tools. Additional chairs are $250 per month each.
What actually happens on a well-run project
| Trigger | Action |
|---|---|
| Client requests bump-out at framing walk | Super texts request, Lizzi drafts CO in 2 minutes |
| Pricing needed | Mac pulls material and labor costs, applies markup, ready in 5 minutes |
| CO document generation | Julia reviews language, generates signed-ready PDF |
| Client signature | E-sign email, typically signed within 24 hours |
| Trade authorization | Milo notifies trade with signed CO attached |
| Invoice | Mac adds CO to next progress invoice automatically |
The math on a mid-size custom builder
Builder doing $6 million in annual revenue across 8 to 12 custom homes per year. Historical CO leakage of 4 percent equals $240,000 per year in unbilled work. MiOpsAI closes that gap by making every CO trackable, priced, and signed before the trade completes the work. Even capturing 60 percent of previously lost COs recovers $144,000 in annual gross margin.
Beyond the direct revenue capture, there is a secondary benefit. Trade relationships improve because trades get paid faster and correctly the first time. Client trust improves because there are no closing surprises. Cash flow improves because COs are billed on the next progress invoice, not written off at project close.
What breaks in a Buildertrend-plus-email stack
Builder uses Buildertrend for schedules and daily logs. Uses QuickBooks for accounting. Uses email and text for client communication. Uses Excel for job costing. When a change happens, it lives in the text thread until someone remembers to enter it into Buildertrend, at which point the pricing is a rough estimate and the client has already forgotten what they agreed to. The CO document generates late, gets pushed to the end of the project, and either gets signed under duress or written off entirely.
Most builders have tried to fix this with SOPs ("every change gets a CO within 48 hours"). SOPs fail because they rely on humans doing the same disciplined step on a job site with 30 other fires happening simultaneously. AI operators do not forget. That is the difference.
Related reading
See our Buildertrend alternative for remodelers for the tool comparison angle, or our real-time margin tracking page for the finance view.
Frequently Asked Questions
Does MiOpsAI integrate with Buildertrend?
Yes. Firms using Buildertrend for daily logs and scheduling can integrate with MiOpsAI so client communication, CO management, financial tracking, and AI operators run on MiOpsAI while field work continues in Buildertrend. Many firms eventually consolidate to MiOpsAI entirely, but the integration path lets you migrate gradually.
How does Mac know how to price a change order?Mac pulls from your estimating database including material costs, labor rates, and subcontractor pricing. During onboarding, we import your standard cost catalog and markup structure. Mac applies your pricing rules automatically. Custom items still require estimator input, but Mac handles 70 to 85 percent of standard COs without human pricing intervention.What if a client refuses to sign a change order?
MiOpsAI tracks every unsigned CO and prevents the trade from being authorized to proceed. If a client refuses to sign, Julia can escalate to your standard change order dispute process. The advantage is that you have a documented record of the request, the pricing, and the client's response, which protects you if the dispute goes to litigation.
Can we use MiOpsAI for spec builds and production homes, not just custom?Yes. Spec builds use the same platform with a different phase structure. Production home builders use template-based projects with faster kickoff. The Hive is asset-class-agnostic within residential construction. Custom, spec, production, and small multi-family all work on the same platform.What about compliance with lien laws and warranty documentation?
Julia handles lien waiver tracking, warranty documentation, and standard compliance documents. Every CO is documented per state requirements including proper language for pricing, scope, and timeline changes. Lien waivers are tracked per trade per progress payment. Warranty periods are calendared and triggered automatically at closing.
What is the cancellation policy?MiOpsAI requires 60-day written notice for cancellation. This gives both teams time to close active projects cleanly, export data, and transition without disruption. Given the multi-month nature of construction projects, the 60-day window is essential for a clean transition.
If your custom home business is losing 3 to 8 percent of revenue to unmanaged change orders, MiOpsAI closes that gap. Request access to see how the CO workflow runs, review the full residential construction platform, or explore flat builder pricing.