ACRE ACRE Operational Architecture
Forty Years Building · Operational Architecture

A complete operation. Run light.

Most of what goes wrong on a build isn't a building problem — it's an information problem. The information existed; nothing caught it.

A custom build generates more than any one person can hold. It buries you:

I'm a fractional COO for custom builders. I install the complete operation I ran on $750M of work, and make it run light enough for your shop to carry.

The ACRE Operating System You hold the judgment. Notion is the operation written down: the instructions the system runs on and the record you own. Cowork (Claude) is the AI processor that runs your Notion SOPs. JobTread runs the money, the build, plans, documents and schedule. Input flows in, through the engine, and decisions surface out to you. HUMAN · YOU The judgment THE ENGINE ACRE INSTALLS · YOUR STACK, YOUR DATA The operation, written down The instructions the system runs on — and the record you own. The processor Runs your Notion SOPs. Codes, routes, drafts, surfaces the brief. The money & the build Budget, commitments, pay apps, billing, plans, documents, schedule. IN Receipts, photos, field notes, emails, meetings THROUGH THE ENGINE Captured, coded, cross-linked, drafted — nothing dropped OUT Decisions surfaced to you. You make the call. Configurators set up a tool. Coaches sell you hours. ACRE installs the operation — and you own it.
40 yearsat the top of the market
$750Mbuilt & developed
Nationwidecustom builders, $1M–$50M
A-01 · The Two Factories

You run two factories. Only one of them shows up on the schedule.

Your Physical Factory

What you can see.

Concrete, framing, finishes. Visible, measurable, owned by trades. When something goes wrong here, it's obvious within hours.

Your Information Factory

What you can't.

RFIs, change orders, pay apps, selections, approvals, photos, daily logs, owner emails. Equally real, equally expensive when it stalls, and no one owns it. So it runs incomplete: the critical work tracked, the rest in somebody's head. Usually yours.

Every project is built twice, first as information, then as the physical building. The systems you have now are like paying someone to do long division when you could just hand them a calculator.

“AI is the pocket calculator for project information.” The calculator, the PC, the smartphone, each one went from novelty to “how did we ever work without it.” AI is the next one.

A-02 · Where the Information Factory Breaks

Rework, overruns, disputes, slipped schedules, the operational failures you already know. These are the things an incomplete operation drops, and a complete one is built to catch.

The $15,000 fireplace. A builder installs a fireplace insert, clean work, no defects. At the walkthrough, the owner asks where the blower is. There isn't one. He's certain he asked for it; maybe he did, in a conversation that never made it to paper. The insert is in the wall, the job is done, and the fix runs fifteen thousand dollars. The crew didn't fail. The building didn't fail. The operation failed, the information existed, and nothing caught it. That's the most expensive category of problem in residential construction, and it never shows up in a cost code.

01

Pay apps stack up

G702/G703 sit in inboxes. The information exists; it's just unprocessed. Retainage tracked in someone's head.

02

Change orders go un-priced

The field finds something, and weeks pass before the information reaches the owner with a price and a signature line.

03

Owner approvals go verbal-then-forgotten

No party-of-record trail. Disputes start exactly where the record ends.

04

The schedule slips quietly

Tasks fall through because nothing ties them back to the information that would flag them.

05

Your PM is at capacity

Because they're the processor, until they aren't. There's no admin hire available at any price.

06

Organizational memory walks out the door

Whatever your office knows lives in three people's heads. One quits and the information leaves with them.

A-03 · The Information Flow

Eight steps every record passes through.

Every record, a receipt, a field note, a change order, an owner email, runs through the same loop. Skip one step and you have information debt. Run all eight and you have leverage. This is the loop the engine runs: Notion holds the rules, the AI processor does the work, JobTread carries the dollars.

