The system,
in the order
the job runs.
Bid, buyout, build, bill. Eight desks, each one live today, each one carrying a rule about what it will not do. Nothing on this page is roadmap.
Estimating
From the drawing set to a scope somebody can price.
Structured takeoff pulled from the drawings, carrying what each trade actually cost you on the last job. It assembles quantities, scope lines and the documents a bid must include.
Buyout
The board that shows what you have actually bought.
Every trade as one of three states: bought, chosen but not awarded, or still an estimate. The middle column is the one nobody has: money you have committed to in conversation and never papered.
Purchasing
A purchase order your sub can sign without an account.
POs generate on your letterhead, send from your address, and are signed on a page at your web address. The packet — COI requirements, tax status, contacts, scope — assembles itself. Nobody your sub deals with learns who built the software.
Compliance
Certificates chased, filed, and read strictly.
COIs are requested, tracked against the purchase order they belong to, and filed automatically when they arrive. Expiries are watched. In New York, every deadline the system tracks carries the statute it comes from.
Submittals & RFIs
Your architect stamps through a link.
Transmittals assemble from the register and go out for review. The architect opens a link, marks up, and returns — no seat, no password, no procurement conversation. RFIs run the same door, with cost and time impact recorded as the answerer’s own claim.
Billing
AIA G702 and G703, off the real schedule of values.
Applications for payment build from the schedule of values and the period’s actual completion, with retainage and previous certificates carried correctly. The continuation sheet is generated, not retyped.
WIP
Where the job actually stands financially.
Work-in-progress with over-billing and under-billing reported separately, forecasts that append rather than overwrite, and a contract sum that only moves on executed paper.
Field
Answers on a phone, one-handed, outdoors.
A superintendent looks up who owns a scope and gets the answer with its contract state attached. The daily log is append-only and works offline, syncing when the site gets signal.
And underneath all of it
It is yours, not ours.
Every desk above runs under your company’s name, on your domain, sending from your address, printing on your letterhead. Your subcontractors, your architect and your owner deal with you. The studio that built it appears nowhere in front of them — not in a footer, not in a from-address, not in the URL they click.
The data underneath is yours too, on a database that can be handed to you. That is the difference between a system you own and a seat you rent, and it is the whole reason this company exists.