Facility Management Software: Build or Buy at Your Technician Count
The line is about 40 technicians and one client portal mandate.
On this page
The line is about 40 technicians and one client portal mandate. Self perform for one or two clients, under roughly 40 technicians, with nobody insisting you work inside their system, and Limble, UpKeep, Fiix or ServiceTitan will serve you properly for a fraction of a build. The moment a second client mandates ServiceChannel or Corrigo, you are paying humans to act as middleware between two systems, and a first release at $60,000 to $130,000 in 12 to 16 weeks starts to clear. Everything after that is deciding how long you are willing to keep paying for the translation.
When is off the shelf genuinely the right call here?
Stay on Limble, UpKeep, Fiix or ServiceTitan if you self perform under one or two client relationships, run fewer than roughly 40 technicians, and no client mandates their own portal. At that size the rigidity is not costing you real money, and a subscription against a six figure build is not a close decision. Buy the tool, hire a strong operations lead, and spend the difference on vehicles.
Those products are built for the facility owner rather than the service provider, and that is a design choice rather than a defect. They assume you own the assets and you are the only party with a service level agreement. If that describes you, they fit.
Buy also when your problem is process rather than software. If unbilled work exists because technicians do not close jobs properly, or because nobody has agreed what a completed job requires, custom software will enforce a discipline you have not established. You will have paid a great deal to discover that. Fix the close out process first and see what remains, because that exercise is free and it is the only honest way to size the software problem.
The test for buying is whether anyone outside your company sets the rules for your work orders. If not, an off the shelf maintenance system is a sufficient system of record. The build case appears when two or more clients each impose their own portal, their own service level definitions and their own status expectations, and only then.
When does a custom build actually pay off?
The problem worth solving is that a facility management provider does not sell labour. It sells a provable promise, and provable means data: a timestamped intake, a technician on site, parts consumed against an asset, a signature, and an invoice that maps back to a line in a master service agreement. Purchased maintenance systems have no place to put the sentence that describes your business, which is that this work order belongs to client A's contract, is governed by client A's service level matrix, must be status mirrored back into client A's portal, and gets billed at client A's rate card. That is a data model problem rather than a settings problem.
In Digital Heroes delivery experience a first release covering multi channel intake with one client portal integration, a unified work order queue, dispatch, an asset registry with scan based capture on offline capable mobile, and a service level engine with per contract policies and a live at risk board runs $60,000 to $130,000 over 12 to 16 weeks. A full platform adding further portals, subcontractor compliance, invoice matching, accounting integration, a client portal and preventive maintenance driven by asset history runs $150,000 to $400,000 across 6 to 12 months.
Build when two or more hold. You employ someone whose actual job is moving data between your system and a client's portal. Month end unbilled work orders exceed two per cent of contract value and nobody can explain why. A client has assessed service level credits you cannot disprove from your own data. Or you subcontract more than a third of volume with no invoice to work order matching.
How do they compare on the things that matter in this industry?
On intake, the difference is where the translation happens. Today work orders arrive from a client's ServiceChannel or Corrigo instance, from an email to a shared address, from a phone call and from a text to whoever owns the relationship, and a dispatcher retypes them. A build gives you one work order object carrying a client, a contract, a service level policy reference and a source channel, with adapters pulling from the portals and writing status back automatically. That write back is the highest return integration in the category, because it removes both the re keying and the failures where you did the work and forgot to update their system.
On service level measurement, the purchased tools lose structurally. Definitions are contract specific and awkward: one client's clock pauses while awaiting parts approval, another runs on business hours defined by a mall's operating schedule, a third starts when the tenant reported it rather than when it reached you. If you cannot compute the number yourself, you are accepting the client portal's version, which is rarely computed in your favour. A build holds each contract's policy explicitly with named pause reasons and an audit trail of who paused the clock and why.
On the asset registry, both routes have asset tables and neither fills them in. The real difference is capture friction. Off the shelf mobile asks a technician on a roof in July for twenty two fields and gets four of them, half wrong. A scan on the asset that already knows the site, the equipment and the last four work orders is what makes a registry survive contact with the field.
On subcontractors, accounting software does not know what a work order is and a maintenance system does not know what a certificate of insurance is, so compliance runs on a spreadsheet of expiry dates and invoices are approved with no job reference. Blocking dispatch to a non compliant subcontractor by rule is the whole point.
On client reporting, a build makes the quarterly review a query rather than a three day assembly job from four exports.
What does total cost of ownership look like at your scale?
Take a provider running 200 sites and 85 technicians, two clients mandating their own portals, roughly a third of volume subcontracted.
The first release prices at about $111,000 over 15 weeks: discovery and domain modelling covering work order, site, contract, service level policy, asset and subcontractor $13,000, multi channel intake with one portal integration and inbound email parsing $27,000, the unified queue and dispatch $21,000, the asset registry with scan based capture and offline capable mobile $26,000, and the service level engine with per contract policies, business calendars, pause reasons and the at risk board $24,000.
Phase two over the following eight months adds the second portal integration at $23,000, subcontractor compliance with certificate expiry and dispatch blocking at $24,000, invoice matching with variance thresholds at $22,000, two way accounting integration with job costing at $31,000, the client portal and reporting layer at $29,000, and preventive maintenance driven by asset history at $19,000. That is $148,000, taking the platform to $259,000 all in.
Running costs are 15 to 20 per cent of build cost a year, roughly $39,000 to $52,000. Portal integration maintenance dominates, because enterprise facility management portals change their interfaces on their own schedule and each change arrives as unplanned work against a deadline you did not set. Add mobile distribution and operating system compatibility testing twice a year on the devices technicians actually carry, which is rarely the newest hardware. Then name the internal owner who onboards new client contracts into the service level engine and clears the exception queue where a subcontractor invoice could not be matched. Hosting is comparatively small, since data volume here is dominated by photographs and grows predictably.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. For a provider in the middle of this decision it is usually the right architecture rather than a halfway house.
Concretely: keep your existing maintenance system as the technician facing tool and the asset record, because your technicians already know it and replacing a working mobile experience is expensive and risky. Build one layer above it that owns the client dimension: the contract, the service level policy with its pause rules and business calendar, the rate card, and the adapters that pull work orders from ServiceChannel and Corrigo and write status back. Orders land in your maintenance system as they do now, and the layer keeps the client's portal current without a human.
That removes the two costs that are actually measurable, which are the dispatcher acting as middleware and the credits you cannot dispute, at a fraction of a full platform. It also leaves the subcontractor module free to be built separately, and in our delivery experience that module is the one that most reliably returns its own cost inside a year, because invoices arriving already matched to a job with a quoted amount surface overbilling that currently passes unchallenged.
Sequence by money rather than by who is asking. Clients ask for a portal first. Build invoice matching first, and integrate the portal covering your largest contract before you attempt a second, because providers who try to launch three portals at once routinely slip.
Which should you choose, by operator size and stage?
Under 40 technicians, self performing for one or two clients, no portal mandate: buy Limble or UpKeep. Fiix and ServiceTitan are worth quoting alongside depending on whether your work looks more like maintenance or more like dispatch.
Forty to eighty technicians with one portal mandated client: stay bought and standardise now while it is free. Reduce your service level variants, agree what a closed job requires, and get certificate expiry dates into one place. All three make a later build cheaper and all three improve your operation immediately.
Eighty or more technicians with two or more portal mandates: build the client layer at $60,000 to $130,000, keep your maintenance system where it is, and integrate the portal covering your largest contract first. Prove the status write back loop before funding the second.
A multi region provider subcontracting a third of volume with unbilled work you cannot explain: expect the full $150,000 to $400,000 programme, budget $20,000 to $30,000 per additional portal, and treat offline mobile as non negotiable at $20,000 to $28,000. A technician who loses a completed work order in a basement stops using the application that week, and then you have paid for a system nobody uses. Pilot with one region and your most sceptical technicians before any portfolio wide rollout, because field adoption is decided in the first fortnight of real use rather than by the feature list.
If you want a second opinion before signing anything, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Timefold reports field service operations moving to automated route optimization typically see 10-25% fuel savings and 15-30% drive-time reductions, and documents a case where a global services firm cut drive time 33% and distance 43% while eliminating overtime. Source: Timefold (2025) →
- ServiceTitan's KPI guide cites an average first-time fix rate near 80% (90% ideal) and describes strong technician-utilization rates as falling in the 60-80% band, with average travel time typically 30-60 minutes depending on service-area size. Source: ServiceTitan (2026) →
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- The EY survey of 508 payroll professionals at U.S. companies with 250-10,000 employees quantifies the direct and indirect cost of payroll inaccuracy, reinforcing the ROI case for payroll automation; the study is the original source of the frequently cited $291-per-error figure. Source: BusinessWire / EY (Ernst & Young) (2022) →
Frequently asked questions
What does it cost to migrate off our current maintenance system?
Expect two to four weeks of project time, usually $8,000 to $15,000 depending on data quality. Work order history is the easy part and should be imported read only for reporting continuity rather than migrated into the live model.
Assets are the hard part, because most existing registries are half populated and duplicated across sites. That cleansing needs your operations team validating the mapping site by site, and it is time worth spending properly rather than compressing.
What happens if our maintenance vendor changes its per seat pricing?
Per technician seat pricing scales with headcount, so your exposure grows every time you win a contract that requires more field staff. Model it against the technician count you expect in three years rather than today's.
The deeper exposure is that per contract service level policies, pause rules and rate cards have nowhere to live inside those products, so the workaround is a spreadsheet regardless of price. A provider whose client layer sits in its own system can change maintenance products as a project.
How long before technicians are actually using it in the field?
Twelve to sixteen weeks to a first release, and adoption is decided in the first fortnight of real use rather than by the feature list. Capture friction is the deciding factor: a scan on the asset instead of twenty two form fields, and offline capture that never loses a completed order in a basement.
Pilot with one region and your most sceptical technicians before a portfolio wide rollout. That pilot is where a slow capture flow gets caught, and catching it later is far more expensive.
Is Limble or UpKeep enough for a facility management provider?
For a self performing provider under about 40 technicians with one or two clients and no portal mandate, yes, and a build would be hard to justify. Both handle work orders, assets and preventive maintenance competently.
They constrain you at the same point, which is that they were designed for the facility owner. There is no concept of a work order belonging to a client contract governed by that client's service level matrix, status mirrored into their portal and billed at their rate card. That is a data model limit, not a settings limit.
What does each client portal integration add to the budget?
Budget $20,000 to $30,000 per portal. ServiceChannel and Corrigo both have enterprise gated interfaces, different data models and per client configuration, so the second integration reuses the intake pipeline but not the mapping, authentication or status write back logic.
Ask any prospective developer what happens when a client's portal rejects a status update, whether they poll or take webhooks, how they reconcile drift when the two systems disagree, and what the retry story is. Vague answers here mean you are funding their education.
Which module pays for itself first?
Subcontractor invoice matching, in our delivery experience. When invoices arrive already matched to a work order with a quoted amount, variance over a threshold routes to a person and everything else approves automatically, which surfaces overbilling that currently passes unchallenged.
That module ran $22,000 in the worked example. Providers subcontracting a third or more of their volume commonly recover more than that in the first year, which is why we sequence it ahead of the client portal that clients keep asking for.
How much of the budget goes to offline mobile?
Typically $20,000 to $28,000 within a first release, and it is not a line you should cut. Technicians work in mechanical rooms, basements and parking structures with no signal, and one lost completed work order will end adoption for that technician permanently.
The cost sits in local storage, photograph handling and conflict resolution when a dispatcher reassigns a job while the technician is offline. Ask for that specific conflict rule before you sign anything.
Can we keep our current system and build only part of this?
Yes, and for many providers it is the right answer. Keep the maintenance system as the technician facing tool and the asset record, and build one layer above it owning the contract, the service level policy with pause rules and business calendar, the rate card, and the portal adapters.
That removes the two measurable costs, which are the dispatcher acting as middleware and the credits you cannot dispute, without asking technicians to learn a new mobile application in the same quarter.
Should we start with an MVP or build the full field service platform in one go?
Start with an MVP that can run one real crew for one real week: scheduling, dispatch, job completion with photos and signatures, and invoicing. That slice typically costs $40,000 to $70,000 and ships in about 12 weeks, and technician feedback then decides phase two. Teams that built the full platform up front reworked 30 to 40 percent of it after field use in Digital Heroes experience, which is the most expensive way to discover what dispatchers actually need.
Should I hire a freelancer or an agency to build my field service software?
An agency in almost every case, because a field service build spans a mobile app, a dispatch web console, a backend, offline sync, and accounting integrations, which is four or five specialties one person rarely covers. A freelancer is the right choice for a single integration or a well-scoped add-on under $15,000. The solo-built field service systems Digital Heroes inherits fail most often at handover, when the freelancer has moved on and nobody can safely modify the sync engine.
At what point does it make sense to switch from ServiceTitan to custom software?
The switch usually pencils out once your ServiceTitan bill passes roughly $75,000 a year and your team still maintains workaround spreadsheets beside it. ServiceTitan keeps pricing quote-only, and the quotes owners share in Digital Heroes scoping calls run several hundred dollars per technician per month on annual contracts, so a 30-technician shop can spend a full custom build's budget every 12 to 18 months in fees. If ServiceTitan fits your workflow cleanly, stay; the case for custom is a workflow the product forces you to bend.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
We're outgrowing Jobber. Should we move up to ServiceTitan or build our own?
Move to ServiceTitan if the problem is missing features on a standard residential trades workflow, because migrating between products is far cheaper than building. Build custom when the problem is fit: multi-day commercial jobs, subcontractor crews, or pricing rules that neither Jobber's Grow plan (about $199 per month billed annually, up to 15 users) nor ServiceTitan models cleanly. In Digital Heroes scoping calls, about half the teams asking this question turn out to need an integration or add-on rather than a new platform, so name the exact workflow gap before committing either way.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
Who can build a custom field service management software system?
Digital Heroes builds custom field service management software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other field service management software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
