SHEET B-002  ·  BLOG POST PROJECT AOS / OPERATING SYSTEM REV 01 STATUS PUBLISHED
← All posts
5 min read

Introducing AOS — construction software that works together.

Construction runs on a patchwork of tools none of which were built for it. AOS is one connected platform for commercial GCs today — project management, pay apps, field paperwork, closeout, and subs on one record. Owner, subcontractor, architect, and residential views are rolling out with early customers who ask for them.

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.

Built for GCs first. Other seats on the same record.

AOS is one platform on one shared database — not five separate products bolted together. The first release is the commercial GC Launch Pack; other tenant views turn on as early customers need them:

  • General contractors get estimating, ITB, 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, pay apps 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 pay-app 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 pay app, an owner approving the same record, 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, starting with GCs and expanding to other seats as they roll out.

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 in the GC Launch Pack and on the near-term roadmap:

  • GC pay apps and AP. Pay apps from the schedule of values, tiered AP approval, lien-waiver gating across all 51 jurisdictions, and GL posting without retyping.
  • Closeout binder. Continuous assembly from RFIs, submittals, warranties, and punch — not a three-month scramble at substantial completion.
  • Subcontractor portal. Subs on AOS submit pay apps from one cost record; cross-tenant delivery into the GC's AP queue is rolling out with design partners.
  • Owner portal (on request). GC-uploaded progress photos and pay-app review for owners — token-scoped, no account required. Rolling out with owner teams when their GC enables access.
  • Field tools. Daily logs, punch, photos, and forms from the browser on a phone today; geofenced timesheets and voice logs available on request. Native App Store apps are not generally available yet.

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.