TL;DR: Contractors don't reject field service software because it costs too much. They reject it because it reads like it was written by someone who has never been on a job site, and they can tell in the first five minutes. The product gap is vocabulary and workflow fit. The harder gap is that this audience is deliberately hard to sell to — and any plan that doesn't solve distribution is only half a plan.
The evidence
PainHunt's field service domains hold 78 posts above the 10/15 threshold, averaging 11.4, with pain intensity 7.3/10 and willingness-to-pay 7.0/10 across 365 extracted pain points. The source mix is broad — 21 app store reviews, 14 Reddit, 9 Bluesky, 8 Medium, 6 from remote job boards — so this isn't one community's grievance.
Three complaints recur, and they're about different things than you'd expect.
Fit, not features. Contractors describe needing software that "speaks their language" and fits their terminology, rather than generic business tools bent into shape. The objection is to vocabulary and workflow assumptions, not to missing capability. Software built around contacts and deals doesn't match a business built around jobs, crews and site visits.
Integration, not addition. The requests are for scheduling, invoicing, job management and customer tracking to be one system. What exists is either an all-in-one built for a different industry, or four tools that don't talk to each other. Nobody in this data is asking for a new capability — they're asking for the ones they already use to stop being separate.
And the part most product people skip: contractors are explicitly described as skeptical of outside sales, hard to reach, and quick to push back — they "talk over salespeople". This appears in the data as often as the product complaints do. It is not a footnote. It is the reason the product gap has stayed open.
Why now
Vertical SaaS has worked its way down from enterprise to the mid-market, and the trades are among the largest remaining segments where the default is still paper, spreadsheets and a phone. The software exists; adoption doesn't.
Smartphones removed the hardware objection years ago — every crew already carries the device. What remains is trust, and trust in this market is earned through the vocabulary and the workflow, not through a feature list.
There's also a generational shift underway. Trades businesses are changing hands, and the incoming operators are more willing to run their business from a phone than the ones they're buying from. That's a real opening, and it's why "contractors won't use software" is a weaker objection now than it was five years ago — but it doesn't help with the selling problem, which is unchanged.
The wedge
Pick one trade and one workflow. Not "field service".
- Go one trade deep. Electricians, HVAC, landscaping — each has its own vocabulary, its own job shapes, its own compliance paperwork. The complaint in this data is precisely about generic software, so the answer cannot be generic software with a different logo. Depth in one trade is defensible; breadth is what already failed here.
- Make the job the central object. Not the contact, not the deal. A job has a site, a crew, materials, a schedule, photos and an invoice hanging off it. Products built on a CRM data model keep failing this audience because the model is wrong before the first screen is drawn.
- Solve distribution before product. This audience does not respond to cold outreach — the data says so explicitly. That leaves supplier partnerships, trade associations, the person who already sells them insurance or materials, and word of mouth inside a single trade in a single region. A great product with no route in is worth nothing here.
- Win on the first invoice, not the feature tour. The moment that earns trust is getting paid faster on a real job. Instrument that, sell that, and let everything else follow.
Risks and honest caveats
- Distribution is the actual business. The product problem is tractable and the sales problem is what has kept incumbents out. If you can't name your route to the first fifty customers, the product insight doesn't matter. This is the single most likely way this fails.
- Established incumbents exist — ServiceTitan, Jobber, Housecall Pro and others are real and well funded. The opening is trade-specific depth and small-operator pricing, not a better general-purpose tool.
- The market is loudest at its least profitable end. One- and two-person operations complain most and pay least. WTP at 7.0/10 is solid for a business tool, but the economics need the 5-to-20-crew segment to work.
- 78 posts is a modest sample. It's consistent and it spans several source types, but it's an order of magnitude smaller than our e-commerce or security clusters. Treat it as a strong hint, not a mandate — and go talk to twenty contractors before writing code.
- Switching costs run backwards here. A business already limping along with paper and a spreadsheet has no data to migrate but also no forcing function to change. The trigger is usually growth or a painful failure, which means timing matters more than persuasion.
How to validate this further
Browse the field service and trades threads in the Pain Point Browser, then pressure-test the one-trade-deep framing with the Idea Validator. Related reading: when the technician sees a failure and tells nobody and verifying contractor skills and credentials.