Step 01 / 14Open
AOS / An interactive walkthrough

What must be true
for a contracting company
to actually work?

Not a product tour. A walkthrough of the logic — built from first principles — behind AOS, the contractor operating system. Every contracting company runs on five essential functions. Remove any one and the company stops working. That's the whole argument. This page proves it.

Begin the walkthrough
begin
/ 01What First Principles Means

Don't copy the guy down the road.
Strip it to what must be true.

Most contracting companies are run by analogy — habits inherited from the trade, the mentor, the last boss. AOS was not built by analogy. It was built by asking, out loud, what a contracting company actually requires in order to work.

"Boil things down to the most fundamental truths, then reason up from there."

— the method, applied to a $20M GC

  1. 01

    Strip the thing to what must be true.

    First-principles thinking ignores how an industry has always been run. It asks: what must be physically, financially, and humanly true for this kind of business to exist, deliver, get paid, and grow?

  2. 02

    Reject reasoning by analogy.

    Most contractors run by copying the guy down the road. That bakes in his blind spots — and inflation moves faster than tradition. Analogy compounds errors; first principles compounds clarity.

  3. 03

    Rebuild from the irreducible parts.

    Once you have the must-be-true list, you have the company's operating spine. Everything else — software, dashboards, meetings, hires — exists to serve those parts. Not the other way around.

/ 02The Derivation

For a contracting company to exist,
deliver, get paid, and grow —
what must be true?

Walk the elimination. Each row is a category of work that no other category can absorb. Marketing can't fix bad estimating. Estimating can't fix bad delivery. Delivery can't fix bad cash. Cash can't fix bad leadership. That is what means.

01Market & Deals
Must be trueQualified buyers must keep asking you for a number.
Fails without itNo input. No company. Pipeline collapses the moment one GC slows down.
02Estimating & Contracts
Must be trueThe numbers and the terms must permit profit before signature.
Fails without itEvery sale is a loss multiplier. Scaling speed = scaling damage.
03Project Delivery
Must be trueScope must convert to installed work safely, on time, on budget.
Fails without itPromises never become product. Reputation and margin die together.
04Cash & Financial Control
Must be trueYou must survive the timing gap between outflows and inflows.
Fails without itInsolvency on a profitable book. You die solvent on paper.
05Leadership & People
Must be trueThe machine must run and improve without the owner being the bottleneck.
Fails without itYou have a job, not a company. Nothing transfers. Nothing sells.
Why we pair · Market & Deals

A market without deals is hobbyist. Deals without a market is luck. They are inseparable.

Why we pair · Estimating & Contracts

An estimate without a contract is theater. A contract without an estimate is gambling.

Takeaway

Five categories. Each one mandatory. None substitutable.

/ 03The Essential Five

Forced by reality,
not by opinion.

Here are the five, in dependency order. Click any card to open the , the KPIs that name them, and the AOS tools that own them.

Read the dependency
  • No deals → no business
  • Bad estimating / contracts → scaling losses
  • Bad delivery → write-offs and lawsuits
  • No cash control → suffocation
  • Weak leadership → no scale, no value
/ 04The Irreducibility Proof

Remove any one.
The company stops working.

Click an essential to remove it. The center shows what the company becomes the instant that function is missing. The other four cannot compensate. That is the entire argument.

Irreducible Set · The Contracting Companyoperational
Operational

All five essentials intact. The company can run, deliver, get paid, and grow.

Takeaway

Five pillars. Pull one and the roof comes down — every time.

/ 05Designed vs Default

Every contractor already runs the five.
The only question is whether they were designed.

You can't opt out of the five. You can only choose whether they run by design or by accident. Accidental systems still produce output — they just produce it through choke points, write-offs, and the owner's nervous system. Toggle to see the same company in both states.

Default Contractor
state · default
  • 01
    Market & DealsRandom referrals and hope
  • 02
    Estimating & ContractsLast job plus ten percent
  • 03
    Project DeliveryHeroic supers, WhatsApp coordination
  • 04
    Cash & Financial ControlCall the GC and beg
  • 05
    Leadership & PeopleOwner as firefighter-in-chief
/ 06Therefore: AOS
Because

every contracting company is a system of five irreducible functions,

And because

when those functions run by default, they run through choke points,

Therefore

you need an operating system designed to cover all five, on purpose.

AOS is that operating system.

for each essential. tied to and meetings. One weekly cadence. The named, measured, and assigned — before they become write-offs.

What that looks like in practice
/ 07Inside Each Essential

Serves all five essentials. Relieves the choke points by naming a KPI and an owner for each — so issues surface in days, not quarters.

Each essential,
with its choke points
and its KPIs.

System 01

Market & Deals

Can you reliably get qualified opportunities?

