A growing services company approached us to build a field-service platform from scratch. They had a clear list of what they wanted and a budget set aside, and they expected a proposal for a custom build. What they got first was a question: how much of this is genuinely particular to your business, and how much is the same job-scheduling and work-order work that hundreds of companies do?
If you would end up maintaining five workarounds to make a bought product fit, you have built custom software anyway — just badly. The reverse is also true.
When we mapped their requirements against what established field-service products already do, most of the list was standard. The genuinely distinctive part was a thin slice — how they priced certain jobs and how they reported to a few key customers. Building the whole platform to get that slice would have meant owning, securing and maintaining a large amount of software that the market already supports well.
The challenges we had to solve
- The client had already decided to build, so the first task was an honest, evidence-based reset of that assumption.
- We had to separate what truly differentiated their business from what was ordinary scheduling and dispatch.
- A bought product still had to fit their pricing and their customer reporting, neither of which it did out of the box.
- The recommendation meant less custom-build work for us, which the client noticed and respected.
How we approached it
We ran a short discovery to document the current workflow in detail and compare it, feature by feature, against a couple of credible products. The gap was small enough that configuring an existing platform was clearly the better five-year position — they would own less code, get updates for free, and avoid carrying a maintenance burden that was not their business. We said so plainly, including the part where it meant a smaller engagement for us.
Where we did add value was the integration. We configured the product to their workflow, then built the connections it could not provide on its own: feeding their pricing rules in, and pulling clean data out into the reports their key customers expected. We kept that custom code small and well-bounded, so it sits cleanly beside the product rather than fighting it, and handed over documentation for both the configuration and the integrations.
Where it stands
The client runs on a product the market keeps current, with a thin layer of integration that handles the parts that are genuinely theirs. They avoided owning a large platform that would have aged on their books, and the engagement started with advice that worked against our own short-term interest. That, more than anything, is why they have come back to us since.