AOS — Blog https://aos.build/blog/ Product updates, engineering notes, and field thinking from the team building AOS — the operating system for AEC. en-us Copyright 2026 AOS Construction Software LLC Wed, 27 May 2026 12:00:00 GMT Wed, 27 May 2026 12:00:00 GMT 60 https://aos.build/assets/og-card.png AOS — Blog https://aos.build/blog/ 1200 630 Construction warranty management: from substantial completion through the warranty period. https://aos.build/blog/construction-warranty-management.html https://aos.build/blog/construction-warranty-management.html Thu, 28 May 2026 17:00:00 GMT AOS Warranty Closeout Project Management Subcontractors General Contractors Two warranty types matter: workmanship warranty (contractor's promise, typically 1-year general / 2-year mechanical / 5-year roofing / 10-year structural) and manufacturer warranty (equipment manufacturer's promise, periods vary 1-50+ years). The two overlap operationally — a leaking roof in year 1 of a 20-year manufacturer warranty might be a manufacturer issue, a workmanship issue, or both.

Warranty management depends almost entirely on the closeout binder: manufacturer warranty registrations in the owner's name, sub workmanship letters per scope, as-built drawings, equipment cut sheets, sub contact info, photo documentation. If the closeout binder is incomplete, warranty management becomes guesswork.

Seven recurring failures: project staff dispersed before warranty period starts, manufacturer warranty registrations missed (often the registration window closes within 30-60 days of install), sub disputes responsibility with no documentation, same defect appearing on multiple buildings without pattern recognition, owner-side maintenance failures classified as warranty claims, warranty extension on corrective work not tracked, latent defects discovered after warranty period.

Read the full post →

]]> Construction project scheduling: CPM, baseline, and the working schedule. https://aos.build/blog/construction-project-scheduling-cpm-baseline.html https://aos.build/blog/construction-project-scheduling-cpm-baseline.html Thu, 28 May 2026 16:30:00 GMT AOS Scheduling Project Management General Contractors Subcontractors CPM scheduling identifies the longest path of dependent activities through a project. Activities on the critical path have zero float; a delay to any of them delays substantial completion by the same amount. The contractual baseline (locked at award) and the working schedule (updated weekly) diverge over the project's life — and the gap between them is where delay claims live.

Schedule slippage traces to recurring patterns: owner-caused delays (with time + sometimes compensable damages owed), design-related delays (RFI/submittal lag), contractor-caused delays (sub mobilization, productivity, rework), force majeure (weather/pandemic/strikes), and concurrent delay (legal treatment varies by contract and jurisdiction).

Seven recurring failures: baseline never properly developed, working schedule updated but nobody reads it, delay events not documented in real time, critical path stale, sub schedule integration weak, time-impact analysis treated as a closeout exercise, look-ahead disconnected from master schedule. AOS doesn't replace Primavera P6 / MS Project — it provides the integration layer that makes scheduling work operationally, cross-tenant.

Read the full post →

]]> Construction safety management and EMR: a working guide for mid-market commercial subs. https://aos.build/blog/construction-safety-management-emr.html https://aos.build/blog/construction-safety-management-emr.html Thu, 28 May 2026 16:00:00 GMT AOS Safety Compliance Subcontractors General Contractors EMR is calculated by NCCI (or state equivalent) comparing your firm's actual workers' comp losses over the trailing 3 years to expected losses for your industry classification and payroll. Below 1.00 = better than average, above 1.00 = worse. The financial effect: a 1.25 EMR pays 25% more for the same WC coverage as a 0.85 EMR; for a $20M-payroll sub the difference can be $200K+ per year. The bigger effect: prequal disqualification on most projects with EMR above 1.00, and disqualification from federal / institutional / safety-mandated projects above 0.85-0.90.

Beyond EMR, standard safety metrics: TRIR (Total Recordable Incident Rate), DART (Days Away/Restricted/Transferred), LTIR (Lost Time Incident Rate), and severity rate. All per 200,000 worker-hours (= 100 FTE-years).

Most mid-market subs manage safety reactively — incidents happen, claims get filed, EMR climbs 1-2 years later. The shift to proactive safety requires: pre-task planning (Job Hazard Analysis) attached to the daily crew, near-miss and observation reporting from mobile, toolbox talks tied to actual work, post-incident root cause analysis, trend analysis at the firm level, crew-level accountability.

