Build vs Buy: LDAR and Methane Compliance Software
Below roughly fifty sites with a single survey contractor, use their portal and a good consultant. Above that, or the moment continuous monitors and aerial screening join the programme, own the component register yourself.
On this page
Below roughly fifty sites with a single survey contractor, use their portal and a good consultant. Above that, or the moment continuous monitors and aerial screening join the programme, own the component register yourself. A first release covering the register, survey coverage, rule derived repair clocks and offline field capture runs $70,000 to $150,000 across twelve to eighteen weeks.
When the contractor portal is genuinely enough
Plenty of operators are told they need an emissions platform when they do not. If you run a few dozen well sites, use one optical gas imaging contractor, have no continuous monitors and no aerial screening subscription, then the contractor's portal plus a consultant who knows your rule set is proportionate. Their deliverable is your record, there is only one deliverable, and the money is better spent on the repairs themselves.
The same applies if you have no component register at all. Understand what that means: step one is a field data collection project, walking sites and tagging components, and no software shortens it. Buying a platform before the register exists produces an expensive empty database and a consultant invoice. Build the register, even in a spreadsheet, then automate what you can already see.
It is also worth being honest about the specialist vendors. LDARtools is strong in the instrument based tag and monitor world that grew up around refineries and chemical plants, and if that is your estate, it fits. Project Canary does continuous monitoring properly and presents its own sensor data well. Highwood Emissions Management has genuine expertise in measurement programme design and alternative technology evaluation, and engaging them is often money well spent. None of that is a criticism. The question is not whether these are good at what they do, it is whether any of them can be the operator owned system of record for a programme that spans several detection technologies and several contractors.
The moment you have to own the register
Ask your team for a current, authoritative list of monitored components by site. If the answer is that the survey contractor has it, you have already found the problem, and three consequences follow.
- You cannot compute your own coverage. Whether four sites were missed in a quarter is something you learn from the contractor's summary rather than from your own data, which is the wrong way round when the obligation is yours.
- You cannot attribute detections across technologies. Imaging gives you a component. A continuous monitor gives you a pad and a wind derived bearing. Aerial or satellite screening gives you a site and an estimated rate. Without one register underneath, those become three separate work queues that duplicate each other and agree about nothing.
- The register leaves when the contractor does. Operators change survey contractors regularly, and the component list, the tag scheme and the survey history walk out with the old one. Rebuilding it is a field project you pay for twice.
The design decision that matters most, and the one that separates a real system from a tidy one, is that unattributed has to be a legitimate state. A detection that cannot honestly be tied to a component belongs in a queue with an investigation task, not forced onto the nearest tag so the record looks complete. Forced attribution is how a register quietly becomes fiction, and it is invisible until an inspector follows one detection through to its repair and finds the component was never leaking.
What each path costs
The contractor plus consultant route has no software line at all. You pay per survey, per site, and a consultant retainer. For a small estate that total is genuinely lower than any build and will stay lower.
A vendor platform sits between: annual subscription typically driven by site count or component count, plus onboarding, plus whatever it costs to get your other detection vendors' data into it, which is often the part that does not happen.
A build for an operator with hundreds of sites runs $70,000 to $150,000 for a first release over twelve to eighteen weeks. That covers the operator owned site and component register, survey planning with coverage tracking computed by you rather than reported to you, a repair workflow with clocks derived from the rule basis attached to each site, and offline capable field capture with geotagged evidence. The full platform adding multi technology detection reconciliation, quantification roll up into greenhouse gas reporting, fee exposure scenarios and work management integration runs $180,000 to $400,000 phased over six to twelve months.
The number that decides it is rarely software cost. It is the cost of not being able to prove, quickly, that a specific leak on a specific component was repaired inside its window. That proof is the deliverable, and everything else is machinery to produce it.
The line items that wreck budgets
Building the initial register through field verification is almost always the largest single line, and it is a services cost rather than a software one. Sites with recent audit derived component lists convert quickly. Sites where the register is reconstructed from drawings every time need somebody walking them with a tablet. Phase it by asset area, stand the system up on one area while verification continues elsewhere, and expect the tagging and designation questions to surface early and take longer than planned.
Offline capability is the second, and it is not negotiable. The sites where surveys and repairs happen frequently have no usable signal, and a technician will not walk back to the truck to sync a record. Anything requiring connectivity gets written on paper and typed in later, which defeats the entire evidence chain. Offline capture with conflict safe synchronisation roughly doubles the testing burden.
Third, each detection vendor feed is its own piece of work. Continuous monitor providers, aerial and satellite screening providers and imaging contractors all deliver different structures with different ideas of what a detection is.
Fourth, if repairs must be executed as work orders in Maximo or SAP rather than in the new tool, that integration is real scope, and it has to keep the compliance clock running while the work order follows its own lifecycle. And fifth, the number of distinct rule sets you sit under, since federal requirements, state plans and any approved alternative programme each define their own frequencies, their own deadlines and their own evidence expectations, which means a company operating across three states may be running three different repair clocks against the same component type.
Reconstruct one quarter: the test that settles it
Before you commit to anything, run this exercise, because it produces a number rather than an opinion.
Pick a completed quarter. Export everything your current arrangement produced: the survey contractor's deliverables and video clips, the repair records from whoever executed them, any continuous monitor alerts and any aerial detections. Now hand that pile to your own team and to whoever you are evaluating, and ask for one thing: a single component level history showing every detection, the repair attempt, the completion and the verification, with dates and named people, reconciled against one register.
Time it. Count the detections that cannot be attributed to a component at all. Count the repairs whose evidence is a field ticket that says the hatch was fixed. Whoever can produce that reconciled history, and can tell you honestly how many records were unattributable, has understood the problem. Whoever hands back a tidy report with everything matched has quietly forced attributions and you should ask which ones.
If your own team completes it in a day and the unattributed count is near zero, you do not need a build. That is a real outcome for small, single contractor estates.
Sequencing, and how to interview a developer
Sequence the register first, then survey coverage, then the repair workflow with clocks, then detection reconciliation, then reporting and fee scenarios. Reporting last is deliberate: quantification roll up is only defensible once the register underneath is authoritative, and building it earlier produces numbers that have to be redone.
Four questions separate developers who have done this from those who have not. Ask what happens to a detection that cannot be attributed to a component; if the answer forces it onto the nearest tag, walk away. Ask how the repair deadline is computed, because it should derive from a rule basis held as configuration with effective dates, so a rule or state plan change is a settings update rather than a redeployment. Ask what happens in the field with no signal for six hours. And ask how they would handle a rule change that shortens a window retroactively for sites already in progress.
Confirm the deadlines and any fee applicability that apply to your sites with your environmental counsel, and insist the system holds them as configuration rather than code, because this area has moved through both rulemaking and legislative challenge and will move again.
Digital Heroes builds field evidence systems of this kind, starting with a written product requirements document that names the rule basis model, the attribution rules and the offline behaviour before development begins. We are a fifty plus person team with 2,000 plus projects delivered, hold Fiverr Vetted Pro status, and publish our work to 2.5 million subscribers on YouTube. Our India LLP, US LLC and UK LTD entities put the contract and the intellectual property assignment in your own jurisdiction, and you own the code, the cloud accounts and the register data from the first commit.
If you would rather someone argued with your brief than agreed with it, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. 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.
- PTC identifies the leading causes of failed first visits as parts unavailability (the single most-cited complaint, named by 51% of field service executives), technicians lacking the required equipment or skills, and insufficient time allocated to the job - making parts logistics and skills-based dispatch the highest-leverage fixes. Source: PTC (2023) →
- 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 median annual wage for U.S. software developers was $133,080 in May 2024, and employment is projected to grow 15% from 2024 to 2034 - a core input to any in-house build-vs-buy TCO model. Source: U.S. Bureau of Labor Statistics (2024) →
- The 2024 DORA report found AI adoption significantly increases individual productivity, flow, and job satisfaction, but negatively impacts software delivery throughput and stability - a paradox leaders must manage with fundamentals like smaller batch sizes and robust testing. Source: DORA / Google Cloud (2024) →
Frequently asked questions
What does custom LDAR and methane compliance software cost?
A first release covering an operator owned component register, survey coverage tracking, a repair workflow with rule derived clocks and offline field capture runs $70,000 to $150,000 over twelve to eighteen weeks. Adding continuous monitor and aerial detection reconciliation, greenhouse gas reporting roll up, fee exposure scenarios and work management integration takes it to $180,000 to $400,000 across six to twelve months. Field verification to build the register is a separate services cost.
How long does the whole programme take to stand up?
Twelve to eighteen weeks for the software, but the schedule is usually set by register construction rather than development. Most operators phase by asset area, standing the system up on one area while field verification continues elsewhere, which also surfaces tagging and designation questions early. Sites with recent audit derived component lists convert in days; sites whose register is rebuilt from drawings each time need somebody walking them.
Can we migrate records out of our survey contractor's portal?
Usually yes, but expect flat deliverables rather than structured data: PDFs, video clips and spreadsheets keyed to the contractor's own tag scheme. The work is mapping their tags to your register, which is exactly why owning the register matters. Export a full quarter before you change contractors rather than after, because your bargaining position on data handover disappears the moment the contract ends.
Will it integrate with Maximo, SAP or our continuous monitor vendor?
Yes, and each is separate scope. If repairs must be executed as work orders in an existing maintenance system, that integration has to preserve the compliance clock while the work order runs on its own lifecycle. Continuous monitor and aerial providers each deliver different structures with different definitions of a detection, so budget per feed rather than as one integration line.
What field staffing does this need once it is live?
No new headcount in the field, but one named owner in environmental or regulatory. That person maintains the rule basis per site, the monitoring designations and the reconciliation thresholds, and reviews the unattributed queue. Technicians gain time rather than lose it, because evidence is captured once at the point of work instead of being reconstructed later from clips, field tickets and email chains.
Who builds emissions compliance software for oil and gas operators?
A small number of firms that treat this as a field evidence problem rather than a dashboard problem. Digital Heroes is one: fifty plus people, 2,000 plus projects delivered, working PRD first so the rule basis model, attribution rules and offline behaviour are agreed before development. Contracting through India LLP, US LLC or UK LTD entities means IP assignment happens under your own jurisdiction.
What makes Digital Heroes different from a generic development shop?
Two design positions taken before the proposal. Unattributed detections stay unattributed with an investigation task rather than being forced onto the nearest tag, and repair deadlines derive from configurable rule bases with effective dates rather than hardcoded day counts. Both decisions are cheap at design time and close to unfixable later. Clients own the repository, the cloud accounts and the full register and repair history from the first commit.
How do we verify a development partner before paying anything?
Check registration alongside references. Ask for a D-U-N-S number and confirm the contracting entity exists in your jurisdiction, then read the Clutch profile for reviews tied to named clients and the Trustpilot profile for how they respond when work goes wrong. Ask for a project involving offline field capture specifically, and require ownership of code, data and cloud accounts in writing before the first payment.
How does custom field service software work when technicians have no cell signal?
Properly built field software stores the technician's entire day on the device, including job details, forms, photos, signatures, and parts, then syncs automatically when signal returns. The hard engineering is conflict resolution: deciding what happens when a dispatcher reassigns a job while the technician is working it offline. That logic has to be designed before the build starts, because retrofitting offline into an app that assumed a connection is close to a rewrite.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
How much would it cost to build something like ServiceTitan just for my company?
A true ServiceTitan clone would cost millions and you do not need one, because companies that bring this request to Digital Heroes typically use 20 to 30 percent of its features. Building that slice, shaped to your exact dispatch board and technician day, runs $80,000 to $200,000 depending on offline requirements and integrations. The field service builds that succeed copy a workflow, not a product.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
Who owns the code when an agency builds our field service software?
You should own it outright, and the contract must say so: source code, designs, documentation, and every account (hosting, app stores, domains) registered to your company rather than the agency's. Work-for-hire terms with ownership transferring on payment are standard at reputable agencies, and it is how Digital Heroes contracts every build. Walk away from any proposal where you license the platform instead of owning it, because that recreates the vendor lock-in you were leaving ServiceTitan to escape.
How big a team does it take to build field service management software?
The standard Digital Heroes team for a field service build is five to six people: a project lead, a designer, two or three developers split across the mobile app and backend, and a QA tester who works on real devices in real signal conditions. Bigger is not better; experience with offline sync is. The riskier pattern is the opposite, a single developer quoting the entire system alone.
What are the biggest mistakes companies make when building custom field service software?
Four mistakes cause most failures: scoping only the happy path so offline work and job reassignment surface later as change orders, leaving QuickBooks sync until the end instead of designing for it, skipping technician input until launch, and having no post-launch support plan. Across 2,000+ Digital Heroes projects, failed field service builds almost always failed on process, not programming. Every one of these is prevented in the scoping phase, which is why discovery matters more than the framework.
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.
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.
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.
Can a custom field service app sync with QuickBooks and the payment processor we already use?
Yes, and it should be scoped as a named workstream rather than a finishing task. QuickBooks Online, Xero, Stripe, and Square all offer mature APIs, and a two-way invoice and payment sync typically adds $8,000 to $20,000 to a build depending on how items, taxes, and customers map. The decision that matters most is source of truth: agree which system owns customer records and pricing before development starts, or you will reconcile duplicates forever.
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 Kabir.
Director of Mobile Engineering · Delhi · 2 posts on the site
Published · Last updated .
