Sixfields Software is built in Northampton, UK by someone who spent years as a field service engineer, using a long list of "industry standard" apps and still somehow ending up coordinating the day in a WhatsApp group. Sixfields is the platform we kept wishing existed.
Sixfields started where most useful software starts: from frustration. Not theoretical, observed from a distance frustration the daily kind, working as a field service engineer.
When you've worked on the tools, you know the pattern. Your hours get sent in by email, a JotForm, or dropped in a WhatsApp chat. The "official" job management app the office picked looked great in the demo and falls apart on site — it eats your battery before lunch, hangs the moment signal drops in a plant room, and buries the one thing you actually need under five things someone in marketing thought you needed. Half the time you submit a job and watch a spinner for 45 seconds wondering if it actually went through. So you stop trusting it. You take photos on your camera roll just in case. The real coordination moves to a WhatsApp group, and the official software becomes a Friday-evening data-entry chore.
The view from the office isn't much better. A scheduling spreadsheet. A separate one for engineer hours. Another for parts, another for invoicing, another for the customer report. The same job details typed in four times because none of the systems talk to each other, and someone has to be the human glue that holds it together. Hours every week — sometimes days — disappear into reconciling, copy-pasting, chasing engineers for the bit they forgot to fill in. Work that produces nothing except a spreadsheet that matches another spreadsheet.
So we built Sixfields. Not as another generic field service tool, but as a platform shaped around the way these businesses actually work — designed by someone who lived in the gap between the official software and the WhatsApp group, and who knows exactly why most field service apps end up in that gap.
Sixfields is a deliberately small operation. Software built by the person who'll actually answer your demo call beats software built by departments who pass you between them — every time, in this category, for the kind of business we work with.
These aren't values posters on an office wall. They're the principles that decide what gets built, what gets cut, and how we treat the businesses that trust us to run on Sixfields.
Generic field service tools force every business into the same workflow. A boiler engineer, a furniture installer and a gym equipment service contractor all get the same forms, the same labels, the same job categories. We refuse to build like that. Sixfields is shaped to your industry on day one, not bent into shape by you over six months.
The most beautiful office dashboard is worthless if the engineer in the van quietly stops opening the app. Every product decision starts with the engineer's experience, on a phone, on a job, with one bar of signal — not with a feature list a desk-bound product manager wrote.
Half the calls into a service business are customers asking for information that should be visible to them already. We build customer-facing tooling — portals, status updates, payment workflows — as a first-class part of the platform. Your customers stop being a phone-call workload and start being part of the loop.
Per-engineer pricing is the field service software industry's worst habit. Hire a seasonal engineer for a busy month and the software bill goes up. Add a subcontractor for a single weekend project and you're paying for a full licence. We don't do that — pricing scales with the business, not the headcount.
Most software vendors will sell to anyone who'll sign. We won't. If a 20-minute demo conversation makes it obvious that Sixfields isn't right for your business, we'll say so — and where possible, point you at someone who is. We'd rather have 50 happy customers than 200 unhappy ones.
Most software companies want to be bigger. More staff, more layers, more meetings between you and the person who'd actually fix your bug. We don't. Sixfields is built deliberately small so the person writing the code is the same person you spoke to at the demo. That's the deal, and we don't plan to change it.
Sixfields is in its early days as a productised platform, but it's the result of years of watching what works and what doesn't on site, in real field service operations. We're deliberately taking on a small number of customers in the first wave so we can do right by every one.
If you're a service business with operations that don't fit generic field service tools, you're exactly who Sixfields is built for. The smaller end of mid-market — too big for ServiceM8, too sharp for BigChange. The early conversations are with us, not a sales team. The setup work is done by the person who built the platform, not contractors. The product roadmap is shaped by the customers who land in the first wave.
If that sounds like the kind of relationship you want with the software running your business, get in touch.
Not a sales rep. Not a discovery call. A genuine conversation about your operation and whether Sixfields is the right fit. We'll tell you straight either way.