Read the full post →

]]> Subcontractor prequalification for general contractors: a working framework. https://aos.build/blog/subcontractor-prequalification-for-gcs.html https://aos.build/blog/subcontractor-prequalification-for-gcs.html Thu, 28 May 2026 14:00:00 GMT AOS Prequalification General Contractors Compliance Subcontractors Seven categories to evaluate: bonding capacity (single-job + aggregate per surety, with rating check), insurance coverage and endorsement capability, safety record (EMR, OSHA recordables, willful violations), financial stability (audited or CPA-reviewed financials, working capital, debt/equity, revenue trend), references (with actual phone calls, not just collected names), operational capacity (backlog, available staff, equipment, geographic logistics), and certifications/compliance (DBE/MBE/WBE, prevailing-wage history, union signatory status, trade certs).

Four prequal philosophies, each with what's wrong: the paperwork ritual (the binder on the shelf), the annual refresh (collected but not evaluated), the project-specific check (labor-intensive but actually screens), and the third-party prequal (broad but shallow). The right answer for most mid-market GCs is a hybrid with structured records that integrate with the award workflow.

Seven recurring failure modes: annual refresh nobody reviews, project-specific prequal skipped on "trusted" subs, reference checks reduced to name collection, financial review without analytic capability, safety record taken at face value, bonding capacity confused with bonding willingness, prequal data not refreshed on change events.

Read the full post →

]]> Construction punch list management: from substantial completion to certificate of occupancy. https://aos.build/blog/construction-punch-list-management.html https://aos.build/blog/construction-punch-list-management.html Thu, 28 May 2026 13:30:00 GMT AOS Punch List Project Management Closeout General Contractors Subcontractors The punch list captures three categories: incomplete work (scope items still owed), defective work (built but doesn't meet spec/drawings/code), and damage caused during construction (often a separate negotiation). What does NOT belong: owner-directed scope changes (those are COs), post-occupancy use issues (warranty), and items the owner doesn't like but were built per approved drawings (also COs). Discipline at list creation prevents disputes later.

Seven recurring failure modes: PDF-and-email workflow that loses items, no photo evidence per item, items reopening silently when another trade damages prior work, ambiguous sub assignments, post-walk list sprawl, single-person architect/owner sign-off bottlenecks, and punch resolutions that don't update warranty / as-built records.

Good workflow: one central structured list with state and audit trail, mobile-first capture in under 30 seconds from the field, photo evidence at every state change, sub assignment by scope (not by guess), defined list freeze at the substantial-completion walk, multi-tier verification, and closeout-binder coupling.

Read the full post →

]]> Construction RFI management: from field question to architect response without inbox limbo. https://aos.build/blog/construction-rfi-management-workflow.html https://aos.build/blog/construction-rfi-management-workflow.html Thu, 28 May 2026 13:00:00 GMT AOS RFI Project Management Subcontractors General Contractors The RFI is a formal written request from a contractor to the architect, engineer, or owner asking for clarification, interpretation, or additional information about the contract documents. Distinct from submittals (which propose specific products for approval) and change orders (which formally modify the contract). The 7-step lifecycle: field identifies question → originator drafts → routing → architect review → response routes back → cost/schedule impact assessment → closure.

Seven recurring failure modes: RFI buried in email instead of logged, no SLA tracking or breach alerts, RFI marked closed before response is applied, cost/schedule impact deferred (the silent margin killer), RFI volume that nobody triages, duplicate or near-duplicate RFIs, and responses that don't reference the original RFI.

The most consequential connection is RFI-to-CO promotion. When an architect's response expands scope, the contractor should promote the RFI to a CO record immediately, not at closeout. This is where most "design clarification" CO disputes originate — and where most silent margin loss in commercial construction happens.

Read the full post →

]]> Construction submittal management: from log entry to install approval without version drift. https://aos.build/blog/construction-submittal-management-workflow.html https://aos.build/blog/construction-submittal-management-workflow.html Thu, 28 May 2026 02:00:00 GMT AOS Submittals Project Management Subcontractors General Contractors A submittal is documentation a sub provides to demonstrate that a proposed product, system, or installation method meets the project specifications. Distinct from an RFI: the RFI asks "what does this mean," the submittal says "here's the specific product I propose to install — does it meet your spec." For a $20M commercial project the submittal log can run 200-500 entries; each one goes through a 9-step lifecycle.