01CaptureReceipts, photos, field notes, emails, meetings.
02ProcessRead, validate, code, cross-link.
03OrganizeFiled by job, division, commitment.
04RetrieveAny question, any time, any device.
05CommunicateOwner recap, sub email, internal nudge, drafted.
06DecideSurface what needs a call. I make the call.
07ExecutePO issued, CO drafted, approval sent.
08LearnEvery record makes the next one faster. The system compounds.
A-04 · Why Me

I built this for myself first.

I'm Marty Kribs. I spent four decades developing and building at the very top of the market, 3 Creek Ranch, Aspen Valley Ranch, and the resort-class work where an operational mistake isn't tolerated.

For most of those years I wondered how we could make the administrative side of a build easier. What I was missing for forty years wasn't a better project management tool, it was a way to actually process the information those tools generate. AI is the first technology I've seen that does it.

So I built this operating system for my own development work first, and I run my projects on it today. You're not buying a generic playbook applied to a trade I had to learn on your job. You're buying the way a $750M builder runs the work.

40
Years building
$750M
Built & developed
Aspen
Jackson
Resort-class
Marty Kribs, founder of ACRE

Marty Kribs · Founder, ACRE

Aspen Valley Ranch
Aspen Valley Ranch · Aspen, CO
Amangani, Jackson Hole
Amangani · Jackson Hole, WY
3 Creek Ranch, Jackson Hole
3 Creek Ranch · Jackson Hole, WY
A-05 · Built For

Built for the builder whose PM is the bottleneck.

The best custom builders

High-end residential, $1M–$50M annual revenue. You sell trust and craftsmanship, not throughput.

PM at capacity

Already maxed out, and there's no admin hire available at any price you'd consider paying.

Office on heroics

Usually yours. You're the bottleneck for every decision worth more than $500.

Built for builders on JobTread, or ready to move to it. If you're committed to a different platform, I'm not your guy, and the diagnostic will say so.

If two of those sound like you, the diagnostic will pay for itself.

A-06 · The Operating System

What runs on the engine.

Most shops don't run an operation, they run a pile of tools and hold the gaps together by hand. What I install is one operation with four parts, and the part that matters is yours to keep.

The engine is three named tools, and the order matters. Your operation is written down in Notion, the SOPs and databases that are both the instructions the system follows and the record you own. Cowork reads the field's raw input and runs those SOPs. JobTread carries the money and the build. Change the SOP and the system's behavior changes, which is the part a competitor can't copy: it's your operation, encoded in a workspace you hold, not a vendor's defaults.

AI is not replacing your judgment. AI is replacing your information processing. Your team stays in charge of leadership, tradeoffs, relationships, and accountability, the system stays in charge of the loop.

Complete-system rigor used to require a back office you can't hire, coordinators chasing paper so the builders could build. That's the part that changed. AI runs the admin layer, so a five-person shop can run a fifty-person system. You get the rigor without the overhead.

01

Receipts & Invoices

Snap or forward, files itself, coded to the job, auto-linked to the PO that backs it.

02

Sub Pay Apps

G702/G703 lands structured. Lien-waiver and COI gates checked before anything's marked paid.

03

Change Orders

Field condition? The PCO drafts at the moment of discovery, photo and field language attached.

04

Client Approvals

Requests drafted; status only moves with the client party-of-record. Nothing slips.

05

Buyout & Commitments

RFQ out, bids structured, award recorded, commitment and SOV created on award.

06

The Daily Digest

Each morning: what moved, who owes what, what's overdue, what needs a decision. One page.

Each module runs on the same engine. That's why adding the next one is faster than installing the first, and why the operation gets sharper every month instead of staler.

A-07 · The Fractional COO

The system runs the loop. I run the system, and make the calls that cost money.

A calculator doesn't tell you what to compute or whether the answer is right. A person does.

Here's what most builders have been sold: tools. A tool for the schedule, a tool for the books, a tool for the field. Each one automates the work inside itself, and does it well. But the failures on a build don't live inside a tool. They live in the gaps between them, between the owner's phone call and the purchase order. No tool you can buy closes those gaps, because closing them isn't a feature. It's an operation, and an operation is built on judgment about how the work actually runs.

