AI operating system for construction companies

Run the company. Keep every decision.

Sara runs operations, Taylor reads the drawings and builds the estimate, Emma builds and manages your subcontractor network. They connect to the files and systems you already use — Drive, Gmail, Calendar, Notion, your project folders — and work together inside one construction workspace. Every project is scoped and priced in writing before we start. You approve anything that leaves the building.

Book a project review ↗See how it works

Sample data

ADDENDUM 02 RECEIVED · TAYLOR READINGWorking

Rockland Mixed-Use · 38 Units

Public work · prevailing wage · bid due in 11 days

OverviewFilesEstimateSubcontractorsActivity

Addendum 02 — newTaylor: "Changed the electrical scope — reissuing as Rev 2."

Working

SubcontractorsEmma: 7 invited · 3 quotes in · 2 chasing · 1 COI outstanding

Verified

Approve bid invitation to 4 electrical subsSara: "Drafted. Nothing sends without you."

Needs you

General contractors

Bid more work without adding estimating headcount.

Remodelers & custom builders

Estimates and subs that keep pace with change orders.

Specialty contractors

Your niche, your units, your production rates — learned once.

GCs bidding public work

Prevailing wage, addenda and bid forms handled by the book.

The crew

Three agents. One team.

Taylor

Estimating · drawings · specs

Takes the full bid package — drawings, specs, addenda, wage schedules, bid forms. Performs takeoffs, finds conflicts, builds labour, material and sub pricing. Produces an estimate with every assumption and source shown.

Never invents a price. Says UNKNOWN when information is missing and always shows the logic.

Sara

Construction COO · your main interface

Understands the whole company. Delegates estimating to Taylor and coordination to Emma, catches problems between them, and brings you only the decisions that need you.

Never claims something was completed unless verified. Never makes the owner's decision.

Emma

Subcontractor & project coordination

Knows your niche, geography, job size and buyout target. Finds subs, sends invitations with the right files, follows up, collects quotes, COIs, W-9s and compliance docs, levels scope against Taylor's estimate. Remembers who performs.

Never lets a dependency go unnamed.

Behind them, several models check each other's work. You only ever deal with three.

How it works

Six steps to a project that runs itself.

Project review

A real call about one real project. You bring the drawings; we walk through exactly what the crew would do with them.

Output: a written walkthrough of your project.

Control: you pick the project; nothing is connected yet.

Scope and one set price

We return scope and one set price, in writing, for that project. Not a plan, not a tier — a document you can hold us to.

Output: a signed scope, price in writing.

Control: price moves only if scope moves.

Connect your files

Drive, Gmail, Calendar, Notion, your project folders. The crew works inside the tools you already use.

Output: a connected workspace, nothing moved.

Control: nothing is moved or replaced. Read access first.

Taylor reads the package

Drawings, specs, addenda, wage schedules, bid forms. Takeoffs, conflicts, pricing — every assumption and source shown.

Output: an estimate with its logic attached.

Control: Taylor says UNKNOWN rather than guessing.

Emma builds the sub list

Bid invitations with the right files, follow-ups, quotes, COIs, W-9s — levelled against Taylor's estimate.

Output: a levelled bid table per trade.

Control: nothing goes to a sub without your approval.

Sara runs it

She watches both, catches what falls between them, and brings you a short queue of the decisions that need you.

Output: a Monday report and an approvals queue.

Control: she brings you only the decisions that need you. You sign. She doesn't.

The work

What you actually get.

The project review

Sample data

Intake summary

Rockland Mixed-Use · 38 UnitsPublic work, prevailing wage · bid due in 11 days

PackageDrawing set (142 sheets), specs, Addendum 01–02, wage schedule, bid form

On it todayOwner + one PM

Pain named on the callEstimating bottleneck, sub follow-up

What the crew would do with it → walked through live

A real call about one real project. No connection, no commitment — a walkthrough.

Scoped and priced

Sample data

Scope document · in writing

What Taylor doesTakeoffs, estimate Rev 1, conflict log

What Emma doesSub list, invitations, quote collection

What stays with youEvery approval, every send, the signature

One set priceAgreed before work starts

Price moves only if scope moves. That sentence is in the document.

Live in your workspace

Sample data

Project page

Estimate Rev 2

Working

Sub quotes · electrical

Waiting on

Bid form draft

Verified

Approve invitation · 4 subs

Needs you

The project page the crew and you share — files, estimate, subs, approvals.

Ongoing operations

Reported every Monday.

After the first project, the crew stays on under a separate monthly arrangement. We host it, monitor it, add your next projects, and stay responsible for it working.

Sample data

Monday report — week of Mar 9

0Projects active

0Estimate issued

0Quotes collected

0Waiting on you

0Waiting on subs

Waiting on subs: Hudson Feeder Co. (quote), Valley Air & Pipe (COI), Ramapo Rebar (W-9), Orangetown Pour (quote)

Reported, not verified: Addendum 03 rumoured per architect's office — unconfirmed.

Proof

Proof, not logos.

One real project, walked through

A public-work bid, name withheld. Every number below comes from the record.

Metric slot — sheets read, from the record

Metric slot — conflicts flagged, from the record

Metric slot — days from package to estimate

