What is os.construction
One operating system for construction. Project management, construction accounting, analytics and AI agents on a single data core.
This describes how os.construction is being built. Details may change before launch.
On this page
os.construction is an operating system for construction companies. It puts project management, construction accounting, analytics and AI agents on one data model, so a record entered in the field is the same record the office bills from and the same record the forecast reads.
Most contractors run the job in one system and the books in another, then rebuild the truth in a spreadsheet at month-end. os.construction is built to remove that gap.
The problem it solves
A typical mid-size contractor runs something like this:
- Project management in Procore or a similar tool: RFIs, submittals, daily logs, drawings, change events.
- Accounting in Sage 100 Contractor, Sage 300 CRE, Vista or QuickBooks: job cost, AP, AR, payroll, the general ledger.
- Reporting in Excel or Power BI: WIP schedules, fade reports, cash forecasts.
- Glue made of exports, imports, sync jobs and people re-keying numbers.
Every hand-off is a chance for the numbers to drift. A change order gets approved in the PM tool but the budget in accounting is a week behind. The pay app is built from a spreadsheet that does not match the commitment log. The WIP schedule is right on the day it is finished and wrong the day after.
None of this is a people problem. It is an architecture problem: two databases will always disagree eventually.
What os.construction is
Four systems, stacked on one data core:
The layers are not integrations. They are views and workflows on the same records. When a superintendent logs a hidden condition, that note can become an RFI, the RFI can become a change order, and the change order is already the budget change, the commitment change and the new line on the next pay app.
A worked example
The docs use one sample project throughout: Riverside Medical Center, Job #24-118, Phase 2. Contract value $48.2M plus $1.1M in approved change orders.
- The super finds missing fire dampers in the L3 corridor and logs it from a phone.
- That log becomes RFI-212, with photos and the spec reference attached.
- The architect’s answer leads to CO #14, priced at $86,400.
- Approving CO #14 updates the budget for the cost code, the affected commitment and the prime contract.
- The approved work shows up as a line on Pay App #9, with 10% retainage calculated.
- WIP, over/under billing and the margin forecast update without anyone exporting anything.
In a disconnected stack, each of those steps is a re-key. In os.construction, each step is the same record moving forward.
Who it is for
General contractors and specialty contractors who feel the gap between the field and the books: supers and PMs who want the office to see what they see, controllers who are tired of reconciling two systems, and CFOs who want a WIP schedule they can trust on any day of the month.
Where it stands today
os.construction is pre-launch. We are building it now with a group of founding contractors, who get access first and help decide what ships first. That is why most pages in these docs are marked Preview: they describe the product as it is being built, and details may change. Pages marked Planned describe work that has not started yet.
We do not publish launch dates or pricing in the docs. Founding contractors get those first.
Was this helpful?
Help shape how it works on your jobs.