Owning Your System vs Cost Per User

The real question is cost per user, not “self-hosted vs SaaS”

Nobody searches for “self-hosted field-service software.” They search for what it actually costs to run their crew on a piece of software, and how that cost changes as they hire. That is the honest way to frame this decision: cost per user, not a philosophical stance on where the server lives.

A per-seat subscription has one cost curve. Jobber’s Connect plan, verified 2026-08-28, runs $105-149 a month on annual billing (year-one promo to renewal rate) for a 5-user bracket, or $199 a month month-to-month; the 10-user bracket runs $161-229 a month annual or $299 a month month-to-month. Housecall Pro’s Essentials plan runs $149-189 a month for up to five users, with additional users at $100 a month each past that. Every one of those numbers repeats every month, for as long as you use the product, and grows every time you add a technician.

An owned system has the opposite curve: a real cost to build it, then a cost per additional user that trends toward zero. In one field-service system we built and hosted, the marginal cost of adding a technician was effectively nothing, because the application shared an already-owned cloud server under an enforced CPU and memory cap, rather than standing up new billed infrastructure. There was no per-seat licence fee of any kind. Adding a fifth or sixth technician cost nothing beyond that person’s own phone.

What you actually give up, said plainly

This is the part a sales pitch for custom software usually skips, and it is the part worth taking seriously before deciding.

No vendor SLA. A subscription product comes with a support line and a service commitment, shared across thousands of customers. An owned system’s support line is whoever built or maintains it. If that is one person, one person’s availability is your uptime guarantee.

No product roadmap. A subscription vendor ships new features to every customer, funded by the collective subscription base. An owned system only gets new capability that someone specifically pays to build. There is no changelog showing up for free.

Key-person risk. This is the one that bites hardest in practice. Undocumented custom code is a real liability if the person who built or maintains it leaves the business relationship. The mitigation is not “don’t own software,” it is insisting on documentation, tests, and a handoff plan as part of the build, not as an afterthought. In one system we delivered, roughly 70 automated test files covered the pricing math, the accounting integration, permissions, and a full end-to-end demo storyline, specifically so the system’s correct behaviour is provable by running the tests, not just trusted because the original builder said so.

A real upfront cost. Zero per-seat fee does not mean zero cost. Someone still has to design, build, test, and maintain the thing. That cost is just structured differently: a build cost and slow-drip maintenance, instead of a recurring monthly charge. Whether that trade pays off is entirely a function of how long you use the system and how much the subscription alternative would otherwise have cost, month after month, for as long as you run the business.

Where the honest line falls

For a small, stable crew with straightforward scheduling and invoicing needs, a per-seat subscription is often the better buy, full stop. A $105-149 a month product does everything a 5-person shop with generic needs requires, arrives with a support line, and carries none of the key-person risk. Building custom software to save money against that price point is usually the wrong call, and we would say so if asked.

The case for owning a system gets stronger as two things happen: your headcount grows, so the per-seat cost you would otherwise pay every month compounds, and your workflow accumulates specific rules a generic product does not model well. When both are true, the direction a custom build’s cost curve is heading, toward zero marginal cost per added user, starts to matter more than the subscription’s lower starting price. When neither is true, subscribe, and put the money you would have spent on a build somewhere it earns a better return.