Construction-tech competitor landscape — synthesis and build brief

Dashboard: Dashboard · method: _RESEARCH-METHOD · grid: _MARKET-PROBLEM-MAP · lens: _OPPORTUNITY-LENS · matrix + heatmap: _CROSS-COMPETITOR · packet: _DOSSIER-PACKET.

This is the synthesis of the deep-dossier program (37 competitors, 2026-06-16). It supersedes the competitive read in the earlier broad market pass, competitor-landscape-report (Stream 1), which keeps the wider-market detail — UX teardown, pricing tables, positioning, success metrics — that this report does not repeat.

Purpose: turn the competitor research into one decision. It states what the market already builds, where the whitespace is, who would threaten us and how, and what we should build first. It is written for someone who has not read the individual dossiers; the evidence sits in those (linked throughout) and in _CROSS-COMPETITOR.

What was covered

About sixty competitors, scored on the same two instruments so the whole field is comparable: the 21-area coverage grid (_MARKET-PROBLEM-MAP) and the four-axis opportunity lens (_OPPORTUNITY-LENS). Twelve got full decision briefs — Raken, Procore, Fieldwire, PlanRadar, Document Crunch, OpenSpace, Trunk Tools, Civils.ai, Kreo, Pype, Sablono, BuildPass. Three ultra-early tools were grouped in one cohort note. The wider field was scanned across seven category notes in _landscape/ — reality capture, estimating/takeoff, field-daily, platforms/system-of-record, materials/handover, and — added after the first pass to test the thesis head-on — the dedicated claims/delay/forensic field and the commercial/QS field our buyer already uses. Reviews were segmented from real Capterra RSC data where it existed (Raken 248, Procore 100-sample, Fieldwire 98, Kreo 25, Pype 24, Sablono 9); the rest leaned on vendor sites, exa, funding press and walkthrough video.

The market in one picture

Reading the coverage heatmap by the six map clusters:

The core finding: one empty column, one contested-but-unmoated column

A direct hunt of the dedicated claims/delay field (_landscape/claims-delay/note) sharpened the earlier read. The honest position is not “two empty columns” — it is more precise and more durable than that:

• Cross-firm historical-cost benchmarking (area 21) is genuinely empty — by everyone. The closest are Kreo and Togal (“learns from your past projects”) and STACK (via 1build’s bought-in catalog): all single-firm or a licensed reference list, never a compounding cross-firm loop. Even the dedicated claims tools score ≤10 here. This is the un-threatened core of the moat.
• Change/claims/entitlement recovery (area 15) is NOT empty — it is contested by a real but sub-scale cohort. The general tools stop at the doorway (Procore’s and Trunk Tools’ agents flag and coordinate; Document Crunch and ContraVault generate notices). But a dedicated cohort goes further: nPlan and Nodes & Links predict schedule risk; SmartPM, ClaimLogic, Steelray and Systech analyse delay; and four real products — Magra, Masin AI, ClaimDD/ClaimEOT and Delay Claim Builder — genuinely assemble cost + time + causation into a quantified, recoverable claim (Eichleay/Hudson overhead, measured-mile disruption, time-impact). Magra (~$36K/yr, change-order + claim, owner and contractor) is the nearest direct competitor, running our exact notice-to-recovery motion. So the absolute “no one recovers money” claim is retired — corrected against evidence.

What keeps the wedge real and defensible after that correction: every one of these recovery tools is a 2024-25 micro-entrant — unfunded or seed-stage, several single-person — and not one holds the cross-firm historical-cost loop (21). Nor does any tool assemble the full chain: free field-capture feeding a structured Commercial Event, feeding recovery, compounding into a cross-firm cost/claim-outcome moat, for the UK commercial/QS buyer. The recovery tools are point solutions you feed by hand; the best evidence feed (Sablono) stops defensively at the doorway; the closest-motion field tool (BuildPass) stops before claims and is not in the UK. The pieces exist separately; the integrated loop and the data moat do not.

Five structural patterns (each evidenced, not asserted)

1. Mostly read, but a real recovery cohort now exists. The bulk of the field — Document Crunch, Trunk Tools, Civils.ai, Pype, the platforms — reads, extracts and coordinates and stops at the doorway to the claim. The exception, found only by hunting the claims field directly, is a small dedicated cohort (Magra, Masin AI, ClaimDD/EOT, Delay Claim Builder) that does cross into quantified recovery. “No one recovers money” is retired. What none of them owns is the field-capture feed and the cross-firm data loop; they are manual-input point tools, 2024-25, unfunded or seed-stage.
2. The variation↔entitlement seam is a real market structure, not a missing feature. Every QS commercial suite (Causeway, Eque2, RedSky, RIB Candy, Planyard, Payapps) runs the money workflow up to variation valuation, CVR and final account — then stops. Delay/disruption entitlement (prolongation, measured-mile disruption, overhead, time-impact → quantum) is sold by a separate vendor category (the forensic/claims engines) and never bundled in. Our wedge sits exactly on that seam — where the market has split into two products and left the join empty.
3. Absorption is the default exit, proven four times. Pype → Autodesk, Payapps → Autodesk, Fonn → The Access Group, Disperse → OpenSpace (plus Trunk Tools’ Procore API revoked while Procore shipped a rival agent). An independent tool built on a platform’s data and buyer is rented land.
4. The evidence supply chain for a claims layer already exists. Tools to consume, not fight: Sablono (the best — time-stamped actual-vs-plan on imported P6/Asta/MSP, public reporting API, QS buyer, UK/EU — but pitched defensively, stops at the doorway), Matrak (delivery/disruption), DroneDeploy and Doxel (visual progress as payment-claim proof), the open-API field tools (Raken/Fieldwire/PlanRadar). Several are UK/EU — our geography.
5. Cross-firm cost is empty by design — and that is the tell. Even the brand-new AI benchmarking entrants (Gauge, Rate QS, BenchIt) are explicitly single-firm; Rate QS markets “your private data, not cross-firm” as a selling point. Vendors are actively building benchmarking and still none pools across firms — demand proven, gap unfilled, because cross-firm pooling is a trust/structural problem, not a modelling one. That is exactly what makes area 21 the durable moat for whoever solves the trust problem. (Platform AI — Autodesk Construction IQ, Trimble’s agents, Oracle’s Advisor for Safety — is real but pointed at risk/extraction, not this.)

