How we work
You don’t need an AI strategy. You need to know where the business is losing time, what depends too heavily on one person, and which problem is worth fixing first.
Book a call2–3 weeks — $4,000–6,000
Find out what’s actually costing you.
We interview your team, map how the work moves today, and identify where better systems create real leverage. You get a prioritized roadmap and a scoped proposal with a number.
What we need from you: four to eight hours across your PMs, estimator, and office, plus access to how you currently produce documents.
What you get: the current-state map, the roadmap, and a scoped build proposal. Yours whether you build with us or not.
About a month — $12,000–15,000
Configure the first priority.
We collect your documents, map the workflows, configure the system around your standards, review it against real jobs, and hand it over with training. One or two purpose-built workflows are included in scope.
What we need from you: your templates, contract language, pricing references, procedures, and a few hours a week from whoever owns the process.
What you get: a working system, your operating knowledge documented, and your team trained on it.
From $2,000
Access, kept current.
Your team uses the system. We keep it running and matched to your business as procedures, contracts, and standards change. New workflows get added as you need them.
Priced by annual construction volume and what’s configured.
Already know what you need?
You don’t have to start with an audit. If the problem is clear, we scope the build.
Book a scoping callTypically 4–8 hours across Phase 1 from each key person involved in the scoped workflows.
That may include the owner or operations lead, a PM who runs the work daily, the estimator when pricing is relevant, and the person handling the administrative work.
That last perspective often reveals where the time is really going.
Depending on what’s in scope, we may ask for:
One point of contact who can keep documents, access, and decisions moving.
Construction OS already contains the architecture for recurring construction work — the documents, the scopes, the pricing conventions, the change procedures, the operating knowledge. We configure it around your company’s documents, rules, terminology, and judgment.
You are not paying us to discover what a change order is.
Not every construction problem fits an existing Construction OS capability. When the business case is real, we design and build a system around a specific workflow, process, or operating need.
The goal is not custom software for its own sake. We build where the problem is worth solving, and where the work can become part of a stronger reusable system over time.
See how purpose-built work gets scopedIf the software you already have solves the problem well, use it.
If judgment is what creates the value, keep the judgment.
Build only where the business case is real.
Your information stays yours. The documented operating knowledge, workflow maps, procedures, and inventories we create from it are yours to keep and use. Reusable Construction OS components, methods, and underlying system IP remain ours unless the agreement says otherwise.
Everything you share during an engagement is treated as confidential.
Construction OS is built by people who have worked both sides of the problem. I ran projects at a $50 million contractor as a licensed Massachusetts Construction Supervisor, and spent twelve years leading enterprise product at Fidelity, Jabra, and Optimizely. Ava Yurasits builds the engineering, agents, and configuration layer.
The technology matters. Understanding the operation matters more.