Five recurring failure modes: install-without-approval (the most expensive), version drift between the approved submittal and the installed product, substitution requests handled informally in meetings rather than as formal records, SLA breach with no escalation documentation, and closeout submittals missing at the end. All five are common; all five are solvable with structured workflow.

What good looks like: one log per project shared across sub, GC, and architect; SLA breach alerts; built-in version control; install-status tied to approval-status; formal substitution workflow; closeout submittals attach automatically at approval.

Read the full post →

]]> Construction cost coding and chart-of-accounts decisions for mid-market firms. https://aos.build/blog/construction-cost-coding-chart-of-accounts-mid-market.html https://aos.build/blog/construction-cost-coding-chart-of-accounts-mid-market.html Thu, 28 May 2026 01:30:00 GMT AOS Accounting Cost Coding Subcontractors General Contractors A cost code is the identifier you use to classify a construction cost. It serves estimating, budgeting, job costing, SOV/pay-app, and GL/financial-reporting purposes — the same cost code shows up in five or six different systems during a typical project. Whether those systems share a consistent structure determines whether reconciliation is a click or a week.

Four common structures: CSI MasterFormat (industry standard, specification-oriented), CSI UniFormat (building-system-oriented, used for early conceptual estimating), custom GC-defined codes, and trade-specific custom codes (each sub trade has its own). Most commercial projects have all four operating simultaneously, with manual reconciliation as the cost.

Most pay-app cycles that bounce back from the GC's accountant for "doesn't reconcile" reasons trace to cost-code drift. The 28th-of-the-month reconciliation that mid-market accountants do is largely a cost-code translation exercise — reducing it cuts your monthly close time by half. Design principles: pick a backbone (usually MasterFormat) and stick to it, limit depth to 3-4 levels, map cleanly to the GL, reserve number ranges for expansion, don't rename codes mid-project, document the structure.

Read the full post →

]]> Construction COI compliance: how subs maintain coverage and how GCs actually verify it. https://aos.build/blog/construction-coi-compliance-subs-gcs.html https://aos.build/blog/construction-coi-compliance-subs-gcs.html Thu, 28 May 2026 01:00:00 GMT AOS Insurance Compliance Subcontractors General Contractors Every commercial sub maintains coverage in four to five categories: Commercial General Liability (CGL), Workers' Compensation and Employer's Liability, Commercial Auto Liability, Excess/Umbrella, and sometimes Professional Liability / Pollution / Builder's Risk. That's four to six certificates per sub per project.

The base COI isn't enough — most commercial GC contracts require specific endorsements: Additional Insured (CG 20 10 / CG 20 37 or analogous), Waiver of Subrogation, Primary and Non-Contributory, and 30-Day Notice of Cancellation. The certificate is just evidence; the endorsements are where the actual coverage lives.

Seven recurring mistakes that cost firms real money: wrong endorsement form (CG 20 10 11 85 vs 04 13 differences), generic vs named AI, insufficient limits, mid-project policy lapse, waiver of subrogation missing on WC, cancellation notice removed by carrier, COI not found when a claim arises. For a GC running 25 projects with 10-15 subs each, that's 250-400 active COI relationships at any moment.

Read the full post →

]]> The ITB process for commercial subcontractors: from bid invitation to award without losing days to GC portal chaos. https://aos.build/blog/itb-process-commercial-subcontractors.html https://aos.build/blog/itb-process-commercial-subcontractors.html Wed, 27 May 2026 23:00:00 GMT AOS Subcontractors Estimating ITB Today the operating environment for mid-market sub estimating is portal proliferation. Every major GC pushes ITBs through their own preferred portal — Procore, GCPay, BuildingConnected, IsqFt, SmartBid, ConstructConnect, etc. A sub bidding to 30+ active GCs logs into 8-15 portals during a typical week. The cost falls entirely on the sub side.

The estimator's day-one decision on every incoming ITB is pursue / no-bid / defer. The faster this triage happens, the more time the estimator has on bids that matter. The most expensive thing a sub estimator does is start quantifying a bid they'll later no-bid.

