For decades, the construction industry has run on a patchwork of tools none of which were built for it: a project management platform from one vendor, accounting from another, payroll from a third, estimating in a spreadsheet, AP in email, sub bids on whatever portal each owner mandates that month.
Every system stored its own version of the same project. Every report was a hand-rolled export. Every reconciliation was a Friday afternoon. The company-of-record always lost time and money to the cost of wiring it all together — and the people doing the integrating were usually field staff who would rather be on a job. The only firms that solved it were the ones big enough to hire a CIO and an integration team.
A 50-person GC shouldn't have to. Neither should a developer with a dozen active projects, a specialty trade billing five GCs a month, an architecture firm doing CA on twenty engagements, or a residential builder managing eighty homes through warranty.
So we built AOS.
One platform. Five tenant types. One record.
AOS is one operating system — not five separate products bolted together — that serves five tenant types from the same database:
- General contractors get estimating, ITB, AIA pay apps, subcontractor management, owner portals, field operations, and the compliance backbone.
- Owners and developers get a portfolio dashboard, two-click pay-app approval, vendor compliance, and a board-ready distribution — on the same record the GC built.
- Subcontractors stop retyping the same pay app into five GC portals. One cost record across every job, AIA-grade G702 / G703 in your own template, certs and insurance always current.
- Architecture firms run construction administration without the inbox: a current drawings register, RFI and submittal SLA tracking, design issues with photo evidence, and AIA G702 certification on a screen.
- Residential builders get selections and allowances tied to budget, construction draws assembled from milestones and lien waivers, change orders the homeowner signs, and warranty that doesn't fall off after closing.
A GC certifying a sub's G702, an owner approving the same pay app, and an architect responding to the RFI behind it are all looking at the same row in the same database — through the view tuned to their job. Same data, different door.
Why this matters now.
The economics of construction software have been backwards for a long time. The dominant PM vendor charges a percentage of your annual construction volume. The dominant accounting vendor charges per-EIN, per-seat, per-module. The dominant compliance vendor sells lien waivers as a separate product. Add it up and a $50M GC is paying six figures a year for a stack of tools that still don't talk to each other.
AOS is priced flat. Not as a tax on construction volume or assets under management. One bundle, with add-ons, across every tenant type.
More importantly, AOS is one record. When a sub uploads a pay-app, the GC sees it in their AR queue, the owner sees it in their approval queue, the architect sees the certification request, and the GL records the commitment — all in the same transaction, on the same row, with the same audit trail. No webhooks. No nightly reconciliation. No "the architect has the data; we don't" friction.
What we ship every week.
AOS is built on a deliberate cadence. We ship a database migration weekly, sometimes more. Recent work that's already live or rolling out to tenants:
- Subcontractor AR. First-class AIA G702 / G703 pay apps from the sub side, with lien waivers across all 51 jurisdictions, executable change orders, and a cross-tenant outbox that delivers the pay app directly into the GC's AP queue.
- Owner project photos. GC-uploaded progress photos that surface to owners through a controlled portal, with AI moderation, flag workflows, and token-scoped share links that survive a GC's master-flag flip.
- Subcontractor crew calendar. Worker assignments, PTO tracking, geofenced timesheets, drag-to-reschedule, and a heat-mapped utilization grid — the same engine GCs use to staff a tower runs your trade.
- Building management for owners. Lease escalators, stepped rent schedules, document storage, and an expiry-nag cron that pings the right people 90 / 60 / 30 / 7 days out.
- Cross-tenant bidding. Owners issue ITBs that subs claim via tokenized link — with off-platform GCs supported through a manual capture path.
This blog is where we'll document what shipped, what we learned, and what's next. Engineering notes on the migration cadence, field case studies, per-pillar deep dives on the modules above.
Read next.
The full feature map walks through six pillars from project management to portals, with a tenant lens that tailors each pitch to your seat. Pricing is one beta bundle plus add-ons, listed in plain dollars. And if you'd rather see AOS on your own data, book a 30-minute demo — we'll show you how a project moves from estimate through closeout on one record.
Welcome.