The major field service software platforms were built for companies with 50 trucks and a full-time dispatcher. That made sense when field service software was a category dominated by large contractors and regional service companies with the IT budgets to implement and maintain complex systems.
The problem: most field service businesses are small. The HVAC company with eight technicians. The landscaping crew with two teams and a scheduler who's also the owner's spouse. The plumbing shop that added a third van last year and still runs on group text. These businesses have the same operational problems as the large companies — dispatching, job tracking, billing, customer communication — but they don't have the IT team, the implementation budget, or the tolerance for a six-month onboarding process.
Field service software for small business has 7,300 monthly traffic potential for a reason. These buyers exist. They're searching. They're not finding what they need.
What small field service businesses need
The complexity gradient between a 10-person field service company and a 100-person company is steeper than most platform vendors assume. At 10 people, the owner is in the field, doing the scheduling, talking to customers, and reviewing invoices — often on the same day. The software has to work in a moving truck with one hand and three minutes of attention.
At 100 people, you have an operations manager, a dispatcher, an office manager, and an IT vendor. The software can be complex because there are people whose full-time job is operating it.
Most field service platforms are designed for the second scenario. The onboarding alone — importing customers, setting up service agreements, configuring the dispatch board, training the team — takes weeks. For a small operator, that's time they don't have and cost they're not willing to absorb for a system they're not sure will solve their problem.
Where the big platforms fall short
The pricing is a problem. Most enterprise-grade field service platforms charge per technician or per user, with minimums and annual contracts. For a five-person operation, that's a meaningful monthly spend on software that was designed for a 50-person team. The pricing isn't just about budget — it signals who the product was built for.
The mobile experience is frequently an afterthought. The desktop application gets the investment; the mobile app gets the port. For field service technicians who live on their phones, a clunky mobile experience isn't a minor inconvenience — it's a reason to stop using the software three weeks after the owner paid for the annual subscription.
The opportunity in the sub-50 market
The field service software market is not undersupplied — there are hundreds of products. It is poorly stratified. The enterprise segment has clear winners. The micro-SMB segment (one to five technicians) has a few simple scheduling apps. The 5-to-50 segment — companies large enough to need real dispatch and invoicing but too small for enterprise implementation — is the gap.
Vertical SaaS that targets this segment and goes deep on a specific trade — HVAC, landscaping, plumbing, electrical — can win on specificity. When the software speaks the language of the HVAC industry, includes the specific forms HVAC techs need, integrates with the parts suppliers HVAC companies use, and prices for a 10-person company rather than a 100-person company, it earns trust that a generic platform can't manufacture.
The operator founder who ran a 15-truck HVAC company for 12 years doesn't need to do 30 customer interviews to understand this market. They've lived the problem. They know what the dispatcher does when the tech calls in sick and three jobs are unassigned. They know what the customer complaint is when the tech shows up 90 minutes late without a heads-up. They know what the invoice dispute is about when the customer calls on a Thursday.
What this means for founders considering this space
Building for small field service businesses is a volume game — the unit economics require keeping implementation costs low, support lean, and pricing accessible. That means making product decisions that prioritize simplicity over feature completeness. It means saying no to the features that 100-person companies want and that would make the product harder for 10-person companies to adopt.
That's a harder product discipline than it sounds. Every feature request from early customers sounds reasonable. Every competitor adding a feature signals that maybe you should add it too. The discipline of staying in your lane — building for the small contractor, deeply, rather than growing up-market to chase bigger contract values — is what makes a small field service software business defensible.
If you've run a small field service company and you know exactly what the existing software gets wrong, that frustration is a product thesis. Tell us what you'd build.