What good workflow looks like: one inbox for all incoming ITBs, bid document pre-parsing, addendum tracking with active alerts, pre-bid clarification log per project, bid quantification linked to historical takeoffs, bid status visible across the team. AOS unifies the inbox across sources and (when the GC is also on AOS) flows award into the subcontract record cross-tenant.

Read the full post →

]]> Prevailing wage and certified payroll for mid-market commercial subs: a 2026 working guide. https://aos.build/blog/prevailing-wage-certified-payroll-commercial-subs.html https://aos.build/blog/prevailing-wage-certified-payroll-commercial-subs.html Wed, 27 May 2026 22:30:00 GMT AOS Subcontractors Compliance Payroll Prevailing Wage The Davis-Bacon Act requires prevailing-wage payment on federally-funded construction $2,000+. Most states have analogous "little Davis-Bacon" statutes for state-funded work — California Labor Code 1720-1860, NY Labor Law Article 8/9, NJ Prevailing Wage Act, Illinois, Pennsylvania, Massachusetts, and many more. The controlling wage determination depends on funding source, not location.

The WH-347 certified payroll form requires weekly per-worker reporting: classification (per the wage determination), hours per day, base rate, gross earned, deductions, net pay. The Statement of Compliance is signed by an authorized officer; false certification is potentially a federal felony.

Fringe-benefit math is where most compliance failures happen. Annualization based on actual hours across all projects (public and private), public-work-only benefits being treated as supplemental wages, and the cash-in-lieu payroll-tax cost — all routinely mis-handled. The seven recurring DOL audit findings: misclassification, apprentice ratios exceeded, fringe over-credited, cash fringe under-paid, owner-operator misclassification, travel-time errors, and non-conforming certified payroll.

Read the full post →

]]> Construction change orders: four patterns and how to manage them without margin erosion. https://aos.build/blog/construction-change-orders-four-patterns.html https://aos.build/blog/construction-change-orders-four-patterns.html Wed, 27 May 2026 22:00:00 GMT AOS Change Orders Project Management Subcontractors General Contractors Almost every commercial change order fits one of four patterns: scope addition (owner-directed, usually lump-sum and approved); field condition (unforeseen, almost always T&M with schedule impact accepted); design clarification (most-disputed, often compromised below T&M cost); and acceleration (T&M with documented premium-time rates, often the largest single COs late in projects).

The CO lifecycle has eight steps (trigger → notice → quantification → submission → negotiation → approval → performance → billing). The single biggest pathology: negotiation and approval often happen after performance, because the schedule can't wait. The sub does the work and then negotiates from a much weaker position.

CO aging is the second-largest hidden carrying cost on commercial projects (after retention). For a sub doing $30M in volume, CO aging running 90 days at 10% of project value means $750K constantly tied up in performed-but-unpaid CO work. Most subs don't surface this aging until it hits a closeout dispute.

Read the full post →

]]> The construction closeout binder: continuous assembly instead of closeout-week panic. https://aos.build/blog/construction-closeout-binder-continuous-assembly.html https://aos.build/blog/construction-closeout-binder-continuous-assembly.html Wed, 27 May 2026 20:00:00 GMT AOS Closeout Project Management General Contractors A typical commercial closeout binder is 1,000-3,000 pages: warranties, O&M manuals, final as-built drawings, final lien waivers, final pay apps with retention release, change-order log reconciliation, permits and certificates of occupancy, test and inspection reports, attic-stock inventory, punch-list closure, and project record documents.

Most binders take 200-400 hours of GC project engineer time and 60-120 days from substantial completion because the documents come from different parties at different times and most PM systems don't have a "this is a closeout item" tag at document creation.

The continuous-assembly alternative: tag every relevant document at the moment it's produced, track what should exist (not just what does), update as-builts continuously from field markup, make subs responsible for their pieces, and roll up to the binder at substantial completion. From three-month fire drill to two-week confirmation, with the side benefit that the warranty period starts when the contract said it would.

Read the full post →

]]> Why GCs should care about their subs' tech stack. https://aos.build/blog/why-gcs-should-care-about-sub-tech-stack.html https://aos.build/blog/why-gcs-should-care-about-sub-tech-stack.html Wed, 27 May 2026 19:30:00 GMT AOS General Contractors Strategy Cross-Tenant The standard mental model in commercial construction is that the sub's internal operations are the sub's problem. That made sense when project communication was phone calls and faxes. It makes less sense in 2026, because the sub's tech maturity now directly drives how much administrative work your GC office has to do for every job that sub is on.

