Construction AI competitor landscape, UX teardown, pricing, sentiment, and strategy

📥 Stream 1 deliverable (GPT-5.5 Pro/Extended). Prompt: PROMPT-packet-1-competitor-research · context: packet-0-shared-base-context · feeds → PROMPT-packet-2-strategy-deck. Dashboard: Dashboard · findings: RESEARCH-FINDINGS-AND-DECISIONS.

Prepared: 16 June 2026
Scope: UK-style mid-market commercial contractor / fit-out / general contractor opportunity.
Working thesis tested: a Commercial Memory Layer that turns messy field/tender/project history into source-linked commercial events, evidence gaps, QS/PM actions, and reusable historical intelligence.

A. Executive summary

The blunt answer

There is no attractive wedge in “AI daily reports.” That market is already full of mobile field-reporting products, Procore/Autodesk/Trimble modules, and a growing tail of cheap voice-to-report apps. The user pain is real, but the category is too easy to copy, too likely to be bundled, and too hard to defend unless the output changes commercial behaviour.

There is also no sane first wedge in AI takeoff, BIM, AR, 360 reality capture, or golden-thread handover. Those markets are technically heavier, procurement-heavy, and already served by specialist products. They may become integration surfaces later, not the starting point.

The credible wedge is narrower and sharper:

Field evidence → Commercial Event → missing evidence prompts → QS/PM review → draft action → source-linked evidence pack → historical memory.

That is not the same as a diary. A diary says “what happened.” A Commercial Event says “what happened, why it may matter contractually/commercially, what proof exists, what proof is missing, who must act, and what should be reused next time.”

Market map

                         HIGH PLATFORM THREAT
              Procore AI | Autodesk Forma/ACC | Trimble + Document Crunch
                                   |
                                   |
HIGH CROWDING  --------------------+--------------------  HIGH SPECIALISM
Daily reports / mobile capture      |       Document risk / RFI / spec AI
Raken, PlanRadar, Fieldwire,        |       Trunk Tools, Document Crunch,
Procore Daily Log, BuildPass,       |       Pype/AutoSpecs, ContraVault,
voice-to-report apps                |       Civils.ai, DeadFront, Specbook
                                   |
                                   |
                         OUR CREDIBLE WEDGE
              Evidence-born commercial event memory layer
                                   |
                                   |
              Long-term extension: actual-cost / entitlement memory
              Rate QS, Zebel, ConWize, BCIS, RSMeans adjacency

What is crowded

1. Daily reporting / site diary capture is crowded. Raken, Procore Daily Log, PlanRadar, Fieldwire, BuildPass, ConstructionDailyReport.ai, Voice Log Pro, SiteLogs, EasySiteLog, and many local/mobile tools all cover some version of “capture notes/photos/weather/manpower and produce a report.” The newer voice tools are especially close to the proposed first demo if the demo is framed as “voice note to daily report.”

2. Project systems of record already cover formal RFIs, submittals, daily logs, observations, change orders, photos, cost, and dashboards. Procore, Autodesk Build/Forma, and Trimble ProjectSight are not lightweight, but they own the procurement conversation for many GCs.

3. AI document intelligence is heating quickly. Procore AI, Trunk Tools, Document Crunch/Trimble, Pype AutoSpecs, Civils.ai, ContraVault, DeadFront AI, and Specbook AI are all attacking specs, contracts, RFIs, submittals, tender packs, project Q&A, or risk review.

4. Takeoff and estimating AI is already noisy. Bluebeam, Kreo, Togal, STACK, PlanSwift Takeoff Boost, Beam AI, Civils.ai, and others compete on “faster first pass.” Users still do not trust fully automated quantities for contractual bids without human review.

5. Reality capture and progress tracking are specialist-led. OpenSpace, Buildots, DroneDeploy, XYZ Reality, and HoloBuilder provide visual records, AI progress tracking, or AR validation. They are too operationally heavy for this first wedge, but they may become evidence sources.

Where there is still room

The gap is not capture. The gap is commercially meaningful interpretation with proof discipline.

Existing tools either:

• capture field data but leave QS/PM/commercial follow-through manual;
• manage formal workflows after someone has already decided to raise an RFI/change/notice;
• answer questions over documents but do not reliably create a field-born commercial event object;
• produce dashboards from stale or incomplete data;
• generate reports without proving entitlement, missing records, or money exposure.

