AI capture puck plus Procore-native integration that converts GC site walkthroughs into RFIs, field reports, and punch lists without manual rekeying.

1. Pocket hit $27M ARR selling a $129 puck—enterprise field workers already pay for dedicated AI capture hardware, validating a device-led GTM model in construction before any construction-specific product exists.
2. Accel and Y Combinator explicitly named construction workers as a Pocket use case, signaling that top-tier VC already sees field documentation as a paid segment—creating a clear opening for a construction-vertical wedge.
3. Privacy-aware manual-trigger recording is preferred over always-on ambient capture in enterprise deployments, which maps directly to construction's consent requirements on union job sites and government-funded projects.
4. HIPAA and SOC 2 compliance is already proven for AI capture pucks, lowering the security review barrier for GC procurement—enterprise-grade data handling is no longer a differentiator to build, only to configure.
5. Webhook and custom workflow integrations in AI capture hardware are already live and production-proven, meaning a Procore-native integration can be built on mature architecture rather than speculative API work.

Catalyst. Pocket's $11M raise and $27M ARR validate that dedicated AI capture hardware has crossed the enterprise adoption threshold; construction workers are already a named paying segment, making this the first moment a construction-vertical product can be built on proven hardware PMF rather than a speculative device bet.

A ruggedized AI capture puck worn on the belt or clipped to a hard hat records spoken observations during site walkthroughs with a single button press. Audio is transcribed and routed through a Procore-native integration layer that classifies each observation as a daily log entry, RFI draft, punch-list item, or safety observation, then pre-populates the correct Procore form with suggested trade, location, and priority fields. The superintendent reviews and approves queued items in a 90-second end-of-walk session on their phone, with no manual transcription or rekeying. SOC 2-class data handling and end-to-end encryption meet enterprise GC security requirements out of the box.

What's different. Unlike software-only note-takers such as Otter.ai and Fireflies, this product is built as a wearable job-site device from the ground up—no phone in hand, no ambient microphone, and no failure in loud or hands-busy field environments. Unlike generic AI hardware that routes to generic calendars and task apps, the wedge is deep Procore certification that writes directly to the GC's existing system of record, eliminating rekey cost and making the ROI calculable per avoided change order. The physical form factor also solves the construction-specific consent problem: crews can see the device activate, removing the union and OSHA-related objections that foreclose always-on tools.

Jobs to be done

flowchart LR
  GC[GC Superintendent] -->|Single button press| Puck[AI Capture Puck]
  Puck -->|On-device transcription| Router[Workflow Router]
  Router -->|Classify and map fields| Procore[Procore API]
  Procore -->|Pre-filled draft forms| Review[90-sec Mobile Review]
  Review -->|Approve| Record[Procore Record Created]
  Record --> Outcome[Zero rekey and zero lag]

Executive takeaways

• Hardware PMF is already proven horizontally, but the investable wedge is vertical workflow routing, not the puck itself [1][2][3].
• Construction documentation pain is severe and measurable, yet most incumbents still assume phones, forms, or photo walks rather than hands-free structured capture [20][26][29][31].
• Procore dependence is both feature and risk: it makes distribution and integration easier, but it also concentrates platform exposure [18][19][31].
• A $199-per-device-month price only works if the product eliminates rekeying, accelerates same-day RFIs, and reduces rework or dispute loss; transcription alone anchors much lower [4][7][8][21][38].

Market definition

The initial market is field-documentation capture and routing for commercial GCs already living in Procore or similar cloud PM systems. The job is not generic meeting notes; it is turning spoken site observations into structured daily logs, RFIs, change orders, and punch items fast enough to matter on the same day [12][13][14][15][19]. The industry base is large enough for a venture-scale wedge: AGC counts more than 919,000 U.S. construction establishments, while Construction Coverage estimates 814,557 construction businesses with employees and $2.2T of 2025 annual spending [9][11].

Customer and buyer

