The story repeats across every trades community: a six-person outfit outgrows spreadsheets, googles "best field service software", lands in three demos, and emerges clutching a quote with five-figure onboarding, per-module pricing and a case study about a utility company with 400 trucks. Then the forum post: "Is this normal? It feels insane for our size." It is not normal, and it is not for you. Enterprise platforms are excellent tools for enterprise problems. Recognising whose problems a product was built for is the entire skill of buying software small, and it can be learned in one article.
Enterprise features solve enterprise problems
Territory optimisation across hundreds of technicians, integration buses for ERP systems, configurable approval hierarchies, dedicated success managers: every one of these earns its price at scale and is dead weight at six people. The tell is not the feature list, it is the assumptions underneath: that you have an IT person, an admin team, a training budget and months to implement. A small trade business has an owner with a phone and a Tuesday evening. Analyst houses like Gartner's FSM market reviews segment the market this way explicitly; the vendors' sales teams just hope you do not.
The overkill tells, in the demo itself
You are in the wrong demo if: pricing needs a custom quote, onboarding is a paid project with a timeline, the phrase "your implementation team" appears, core needs like invoicing or safety forms are separate modules, or the mobile app is a companion rather than the heart. One question exposes almost everything: "Can I sign up today, import a spreadsheet of customers, and schedule tomorrow's jobs tonight, alone?" If the answer involves a salesperson's calendar, the product's centre of gravity is above your weight class.
What the middle actually covers now
The genuine surprise for owners emerging from enterprise demos is how much the modern mid-market covers: drag-and-drop dispatch, offline field apps, photos and safety forms, quote-to-invoice, accounting sync, multi-crew scheduling, at per-user prices with self-serve setup. SKEDS' entire pricing page is public for exactly this reason: 0 for solo, 39 and 59 USD per user for crews, every core capability included rather than modularised, setup measured in an evening via the product tour.
Total cost is the honest comparison
Compare three-year totals, not sticker prices: licence plus onboarding plus training plus the modules you will discover you need plus the admin hours the system demands. Enterprise stacks routinely land at ten to twenty times the mid-market total for a small crew, while delivering features that go unused past the demo. Spend the difference where small businesses actually compound: another van, marketing, or simply margin, the arithmetic our software cost guide walks through line by line.
Leave the door open for the day you are big
The legitimate worry: "will I outgrow the smaller tool?" Protect yourself with portability, not premature scale: insist on data export, per-user pricing that climbs linearly, and roles that exist before you need them. A business that reaches forty trucks with clean job history exports can migrate upmarket in a controlled project. A six-person shop that bought enterprise on day one never gets the forty trucks, because the software ate the growth budget, a pattern the forums document with painful regularity.
Frequently asked questions
How do I know if software is enterprise-grade overkill?
Ask to sign up and set up alone, tonight, from a spreadsheet. Custom-quoted pricing, paid onboarding projects, implementation teams and per-module selling all signal a product whose real customer has an IT department. Nothing wrong with those products, except the fit.
Are free tiers a trap?
Judge the shape: a free tier that is a full product for one user, like SKEDS Starter, is a genuine on-ramp. A free tier that locks invoicing or the mobile app behind the first paywall is a demo wearing a price tag. Either way, check export rights before you load your data.
What if we grow into enterprise needs later?
Then migrate later, from strength: clean job history, customers and financials export into an upmarket implementation as a controlled project. Buying ten-truck software at six people to avoid a hypothetical future migration usually prevents the growth that would have justified it.
The bottom line
The pattern across every topic on this blog repeats here: the businesses that win are not working harder, they are keeping better records and letting systems carry the routine. Start with one change this week, measure it for a month, and let the results argue for the next one. And if you want the whole loop, scheduling, field app, safety and invoicing in one place, start a free SKEDS trial and test it on a real week of your own jobs.
Key takeaways
- Enterprise assumptions: IT staff, admin teams, implementation months
- The killer question: can I set up alone, tonight, from a spreadsheet?
- Mid-market now covers the full trade workflow at per-user prices
- Compare three-year totals including onboarding and modules
- Buy portability, not premature scale; export rights protect growth
Stop running the job from a spreadsheet
Schedule your crew, run jobs from the van, and invoice the moment they are done. Free for one user, forever.
Start free trial