Four places sub tech limitations hit the GC's P&L: (1) AP processing cost per sub per cycle — 60-300 hours/month of GC office labor for a typical $100M GC, eliminable when subs are on connected platforms; (2) RFI cycle time — the difference between 8-day and 14-day average turn-time, which on a critical-path RFI is a week of schedule slip; (3) retention disputes at closeout — multi-week reconciliations that the GC technically wins but pays for in labor; (4) field signal latency that arrives in the office 24-48 hours late, when issues have already compounded.

The strategic move isn't "don't bid these subs" — it's helping the subs you want to keep work with onto modern tooling so the operational compression is mutual. The compounding lands hardest when both sides are on the same platform.

Read the full post →

]]> Construction AP automation and tiered approval for mid-market GCs. https://aos.build/blog/construction-ap-automation-tiered-approval-mid-market-gc.html https://aos.build/blog/construction-ap-automation-tiered-approval-mid-market-gc.html Wed, 27 May 2026 19:00:00 GMT AOS General Contractors Accounting AP Automation A typical mid-market commercial GC processes four distinct types of AP documents: subcontractor pay applications (the largest dollar volume), supplier invoices for materials (the largest count), consultant and service invoices, and field purchases and reimbursements. Each has its own approval logic and supporting-document requirements.

Construction AP requires a five-tier approval chain: field verification (superintendent or PM confirms percent-complete or receiving), PM review (contract terms, change orders, budget fit), accounting review (GL coding, retention, lien waivers, prompt-pay deadlines), owner certification (for some contract structures), and payment release (with lien waiver execution at the moment of payment). Generic SaaS AP tools assume one or two-tier approval — construction needs five.

Three-way matching is automatic when the source records (contract SOV, budget, percent-complete) live in the same platform. Lien-waiver coupling means the payment can't release until the waiver is signed in the correct state's statutory form for the exact released amount. Retention coupling means the platform tracks at the SOV-line level with state statutory triggers. End-to-end automation eliminates somewhere between one and two full-time GC AP positions.

Read the full post →

]]> Construction lien waivers explained: a state-by-state guide for subcontractors and GCs. https://aos.build/blog/construction-lien-waivers-state-by-state.html https://aos.build/blog/construction-lien-waivers-state-by-state.html Wed, 27 May 2026 17:00:00 GMT AOS Lien Waivers Compliance Accounting Lien waivers vary on two axes: conditional vs. unconditional, and progress vs. final. That gives four combinations, all of which a typical commercial sub uses regularly. Conditional progress waivers go before payment; unconditional final waivers go at closeout after payment clears.

Several major commercial-construction states prescribe statutory waiver forms — California (Civil Code 8132-8138), Texas (Property Code Chapter 53), Florida (Statute 713.20), Georgia, Missouri, Mississippi, Wyoming, Arizona, Nevada, Utah. Using a custom form in these states can void the waiver. Other states regulate without prescribing specific forms.

The seven errors that delay payment via lien waivers: wrong-amount waiver, wrong-state form, conditional vs unconditional mixed up, missing supplier waivers, notarization missed, improper signing authority, date errors.

Read the full post →

]]> A field-tech adoption playbook for self-perform specialty trades. https://aos.build/blog/field-tech-adoption-self-perform.html https://aos.build/blog/field-tech-adoption-self-perform.html Wed, 27 May 2026 16:30:00 GMT AOS Subcontractors Field Operations Adoption Field-tech rollouts fail the same way every time: the app was designed in an office and handed to the field, the foreman has no incentive to use it, the training was a one-time event, the data isn't visible back to the field, and the mandate came from above without on-ground buy-in. "The foremen are resistant to change" is a common executive framing and almost always wrong.

The foreman-first design principle: voice input over typing, offline-first, gloved-fingertip tap targets, geofenced workflows, drawing markup that works on a phone, photo capture with context preserved. The four-stage rollout: pick one crew, spend two weeks in the field, make data visible back to the field, then let the pilot foreman help expand.