The end user is the superintendent, assistant superintendent, project engineer, or foreman doing site walks and closeout follow-up. Procore notes that site supervisors and project managers commonly own daily logs, while field-first vendors like Raken and Fieldwire are explicitly built around the same field actors [13][21][27]. The practical buyer is an operations VP or construction IT leader who already owns Procore process standardization, security review, and integration governance [17][18][19][35].

Buying triggers

• A recent documentation failure, missing records during handoff, or owner dispute creates urgency because incomplete project records visibly extend schedules and destroy margin. [20][12][15]
• Teams that are already behind schedule feel more pain from delayed field updates because execution gaps compound once work stalls. [31][32]
• GCs already paying for structured logs, RFIs, and change-order workflows in Procore or adjacent tools are primed to buy something that improves capture without changing system of record. [13][14][15][19]

Willingness to pay

Public price anchors show the category split clearly: generic AI note-takers cluster around low double-digit monthly spend, Pocket monetizes with a device plus premium AI plan, and Fieldwire tops out at $89/user/month before deeper enterprise negotiation [4][7][8][21][38]. That means the proposed $199/device/month price cannot be sold as note-taking software; it has to be sold as avoided rekeying, faster same-day documentation, and lower rework or claim exposure [15][20][31]. [4][7][8][21][38][15][20][31]

Category dynamics

Growth signal 8.74% projected 10-year growth in the construction-manager workforce (proxy for seat growth)

Validation signals

• Pocket says it has sold more than 130,000 units and explicitly cites construction workers as active users.
• Pocket's press release claims a $27M annualized revenue run rate, enterprise customers, and HIPAA/SOC 2 positioning.
• A March 2026 survey found only 13% of respondents considered asset documentation mostly complete and nearly 80% reported significant gaps or scattered records.
• Buildots finds average schedule adherence of 48% across 200+ anonymized projects, underscoring how costly delayed field visibility can become.
• OpenSpace says one customer cut capture, upload, and mapping time by 95%, proving field teams will adopt automation when it saves real hours.

Regulatory & technical constraints

• Enterprise buyers still need structured logs and reports for audits and compliance; raw audio alone does not satisfy the job-to-be-done.
• Deployment policies must address workplace recording rights and carve-outs rather than rely on blanket no-recording rules.
• Jobsite capture has to survive noisy, mobile, hands-busy conditions and still map output into precise project objects after review.

Competition is real but fragmented. Procore owns the system of record, Raken and Fieldwire own mobile field workflows, OpenSpace and Buildots automate visual or progress capture, and Otter, Fireflies, Pocket, and Plaud keep reducing the cost of AI note capture [1][3][6][7][8][21][27][30][31]. No incumbent combines ruggedized field audio capture with Procore-native record creation, so the startup only wins if it sells a faster path from spoken observation to approved structured record—not just another transcript [12][18][19][31].

Why incumbents do not win by default

• Systems of record. Procore wins the budget and workflow position today, but it still expects teams to enter or review structured data inside a broad platform rather than through dedicated hands-free field capture.
• Field-reporting specialists. Raken proves crews will use field-first documentation software, but its workflow still starts from forms, photos, and manual updates rather than domain-tuned audio capture.
• Mobile field-management suites. Fieldwire covers RFIs, punch items, reports, and change orders with public SMB-friendly pricing, which makes it a credible substitute for many buyers before they consider dedicated hardware.
• Horizontal AI notetakers. Otter and Fireflies set a low-cost benchmark for AI notes, but they are optimized for meetings, not noisy jobsites or construction object models.
• Reality-capture platforms. OpenSpace and Buildots show that automated capture has real construction demand, but their strength is visual context and progress analytics rather than converting speech into RFIs or daily logs.