The wedge should be positioned as:

        messy source material
 voice | photos | WhatsApp | email | Procore logs | delivery notes | programme | BoQ
                    |
                    v
              Commercial Event
  facts | source links | uncertainty | missing evidence | cost/schedule implication
                    |
                    v
       Human-reviewed commercial action pack
  confirmation email | RFI | variation note | notice prompt | claim-support pack
                    |
                    v
             historical commercial memory
  why we lost money | what evidence was missing | what rates/risks recur

What not to build

Do not build:

• a generic site diary app;
• a Procore clone;
• a generic dashboard;
• a chatbot over documents with no workflow ownership;
• automated takeoff / drawing measurement as the first wedge;
• a 360 capture / AR / progress-tracking product;
• a formal notice/claim generator that bypasses human approval;
• anything that asks the site manager to fill a second Procore.

Recommended wedge statement

“We don’t replace Procore or your current diary. We catch commercially relevant events at the point they happen, assemble the evidence, flag what is missing, and give the QS/PM a reviewable action pack before entitlement is lost.”

First demo recommendation

The fictional late partition-track delivery scenario is the right demo, but it must not look like “voice note → pretty diary.” It should look like:

1. Open magic link.
2. Record messy voice note.
3. Upload photos/files.
4. Answer only 1–3 targeted follow-ups.
5. Output a commercial event card, not just a report.
6. Show missing delivery note as a red evidence gap.
7. Draft a QS review action, not an automated claim.
8. Generate a source-linked evidence pack with transcript/photo/file provenance.
9. Export to email/PDF/Excel/Procore/SharePoint.

B. Competitor matrix

Legend: Threat level = High / Medium / Low for the proposed Commercial Memory Layer. Role = direct competitor, adjacent competitor, platform threat, integration partner, or learning reference.

C. UX teardown by workflow

1. Field capture

What the market already does

Raken is the strongest established field-daily-report UX reference. The field user enters work logs, notes, photos, time cards, checklists, equipment/material data, and can use voice-to-text. The office uses the web app for review, dashboards, reporting, and integrations. It is built for construction teams of 5 to 5,000 and explicitly separates field mobile capture from office web review.

ConstructionDailyReport.ai, Voice Log Pro, SiteLogs, and EasySiteLog show where the category is moving: tap record, speak, attach photos, auto weather, generate a clean report. These tools are dangerous to your demo only if the demo’s headline is “voice to report.” SiteLogs and EasySiteLog show the cheap end of the market. ConstructionDailyReport.ai shows the premium/industrial angle, including claim flags and claim diary.

PlanRadar and Fieldwire are more drawing/ticket/task-centric. Capture is usually tied to tickets, plans, tasks, forms, checklists, defects, or project-management objects. This is useful for structured construction management, but it is not as low-friction as a single voice-note capture flow.

Procore Daily Log / Autodesk Build / Trimble ProjectSight are system-of-record capture workflows. They are broad, configurable, and formally auditable, but they can be too heavy for an exhausted site manager at 17:30.

Field-user UX pattern

Best field UX pattern:

open link/app
   |
   v
press record / add photos
   |
   v
answer only missing critical facts
   |
   v
submit

Worst field UX pattern:

login -> choose project -> choose module -> choose form -> fill 20 fields -> upload photo
-> tag location -> tag trade -> select cost code -> submit -> fix validation errors

Screen inventory: field capture

2. Daily report generation

Daily report generation is already commoditized. Raken produces daily, super daily, manpower, project summary, and task reports. ConstructionDailyReport.ai, SiteLogs, Voice Log Pro, and EasySiteLog all convert voice/text/photos/weather into PDF-style reports. Procore, Autodesk, PlanRadar, and Fieldwire all export reports from structured project records.

The lesson: do not compete on report generation alone. Your diary draft should be a byproduct. The primary object should be the Commercial Event.

Recommended output hierarchy:

1. Commercial Event card       <-- primary
2. Missing evidence checklist  <-- primary
3. QS/PM action pack           <-- primary
4. Evidence pack               <-- primary
5. Daily diary draft           <-- secondary byproduct
6. Dashboard                   <-- secondary byproduct

