Gas Leak Survey Software: Buy OPTIMAIN, or Build the Coverage Proof Yourself?
Miles of main and the number of rule sets you carry decide this, not leak volume.
On this page
Miles of main and the number of rule sets you carry decide this, not leak volume. Under roughly a few hundred miles of main with one survey crew, one state jurisdiction and one detection method, buy, and most distribution operators in the country sit exactly there. Past roughly 2,000 miles, or the moment you carry two state codes, or the moment walked survey and advanced detection have to reconcile into one coverage answer, a custom layer starts to earn its place. Note the shape of that: it is a layer over your detection providers and your geographic information system, not a replacement for either.
When is off the shelf genuinely the right call here?
If you run a small municipal or cooperative system, a few hundred miles of main, one survey crew, one state code and a leak backlog a supervisor can hold in their head, do not build. A disciplined spreadsheet and a survey supervisor who actually walks the routes will cover it, and the money is better spent on detection equipment and a second technician. We say this often enough that it is worth putting first.
The packaged options here are real. Heath Consultants sells OPTIMAIN, which is the closest thing the market has to a survey and leak management product, and it is naturally organised around Heath instruments and Heath survey services. If your programme already runs through one provider end to end, that alignment is a feature rather than a limitation, and buying it is the cheaper and faster answer. SENSIT and Heath both build the handheld instruments crews carry, and those instruments come with their own logging and their own record formats.
Buy, or rather stay bought, if your survey is fully outsourced. A contractor who walks your system and hands you their own coverage record is providing the evidence as part of the service. If your state inspector accepts that record today, you have no problem worth funding a build to solve. Buying detection capability is a separate question and usually a better one: Picarro mobile analysis, ABB Ability MobileGuard and Bridger Photonics aerial survey all find leaks an older walking instrument would miss, and adopting one of them is a stronger use of capital than any software project on this page.
The honest test is whether you can answer a coverage question for a single district without anyone reconciling route sheets against the pipe data by hand. While that answer is yes, you have not outgrown what you can buy.
When does a custom build actually pay off?
The signals are operational and easy to check this week rather than theoretical.
Somebody reconciles completed route sheets against the geographic information system by hand to answer a coverage question, and that exercise takes days rather than minutes. You run two or more detection technologies, so walked survey findings live in one place and mobile or aerial indications live in another. You operate across more than one state, so survey intervals, grading definitions and repair timelines differ by district and each is a separate rule set. Repair deadlines are invisible to whoever schedules the crews, so leaks get repaired late by accident rather than by decision. Grading varies between crews and nobody can quantify by how much. Or your main replacement programme is prioritised on pipe vintage alone, because leak history is not usable at segment level.
The root cause behind all of those is the same. Routes were drawn once. The system has changed since through replacements, extensions, new services and abandonments, and the route sheet still says what it always said. Coverage proof organised by street does not answer a question asked by pipe segment, and no packaged tool can close that gap for you because the gap lives in your own pipe data and your own route history.
The second reliable trigger is a mixed detection estate. A vehicle mounted analyser or an aerial pass covers a wide swathe. A walked survey covers a route. Reconciling those two coverage models into one defensible statement about a segment is genuine design work, and it is specific to which technologies you use and where you use them. Vendors have no commercial reason to reconcile their coverage model against a competitor's, so that join stays open by design.
The strongest trigger in practice is an inspection finding on coverage proof. That converts an internal irritation into a dated commitment with a regulator watching, and it is the point at which most utilities stop discussing this and fund it.
How do they compare on the things that matter in this industry?
Feature grids miss the point here, because the constraint sits between the products rather than inside any one of them.
- Coverage model. Packaged survey management records that a route was completed. What an inspector asks is whether a specific main and the services off it were surveyed within the required cycle. Tying survey activity to segments with effective dates is the difference, and it costs $20,000 to $35,000 to build properly.
- Detection vendor diversity. Each detection provider delivers indications in its own structure on its own cadence with its own spatial precision. Onboarding each one runs $8,000 to $16,000. A product organised around one vendor's instruments will always treat another vendor's output as an import rather than as a first class source.
- Grading capture. A free text grade field records the conclusion and loses the reasoning. Recording the readings and observations the grade definition depends on, proposing a grade from them, and capturing overrides with a reason is $12,000 to $22,000 of work, and the override data is what makes crew inconsistency visible at all.
- Clock visibility. Repair clocks by grade belong in the scheduling view, not only in a compliance report. This is a workflow boundary rather than a feature, and it is exactly the boundary that packaged products struggle to cross because scheduling usually lives in the work management system.
- Multi state rule sets. Survey cycles, grading definitions and reporting formats vary by state code. A configuration ceiling here is a hard one: if the product models one rule set, a second state means a second instance and a manual merge.
- Data portability. Leak records are regulatory evidence with a long retention life, and they feed replacement decisions for decades. Ask any vendor what a full structured export looks like before you sign, not after.
What does total cost of ownership look like at your scale?
From Digital Heroes delivery experience the bands are consistent. A survey record with grading and repair clocks runs $40,000 to $70,000. A first production release adding segment level coverage proof against the geographic information system, offline field grading and instrument log ingestion from one or two detection technologies runs $70,000 to $140,000 and ships in 12 to 16 weeks. A full platform adding lost and unaccounted for gas and methane reporting, work order integration and leak history driven replacement prioritisation runs $180,000 to $420,000 across 6 to 12 months.
On the running side, plan for 15 to 20 percent of build cost a year as a support retainer, $6,000 to $18,000 a year for state rule changes, $5,000 to $12,000 for synchronising against a geographic information system that gains and retires mains continuously, and $4,000 to $10,000 for hosting and evidence retention. Each additional detection platform adopted adds its own $8,000 to $16,000 to onboard.
Set that against what you keep paying either way. Detection instruments, vehicle mounted analysers and aerial survey services sit outside the software and usually cost more than it. If you keep a packaged product in the picture, its licence continues alongside the build. The comparison that matters is not build against buy in the abstract, it is the annual cost of the layer against the days of manual reconciliation, the risk carried by a coverage answer nobody can reproduce, and the replacement capital currently allocated on vintage alone.
What does the hybrid look like, and when is it the honest answer?
For most utilities in the middle of this range the hybrid is the recommendation rather than a compromise. Keep what you have bought and build the join.
The clean split is this. Detection providers keep doing detection: Picarro, Bridger, your mobile survey contractor and your handheld instruments all keep producing indications, and none of that changes. If you run OPTIMAIN or a contractor record for the survey management side, keep it. The custom layer owns three things nobody else will own for you: coverage resolved against pipe segments with effective dates, the graded leak record with its clock and its evidence, and the reporting your state actually asks for.
That split works because the boundaries are clean and the interfaces are files rather than deep integrations. Indications arrive as exports. Pipe segments arrive from the mapping team. Repairs go out to the work management system and completion comes back. Nothing in the middle requires a vendor's cooperation, which is why the layer survives a change of detection provider.
The smallest useful version of the hybrid is the coverage engine alone, run over last year's survey data and compared against what you reported to the state. That is the cheapest possible test of whether your coverage logic matches the way your inspector reads the regulation, and it has a habit of finding segments reported as surveyed that were not. Add the graded leak record and clocks second, and leave replacement prioritisation until you have a year of clean segment level history to prioritise against.
Which should you choose, by operator size and stage?
Under a few hundred miles of main, one crew, one state: buy, or stay manual and spend the money on detection equipment. Nothing else here applies to you yet.
Survey fully outsourced to a contractor whose record your inspector accepts: buy, and revisit only if you bring survey in house or your inspector starts asking for segment level proof.
Roughly a few hundred to 2,000 miles, single state, one detection technology: buy the packaged product and measure one thing. Time how long it takes to prove coverage for one district by segment. If that is under a day, keep configuring. If it takes a week, you are already paying for the build in salary.
Above roughly 2,000 miles with two or more detection technologies: build the layer. This is the population where the manual join has become a permanent job and where a mixed detection estate has no packaged answer.
Multi state operators of any size: build, and build the rule model first. Two state codes in one product is where configuration ceilings show up fastest, and a second instance with a manual merge is not a coverage answer.
Post acquisition utilities: build the leak record layer before anything else. Two survey histories in two formats over one pipe network is exactly the problem a layer solves and a product does not.
Anyone carrying an open inspection finding on coverage proof: build, start with the coverage engine, and put a cycle boundary date in the plan before the regulator picks one for you.
When you are ready to turn this into a specification, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- IBM frames first-time fix rate as a core field service KPI, noting the industry average sits around 80% (roughly one in five jobs needs a return visit). Correction: IBM cites best-in-class providers at 89-98%, not '85%+'. Source: IBM (2024) →
- Comparesoft reports the field-service industry-average first-time fix rate is about 80%, best-in-class providers reach roughly 90%, scores below 70% put the business at risk, and providers exceeding 70% FTFR saw customer retention around 86%. Source: Comparesoft (2024) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
Frequently asked questions
What does it cost to switch away from OPTIMAIN or a contractor record later?
The cost is proportional to how much of your leak history lives inside the product rather than beside it. Open leaks always have to move and that is manageable. Closed leak history going back a decade is where the effort concentrates, and it only justifies the cleanup if replacement prioritisation depends on it.
The practical protection is to ask for a full structured export before you sign anything, and to test it once a year rather than on the day you need it. If a layer already holds a synchronised copy of segments, coverage and graded leaks, switching detection or survey management vendors becomes a procurement decision instead of a migration project.
What happens if our survey contractor or software vendor changes pricing?
Model it against your projected mileage and crew count rather than today's, because growth is what changes the answer more than any single price rise. Survey services and detection contracts usually move together, and a repricing on the services side dwarfs anything on the software side.
Owning the coverage and leak record does not remove those costs, since you are keeping the detection providers. It does mean a repricing becomes a commercial negotiation instead of a hostage situation, because your compliance evidence no longer lives inside the thing you would be leaving.
How long does a leak survey build take, and when should we go live?
A first production release covering segment level coverage proof, offline field grading and instrument log ingestion ships in 12 to 16 weeks, in Digital Heroes delivery experience. A full platform with emissions reporting and replacement prioritisation runs 6 to 12 months of phased delivery.
The go live date matters more than the duration. Aim for a survey cycle boundary, and give field crews the application on at least two weeks of low stakes routes first. Handing a technician a new tool on a compliance critical day is the fastest way to lose credibility with the crews you need on side.
Is Heath OPTIMAIN enough, or do we need something custom?
For a single state operator running Heath instruments and Heath survey services end to end, it is generally enough, and we would tell you so rather than sell you a project. That alignment between instrument, service and record is the whole point of buying it.
Where it strains is a mixed estate. If some of your miles are walked with one instrument, some covered by a vehicle mounted analyser under contract with another provider and some by aerial survey, you are asking one vendor's product to reconcile coverage models it was never built to reconcile. That reconciliation is the thing worth owning, not the survey management around it.
Do we need to fix our pipe data before we build anything?
Usually yes, and it is often the better first investment on its own. Segment level coverage proof is only as good as the mains and services underneath it. If material, install date and service line locations are accurate, coverage becomes a query. If they are not, the software will spend its life reporting gaps that are really mapping gaps.
The cheap diagnostic is to export one district's segments and try to prove last cycle's coverage against them by hand. Whatever that exercise finds is the mapping work you owe yourself before any build, and however long it takes is the size of the problem you would be buying out of.
How do we handle two states with different survey and grading rules?
Model the rules as data rather than as code paths, so survey interval, grading definition and repair timeline are attributes of a jurisdiction that a segment belongs to. Adding a third state then becomes a configuration exercise rather than a release.
This is the specific point where packaged products tend to hit a configuration ceiling, because most were designed around one rule set and a second state means a second instance with a manual merge at reporting time. If you are a single state operator and expect to stay one, this argument does not apply to you and you should discount it.
Can a build actually reconcile aerial or mobile survey against walked coverage?
Yes, but honestly rather than automatically. A wide swathe pass and a walked route are different coverage models, and the reconciliation rule has to be written down and agreed with your own compliance people before anyone codes it. That agreement is the work; the software is the easy part afterwards.
What the layer does well is keep both models visible on the same segment, so a supervisor can see that a length of main was covered by mobile survey in March and by a walked survey in September, and the regulatory requirement can be evaluated against whichever the state code actually recognises.
Who owns the leak records and the code if we hire an agency?
You should own the repository, the database, the cloud accounts and a working export path, agreed in writing before kickoff. At Digital Heroes the client owns everything from the first commit, and we would advise walking away from any developer who hedges on it.
The reason is specific to this category. Leak records are regulatory evidence with a long retention life and they feed replacement decisions for decades. Access to your own compliance history cannot depend on a vendor relationship staying healthy, because the day you need it most is the day the relationship is under strain.
Will custom field service software scale if we grow from 10 technicians to 100?
Yes, when it is architected for growth from day one, and scale is where custom wins because cost per technician falls as you add crews instead of rising with every seat license. The real scaling work is operational: multi-branch dispatch, role permissions, and roll-up reporting, which usually arrives as a phase two costing 30 to 50 percent of the original build. State your three-year headcount plan in the first scoping call so the data model supports branch two before branch two exists.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
What does it cost per year to maintain custom field service software?
Budget 15 to 20 percent of the original build cost per year, so $15,000 to $20,000 on a $100,000 platform. That covers hosting, security patches, integration API changes, a monthly block of small improvements, and the iOS and Android updates Apple and Google ship on their own schedule. Skipping it is not a savings; the technician app needs attention every OS cycle or it eventually stops opening on new phones.
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.
Do my field technicians need a native mobile app, or will a web app work?
If your technicians ever work in weak signal, you need a native or offline-capable app, because a plain web app fails exactly where field work happens: basements, mechanical rooms, and rural routes. Cross-platform frameworks like React Native or Flutter give one codebase for iPhone and Android with full offline storage, which is how Digital Heroes builds most technician apps. A web app is the right call for the office dispatch console, where connectivity is guaranteed.
How long does it take to build a custom field service app with scheduling, dispatch, and a technician mobile app?
Plan on 12 to 16 weeks for a working first release covering scheduling, dispatch, and a technician mobile app, and 5 to 7 months for a full platform with offline mode and accounting sync. Across 2,000+ Digital Heroes projects, field service timelines slip in two predictable places: underscoped offline behavior and integration testing against QuickBooks or the payment processor. Both belong in week one of planning, not month four.
What should I have ready before I contact a development agency about field service software?
Bring your current workflow, not a feature list: how a job moves from first call to paid invoice today, where it breaks, what tool you use now with its monthly bill, and the workaround spreadsheets your team maintains. Add your integration list (accounting system, payment processor, phone system) and an honest budget range. A good agency can scope accurately from that in one or two calls, while a vague request for an app like ServiceTitan costs you weeks of discovery.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
Is Housecall Pro enough for a growing HVAC or plumbing company, or do we need custom software?
Housecall Pro holds up well to roughly 10 to 20 technicians on standard residential jobs, with its Essentials plan listing around $129 per month for up to five users. The ceiling appears with commercial work: multi-visit projects, progress billing, equipment service history, and inventory are thin, which is when owners start managing the business in exported spreadsheets. Use the spreadsheet count as your signal: three or more recurring workarounds mean the tool no longer fits.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
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
More from Vivaan.
Senior Backend Engineer · Node · Delhi · 2 posts on the site
Published · Last updated .