Construction Field AI Scribe is a ruggedized AI capture puck paired with a Procore-certified integration that converts spoken site observations into pre-filled RFI drafts, daily log entries, and punch-list records—eliminating the two-to-four hours GC superintendents spend daily on manual rekeying. The target buyer is the operations VP at commercial GC firms with 50–250 field crew that already pay for Procore and have experienced change order disputes caused by documentation lag. Pocket's $27M ARR and 130,000+ units proves that enterprise field workers pay for dedicated AI capture hardware; Accel explicitly named construction workers as a paying segment before any construction-vertical product exists, creating a first-mover window. No incumbent closes the exact field-audio-to-Procore-record gap—Raken and Fieldwire require manual form entry, Procore expects data entry rather than capturing it—so the company wins by routing spoken observations to approved structured records faster than any assembled substitute. Defensibility rests on Procore Marketplace distribution, per-customer vocabulary fine-tuning, and a construction-domain classification model that accumulates switching costs with every approved field record. The beachhead is post-dispute selling to operations VPs whose recent change order exposure has already created a budget event; a single avoided $50,000 dispute exceeds two years of subscription cost. Three open questions govern near-term execution: achievable word-error rate on noisy job sites, Procore API write-back feasibility at fleet scale, and preferred hardware form factor after field pilots.

Problem

• GC superintendents spend two to four hours daily rekeying site observations into Procore—voice memos and paper notes captured during walkthroughs are transcribed by office admins at end of shift, creating a 24-hour documentation lag that causes missed RFIs, incomplete daily logs, and costly change orders.
• A single missed RFI or undocumented field event can trigger a change order costing $10,000 to $500,000; no purpose-built hands-free capture solution exists for field environments where handling a phone during active site work is impractical or prohibited.
• Privacy-aware recording is structurally required on union and government job sites; always-on ambient capture tools cannot be deployed in these environments, leaving construction without a compliant hands-free documentation option that creates an auditable paper trail.

Solution

• A ruggedized AI capture puck worn on the belt or clipped to a hard hat records spoken site observations with a single button press, transcribes on-device, and routes each utterance through a Procore-native classification layer that maps it to the correct form type: daily log, RFI draft, punch-list item, or safety observation—with suggested trade, location, and priority fields pre-filled.
• Queued Procore form drafts are reviewed and approved by the superintendent in a 90-second end-of-walk mobile session—no manual transcription, no office rekeying, no change to the GC's existing system of record.
• User-triggered button-press recording, SOC 2-class data handling, end-to-end encryption, and no model training on customer data meet enterprise GC security requirements and union-site consent rules without additional configuration.

Why we win

• Procore-certified integration and App Marketplace listing are both the distribution moat and the trust signal GC IT procurement requires; no horizontal hardware or software-only competitor has this certification for construction field audio routing.
• Physical button-press consent is structurally required on union and government job sites; always-on competitors are foreclosed from these accounts by default, shrinking their addressable construction market to non-union commercial work only.
• Per-customer vocabulary fine-tuning and the approval-loop feedback create a labeled corpus of construction speech mapped to Procore objects that generic note-takers cannot accumulate, compounding routing accuracy and switching costs with every approved field record.
• ROI is calculable and defensible per avoided change order—$199 per device per month anchors in cost-avoidance language, not abstract productivity, which is required to clear GC procurement and survive a CFO review.

Milestones

flowchart LR
  Wedge[Post-dispute GC outbound] --> Pilot[First paid pilots - 3 GCs]
  Pilot --> Validation[Field accuracy validated]
  Validation --> Marketplace[Procore Marketplace listing]
  Marketplace --> Growth[25 customers and Series A]
  Growth --> Platform[Subcontractors and adjacent platforms]

Founding team

Experiment roadmap

Risk assessment

What must be true

• Field audio classification reaches 85%+ accuracy on active job sites with PPE, wind, and machinery noise within 6 months of pilot data.
• At least 5 of the first 10 GC pilot customers convert to production contracts at $199 per device per month without requiring a meaningful price concession.
• Procore API supports direct write-back into daily log, RFI, and punch-list objects at fleet scale without rate-limit or certification blockers that prevent Marketplace listing.
• The post-dispute buying trigger is repeatable enough to generate a qualified pipeline of 20+ GC conversations per quarter through direct outbound alone.
• A dedicated ruggedized device is preferred over a phone-based accessory by at least 60% of field supervisors after a 30-day job-site pilot.

