Dashboard: Dashboard · market grid: _MARKET-PROBLEM-MAP · opportunity lens: _OPPORTUNITY-LENS · cross-competitor: _CROSS-COMPETITOR · tone exemplar: raken/dossier · format exemplar: _micro-entrants/cohort
This is a scan, not a teardown of five tools clustered in the downstream/adjacent bands of the grid — material tracking (18), programme/production (9-10), and O&M/handover/golden-thread (17). None of them competes for our wedge (money-recovery, area 15) or our moat (cross-firm historical cost, area 21). They matter to us for a different reason: two of them sit on exactly the data a delay or disruption claim needs as evidence. Sablono’s production actuals-vs-plan is the schedule-slippage record a delay claim is built on; Matrak’s material-delivery and install tracking is the late-/out-of-sequence-delivery record a disruption claim is built on. The other three (Zutec, Operance, Catenda Hub) are lifecycle/handover plumbing — relevant context, and three of the five are UK/EU, which fits our UK mid-market focus, but they are off our line.
This note establishes, per tool: what it builds, who buys it, region, openness, its AI (shipped vs announced), where it sits on the 21-area grid, and its distance to our claims layer. It deliberately does not run the deep 14-section dossier treatment — these are tier-B/C adjacents.
Per-tool mini-profiles
Matrak — material tracking + AI takeoff (Australia)
Matrak tracks construction materials from manufacture through logistics to on-site installation, with QR-code item tracking mapped directly onto project drawings and BIM models — a “single source of truth” for the supply chain spanning head contractors, manufacturers, suppliers, logistics and installers. It has pushed up-funnel into estimating with AI Takeoff (auto-reads plans, identifies products, generates BOQs for tenders) and added Digi, an agentic AI assistant that proactively monitors projects and emails team/suppliers to head off delays. Pricing is published and transactional — tiered by items tracked: Single-Use $745/mo (4,000 items), Starter $1,640/mo (6,000), Medium $3,200/mo (12,000, adds API), Enterprise custom; billed annually. It has a public API and named integrations (Procore, Autodesk Construction Cloud, SAP, Power BI, dRofus, Ynomia), is Australian (Matrak Industries Pty Ltd; ~$2.9M raised Apr 2024, G&M Capital + ex-Aconex chairman Simon Yencken, expanding into China), and its own review snippets cite “reduction in disputes regarding progress claims” — i.e. its delivery/install record is already used as progress-claim evidence. Relevant to us as a data source for disruption claims, not as a competitor.
Sablono — production / programme execution (Germany; UK-heavy)
Sablono is a “construction execution platform” for large, complex, multi-trade projects: it imports the master schedule (from Primavera P6, Asta Powerproject, MS Project, Excel, bim+), turns summary tasks into a deliverables tree, then tracks real-time progress and QA against it via mobile QR scanning — actual-vs-plan visibility, lean-style handovers between trades, and quality audit trails. Buyers are construction managers, quantity surveyors, quality teams and project-controls specialists at enterprise/mid-market contractors and renewables firms. Three packages — Track (progress), Trace (+QA/sign-off), Flow (enterprise, unlimited) — with project/activity caps (5 projects, 10k activities/project on the lower tiers); pricing is quote-only and enterprise deals can exceed $30k/month. It is German (Sablono GmbH) but visibly UK-focused (Morgan Sindall, Domis, FT Construction case studies; German/Spanish locales too); has an API and bidirectional schedule sync. AI is thin — only a website assessment chatbot; no shipped product AI found. Of all five, Sablono holds the single most claim-relevant dataset: time-stamped actual-vs-plan production progress is the backbone evidence of a delay/extension-of-time claim. Strong candidate data source for delay claims; QS buyer overlaps ours.
Zutec — handover / golden-thread / quality + defects (Ireland/UK)
Zutec is a building-lifecycle data platform organised in four module groups: Document Management (CDE, technical submittals, RFI, site diary), Quality Management (Part L compliance, QA inspections, snagging & defect management, temporary works), Handover Management (digital handover, O&M manuals, Gateway 3, fire & emergency files, digital asset register) and Asset Management (cladding remediation, fire-door audits, high-risk-building compliance). Buyers are contractors, housebuilders, developers, asset owners and BTR/housing-association operators; it leans hard into UK Building Safety Act / golden-thread compliance and is UK/Ireland-based (Zutec Inc. (Ireland) Ltd; the “Zutec Field” iOS app rates 3.5 on 11 GB ratings — small, mixed). Its AI, “Building AI,” is described as turning static building data into operational value but is not detailed — announced/vague, not a demonstrably shipped LLM feature. Pricing and API specifics are not public. Its data (defects, QA, site diaries) could in principle support a quality/rework dispute, but the product is built for compliance handover, not money recovery. Adjacent lifecycle plumbing; off our line.
Operance — asset / O&M handover, golden thread (UK)
Operance is a UK building-information platform centred on digital handover and the golden thread for the Building Safety Act: contractors assemble O&M manuals and asset data (uploading IFC models, COBie spreadsheets, data templates per ISO 19650), and building owners/operators/occupiers then search, share and maintain that data live — including via an FM mobile app. It is sold to contractors, building owners and consultants, and bundles services (BIM consultancy, digital-transformation, in-house O&M tooling) around the software. It describes itself as “AI-powered” for data management/search but gives no specifics — vague AI, nothing concretely shipped surfaced. Pricing and funding are not public; the real domain is operance.app (app-store pulls under “Operance” returned unrelated apps, so no store rating is asserted). Pure handover/O&M; furthest of the five from a claims signal.
Catenda Hub (formerly Bimsync) — open-BIM coordination + CDE (Norway/EU)
Catenda Hub (rebranded from Bimsync) is an openBIM collaboration platform / common data environment: a high-performance IFC web viewer, model coordination, BCF-based issue management, document management with ISO 19650 version control, and a strong public API with 40+ integrations (Revit, ArchiCAD, Navisworks, Teams, SharePoint, Power BI). Buyers are AEC professionals — architects, engineers, project managers — coordinating models across firms; its differentiator is open standards (no vendor lock-in) and that API. It is Norwegian/EU. AI (“Catenda AI”) is referenced as a separate offering but no clearly-shipped LLM feature was confirmed (recent release notes are openBIM/document features, not AI). Pricing is not public. This is coordination/design-side tooling; its issue/coordination data is upstream of, not direct evidence for, a commercial claim. BIM-coordination context; off our line.
Comparison
| Tool | Builds | Buyer | Region | AI angle | Feeds our claims layer? | Read |
|---|---|---|---|---|---|---|
| Matrak | Material tracking (mfr→install) + AI takeoff + supply-chain agent | Head contractors, mfrs, suppliers, installers | Australia (→China) | AI Takeoff (BOQ from plans) + Digi agent shipped; “Matrak AI” legacy-doc reader announced/limited rollout | Yes — delivery/out-of-sequence-install record = disruption evidence; reviews already cite progress-claim dispute reduction | Data source, not competitor |
| Sablono | Programme/production execution; actual-vs-plan + QA on imported schedule | CM, QS, project controls, quality | Germany (UK-heavy) | Website chatbot only; no shipped product AI | Yes (strongest) — time-stamped actual-vs-plan = delay/EoT evidence backbone | Data source; QS buyer overlaps ours |
| Zutec | Handover/golden-thread + quality/defects + asset compliance | Contractors, housebuilders, developers, asset owners | Ireland/UK | ”Building AI” — announced/vague | Weak — defects/QA could back a rework dispute, but built for compliance handover | Adjacent plumbing; off line |
| Operance | Digital O&M handover, golden thread, FM app (BSA) | Contractors, building owners, consultants | UK | ”AI-powered” — vague, nothing concrete | No — pure handover/O&M | Adjacent; furthest from claims |
| Catenda Hub (Bimsync) | OpenBIM CDE: IFC viewer, BCF issues, coordination, strong API | Architects, engineers, PMs (AEC) | Norway/EU | ”Catenda AI” referenced; no clear shipped LLM feature | No — coordination data is upstream of, not evidence for, a claim | BIM context; off line |
What this category tells us
- Two of the five produce data we would consume as claim evidence — and they are the two worth watching. Sablono’s time-stamped actual-vs-plan production progress is the literal evidence base of a delay / extension-of-time claim (area 15 input); Matrak’s material delivery and out-of-sequence install tracking is disruption evidence (late/wrong-order deliveries that derail labour productivity). These are inputs to our wedge, not competitors for it. Sablono is the more valuable of the two because it is schedule-anchored and sells to the QS / project-controls buyer we also target.
- None of the five moves toward the money. Every one stops at tracking, coordination or compliant handover. Matrak’s agent (Digi) emails to prevent delays and its reviews note fewer progress-claim disputes — but it never assembles, quantifies or recovers an entitlement. No tool here generates a delay narrative, quantifies disruption, or reuses historical cost. The recovery step is as empty in this band as the cross-competitor set found it everywhere else (highest area-15 score in the whole field is still only Procore 70; these five are all ≤25).
- The UK/EU angle is real and favourable to us. Sablono (German, UK-heavy case studies), Zutec (Ireland/UK), Operance (UK) and Catenda (Norway/EU) are all European — three of them sell directly into the UK contractor/handover market we focus on. That means the schedule- and delivery-evidence data we would want to consume is being captured in our target geography, and at least one host (Sablono) already serves the QS buyer.
- AI here is mostly talk, with one genuine exception. Sablono, Zutec, Operance and Catenda show vague “AI-powered” / “Building AI” / chatbot claims with little or nothing demonstrably shipped — a wide talk-vs-ship gap. Only Matrak has shipped real AI (AI Takeoff producing BOQs, the Digi monitoring agent), with a legacy-document reader in limited rollout. Notably Matrak’s AI points up-funnel into estimating/takeoff (area 2) and operations, not toward claims — consistent with the field-wide pattern that everyone reaches for capture/coordination AI and no one reaches for the recovery layer.
- Distance-to-wedge is uniform: adjacent, consumable, not contested. None is a build-alongside host in the Raken/Fieldwire sense (those own daily-log/RFI capture); these own programme, materials and handover. The right posture is data-partner / input-source for Sablono and Matrak, and context only for Zutec, Operance and Catenda. No GO targets, no head-on fights — these strengthen the case that the claims-recovery layer above them is unoccupied.
Sources and method
Light scan per the brief (exa web + app-store via _research/pull.py, plus vendor product/pricing pages). Per-tool raw under raw_<slug>/raw/ (exa_answer, exa_search, app-store search/app/reviews, youtube). Vendor pages: matrak.com (+ /pricing, China/AI blog), sablono.com (+ pricing, schedule-import blog), zutec.com, operance.app, catenda Hub. App-store identity confirmed for Matrak (Matrak Industries Pty Ltd, AU), Sablono (Sablono GmbH, DE), Zutec (“Zutec Field”, Zutec Inc. (Ireland) Ltd) — store ratings are tiny and noted as such; Operance and Catenda/Bimsync app-store matches were unrelated apps (CNotes/iD Mobile; BIM360/BIMx) and are NOT cited. No Capterra/G2 browser scrape run (per brief). Discipline: no absence-claim asserted without a check — “AI vague/not shipped” reflects what the public surface showed, not a definitive absence; “feeds claims” reflects data type, not a built feature.