3. Evidence and photo management

The market is good at storing photos. It is worse at converting photos into entitlement-ready evidence.

Raken / Procore / Autodesk / PlanRadar / Fieldwire manage photos inside daily logs, tasks, issues, and project records. OpenSpace / HoloBuilder / DroneDeploy / Buildots provide richer visual context and historical visual records. Matrak / Sablono provide object/activity status records that can support disputes around material delivery, progress, QA, or handover.

The gap is evidence reasoning:

Photo exists?                       Commodity.
Photo linked to event fact?          Less common.
Photo proves labour stood idle?      Rare.
Photo proves delivery time?          Only if timestamp/location/context are clear.
Photo plus delivery note missing?    Commercially useful.
Photo plus programme activity?       Strong.
Photo plus cost impact owner?        Where QS value begins.

Your evidence view should show:

• source type: voice transcript, photo, delivery note, email, programme, BoQ, RFI log;
• timestamp/date;
• who supplied it;
• extracted fact;
• confidence/uncertainty;
• linked commercial implication;
• missing evidence needed to strengthen the event.

4. Commercial / RFI / change workflows

Formal RFI/change workflows are not empty. Procore, Autodesk Build, Trimble ProjectSight, and Fieldwire Business Plus already support RFIs, submittals, change orders, notices, and/or budget/change workflows. OpenSpace can generate/link Procore RFIs from Field Notes with visual context. Autodesk Build can link RFIs to issues and potential change orders. Document Crunch/Trimble and Trunk Tools are moving AI into risk review, RFI/submittal automation, and source-cited answers.

The wedge is before formal workflow initiation:

Incumbent formal workflow:
Someone notices issue -> decides action -> creates RFI/change/notice in Procore/ACC

Our proposed workflow:
Messy site fact -> AI detects Commercial Event -> missing proof prompts -> QS/PM reviews
-> human-approved RFI/change/notice/email -> export to system of record

This is an important distinction. You are not replacing the RFI/change module. You are making sure commercially relevant events do not die in voice notes, WhatsApp, photos, memory, or a weak diary line.

5. Dashboard and admin review

Dashboards are everywhere and often distrusted if the underlying data is stale. Raken, Procore, Autodesk, PlanRadar, Sablono, Matrak, ConWize, and Zebel all show dashboards/status views.

The admin dashboard should therefore be narrow and evidence-led:

Avoid vanity dashboard metrics until source data is trusted.

6. Exports and integrations

Integrations are table stakes but should be pragmatic:

• Phase 1: PDF evidence pack, email draft, Excel/CSV event log, SharePoint folder export.
• Phase 2: Procore documents/photos/RFI/change-event export; Autodesk Docs/Build issue/RFI export; Raken/PlanRadar/Fieldwire import/export if partner requires.
• Phase 3: cost/ERP/estimating loop into tender and final-account memory.

Do not lead with “we integrate with everything.” Lead with “we create defensible event evidence and put it wherever your team already works.”

D. Pricing comparison

Prices are public only where vendors publish them. Quote-based enterprise pricing is common. Third-party pricing can be outdated or wrong; treat it as directional only.

E. User review and sentiment synthesis

Top recurring positive patterns

1. Field teams like tools that save obvious time immediately. Raken, SiteLogs, ConstructionDailyReport.ai, and EasySiteLog all sell on less typing and faster daily logs. Reviews for Raken repeatedly praise easy daily reports, photo uploads, and field-to-office communication.

2. Photo documentation is one of the clearest adoption hooks. Users like quickly attaching site photos to logs, tasks, tickets, or reports. The weakness is that photos become piles unless linked to a specific issue, event, time, location, and action.

3. Centralised project records improve meetings and reduce chasing. Raken reviews mention concise update meetings; PlanRadar/Fieldwire/Procore reviews often praise centralisation and visibility.

4. Mobile-first matters more than feature breadth for field adoption. Products that feel fast on a phone win the field. Products that require desktop admin or complex setup get complaints.

5. Good customer support/onboarding materially affects sentiment. Raken and BuildPass reviews frequently mention support as a positive; enterprise systems often live or die by implementation quality.

6. Formal systems of record are bought for control, auditability, and owner/GC requirements. Procore/Autodesk/Trimble are not loved by everyone, but they are bought because they consolidate workflows and create formal records.