So I don't hand you another tool to evaluate and stitch in. I install the whole operation, your SOPs in Notion, the AI processor that runs them, JobTread underneath the money and the build, wired into one loop that doesn't drop things. It's the same stack I run my own developments on, proven before it ever reaches your jobsite.

Plenty of people will set up JobTread for you. What they can't bring is forty years at the top of the market deciding how it gets set up, which cost codes, which gates, which sign-offs, what the field actually does versus what the manual says. That judgment is the product. The software is just where it lives. You're not buying a configuration. You're buying the way a $750M builder runs the work, installed, and yours to keep.

The system clears the desk. I make the calls. Forty years of judgment in the room for the decisions that move the number on a build, the COO you can't hire and can't afford full-time, for a fraction, only as long as you want me.

This is the part most fractional advisors won't say out loud: a working operation is a relationship, not a binder. I stay on as your operator so the office stops carrying it alone, and so each new month the system gets sharper, not staler.

What the fractional role looks like

  • I own the operating rhythm, weekly review, monthly numbers, the office runs on a cadence instead of crisis.
  • Senior judgment on the calls that cost money, change orders, owner conflicts, schedule trade-offs, buyout decisions.
  • The information system is mine to run, I keep the loop tight, I add the next module, I train your people into it.
  • I'm the operator your PM can pick up the phone and call, on the days the wheels are coming off.
  • Cancel anytime. The system stays running either way.
A-08 · The Split

What stays yours. What becomes mine.

I don't take over your company. I take the operating layer off your desk so you stay on building and clients, and so the business doesn't route every decision through you.

 YouACRE
Vision & growthOwns,
The build & the craftOwns,
The client relationshipOwnsI prep reporting
Weekly operating rhythm, I run it
Selections → buyout → billing spine, I run it
Owner updates, digests, reportingYou sendI draft
SOPs & accountabilityApprovesI build & run
Issues surfaced & followed through, I own
The information systemYou own itI run it
A-09 · What You Keep

The system is yours. Stop anytime and it keeps running.

Every record lives in Notion, a workspace you own, visible, searchable, traceable to its source. The money reconciles in JobTread, in your account, not mine. AI assists; people review the financials, the decisions, and anything client-facing. No black box, no lock-in, no losing access to your own data.

Every other fractional COO leaves you notes that fade. I leave you an operating system, your operation written down, running, and improving, that keeps working whether I'm in the chair or not.

Most operations are warehouses built for human pickers, every shelf and aisle assumes a person walks the floor and carries it by hand. What I install is the redesign: an operation built so information moves the way it can move now, and so when your work, your team, or the tools change again, the operation bends instead of breaks. That adaptability is the edge, not any one piece of software.

A-10 · The Whitepaper

Complete by Design.

Why most construction failures are operations failures in disguise, what a complete project-management system actually looks like, and how AI finally makes that rigor affordable for a small shop.

Email it to yourself. No follow-up unless you ask for one.

We won't share your address. You'll get the PDF on the next page.

A-11 · The Engagement

One small step. Not one big leap.

You start with a fixed, low-risk diagnostic. Everything past it is scoped from what we find, quoted to your operation, never off a menu.

Step 01 · This Week

The Diagnostic

I map exactly where your operation leaks time, margin, and control, and hand you the prioritized fix list. It's yours to keep either way, whether or not we go further.

$2,500 · fixed
Step 02 · By a Date

The Install

I stand up one high-pain spine, running clean, your team trained on it, on a system you own. Fixed scope, fixed fee, quoted from the diagnostic.

Scoped post-diagnostic
Step 03 · Ongoing

Fractional COO

I run and sharpen the operation part-time; the system carries the load; we review the numbers monthly. Scoped to your business. Cancel anytime.

Monthly · cancel anytime
A-12 · Start Here

Start with the diagnostic.

We'll spend the time on your bottleneck, not on a demo. You leave with a clear read on where your operation leaks, and a fix list that's yours to keep, whatever you decide next.