From estimating tool to preconstruction platform
Until mid-2026, Kanopi was an estimating engine. The platform decision widened it to the full preconstruction chain: architecture, design, takeoff, and estimating, each phase feeding the next.
The four phases chain deliberately. Architecture produces the drawing set and the open-decisions register. Design reads the architecture package and produces a locked finishes schedule and openings count. Takeoff reads the design package and produces verified, provenance-tagged quantities. Estimating reads the takeoff and produces the bid. Each handoff has a load-bearing seam, and a broken seam blocks the downstream phase: no pricing without verified quantities, no takeoff without a locked finishes schedule.
Architecture
Engagement classification, plan ingest, the open-decisions register, and the engineering-team thicket, captured in a structured package.
Design
Renderings, inspiration sequences, design options, and a finishes and materials schedule stubbed in the exact units takeoff consumes.
Takeoff
Quantity extraction with provenance tags on every line and three-pass verification before anything is allowed to be priced.
Estimating
The engine anchors quantities against the rate library and renders the bid. The part that has been live the longest.
Design and Estimate, one brand
The June 2026 brand decision: Kanopi is the single umbrella for both halves of the platform. Kanopi Design is the agentic architecture system, AI agent teams producing permit-ready plan sets under a human orchestrator, with licensed-architect review and stamp. Kanopi Estimate is the bidding engine. The connective tissue is the model-direct takeoff: the building model feeds the estimate, which makes "design it, price it" one integrated motion rather than two bolted-together tools.
Design is proven internally only. The agent teams produced the permit-ready model for one of our own buildings, caught and fixed their own errors in review, and our internal estimate of the savings against a conventional outside-architect engagement is roughly $250K. That is one building, ours, with no third-party Design client yet. We treat Design as roadmap and Estimate as the product with live proof.
The app that wraps the engine
The sellable wrapper is a multi-tenant web app organized around five surfaces, all of which already run the practice's own work today:
- Intake. Upload plans, answer a structured question set, pick the contract type. The intake protocol that disciplines our own bids becomes the onboarding flow.
- Storage. Plan sets, photos, sub bids, permits, and correspondence per project, in one place the estimate can see.
- Bid builder. The engine auto-fills; the operator reviews line by line, drills into any number's provenance, and overrides with a recorded reason.
- Pipeline. Status board, dollars-per-square-foot benchmarks, and win/loss data that feeds back into calibration.
- Sharing. Per-bid links with read-only and vendor-redacted views.
The honest runway to self-serve: the app is roughly 70% of the way there. File-upload UI, per-organization auth isolation, and billing are the remaining engineering blocks, alongside the deeper engine work listed on the Roadmap. This is why the 2026 posture is integration-led rather than self-serve-led.
The productization workstreams, and who delivers
Six workstreams carry Kanopi from internal tool to product. Each has an owner among the Common Ground principals.
| Workstream | What it is | Owner |
|---|---|---|
| Calibration depth | Add built, firm-cost anchors per track; retire the single-anchor risk. | Jesse Fowler |
| Beta cohort | Seed contractors onto the free-bid beta and capture their calibration data. | Jesse Fowler + Robby Prochnow |
| Integration partnerships | The 2026 roadmap motion across the construction software stack. | Jesse Fowler + Robby Prochnow |
| Brand package | A real identity to replace the placeholder wordmark. | Jimmy Khounlavong |
| Capital structure | If and when outside capital is warranted. | Alex Prince |
| Entity and IP hygiene | Legal entity formation and IP assignment. | Nick Scavio |
Jesse Fowler
Built and operates the engine on live bids. Owns calibration, the estimating doctrine, and the product direction.
Alex Prince
Owns the capital path if the bootstrap-versus-raise decision tips toward a raise.
Jimmy Khounlavong
Owns the real brand package and the product's visual identity when it graduates from placeholder.
Robby Prochnow
The agentic engine behind the outreach and integration motion. Beta-cohort recruitment, partner pipelines, and the CRM machinery that runs them are agentic systems Robby architects, the same class of system that powers the takeoff engine itself. On a product whose core claim is autonomous AI doing skilled work, this seat carries unusual weight.
Nick Scavio
Entity formation, IP assignment, and the contract frameworks the bids ride on.
Our lean is to bootstrap through 2026 (see Roadmap). If outside capital becomes the right structure, the capital raise sits under Prince Capital and the licensed broker-dealer platform to ensure compliance. Prince Capital is a FINRA-licensed private investment advisory firm and licensed broker dealer; Common Ground stays on the operating side.