7. AI document tools are valued when they reduce specialist drudge. Document Crunch users like AI checklists, plain-English risk summaries, and chat over contract documents. Trunk Tools sells time saved answering field questions from project documents.

8. Takeoff AI is valued as a first-pass accelerator, not a replacement for estimators. Users repeatedly say the estimator still owns scope, waste, rates, assumptions, and final numbers.

9. Reality capture has strong value where visual proof matters. OpenSpace/HoloBuilder/DroneDeploy/Buildots/XYZ help remote visibility, QA, progress, and dispute context, especially on complex projects.

10. Historical internal data is seen as more valuable than generic benchmark data. Reddit/QS/estimating discussions repeatedly point to internal rates, actual tenders, supplier/subcontractor quotes, and project-specific productivity as more useful than generic cost books.

Top recurring negative patterns

1. Procore and similar platforms are expensive and non-transparent. Pricing often depends on products and construction volume; users complain about high cost and renewal/audit concerns.

2. Adoption dies when field users are asked to do extra admin. Reddit discussions about Procore/ACC adoption repeatedly identify training, friction, double entry, and stale data as the reason tools fail.

3. Double entry is toxic. If accounting, estimating, Procore, Excel, SharePoint, and email all need updating, users will keep one tool current and let the others rot.

4. Dashboards become useless when data is stale. Office users want visibility, but field teams often do not update systems after long days. Once trust is lost, people go back to WhatsApp, email, and spreadsheets.

5. Mobile/offline/sync limitations matter on site. PlanRadar/Raken/Fieldwire reviews mention sync/offline/mobile limitations. Underground/poor-signal environments are especially harsh.

6. Setup and configuration are underestimated. Fieldwire, Raken, Procore, Autodesk, STACK, ConWize, Sablono, and Matrak all require some setup discipline. “No training required” is rarely true at scale.

7. AI trust is fragile. Construction users worry about hallucination, missed quantities, incomplete summaries, and AI-generated RFIs that create noise. Source citations and human review are non-negotiable.

8. Cloud tools can struggle with large jobs. Users complain about slowness in cloud estimating tools and large plan sets; PlanSwift users complain about legacy performance/memory issues.

9. Generic cost data is not enough for real bids. RSMeans/BCIS-type data can support benchmarking and early advice, but users still rely on local subcontractor quotes, supplier prices, and internal historical data.

10. Broad platforms feel stitched together. Users often describe Procore/Autodesk/Trimble ecosystems as powerful but clunky, with modules that do not always fit the way each team works.

Field-user vs office/admin/commercial-user sentiment

F. Strategic implications for the proposed product

What is already commoditized

1. Daily report generation. Many tools turn notes/photos/weather/manpower into PDFs.
2. Photo capture. Everyone supports photos.
3. Basic dashboards. Dashboards are expected and rarely defensible.
4. Generic document summarization. LLMs and platform AI are moving fast here.
5. AI first-pass takeoff. Plenty of tools promise speed; trust remains the bottleneck.
6. RFI/submittal formal workflow modules. Platforms already own this inside the system of record.

What is heating up

1. Platform AI agents. Procore’s 2026 AI agents and Autodesk/Trunk Tools integrations show where platforms are going.
2. Construction-specific document risk. Document Crunch/Trimble is the clearest sign that contract/risk intelligence is becoming a strategic category.
3. Source-cited project Q&A. Trunk Tools and Procore AI are pushing sourced answers across project documents.
4. AI submittal/RFI automation. Pype/AutoSpecs, Trunk Tools, Document Crunch Project Assist, and Procore agents are all attacking workflow drudge.
5. Visual action from reality capture. OpenSpace Field and integrations into Procore/Autodesk are moving from visual record to task/RFI/action creation.
6. Private historical cost intelligence. Rate QS, Zebel, ConWize, and contractor spreadsheet pain show a credible long-term path.

What is too hard or expensive to attack first

The credible wedge

The credible wedge is Commercial Event Memory, starting with field evidence and extending into tender/final-account memory.

Core object

