Every review, comparison, and buying guide on FieldServiceSoft follows the same process. This page sets out exactly how we evaluate software, what we look at, and where our limits are — so you can judge the reasoning behind our recommendations rather than taking them on faith.
What we evaluate
When we assess a piece of field service software, we work through the same five areas. They’re ordered by how much they affect a real service business, not by how impressive they look on a demo call.
- Dispatch and scheduling. Can you see your whole day at a glance? How does the system handle rescheduling, cancellations, and a job that runs long? A calendar that looks clean in a demo often falls apart when a technician runs two hours behind.
- Mobile experience for technicians. The app is where the software either works or dies. We look at load speed, offline behaviour, how many taps it takes to close out a job, and whether a tech can invoice from the driveway.
- Invoicing and payments. How quickly can an invoice go out, and what does the payment processing actually cost? Processing fees are frequently larger than the software subscription itself, and they’re rarely mentioned in a sales pitch.
- Integration and data portability. Whether it syncs properly with accounting tools like QuickBooks, and whether you can get your customer and job data back out if you leave. Lock-in is a cost, even when it isn’t on the invoice.
- Pricing at realistic team sizes. We quote what the software costs for a specific number of users — usually five technicians, since that’s the size where most owners start looking — not the advertised entry price for two seats.
How we gather information
We don’t claim to have run every product on live jobs — that would be dishonest, and no single reviewer could. Here’s what we actually do:
- Vendor documentation and pricing pages. We read the published pricing, feature lists, and contract terms directly rather than relying on secondhand summaries.
- Owner feedback. We read reviews from real business owners on independent platforms, and we look specifically at what long-term users complain about — the complaints are usually more informative than the praise.
- Direct conversations where possible. When we can speak to owners or technicians who use a product daily, that goes into the assessment, and we say so in the article.
- Cross-checking. Where a vendor makes a strong claim, we check whether independent sources agree before repeating it.
How we handle pricing
Software pricing changes often, and it varies by region, contract length, and team size. We state the figures we found at the time of writing, and we date every article. If you find a price has changed, tell us and we’ll correct it — accuracy here matters more to us than being first.
Always confirm final pricing with the vendor before you buy. Nothing on this site is a substitute for a written quote for your own team size.
What we don’t do
- We don’t accept payment for a positive review. No vendor pays us to be recommended, and no vendor sees our content before it’s published.
- We don’t rank by commission. Some links on this site are affiliate links and we may earn a commission if you sign up. The commission rate has no bearing on what we recommend or where a product places in a comparison.
- We don’t recommend a product we wouldn’t use ourselves. If a tool is genuinely wrong for the businesses we write for, we say so, even if it means recommending nothing in that category.
Our limits
We’re a small, independently operated site. We haven’t tested every product exhaustively, and software changes faster than any review can keep up with. What we can promise is that our reasoning is transparent, our sources are checkable, and we correct errors when they’re pointed out.
If something here is wrong, tell us. Corrections make the site better for everyone reading it.
Our affiliate relationships
FieldServiceSoft is reader-supported. Some links on this site earn us a commission at no extra cost to you. That relationship is explained in full on our Affiliate Disclaimer page, and our data practices are covered in our Privacy Policy.
Last updated: September 2026