Roadmap — Kanopi · Common Ground Data Room

The 2026 posture, locked

Through 2026, Kanopi runs an integration roadmap, not a public launch.

This is a deliberate choice, made in May 2026 and held since. "Launch" implies any contractor can sign up and self-serve; the product is not there, and pretending otherwise would burn the credibility the calibration numbers earn. What Kanopi actually does this year is connect: integration conversations across the construction software stack, a small beta cohort of contractors on free bids, and calibration depth. The public call to action is integration-partner inquiries, not sign-ups.

How the build got here

April 2026

Engine charter and positioning approved. The platform architecture is set and the load-bearing line ("Kanopi gives you your answer") is locked.

April 2026

First fully autonomous bids. Plan PDF to assembled bid with no human in the loop, two to four minutes each. The anchor calibration run lands within 7.1% of actual built cost.

May 2026

Multi-track rate architecture set. Six tracks with anchor doctrine, variance bands, and intake protocols; the anchor-protection rule is written down.

May 2026

Posture locked. Integration roadmap through 2026; the word "launch" is retired from all public copy.

June 2026

Platform expansion and unified brand. Architecture, design, and takeoff phases join estimating as one chained platform; Kanopi Design and Kanopi Estimate consolidate under one name.

June 2026

This data room. The productization read moves onto a shared working surface under Common Ground.

2026 integration targets

The roadmap motion runs across five categories of the construction stack, in each case feeding off documents and data the builder already has:

Takeoff and plan tools — read the same plan sets, return calibrated pricing.
Document management — pull plan revisions and sub quotes from where they already live.
Accounting — actual-cost data flowing back is what deepens calibration; this is the highest-value integration class for the library.
Scheduling — duration-tied rates connect bid math to the build calendar.
Bid presentation — calibrated numbers rendered in whatever format the client relationship needs.

Engineering runway before self-serve

Stated plainly, because the posture depends on being honest about it:

Takeoff verification rebuild: three-pass checks on quantity aggregation, hardened beyond the current stack.
Rate decomposition: splitting blended dollars-per-square-foot rates into material, labor, equipment, and sub markup components.
A queryable rate database fed directly from quote documents, which unblocks labor-parity calibration on the panelized track.
A second built, firm-cost anchor per track. The single-anchor risk is the most important open item in this entire data room.
App productization: file upload, per-organization auth isolation, billing, per-bid share tokens, and an intake wizard.

The structural decision we are holding open

Three structures are on the table for what Kanopi becomes. We are deliberately not choosing yet.

Structure ABootstrap

Keep building inside Common Ground

The practice funds the build; every live bid deepens calibration. Our risk: slower engineering runway. Our upside: full ownership of an asset whose value compounds with every project.

We'd take this when: the beta cohort and integration motion can run on practice cash flow. This is the default.

Structure BCapitalize

Productize with outside capital

Raise against the calibration proof to buy the self-serve runway faster. Our risk: selling equity before the second anchor track makes the data story bulletproof. Our upside: speed into a market with no calibrated incumbent.

We'd take this when: a second track is anchored and beta contractors are converting.

Structure CEmbed

Partner with an incumbent platform

License or embed the calibration engine inside an established platform's distribution. Our risk: the engine becomes a feature of someone else's product. Our upside: distribution we could not build alone, and the integration posture already points this direction.

We'd take this when: an integration conversation matures into something structural on terms that protect the library.

Our lean

Bootstrap through the 2026 integration year. Revisit capital when a second anchor track is calibrated and beta contractors are live. Nothing about the current cash position forces a worse decision earlier, and the calibration data only gets more valuable.

Open questions we are tracking

Which track earns the second anchor first: the next custom-residential close-out, or holding for a multifamily comp that retires the provisional hotel anchor.
How aggressively to gate engine-run costs during heavy bidding months while the beta is free.
Whether the design phase gets its own pipeline status track or stays folded into the bid pipeline until volume justifies it.
When the brand-package and entity workstreams should land relative to the first paying beta cohort.

Market

Back to

Overview