Open diligence questions

• What Procore API endpoints and rate limits apply to daily log, RFI, and punch-list write-back, and what is the actual timeline and cost of App Marketplace certification?
• Which specific documentation failure scenarios have GC operations VPs already budgeted to solve, and what is the incumbent solution (voice memo plus admin rekey, Raken, Fieldwire) currently in place?
• What are the labor-law and union-consent requirements for wearable recording devices at the top 20 commercial GC accounts in target markets, and which states or project types are most restrictive?
• Which contract electronics manufacturers with industrial wearable experience are available at seed-stage volumes of 1,000–5,000 units, and what are minimum order quantities and lead times?
• Has any GC operations VP seen a live demo or prototype and committed in principle to a paid pilot, and if so, what objections surfaced?
• How does Pocket's existing webhook and enterprise workflow architecture map to Procore-specific write-back requirements, and what engineering effort must be rebuilt versus adapted?

Model sanity

• Revenue engine. Base revenue comes from scaling from 3 paid accounts in Y1 to 25 by Y2 exit and 100 by Y3 exit while each GC standardizes roughly 25 to 26 billed field-supervisor devices.
• Must go right. The Procore-native workflow and solutions onboarding must stay repeatable enough that gross margin can cross 70% as deployments move from pilots to fleet rollouts.
• Model breaks if. If sales cycles drift back toward normal 6-12 month construction software timing or average deployments stall below about 20 devices per GC, downside cash falls toward the low-$200Ks.
• Next-round proof. The next financing story is 25 paying GCs, about 625 active devices, Marketplace credibility, and a visible path from the Q4Y2 $1.5M ARR proof point into positive H2Y3 EBITDA.

Scenarios

Sensitivity

flowchart LR
  Trigger[Post-dispute trigger] --> Pilot[Paid pilot]
  Pilot --> Account[Production GC account]
  Account --> Seats[Active devices per GC]
  Seats --> Revenue[Subscription + onboarding revenue]
  Revenue --> GrossProfit[Gross profit]
  GrossProfit --> Cash[Cash and runway]

Flags: The BP 24–36 month milestone combines $6M ARR with 1,000+ active devices, but at $199 per device per month that ARR level actually requires roughly 2,500 billed devices unless account expansion or add-on pricing is materially higher. · customersEop includes paid pilots as well as production subscriptions through Y1, so early logo count is ahead of true production-logo count. · Cash is proxied by EBITDA, which likely understates working-capital needs for the planned first production run of hardware and replacement inventory. · The base case assumes the post-dispute trigger really compresses enterprise buying cycles; if it does not, the seed ask likely needs to move toward the top of the stated BP range.

• Procore platform dependency. Deep integration with Procore creates single-channel concentration risk—a change in API terms, competitive product roadmap, or Marketplace policies could foreclose the primary distribution channel overnight. Mitigation: Build parallel integrations with Autodesk Build and Fieldwire before Series A so no single platform accounts for more than 60% of active customers.
• Hardware manufacturing complexity. Building a ruggedized device to job-site durability standards requires supply chain and manufacturing expertise that software-only founding teams typically underestimate, risking delayed launch and margin compression. Mitigation: Partner with a contract electronics manufacturer experienced in industrial wearables and price devices on subscription to target 60%+ gross margin from month one rather than selling hardware at cost.
• Long enterprise procurement cycle. Enterprise GC procurement decisions are driven by IT and operations VPs who evaluate tools during project transitions, creating 6 to 12 month sales cycles that can strand a seed-stage company before it finds repeatability. Mitigation: Seed the first ten customers through a pilot priced at device cost only, targeting superintendents who have experienced a recent change order dispute since that triggering event typically shortens the sales cycle to four to six weeks.