Self-perform specialty trades — concrete, steel, drywall, MEP, glazing — need yard-to-site equipment tracking, prefab tracking, crew-of-the-day with worker typeahead, and trade-specific productivity units that generalist platforms don't have built in.

Read the full post →

]]> Construction retention rollforward by GC: a working guide for sub accounting. https://aos.build/blog/retention-rollforward-sub-accounting.html https://aos.build/blog/retention-rollforward-sub-accounting.html Wed, 27 May 2026 16:00:00 GMT AOS Subcontractors Accounting Retention Retention drift traces back to three failure modes: retention tracked at the project level (not SOV-line), state statutory triggers not applied, and pay-app handoffs that lose the rollforward math. A defensible retention statement needs tracking by project, by GC, by SOV line, by release trigger, and by state statutory rule.

State retention-release rules every sub should know: California caps at 5% on public works with 60-day release after completion; Texas Property Code Chapter 53 governs with 7-day prompt-pay protections; Florida 715.12 mandates automatic reduction to 5% after 50% completion on public projects $200K+; New York General Business Law Article 35-E requires 30-day release; Pennsylvania CASPA, Illinois Prompt Payment Act, Washington RCW 39.04.250, and many more apply when contracts are silent.

If the contract is silent on retention, the state statute applies — and subs who don't track statutory triggers leave money on the table.

Read the full post →

]]> Why the mid-market GC software stack is broken (and what to put in its place). https://aos.build/blog/mid-market-gc-stack-is-broken.html https://aos.build/blog/mid-market-gc-stack-is-broken.html Wed, 27 May 2026 14:00:00 GMT AOS General Contractors Industry Thesis A mid-market general contractor in 2026 — a firm doing $50 million to $300 million a year, running 15 to 60 active projects, with a 30 to 200 person office — sits in the most under-served bracket of construction software. Too big for QuickBooks. Too small for the enterprise platforms whose pricing assumes you're a top-50 ENR contractor. Stuck stitching together four to six vendors that don't talk to each other, paying the integration tax in office labor.

The dominant narrative is that the big GC platforms have won. For ENR-100 contractors with a CIO and a 20-person IT department, the story is roughly true. For everyone else, it isn't.

A typical $120 million regional GC runs 8-12 separate software systems totaling $150K-$400K a year, with a much larger invisible cost paid in office labor reconciling the patchwork. This post walks through why the stack is shaped this way, what's specifically broken (estimate ≠ budget ≠ SOV ≠ pay app, 45-75 day pay-app cycles, late field signal, Friday-PDF owner reporting), and what a real replacement has to do.

Read the full post →

]]> Procore alternatives for subcontractors and mid-market GCs in 2026. https://aos.build/blog/procore-alternatives-2026.html https://aos.build/blog/procore-alternatives-2026.html Wed, 27 May 2026 13:30:00 GMT AOS Procore Alternatives Software Selection Comparison Procore is the default project-management platform in commercial construction, and for a lot of firms it works fine. For others — especially mid-market subs and GCs in the $20M-$300M range — the price doesn't pencil, the field experience is an office product handed to the foreman, or the per-active-project model taxes growth.

Four recurring reasons firms look for alternatives: pricing scales faster than value, the sub side is a portal rather than an operating system, construction accounting isn't Procore's strong suit, and field experience doesn't survive contact with the actual field.

This guide covers AOS, Sage 300 CRE / Sage Intacct Construction, Foundation Software, Viewpoint Vista / Trimble Construction One, Buildertrend, CMiC, and Autodesk Construction Cloud — by audience, price point, strengths, and tradeoffs. Includes a quick-reference shortlist by firm shape.

Read the full post →

]]> When the GC and the sub share a record: what actually changes on a commercial project. https://aos.build/blog/both-sides-on-one-record.html https://aos.build/blog/both-sides-on-one-record.html Wed, 27 May 2026 13:00:00 GMT AOS Cross-Tenant Workflow Product The strategic differentiator of AOS isn't that it's a better PM tool, or a better construction-accounting system, or a better field-ops app. The strategic differentiator is that when both the GC and the subcontractor on a project are on AOS, they share the same project record. The document handoff seam between them disappears.

