One bundle for your side of the job. Founding-customer pricing.

Closed beta runs Jun 14 → Jul 13, 2026 (invite-only, free). Open beta runs Jul 13 → Dec 14, 2026 for new signups; existing beta tenants keep running through Dec 31. GA opens Jan 1, 2027. Every beta tenant — closed or open — keeps the beta rate for two years from Jul 13, 2026 (through Jul 13, 2028). At that point you roll to then-current GA pricing with 90 days notice and the option to leave clean. No auto-bumps.

You win either way. The beta-cohort guarantee: if GA pricing for the same bundle (base plus the add-ons you're running) comes in lower than your locked beta rate, you automatically drop to 10% below the GA rate for the rest of your lock window. The math is whichever is lower — your locked beta rate, or GA × 0.9. We'll never have a beta tenant paying more than 90% of what a new customer pays for the same scope. You're a founding customer; loyalty should not be a tax.

The $500 / mo beta base is a founding-customer rate that holds for 24 months. GA pricing publishes Jan 1, 2027. We're aiming for a reasonable price point: a typical customer under $15M annual revenue runs $1,000-$2,000 / mo all-in (base plus add-ons). Larger companies pay more — but the axis is project count and compliance depth, not your construction volume. We don't charge for the dollars flowing through. Beta tenants who sign in 2026 stay on their locked rates through Jul 13, 2028 regardless of where GA pricing lands; at lock-window end you roll to then-current GA rates with 90 days notice and the option to leave clean.

By usage, not by construction volume. Most construction software prices on a percentage of annual construction value (often 0.4–1.0% of ACV), which means a strong year of bookings turns into a six-figure invoice from your software vendor. AOS doesn't do that. The base bundle is a flat monthly fee. Add-ons are flat monthly fees. Larger firms pay more because they (a) cross the 50-active-project beta cap and need a higher project tier, (b) carry multiple EINs and add the Accounting & AP per-EIN line, (c) have the compliance / multi-state footprint that justifies the Compliance Pro add-on. Each of those is a real workload we're servicing — not a percentage of your top line.

Yes — beta slots are capped to keep onboarding quality high and feedback loops tight. Closed beta is invite-only and the smallest cohort; tell us about your company and we'll let you know if there's room. Open beta opens to public signups on Jul 13 with a larger cap, but we'll close intake as soon as the cohort fills (or Dec 14, whichever comes first). Earlier signups get more onboarding attention.

Closed-beta tenants (Jun 14 → Jul 13) get the most one-on-one onboarding, the strongest input into roadmap, and don't pay anything until Jul 13. Open-beta tenants (Jul 13 → Dec 14) pay from day one at the open-beta rate. Both cohorts get the same two-year price lock running from Jul 13, 2026 through Jul 13, 2028.

The last two weeks of December are a hard stop on new accounts — we use that window to finalize GA pricing, lock the GA contract terms, freeze billing changes, and make sure every existing beta tenant is solid going into GA. New signups resume on Jan 1, 2027 at GA pricing. If you want a beta rate, sign up before Dec 14.

We don't yet have enough usage data to know exactly where the tier boundaries belong. Rather than guess and force customers to re-tier later, we're starting with one inclusive bundle plus add-ons. At GA we'll tier based on what actual customers actually use.

The beta bundle covers up to 50 active projects at any one time during the beta period. Closed projects don't count. If you're approaching the cap or need to run more, drop us a line — we're sizing larger pilots case-by-case during beta.

Every AI feature (invoice parse, voice log categorize, broker quote review, photo analysis) consumes credits from your monthly bucket. The beta bundle includes 2M credits / month — about 200 invoice parses or 400 voice logs at typical per-action cost. You watch consumption live, get alerted at 75% / 90% / 100%, and decide what happens at the cap: pause AI features until next month's reset, buy a top-up pack ($50 buys 5M credits, $150 buys 20M), enable pay-as-you-go overage at $12 per million, or auto-refill with a monthly ceiling you set. The default at 100% is "hard pause" — we never bill you for credits you didn't explicitly authorize.

Yes. Per-user credit caps are inheritable from role — give all estimators a 200k monthly cap, all PMs 500k, admins unlimited. Caps are enforced at the API layer; once a user hits theirs, their AI features pause for the rest of the month while everyone else's keeps working. You can also raise an individual user's cap mid-month from the admin panel; the change is logged in the audit trail.

Every AI call is logged with timestamp, user, feature, credit count, and dollar value. Export to CSV from the admin panel any time. The bundled 2M credits stay inside the $500/mo line item on your bill; top-up packs and PAYG overage are itemized as separate AP charges with the period and pack ID. Most CFOs map the AI line to a single "Software — AI services" GL account.

Three protections, in order: (1) the pre-flight cost preview shows projected credits before any bulk operation, so you decide whether to run it or split it; (2) per-user caps prevent any one user from running the whole company dry; (3) the per-tenant cap is the absolute ceiling — at 100% AI pauses until you buy a top-up pack or your monthly bucket resets on the 1st. You can also pre-buy a 20M-credit pack at month-start if you know a heavy cycle is coming.

We want beta customers to give the platform to everyone on their team without weighing the math on each seat. Per-user pricing creates friction at exactly the moment we want the opposite — broad usage, honest feedback, real adoption signal. Expect AOS to add a reasonable per-user component at GA; founding-cohort customers keep their beta rate (flat-only) for the duration of their engagement.

External users are people outside your company who interact with AOS through a portal — owners approving pay apps, subs responding to bid invitations, board members reviewing packets, ex-employees pulling W-2s, architects on read-only RFI access. They sign in via secure one-click links (no account creation) and are never counted as billable seats. This stays true at GA.

It depends on what you do. Payroll if you don't already have a construction payroll vendor. Accounting & AP if you want to replace your AP stack. Subcontractor ITB if you're a GC sending bid packages out. Sub Compliance if you carry the audit burden for sub COIs / W-9s. Owner Finance & Boardroom if you have a board or institutional ownership. Compliance Pro if you work across multiple states or pay per diem. Residential Builders if you build custom or spec homes — selections, draws, homeowner portal, and warranty become first-class instead of bolted-on.

Enough. The GC base bundle gives you the construction record (drawings, RFIs, change orders, daily logs, AIA pay apps for the lender, field crew + timesheets, training & safety, helpdesk). The Residential add-on layers on the homeowner-facing pieces (selections, allowances, draws, signed COs, walkthrough, warranty, multi-lot pipeline). Together it's the residential builder OS — no second tool. Flat $1,099/mo for the pair, regardless of how many homes you build or how many allowances each one has.

Zero of any of those. The Residential add-on is flat monthly. Build one home or fifty (up to the 50-active-project beta cap); track ten allowances per home or fifty; assemble four draws or fourteen. Same $599/mo. We don't price residential software on a per-home or per-transaction basis — that's exactly the model we built AOS to replace.

No. The owner portal and basic sub bid response are included in the beta bundle. The board portal is part of the Owner Finance & Boardroom add-on. External users (owners, subs, board members, alumni, architects) are never counted as billable seats.

Yes. Add-ons can be turned on or off month-to-month; you'll only be billed for the months a given add-on was active. The beta bundle itself is a monthly commit (no minimum term) during the beta period.

Yes. We import users, projects, cost codes, vendors, and subcontractors via XLSX templates as part of every onboarding. Larger pilots get help pulling open AP, in-flight pay apps, active subcontracts, employee history (for the alumni portal), and active lien rights from your prior system as part of the implementation.

Annual will save roughly 10–12% compared to monthly. There's no auto-renew lock-in: you can switch to monthly or cancel at any renewal with 30 days notice. We don't keep a customer who doesn't want to be one.

US-based managed cloud (Ohio region) with daily backups and encryption at rest. AOS is SOC 2-aligned and the security questionnaire is available on request. IP addresses and user agents on external portals are stored only as secure one-way hashes — never as raw values.

The Owner bundle includes modules GCs pay for as add-ons — the Boardroom, the cash forecast 30/60/90, the building & lease portfolio, and the owner↔GC bridge. Buying those as add-ons against the GC base costs more than the Owner bundle's $750. We priced the Owner bundle to undercut the unbundled equivalent — not to charge Owners more.

The $750 base includes 5 internal seats on your team — typically your CFO, asset manager, construction manager, accounting lead, and one more. Additional internal seats are $50 / user / month. External users are never billable: your GCs (on the tokenized portal), board members, investors, A/Es, and tenants sign in via secure one-click links and never count against your seat total, beta or GA. Why the seat fee on the Owner side and not the GC side? Owner-team usage tends to be deep and continuous (CFO + asset manager checking the dashboard daily); GC-team usage skews toward field crews with light-touch tools where per-seat pricing creates the wrong incentive. We're matching the model to how each side actually uses the platform.

Internal = anyone on your direct payroll or your management company's payroll who logs in to AOS to do their job (CFO, asset manager, accountant, construction manager, analyst). External = anyone outside your operating entity who interacts with AOS through a portal: your GCs and their subs (via the tokenized GC portal), board members (via the board packet portal), investors (via the LP portal), A/Es (read-only RFI access), and tenants (lease / TIA portal). External users never count toward your seat total. If you're unsure where a particular person fits — for example, an outsourced fractional CFO — talk to us; we'll typically count them as a single internal seat.

Anything currently in design, bidding, construction, or punch list. Closed projects don't count toward the 15-project beta cap. Routine maintenance and turnover work doesn't count either — only capital projects with a budget you're tracking. If you're running more than 15 active capital projects, talk to us; we're sizing larger portfolios case-by-case.

Each individual property in your portfolio, whether owned or under management. Multi-tenant buildings count as one. Sub-units (leases inside a building) don't count toward the cap — those are tracked freely under each building. Disposed properties drop off automatically.

Each OpCo or JV is a separate "entity" (EIN) in AOS. The base Owner bundle includes one EIN. Add the Accounting & AP add-on for multi-EIN consolidation at the holding level — balance sheet, P&L, and cash flow roll up across all entities. JVs get their own minority-partner accounting with promote / waterfall structures handled. Each additional EIN beyond the first is $750/mo on top of the $1,000 add-on base.

Yes. Non-AOS GCs sign in to a tokenized portal at /gc-portal/<token> — no account creation, no software for them to buy, free for the GC. They draft pay apps, respond to RFIs and submittals, post schedule updates, and upload lien waivers. You see everything on your portfolio dashboard, side-by-side with data from your GCs who are on AOS. The GC-side experience is intentionally minimal — they don't have to learn a new tool, they just respond to your structured asks.

No, they're never billable. Board members are external users — they sign in via per-member secure links and never count against your seat total, beta or GA. The basic board packet is included in the Owner bundle: generate, approve, distribute with engagement analytics (who opened, who read what) and a pre-meeting Q&A channel.

In the base bundle. AOS tracks buildings, leases (NNN / MG / FS), escalators (fixed-pct + fixed-amount, compounded or additive), CAM / RE-tax / insurance reconciliation, security deposit, notice periods, and holdover. Plus renewal options, TIA obligations and draws (planned / spent / paid / remaining), expiry alerts at 90 / 60 / 30 / 7 days. Lease-level rent rolls feed the cash forecast automatically.

Out of scope for the beta. The tax planner doesn't model 1031 timing yet; you'll continue running those through your CPA. On the roadmap for GA Q2 2027. If 1031 timing is on the critical path for your evaluation, let us know — we'll prioritize.

Out of scope. The Accounting & AP add-on emits clean consolidated financials (balance sheet, P&L, cash flow) at the holding level that your filing team or external consultant uses to draft the public filing. We're focused on the operating record and the management view, not the public-disclosure pipeline.

Closed beta runs Jun 14 → Jul 13, 2026 (invite-only, free). Open beta runs Jul 13 → Dec 14, 2026 for new signups; existing beta tenants keep running through Dec 31. GA opens Jan 1, 2027. Every beta tenant — closed or open — keeps the beta rate for two years from Jul 13, 2026 (through Jul 13, 2028). At that point you roll to then-current GA pricing with 90 days notice and the option to leave clean.

You win either way. The beta-cohort guarantee: if GA pricing for the same bundle (base plus the add-ons you're running) comes in lower than your locked beta rate, you automatically drop to 10% below the GA rate for the rest of your lock window. We'll never have a beta tenant paying more than 90% of what a new customer pays for the same scope.

By portfolio size and entity count, not by construction dollars or asset value. Most institutional-software vendors price on assets-under-management (often 10–40 bps of AUM), which means a year of portfolio growth turns into a six-figure bill from your software vendor. AOS doesn't do that. The base bundle is a flat monthly fee. Add-ons are flat monthly fees. Larger Owners pay more because they (a) cross the 25-building or 15-active-capital-project beta cap and need a higher tier, (b) carry multiple OpCos or JVs and add the per-EIN line on Accounting & AP, (c) want the Compliance Pro depth for lien rights and insurance renewal. Each of those is a real workload we're servicing — not a percentage of your top line.

Same model as the GC side — see AI usage & credit budgets above. Owners typically run lighter on credits than GCs do (less invoice parsing, less voice-log work). The included 2M credits / month covers most Owner workflows: pay-app review, broker-quote review for insurance renewals, board-packet draft summarization, and occasional vendor document parsing.

Annual will save roughly 10–12% compared to monthly. There's no auto-renew lock-in: you can switch to monthly or cancel at any renewal with 30 days notice. We don't keep a customer who doesn't want to be one.

Yes. We import buildings, leases (with all escalator structures), vendors, active capital projects, GC relationships, and entity / chart-of-accounts structure via XLSX templates as part of every onboarding. Larger pilots get help pulling open AP, in-flight pay apps from each GC, active subcontracts at the GC level, pending TIA obligations, and pending lien rights from your prior system as part of the implementation.

US-based managed cloud (Ohio region) with daily backups and encryption at rest. AOS is SOC 2-aligned and the security questionnaire is available on request. IP addresses and user agents on external portals (your GCs, board, investors) are stored only as secure one-way hashes — never as raw values.

It is, when you're working on a project hosted by an owner or GC who's already on AOS. Your CA team signs in as external users via one-click links — no account creation, no seat fees. That path doesn't change. The paid A/E tier is for firms who want to run AOS as their own operating system, across every project — including the ones where the owner or GC isn't on AOS. You get the firm-wide dashboard, time tracking, phase billing, project profitability, and the CA workflow working from your tenant outward — not borrowed from someone else's.

Three reasons firms move from the free external-user path to a paid tenant: (1) your principals want one screen showing every project the firm is engaged on, regardless of which owner / GC platform each runs on; (2) you want time tracking, phase billing, and project profitability on the same record as the CA workflow; (3) you want your own contract management, license tracking, and E&O renewal calendar instead of inheriting whatever the GC's compliance module looks like. Most small firms (under 8 staff) stay on the free path; firms above ~10 staff with 6+ concurrent projects usually move to paid.

The $600 base includes 5 internal seats — typically your principal, two project architects, a project engineer or specifier, and your contract admin / billing person. Additional seats are $50 / user / month. External users are never billable: consultants you sub-contract to (MEP, structural, civil), your owner-side counterparts, the GC's PMs, and any outsourced CA support sign in via secure one-click links and don't count against your seat total.

Any project your firm has an active fee on — design, CA, or both. Closed projects (final payment received, file archived) don't count. If you're chasing a project but haven't signed yet, it doesn't count. Projects on hold for more than 90 days drop off automatically (you can reactivate any time). If you're running more than 20 active projects, talk to us — we're sizing larger firm pilots case-by-case during beta.

Standard AIA fee structure baked in: SD / DD / CD / BN / CA phases with budget hours and budget fee per phase. Staff log time against project + phase from any device; PMs see burn-down per phase in real time. Invoice generation is one-click — pulls hours through the fee schedule, applies your billing rates (with or without multipliers), produces an AIA-formatted invoice (or your firm's own template). T&M and not-to-exceed projects supported. Reimbursable expenses linked. The Time Tracking & Billing add-on is where this lives.

Two paths. (1) If you're paying them as 1099 vendors, they live as external consultants in your tenant — they upload deliverables to the project record via a tokenized portal, you pay them through the Accounting & AP add-on. They don't count as seats. (2) If a consultant team is large enough to want their own AOS tenant, they get one and you bridge tenants — same pattern as the Owner↔GC bridge. Either way, your CA workflow stays inside your tenant.

Yes. Outsourced finance staff typically count as a single internal seat. They get the same access as your in-house accountant. Audit trail records who did what across every entry.

One screen across every active project your firm is engaged on. RFI SLA breaches surface in red, submittals about to age out in amber, pay apps queued for certification in the action column, design issues with site photos pinned by project. Sortable by principal-in-charge, by phase, by client, by fee remaining. Time burn-down per phase shown next to each project. The "what's burning at our firm right now" question becomes a single dashboard, not a Friday status meeting.

Disciplines are first-class. Each project can have multiple disciplines engaged with separate fee structures and separate phase plans. Time tracking and billing roll up at the firm level but stay separable for partnership P&L. If you operate disciplines as separate EINs / OpCos, add the Accounting & AP add-on for multi-EIN consolidation.

Yes, in the Compliance Pro (A/E) add-on. Per-person professional license tracking with state, registration number, expiry, CEU credits, and renewal alerts at 90 / 60 / 30 / 7 days. Firm-level E&O / professional liability insurance auto-renewal with broker RFQ. COI distribution to owners. Stamping authority (who's the registered architect / engineer on which project, with NCARB / NCEES record sync) tracked at the project level.

Closed beta runs Jun 14 → Jul 13, 2026 (invite-only, free). Open beta runs Jul 13 → Dec 14, 2026 for new signups; existing beta tenants keep running through Dec 31. GA opens Jan 1, 2027. Every beta tenant keeps the beta rate (base + seats + add-ons) for two years from Jul 13, 2026 (through Jul 13, 2028). At that point you roll to then-current GA pricing with 90 days notice and the option to leave clean.

You win either way. The beta-cohort guarantee: if GA pricing for the same bundle (base + seats + add-ons) comes in lower than your locked beta rate, you automatically drop to 10% below the GA rate for the rest of your lock window. We'll never have a beta tenant paying more than 90% of what a new customer pays for the same scope.

Same model as the other tabs — see AI usage & credit budgets. A/E firms typically use AI for spec parsing, submittal review acceleration, drawing markup OCR, and meeting-minute summarization. The included 2M credits / month covers a typical firm's monthly load.

Yes. We import projects, phases, fee schedules, clients, staff, time-tracking history (last 13 months), open invoices, and active consultant subcontracts via XLSX templates as part of onboarding. Larger firm pilots get help pulling open WIP, license records, and contact CRM data from your prior system.

US-based managed cloud (Ohio region) with daily backups and encryption at rest. AOS is SOC 2-aligned and the security questionnaire is available on request. IP addresses and user agents on external portals (consultants, clients, contractors) are stored only as secure one-way hashes — never as raw values.