If no one with money is asking you to price work, you do not have a contracting company. Marketing, for contractors, is the system that causes the right people to ask you for a number — on purpose, not by accident.

  • 01No defined ideal customer profile
  • 02Referral-only deal flow
  • 03Reactive bidding, never proactive positioning
  • 04No tracking of bid-hit by customer or project type
KPIs · Market Scorecard
Last 5 weeks
+22
11
Qualified Opportunities (wk)
+4
31%
Bid-Hit Rate
+12
$8.4M
Proposal Volume
-3
42%
Top Customer Concentration
/ 08AOS Command Center

Serves Leadership & People. Relieves the 'owner-as-firefighter' choke point — the whole company runs on one screen and one weekly cadence.

One hub for the
whole operating system.

live · all seats reporting
aos.command
Q4 · Wk 9
Backlog
+8.2% vs prior
$24.6M
GM at Award
+1.2pt vs prior
21.4%
AR Days
−6 days vs prior
58
CO > 30d
+$132K vs prior
$612K
W5
Qualified Opportunities
Sales · Goal ≥ 10
W5
11
W1
8
W2
11
W3
9
W4
12
W5
11
Bid-Hit Rate
Estimating · Goal ≥ 28%
W5
31
W1
26
W2
31
W3
29
W4
33
W5
31
GM at Award
Estimating · Goal ≥ 20%
W5
21.4
W1
19.8
W2
21.1
W3
20.4
W4
21.9
W5
21.4
Schedule Adherence
Ops · Goal ≥ 90%
W5
88
W1
84
W2
87
W3
86
W4
88
W5
88
AR Days
Finance · Goal ≤ 50
W5
58
W1
64
W2
62
W3
60
W4
59
W5
58
CO Aging > 30d
Ops · Goal $0
W5
612
W1
480
W2
510
W3
540
W4
580
W5
612
L10 Completion
Leadership · Goal 100%
W5
100
W1
100
W2
100
W3
92
W4
100
W5
100
SOP Adoption
Leadership · Goal ≥ 80%
W5
74
W1
63
W2
67
W3
70
W4
72
W5
74
/ 09SOP Builder

Serves Project Delivery. Relieves the 'tribal knowledge' choke point — a process leaves the owner's head and becomes a transferable asset.

SOPs are not
documents.
They're the OS.

Every AOS ships tied to a , a meeting, a KPI, and a handoff. Here's a real one: Pre-Job Planning.

SOP / PJP-01
Pre-Job Planning SOP
Owner
Project Executive
Cadence
Per job
Tied to
Delivery KPIs
SOP Stepper
Step 1 of 9
Field 01

Process Owner

Single accountable seat. Not a name — a seat.

Value
Project Executive
/ 10EOS Lineage

Lineage, not pitch. What AOS kept from EOS, and what it sharpened for contractors who run jobs, crews, and cash.

EOS gives structure.
AOS makes it
construction-specific.

isn't wrong. It's just generic. takes the same six components and wires them around the realities of jobs, crews, backlog, margin, and cash.

Vision
Contractor V/TO — backlog targets, margin targets, regional plan, org build-out
People
Accountability chart by construction seat — PE, PM, Super, Estimator, Finance
Data
Contractor scorecards — bid-hit, GM at award, schedule adherence, AR days, CO aging
Issues
L10 issues tied to real jobs, real subs, real change events — not abstract
Process
SOP Builder — pre-job planning, buy-out, change orders, billing, closeout
Traction
Weekly L10 cadence, quarterly rocks, to-dos tied to job-level outcomes

EOS is the lineage. AOS is the contractor implementation.

/ 11Upside Unlocked

Serves the whole business. When the five essentials are covered, the upside follows: predictable margin, low owner dependence, transferable value.

Cover the essentials.
Unlock the upside.

Organized systems compound into something a strategic buyer or PE firm can actually underwrite: predictable margin, clean books, full bench, transferable execution.

Margin
Predictable
Owner Dependence
Low
Reporting
Investor-grade
Scalability
Transferable
1

Chaotic Operator-Led

Stage 1 / 4

Owner is the system. Margins random. No transferable value.

2

Organized Operator-Led

Stage 2 / 4

Documented processes, but execution still routes through the owner.

3

System-Driven

Stage 3 / 4

Scorecards, SOPs, cadence. Owner steps out of daily firefighting.

4

Investable & Scalable

Stage 4 / 4

Predictable margin, full bench, clean books. PE-ready. Strategic-buyer-ready.

/ 12Quick Check

Before installing it —
does the logic hold?

Two quick checks. Remove any one essential and see what the company becomes. Then answer the question that follows.

Check 1 · Remove any essential
Check 2 · So what's the winning move?

If all five essentials are mandatory and none can substitute for another, what is the only thing that actually works?

Install the OS

You can keep running it on
memory, muscle, and meetings
that go nowhere.

Or you can install the operating system. Cover the five essentials. Run it weekly. Compound.

A
AOS · Contractor Operating System
Augmented EOS for contractorsBuilt for the field, the office, and the boardroom