Seven specific workflows change in measurable ways: (1) pay-app cycle compresses from 60 days to 30 with full status visibility; (2) retention shifts from dispute-prone to dispute-proof because the GC's liability and the sub's receivable are the same database row; (3) change orders move from email purgatory to one approval flow with live aging; (4) RFIs and submittals get SLA tracking instead of inbox chaos; (5) field signal arrives live instead of next-day; (6) drawing version drift disappears; (7) closeout compresses from a three-month scramble to a two-week confirmation.

For a typical mid-market commercial project, the aggregate value lands somewhere between 1% and 5% of project value, paid in office labor reduction and faster cash cycles.

Read the full post →

]]> Subcontractors are the most under-served seat in construction technology. https://aos.build/blog/subcontractor-software-most-underserved-seat.html https://aos.build/blog/subcontractor-software-most-underserved-seat.html Wed, 27 May 2026 12:00:00 GMT AOS Subcontractors Industry Thesis Walk into any mid-market commercial subcontractor on a Monday morning and watch what the office staff actually do. They log into Procore for the GC running the school job. Then GCPay for the hospital. Then Textura for the office tower. Then somebody's home-grown SharePoint portal for the courthouse renovation. Then a different Procore instance for a different GC. Then their own QuickBooks. Then Excel.

That's the operating system of a $30 million sub in 2026. Not a platform. A stack of other people's portals.

Nobody set out to design it this way. It's just where construction software ended up after two decades of building GC-first platforms and treating subs as a downstream data-entry endpoint. The cost of that decision falls almost entirely on the sub side — in office hours, in slow cash flow, in retention drift, in pay apps that go sideways because the sub can't see what's happening on the GC's side of the record.

This is a post about that gap. Why it exists, what it actually costs the sub side, and what changes when somebody finally builds an operating system for the sub's own business instead of another portal to log into.

Read the full post →

]]> AIA G702 and G703 for subcontractors: a working guide. https://aos.build/blog/aia-g702-g703-guide-for-subcontractors.html https://aos.build/blog/aia-g702-g703-guide-for-subcontractors.html Wed, 27 May 2026 12:00:00 GMT AOS Subcontractors Accounting Pay Apps If you're a commercial subcontractor in the United States, the AIA G702 and G703 are the forms you bill on. Most GCs require them, most owners expect them, and most pay-app disputes you've ever had are over a line that got mishandled on one of these two pages.

The G702 is the Application and Certificate for Payment — a one-page summary of the original contract sum, billed to date, billed this period, retention withheld, and the net amount due. The G703 is the Continuation Sheet — one row per SOV line item with the math behind the G702.

Together they're the complete pay-application package every commercial subcontractor in the US bills on. This guide walks through what every field actually means, the seven common errors that delay sub payment, and how AOS generates the whole package from your live SOV with retention tracking and lien-waiver lifecycle on one record.

Read the full post →

]]> How to choose construction software when you're a mid-market sub or GC. https://aos.build/blog/choosing-construction-software-mid-market-sub-gc.html https://aos.build/blog/choosing-construction-software-mid-market-sub-gc.html Wed, 27 May 2026 12:00:00 GMT AOS Buyer Guide Mid-Market Software Selection If you run a mid-market commercial subcontractor or GC — $20M to $100M annual volume, 30 to 300 employees — you've probably gotten the same demo three times. The big-name PM platform "designed for firms like yours" but priced for firms three times your size. The legacy construction-accounting system that runs on the same Windows codebase it shipped in 2009. The point tool that solves exactly one workflow well and integrates with nothing else.

This is a practical guide to evaluating construction software at that size: the five tradeoffs that actually matter (consolidation vs best-of-breed, mobile that works in the field, per-seat vs flat pricing, data ownership, and the shape of the buyer), and twelve questions to ask every demo that separate the platforms that work from the ones that look good in slides.

Read the full post →

]]> Introducing AOS — one operating system for every seat in AEC. https://aos.build/blog/introducing-aos.html https://aos.build/blog/introducing-aos.html Fri, 22 May 2026 12:00:00 GMT AOS Launch Product 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.

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, owners and developers, subcontractors, architecture firms, and residential builders. 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.

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.

What we ship every week.

AOS is built on a deliberate cadence. We ship a database migration weekly, sometimes more. 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, and per-pillar deep dives.

Read the full post →

]]>