Commercial Event
├── Facts
│   ├── what happened
│   ├── where
│   ├── when
│   ├── who was involved
│   └── programme / cost / trade context
├── Evidence
│   ├── voice transcript
│   ├── photos
│   ├── files
│   ├── emails / WhatsApp
│   ├── delivery notes
│   ├── programme extract
│   └── Procore/RFI/change logs
├── Missing evidence
│   ├── delivery note missing
│   ├── no instruction confirmation
│   ├── no labour allocation record
│   ├── no programme activity link
│   └── no cost impact owner
├── Commercial implication
│   ├── potential delay
│   ├── idle labour
│   ├── variation / compensation event candidate
│   ├── notice clock risk
│   └── uncertainty label
├── Human review
│   ├── QS owner
│   ├── PM owner
│   ├── status
│   └── approval history
└── Actions
    ├── confirmation email draft
    ├── RFI draft
    ├── variation note draft
    ├── evidence pack
    └── export history

Positioning against existing tools

What the first demo must explicitly avoid looking like

Do not show:

• “AI daily report summary” as the main reveal;
• a generic dashboard with charts but no evidence;
• an autonomous legal/claims bot;
• a chat interface that answers without source links;
• a Procore duplicate workflow;
• a 10-field mobile form;
• “AI thinks you should claim £X” without proof and human review.

Show instead:

Voice note: “Partition track turned up late…”
       |
       v
Commercial Event: Late material delivery causing drylining disruption
       |
       +-- evidence found: voice timestamp, photos, site metadata
       +-- evidence missing: delivery note, supplier ETA email, programme activity, labour standing-time record
       +-- commercial implication: potential delay / idle labour / variation review
       +-- uncertainty: delivery responsibility not proven yet
       |
       v
QS action pack: review, request missing delivery note, confirm instruction, draft email/RFI

Pilot hypothesis

The best pilot is not “use our tool for all diaries.” That is too broad and will fail adoption.

The pilot should be:

1. Select one live project or recently painful project.
2. Track only Commercial Events for 2–4 weeks.
3. Capture through site manager voice/photos plus PM/QS review.
4. Export action packs into existing systems.
5. Measure recovered/avoided exposure, evidence completeness, and time-to-action.

Suggested first partner ask

Ask for one real commercially painful event and the messy surrounding records:

• site diaries;
• Procore/ACC/Raken/PlanRadar logs if available;
• emails;
• WhatsApp messages;
• photos;
• delivery notes;
• programme extract;
• RFI log;
• variation/change log;
• cost impact or final account movement.

Then reconstruct:

1. what happened;
2. what evidence existed;
3. what evidence was missing;
4. what should have been flagged earlier;
5. what commercial action should have happened;
6. what money or entitlement may have been exposed;
7. how the product would catch it next time.

Success metrics for a serious pilot

Final strategic take

The company should not be “AI agents for construction.” That is vague and will get crushed by platforms. It should not be “voice daily reports.” That is already a feature and a cheap app category.

The defensible product is:

A commercial evidence and memory layer for contractors: capture field facts while they are fresh, prove what matters, force the missing-evidence conversation early, route human-approved commercial actions, and reuse the history to price and manage the next job better.

The proof in the partner meeting should be a working flow that feels almost trivial to the site manager and uncomfortably useful to the QS.

Source URLs used

Field reporting / daily diaries / voice tools

• Raken daily reports: https://www.rakenapp.com/features/daily-reports
• Raken request pricing: https://www.rakenapp.com/request-pricing
• Raken help: daily reports: https://help.rakenapp.com/en/articles/14465435-daily-reports-in-raken
• Raken Procore integration: https://help.rakenapp.com/en/articles/14447769-procore-integration-overview
• Raken Capterra reviews/pricing: https://www.capterra.com/p/153591/RAKEN/reviews/ ; https://www.capterra.com/p/153591/RAKEN/pricing/
• Raken G2: https://www.g2.com/products/raken/reviews
• Fieldwire pricing: https://www.fieldwire.com/pricing
• Fieldwire help pricing: https://help.fieldwire.com/hc/en-us/articles/360003823371-Fieldwire-Pricing-Plans
• Fieldwire RFIs: https://help.fieldwire.com/hc/en-us/articles/360058420652-RFIs-on-Fieldwire
• Fieldwire submittals: https://help.fieldwire.com/hc/en-us/articles/11939074744475-Submittals-on-Fieldwire
• Fieldwire reviews: https://www.capterra.com/p/154965/Fieldwire/reviews/ ; https://www.g2.com/products/fieldwire/reviews
• PlanRadar pricing UK: https://www.planradar.com/gb/pricing/
• PlanRadar site diary: https://www.planradar.com/gb/site-diary/ ; https://www.planradar.com/gb/create-site-diary/
• PlanRadar Capterra/G2: https://www.capterra.com/p/156698/PlanRadar/ ; https://www.g2.com/products/planradar/reviews
• BuildPass: https://buildpass.com.au ; https://help.buildpass.com.au/en/articles/14493624-what-is-site-diary ; https://www.capterra.com/p/266118/BuildPass/
• ConstructionDailyReport.ai: https://www.constructiondailyreport.ai/
• Voice Log Pro: https://www.voicelogpro.com/
• SiteLogs: https://sitelogs.io/
• EasySiteLog: https://www.easysitelog.com/
• ConstructionDailyReports pricing: https://www.constructiondailyreports.com/pricing

