How the OS works.

Concepts, workflows and data paths for os.construction. We're building it with founding contractors, so most pages are marked Preview and describe the product as it's being built.

16 articles

• What is os.constructionGetting started · One operating system for construction. Project management, construction accounting, analytics and AI agents on a single data core.
• How the founding program worksGetting started · Founding contractors get access first, lock in founder pricing and shape what gets built. Here is what joining involves and what to expect.
• Key concepts: one data coreGetting started · Why os.construction keeps projects, accounting, analytics and agents on a single record model, and what that changes day to day.
• Projects and the record modelConcepts · How a job is structured in os.construction, what a record is, and how links between RFIs, change orders, commitments and pay apps keep the story connected.
• Cost codes and budgetsConcepts · How cost codes, cost types and budgets work in job costing, and how os.construction keeps budget, committed cost and actual cost on the same structure.
• Commitments and change ordersConcepts · Subcontracts, purchase orders, owner change orders and commitment change orders, and how one approved change updates budget, commitments and billing together.
• Pay apps, SOV and retainageConcepts · How progress billing works with a schedule of values, AIA G702/G703 and retainage, worked through Pay App
• WIP and over/under billingConcepts · How a work-in-progress schedule is calculated with the cost-to-cost method, what over and under billing mean, and why os.construction computes WIP live instead of at month-end.
• Roles and permissionsConcepts · How os.construction is designed to control who sees and does what, by role, by project and by record type, including outside companies and AI agents.
• How agents workAgents · What AI agents in os.construction do, what they can read, how they propose work, and why a human approves every action before anything posts or sends.
• Approvals and audit trailAgents · How agent proposals are reviewed and approved, who can approve what, and how every action by a person or an agent is recorded in the audit trail.
• The six launch agentsAgents · AP, Billing, Risk, RFI, Compliance and Reporting. What each agent planned for launch does, what it reads, and what it asks you to approve.
• Importing from your current stackData · Planned migration paths from Procore, Sage 100 Contractor, Sage 300 CRE, QuickBooks and Vista. What we intend to bring over, where it maps, and how a cutover is meant to work.
• Data ownership and exportData · Your data stays yours. What that means in practice, what you will be able to export, and the commitments we are designing around.
• Field capture on phonesMobile · Daily logs, photos, RFIs and punch items captured on a phone, landing directly in the job record so the office sees what the field sees.
• Live dashboards and WIPAnalytics · Dashboards, WIP and portfolio views computed from the same records accounting closes on, current every day instead of rebuilt at month-end.