Target board (sorted for our play)

What we should build (the wedge)

The position that is simultaneously high-prize, unoccupied, and defensible against bundling:

• The job: turn the field and commercial record into recovered money — structured variations, change-order and delay/disruption evidence, entitlement narratives — then, over time, price and risk the next job against cross-firm historical cost. Point tools now exist for pieces of the first half (Magra quantifies, Gather Insights detects events and drafts notices); what no one closes is the whole loop — capture → structured Commercial Event → entitlement quantum → recovery → a cross-firm cost/outcome loop — and area 21 (cross-firm cost) is unoccupied by anyone.
• The buyer: the commercial / QS / project-controls office — a buyer the platforms do not sell to (they sell to ops/IT/the GC’s PM). This avoids the head-on fight and the channel the distribution-owners own.
• The entry: a free, narrow capture point (the lesson from the field-daily tier: capture is now free and earns no premium alone). Free capture must feed the paid money layer; value accrues up-funnel. First demo = the Field Evidence flow; first paid wedge = Tender Intelligence; durable moat = Historical Cost Intelligence.
• The build posture: alongside the open-API field tools, not on a single platform’s API (which can be revoked — see Trunk Tools). Ingest from many sources so no one host can cut us off.
• The moat is the cross-firm data loop, not the model or the workflow. The recovery workflow is now copyable — Magra and others have it. What is not copyable, and is empty by design, is cross-firm historical-cost and claim-outcome data (area 21): every benchmarking entrant keeps its data single-firm (Rate QS sells “your private data, not cross-firm” as a feature), because pooling across firms is a trust and structural problem, not a modelling one. Whoever earns the trust to pool it — accountability, multi-year proprietary outcomes, the QS buyer’s confidence in an adversarial setting (the Document Crunch founder’s point) — owns the compounding asset a distribution-owner cannot quickly assemble and the point tools cannot reach. The workflow gets us in; the data loop keeps us.

Risks and the walk-away test

• A distribution-owner bundles the wedge. The standing risk; already realised twice (Pype→Autodesk, Payapps→Autodesk). The QS incumbents (Causeway, Eque2, RedSky, RIB Candy) own the desk and the data and are legacy-slow today, but could bolt on an AI claims/benchmarking layer. Mitigation: own a P&L line (recovery) and a data loop (cross-firm outcomes) they cannot quickly assemble, for a buyer they under-serve.
• An incumbent points captive-data AI at cost/claims. Oracle’s Advisor for Safety shows the mechanism exists. Watch Trimble’s Viewpoint Finance Assistant and Procore’s agent roadmap; if either ships a real entitlement/recovery product, the window narrows.
• A nearest competitor closes the loop first. The live three: Gather Insights adds quantum (it already does NEC/JCT compensation-event detection + notices for our exact UK QS buyer — best-positioned to take the money half next); Magra adds a capture feed or reaches the UK (it already quantifies); BuildPass enters the UK/commercial (it already has capture + agentic AI). Each holds one or two pieces; the danger is one of them assembling the rest before us.
• What would make us walk away: any of the above shipping the integrated loop with cross-firm benchmarking before our data loop locks. Today none pools cost across firms — Rate QS even sells the opposite — so area 21, the moat, is still open. That is the single fact to keep re-checking.

Recommended next moves

1. Stop researching the field — it is mapped. The two target columns are empty and the supply chain is identified.
2. Build the Field Evidence demo (workstream 4) — the free capture point that produces the Commercial Event record, designed from the start to feed recovery, ingesting from open-API hosts rather than living on one.
3. Spec the Tender Intelligence wedge (the first paid step) against Civils.ai and ContraVault as the only (shallow, early) tender-side AI — read tender docs, but carry it through to the bid-decision and, later, price against history.
4. Stand up Historical Cost Intelligence as the moat — the cross-firm data loop nobody has; start accumulating from the first projects.
5. Feed the partner deck (workstream 2) from this report and the target board.

Sources

Per-competitor evidence in dossiers/<slug>/dossier.md and the five _landscape/*/note.md scans; quantified scoring and both heatmap tables in _CROSS-COMPETITOR; method, limits and the no-absence-claims discipline in _RESEARCH-METHOD.