Why field teams don't use Procore

The adoption numbers nobody publishes

Procore reports their licensed-user counts. Software vendors love that number because it grows. What they don’t report is the daily-active-user count among field workers specifically — the tradespeople, foremen, and supers who are supposed to use the app to look up drawings, check RFIs, and file daily logs.

Across the supers and PMs we’ve interviewed, the number is remarkably consistent: 20-35% of named field users open the app weekly. The rest log in once during onboarding and then revert to the same behaviors they used before the app existed — asking the foreman, asking the PM, asking the super, reading off a paper set in the truck.

Why the app sits unused

It’s tempting to assume it’s a UX problem. Better navigation, simpler workflows, a more polished mobile design. The vendors have all worked hard at this. Procore Mobile, Autodesk Build mobile, BIM 360 Field, Fieldwire — these aren’t bad apps. Some of them are excellent.

The real reason is structural. Tradespeople don’t primarily interact with project software because:

1. They don’t have a login

On commercial projects, Procore licenses live with the GC. Subs — electrical, mechanical, plumbing, drywall, framing — bring 30-150 tradespeople onto the project, none of whom get a Procore account. The GC’s PM doesn’t want to provision 150 logins and the sub doesn’t want to pay for 150 seats.

So those tradespeople ask their foreman. The foreman asks the sub’s PM. The sub’s PM asks the GC’s PM. The GC’s PM opens Procore, finds the thing, types the answer back. The data flow is human chains, not app access.

2. The app context-switches them out of work

A tradesperson installing conduit is using both hands. The phone is in a pocket or clipped to a belt. To check what the spec says on conductor type, the tradesperson has to:

1. Stop the install
2. Pull out the phone
3. Unlock (often with gloves on)
4. Open the right app
5. Authenticate (occasionally fails)
6. Navigate to specs
7. Find the section
8. Read
9. Lock the phone, put it away
10. Re-glove, re-tool

That’s 90 seconds of friction. Texting their foreman or super takes 20. The behavior follows the path of least resistance.

3. Field-condition phones are not app-friendly

Cracked screens, sun glare, gloves, sweat, dirt, intermittent 4G in basements and stair towers. Most field-collab apps assume a clean phone with a working touchscreen and good signal. SMS doesn’t.

4. The login expires

Construction projects span months. App credentials expire, OAuth tokens get revoked, the app updates and requires re-login. Each re-auth event creates a 50%+ chance the tradesperson never opens the app again.

What “mobile-first” actually means in this domain

The construction-software industry has been saying “mobile-first” for a decade. What they mean is “our app works on a phone.” What field workers need is something different: a tool that doesn’t require an app at all.

Tradespeople use phones for two things during the workday:

• Phone calls (mostly to dispatch + supervisors)
• Text messaging (everyone they work with)

SMS volume across US trade workers averages 60+ messages per workday. The behavior is fully formed. Building a new app and asking those workers to adopt it is fighting the existing behavior. Building on top of the existing behavior is the path that doesn’t require adoption work.

What the post-app pattern looks like

At Forward we’ve been building this for the last year. The pattern is conceptually simple:

1. The GC’s data stays where it is (Procore, Autodesk Construction Cloud, OneDrive, SharePoint).
2. A texting interface sits on top of that data — a phone number per project, per tenant, or per crew.
3. Field workers text the phone number with plain-English questions. The texting layer interprets, queries the right data source, cites the answer, and replies.
4. Field workers don’t need an app, a login, or any training. The behavior is the same one they already use.

We’ve seen 80-100% field-user adoption on this pattern, compared to 20-35% on app-first. The difference is the absence of a learning curve. If you can text your kid, you can text the project bot.

What doesn’t change

The PM still runs the dashboard. The architect still reviews in Procore. The owner’s rep still gets project reports the same way. The OAuth grants are auditable; the writes still happen with PM approval; the source of truth is still the structured tool.

What changes is the field-side delivery channel. And that change is the difference between a $50K/year app investment that 30% of your field uses, and a $20K/year project budget that effectively all of them use.

What this means for the next year

The construction-software industry has built impressively polished apps for the desk-bound half of the workforce. The field-bound half has been treated as an adoption problem — if only they’d use the app, the data flow would work. They won’t. Twenty years of evidence says they won’t.

The next layer of construction software won’t be a better app. It’ll be an absence of an app — protocols (SMS, voice, AI agents) that meet the field worker where they already are. If you’re evaluating tools this quarter, ask the vendor: “what’s your DAU on field users specifically?” If they answer in installs instead of daily active users, you have your answer about whether they’ve solved the problem.