Platforms / systems of record

• Procore pricing: https://www.procore.com/pricing
• Procore AI: https://www.procore.com/en/ai
• Procore AI agents announcement: https://www.procore.com/news/procore-groundbreak-2026-ai-agents
• Procore Daily Log support: https://support.procore.com/products/online/user-guide/project-level/daily-log
• Procore Capterra/G2: https://www.capterra.com/p/146832/Procore/reviews/ ; https://www.g2.com/products/procore/reviews
• Autodesk Construction Cloud: https://construction.autodesk.com/
• Autodesk Build help: https://help.autodesk.com/cloudhelp/ENG/Build-About/files/What_is_Build.html
• Autodesk pricing: https://www.construction.autodesk.com/pricing/
• Autodesk Build project management: https://construction.autodesk.com/products/bim360/
• Autodesk Capterra/G2: https://www.capterra.com/p/194623/Autodesk-Construction-Cloud/ ; https://www.g2.com/products/autodesk-forma/reviews
• Trimble Construction One: https://constructible.trimble.com/construction-management-software/trimble-construction-one
• Trimble ProjectSight pricing: https://projectsight.trimble.com/pricing
• Trimble ProjectSight help/features: https://projectsight.trimble.com/help

Tender / document intelligence / risk / RFI / closeout

• Document Crunch: https://www.documentcrunch.com/
• Document Crunch contract review: https://www.documentcrunch.com/construction-contract-review
• Trimble acquiring Document Crunch: https://investor.trimble.com/news-releases/news-release-details/trimble-acquire-document-crunch
• Document Crunch Project Assist news: https://investor.trimble.com/news-releases/news-release-details/document-crunch-launches-first-ai-risk-intelligence-platform
• Document Crunch G2: https://www.g2.com/products/document-crunch/reviews
• Trunk Tools: https://www.trunktools.com/
• Trunk Tools Autodesk/Forma integration: https://www.trunktools.com/news/autodesk-trunk-tools-bring-ai-agents-to-autodesk-forma
• Trunk Tools Business Insider funding article: https://www.businessinsider.com/trunk-tools-funding-construction-ai-series-b-pitch-deck-2025-7
• Autodesk Pype: https://construction.autodesk.com/products/pype/
• Autodesk AutoSpecs: https://construction.autodesk.com/products/autospecs/
• AutoSpecs help: https://help.autodesk.com/view/AUTOSPECS/ENU/
• Pype AutoSpecs G2: https://www.g2.com/products/pype-autospecs/reviews
• ContraVault: https://www.contravault.com/ ; https://www.contravault.com/tender-hunt
• Civils.ai: https://civils.ai/ ; https://civils.ai/pricing ; https://civils.ai/blog
• DeadFront AI: https://www.deadfront.ai/
• Specbook AI: https://specbook.ai/

Takeoff / estimating

• Bluebeam pricing: https://www.bluebeam.com/pricing/
• Bluebeam G2: https://www.g2.com/products/bluebeam-revu/reviews
• Kreo: https://www.kreo.net/ ; https://www.kreo.net/pricing
• Togal: https://www.togal.ai/ ; https://www.togal.ai/pricing
• STACK pricing: https://www.stackct.com/takeoff-and-estimate-pricing-0126/
• PlanSwift: https://www.planswift.com/ ; https://www.planswift.com/checkout/
• ConstructConnect PlanSwift: https://www.constructconnect.com/products/planswift
• Beam AI: https://www.ibeam.ai/ ; https://www.ibeam.ai/pricing