The rules, stated as guarantees

"Sara never claims something was completed unless verified. Never makes the owner's decision."

"Taylor never invents a price. Says UNKNOWN when information is missing and always shows the logic."

"Emma never lets a dependency go unnamed."

How the crew catches its own mistakes

Every estimate line, sub quote and claim is cross-checked before it reaches you. When two sources disagree — a spec section against a drawing sheet, a quote against a levelled scope — the item is flagged CONFLICT and held, not smoothed over. Anything the crew was told but hasn't confirmed stays marked REPORTED — NOT VERIFIED until it's checked against the document itself.

What we connect to

The systems the crew works inside.

Keep your tools. Nothing is moved or replaced — read access first, and you approve anything that leaves.

Connected todayNext Next — future tense only, nothing reads as liveIcons are each system's own mark, monochrome. Hover to pause.

Google DriveTaylor reads the drawing set, specs and addenda from your project folder. Read access first.

GmailEmma drafts bid invitations and follow-ups; nothing sends until you approve.

Google CalendarSara holds the bid due date, COI expiries and quote promises against the week.

Google WorkspaceThe estimate, scope document and Monday report land as files you own.

NotionProject notes and the sub network read and updated in place.

Procore NextEstimate lines will post to the job cost.

Buildertrend NextSchedules and daily logs will sync both ways.

QuickBooks NextApproved sub invoices will flow to the books.

Sage NextJob cost codes will map to estimate divisions.

Bluebeam NextMarkups will read into Taylor's takeoff.

PlanSwift / STACK NextExisting takeoff files will import as Taylor's starting point.

DocuSign NextApproved contracts will route for signature.

Microsoft 365 NextOutlook and OneDrive will work the way Gmail and Drive do today.

Dropbox NextProject folders will read in place.

Excel NextEstimates will export to your own sheets.

Google DriveTaylor reads the drawing set, specs and addenda from your project folder. Read access first.

GmailEmma drafts bid invitations and follow-ups; nothing sends until you approve.

Google CalendarSara holds the bid due date, COI expiries and quote promises against the week.

Google WorkspaceThe estimate, scope document and Monday report land as files you own.

NotionProject notes and the sub network read and updated in place.

Procore NextEstimate lines will post to the job cost.

Buildertrend NextSchedules and daily logs will sync both ways.

QuickBooks NextApproved sub invoices will flow to the books.

Sage NextJob cost codes will map to estimate divisions.

Bluebeam NextMarkups will read into Taylor's takeoff.

PlanSwift / STACK NextExisting takeoff files will import as Taylor's starting point.

DocuSign NextApproved contracts will route for signature.

Microsoft 365 NextOutlook and OneDrive will work the way Gmail and Drive do today.

Dropbox NextProject folders will read in place.

Excel NextEstimates will export to your own sheets.

Don't see yours? Bring it to the Project Review.

Full list, and what each one does →

FAQ

Asked on every call.

What does it cost? +

Every engagement starts with a Project Review — a real call about one real project. We return scope and one set price, in writing, for that project. Price moves only if scope moves. After the first project the crew stays on under a separate monthly arrangement covering hosting, monitoring and new projects. There is no price list because there is no standard project.

How long until the crew is live on my project? +

The Project Review happens this week. Scope and price come back in writing within days. Once you approve, the crew is reading your package the same week. One real project sets the pace — nothing is connected until you pick it.

Who sees my drawings and my numbers? +

You, the people you name, and the crew working your project. Access is scoped per project — a company that engages us for one job does not open its whole Drive. We start with read access, and anything that leaves the workspace waits on your approval. Your files stay in your systems; nothing is moved or copied out to be trained on.

Does the AI send anything without me? +

No. Emma drafts bid invitations and follow-ups; Taylor drafts requests to the architect; Sara drafts the Monday report. Every send sits in your approvals queue until you approve, edit or send it back. The crew drafts. You decide.

Can it stamp drawings or act as my architect? +

No. Taylor reads drawings and specs, performs takeoffs, flags conflicts and, later, helps with markups and constructability review. Licensed, stamped design responsibility stays with your architect or engineer of record. Design-assist is not licensed design, and we keep that line visible.

What happens when Taylor doesn't have enough information? +

The line reads UNKNOWN, with the reason and who has the missing item — "fixture schedule not in the set, request from architect." The estimate total is withheld until every UNKNOWN is resolved. Taylor never fills a gap with a guess.

What if I already tried AI or software and it didn't stick? +

Most of it asked you to move your work into a new tool and then left you to run it. We do the opposite: the crew works inside the folders, inbox and calendar you already use, and we stay responsible for it working under the ongoing arrangement. If a piece isn't earning its place after the first project, that comes out in the Monday report and we change it.

Do I have to move off Drive / Gmail / my folders? +

No. Keep your tools. The crew connects to Drive, Gmail, Calendar, Workspace and Notion with read access first, and works inside them. Nothing is migrated.

Start here

Book a project review.

Bring one project. We'll show you what the crew would do with it.

Book a project review ↗

Calendar embed — placeholder · Cal.com / Calendly · 30 min · "Project Review"
Until the calendar is live, the form on the book page reaches a real person the same day.