Reality capture / progress tracking

• OpenSpace pricing: https://www.openspace.ai/smb-pricing-webpage/
• OpenSpace Procore marketplace: https://marketplace.procore.com/apps/openspace
• OpenSpace generate Procore RFI: https://support.openspace.ai/hc/en-us/articles/41945192149907-Generate-Procore-RFI-in-OpenSpace
• OpenSpace Autodesk integration: https://construction.autodesk.com/workflows/construction-software-integrations/openspace/
• OpenSpace G2: https://www.g2.com/products/openspace/reviews
• Buildots Autodesk integration: https://construction.autodesk.com/workflows/construction-software-integrations/buildots/
• Buildots Procore marketplace: https://marketplace.procore.com/apps/buildots
• Buildots G2: https://www.g2.com/products/buildots/reviews
• DroneDeploy pricing: https://www.dronedeploy.com/pricing/
• DroneDeploy construction: https://www.dronedeploy.com/construction/
• XYZ Reality: https://www.xyzreality.com/ ; https://www.xyzreality.com/atom ; https://www.xyzreality.com/autodesk ; https://www.xyzreality.com/construction-progress-tracking
• HoloBuilder pricing: https://www.holobuilder.com/pricing/
• FARO HoloBuilder: https://www.faro.com/Products/Software/HoloBuilder-Software

O&M / handover / golden thread

• Zutec: https://www.zutec.com/
• Zutec O&M manuals: https://zutec.com/solutions/operations-and-maintenance-manuals-for-asset-owners
• Zutec Excel handover article: https://zutec.com/blog/why-its-time-to-retire-excel-trackers-for-construction-handover-and-o-m-manuals
• Operance building handover/O&M: https://www.operance.app/building-handover-information/ ; https://www.operance.app/digital-handover/
• Glider software: https://glidertech.com/software/
• Glider handover: https://glidertech.com/solutions/deliver-and-handover/
• gliderbim: https://glidertech.com/products/gliderbim/

Asset/material tracking

• Matrak: https://matrak.com/
• Matrak pricing: https://matrak.com/pricing/
• Matrak materials tracking: https://matrak.com/materials-tracking-software/
• Matrak builders: https://matrak.com/builders/
• Sablono: https://www.sablono.com/
• Sablono pricing: https://www.sablono.com/pricing-test
• Sablono Visual Tracker: https://www.sablono.com/en/product/progress-and-workflows/visual-tracker
• Sablono Track: https://www.sablono.com/product/track

Historical cost intelligence

• BCIS: https://www.bcis.co.uk/ ; https://www.bcis.co.uk/products/construction/
• RSMeans: https://www.rsmeans.com/ ; https://www.rsmeans.com/pricing ; https://www.rsmeans.com/products/enterprise-solutions.aspx
• Rate QS: https://rateqs.com/
• ConWize: https://conwize.io/ ; https://conwize.io/estimating/
• Zebel: https://zebel.io/ ; https://zebel.io/pricing ; https://zebel.io/cost-estimating

User-sentiment sources used selectively

• Reddit discussion on Procore/ACC adoption friction: https://www.reddit.com/r/ConstructionManagers/comments/1l1ez8e/why_do_tools_like_procore_and_autodesk/
• Reddit RFI/Procore discussion: https://www.reddit.com/r/MEPEngineering/comments/1swi906/are_gcs_weaponizing_rfis_and_procore_or_am_i_just/
• Reddit AI takeoff skepticism: https://www.reddit.com/r/estimators/comments/1kadwx5/are_there_actually_any_aibased_takeoff_software/
• Reddit PlanSwift issues: https://www.reddit.com/r/estimators/comments/1hg46xa/constructconnect_planswift_frustrations/
• Reddit RSMeans/BCIS/QS discussions: https://www.reddit.com/r/estimators/comments/1texj68/is_rsmeans_worth_learning_for_a_beginner_estimator/ ; https://www.reddit.com/r/quantitysurveying/comments/1acmey5/whats_everyones_opinion_of_bcis_for_construction/