How to Hire a Gas Measurement and EFM Software Development Company
Shortlist three vendors who have actually pulled records off ABB, Emerson and Thermo flow computers, and judge them on the edit trail rather than the dashboard.
On this page
Shortlist three vendors who have actually pulled records off ABB, Emerson and Thermo flow computers, and judge them on the edit trail rather than the dashboard. Expect $70,000 to $150,000 for a first release in 12 to 18 weeks, and $180,000 to $450,000 for a full measurement platform. If a quote omits validation policy discovery and a two-month parallel close, it is not a real quote.
What a gas measurement software company actually does
Buying electronic flow measurement software has more in common with commissioning a custody transfer meter than with buying an app. The output is not a screen, it is a number you invoice on. A two percent bias sits there quietly for months until somebody on the other side of the transaction goes looking for it, and by then the volume has already become a payment, a royalty decimal and a state report.
What makes this category hard to buy is that the difficulty is invisible from the demo. Every vendor can show you a map of meters and a green tick. What separates a real measurement build from a reporting tool is what happens on the ugly days: a flow computer whose clock ran backwards, an orifice plate swapped at 10:42 with no paperwork, a chromatograph result that lands three weeks late and invalidates a month you already closed. None of that appears in a sales meeting, and most buyers find out which kind of vendor they hired during their first counterparty audit.
The visible build is a polling service, an exception queue and a volume statement. That is roughly a third of the engagement, and it is the third that never overruns. The rest looks like this. A device profile per flow computer make and firmware generation, because an ABB Totalflow, an Emerson ROC and a Thermo AutoPILOT disagree about what a partial day is and about what happens to a record when a technician writes a configuration change mid-day. A written form of your validation and estimation policy, which today exists as one measurement technician's judgement and has to be extracted before anyone can code it. An append-only event store, so a meter-day is a raw record plus an ordered list of edits, each carrying an author, a reason and a supporting document. Recalculation under AGA and API methods with your operator options stored on every result. Composition and calibration records turned into dated structured series instead of PDFs on a share drive. And revision propagation, so a corrected composition in a closed month raises tasks against allocation and revenue detail. A vendor who scopes only the polling will hand you something that looks finished and cannot survive an audit.
What an EFM build really costs in 2026
These are Digital Heroes delivery bands, drawn from 2,000-plus projects rather than from a market survey.
| Project tier | Cost | Timeline |
|---|---|---|
| Single-vendor pilot: polling and normalisation across one flow computer make | $45,000 to $85,000 | 8 to 12 weeks |
| First release: multi-vendor polling, rule-driven validation, append-only edit trail, closeable volume statement | $70,000 to $150,000 | 12 to 18 weeks |
| Full platform: AGA and API recalculation, composition and calibration records, allocation, counterparty statements | $180,000 to $450,000 | 6 to 12 months |
| Support, device profile maintenance and enhancements | 18 to 22% of build per year | Retainer |
Two line items go missing from nearly every quote in this category.
The first is validation policy discovery. Your estimation rules are not written down anywhere. Somebody has to sit with the measurement tech for two to four weeks and turn sentences like the DP looked frozen against a well that should have been flowing into rules with a condition, a severity and a named estimation method. Vendors omit it because they assume you have a document. You do not. Budget it explicitly or it becomes the change order that sours the project.
The second is the parallel close. You do not cut a measurement system over cold, ever. You run the new close alongside the spreadsheet for two full month-ends, including one with a prior period adjustment in it, and you reconcile line by line. That is real engineering and analyst time in months four and five, after most vendors have booked their final milestone. Also watch the pricing behaviour around device support. A quote that says all major flow computers supported is quietly pricing one. Each additional make and firmware generation is weeks of work, not a configuration toggle, and it is the most common place a fixed price turns into a rate card.
Signals of a strong measurement partner
- They draw a meter-day before they draw a screen. If the first sketch is a table of volumes, you are buying a reporting tool. You want a raw record, an ordered event list, and a computed result carrying its calculation standard and method options.
- They name devices and describe what broke. Anyone who has genuinely done this talks unprompted about clock drift, record rollover, partial days and one particular vendor's event log format.
- They ask for your gas purchase contracts. Counterparty audit rights routinely go further than API MPMS Chapter 21.1 requires, and a partner who has been through an audit asks to read the clause before quoting the retention design.
- They treat composition as a dated series with a source. Chromatograph, lab and spot samples are different things with different effective-date behaviour, and a team that models them as one field will corrupt every recalculation.
- They refuse to replace Flow-Cal or PGAS reflexively. The honest read is that those tools parse device formats well. A good partner tells you which parts to keep and prices integration as the more expensive option it usually is.
- They put reproducibility in writing. Every recomputed value should store the standard, the operator options, the inputs and the version of the calculation code, so a number can be rebuilt exactly two years later.
- They insist on the parallel close in the plan, not as an option. A vendor who is relaxed about cutting over in a single month has never been on the phone with a revenue accountant in December.
Red flags on a measurement vendor
- All major flow computers supported, no list. Ask for makes and firmware generations by name. Vagueness here is the single most reliable predictor of overrun.
- Edits described as corrections. If a posted meter-day can be overwritten and the reason field is free text, you have built an audit finding with a login screen.
- AI volume prediction in the pitch deck. Anomaly detection against a meter's own history is genuinely useful after a year of clean data. A model that guesses volumes you bill on is not a product, it is exposure.
- No question about who validates. A vendor who never asks to meet your measurement tech is planning to build limit checks and call it validation.
- Hedging on the repository. Measurement software is your revenue recognition process. If a supplier holds the code, they hold your ability to defend a dispute.
Questions to ask on the first call
- Which flow computer makes and firmware generations have you polled in production, and what broke on each?
- How does a meter-day record store the difference between a raw value, an edit and a recomputed result?
- An orifice plate changed at 10:42 with no work order. What does the system do with the affected hours?
- We discover a bad chromatograph composition affecting three closed months. Walk me through what happens downstream.
- How do you distinguish a genuine shut-in from a plugged tap, and what data do you need to do it?
- What do you store so a volume can be reproduced exactly under audit two years from now?
- Are you replacing Flow-Cal or integrating with it, and what is the cost difference?
- How many weeks are you budgeting to write down our validation and estimation policy?
- What does the parallel close look like, and which of your people are on it in month five?
A simple way to decide
Do not pick a builder from proposals. Buy a paid discovery phase from your top two, three to four weeks each, and give both the same input: one full month of raw records from your three worst meters, your gas purchase contract, and an afternoon with the measurement tech. What you are buying is a written specification you own outright, containing the device profiles, the validation rules in your own language, the recalculation method options and the revision model. Take that document to any firm on earth. If neither vendor can produce it, you have learned something cheaply.
Digital Heroes works PRD-first for exactly this reason, and contracts through an India LLP, a US LLC or a UK LTD so the specification and the code assign under your own law rather than someone else's. The client owns the repository from the first commit.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Across 1,471 IT projects the average cost overrun was 27%, but one in six projects was a 'black swan' with an average cost overrun of 200% and a schedule overrun of nearly 70%. Source: Harvard Business Review (Bent Flyvbjerg & Alexander Budzier, University of Oxford) (2011) →
- OECD research finds that digitalisation offers SMEs opportunities to improve performance, spur innovation, enhance productivity and compete more evenly with larger firms; it reports that increased use of online platforms produced significant multi-factor productivity gains in SME-heavy sectors such as hospitality and retail, while smaller firms lag in adoption due to skills, resource and financing gaps. Source: OECD (2021) →
- In an RCT, the no-show rate was 23.5% for patients receiving a text-message reminder versus 38.1% for the control group - a 14.6 percentage-point reduction (p = 0.04). Source: Clinical Pediatrics / PubMed Central (Lin et al.) (2016) →
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
Frequently asked questions
How much does it cost to hire an EFM software development company?
A single-vendor pilot covering polling and normalisation for one flow computer make runs $45,000 to $85,000. A first release with multi-vendor polling, rule-driven validation, an append-only edit trail and a closeable volume statement runs $70,000 to $150,000 over 12 to 18 weeks. A full platform with AGA and API recalculation, composition and calibration records and allocation runs $180,000 to $450,000. Budget 18 to 22 percent of build cost yearly for support and device profile maintenance.
What should I check before signing with a gas measurement developer?
Ask which flow computer makes and firmware generations they have polled in production and what broke on each. A team with real experience talks immediately about clock drift, record rollover and partial days. Then ask them to describe a meter-day record. If they draw a table of volumes rather than a raw record plus an ordered event list plus a computed result with method metadata, they are quoting a reporting tool.
Why do EFM software quotes go over budget?
Two reasons dominate. Device support is quoted as though all makes are equivalent, when each additional flow computer brand and firmware generation is weeks of genuine integration work. And validation policy discovery gets left out, because vendors assume your estimation rules are documented somewhere. They are not, they live in one technician's judgement, and extracting them takes two to four weeks of interviews before anyone can write code.
Should we replace Flow-Cal or build alongside it?
Flow-Cal parses a wide range of device formats and recalculates competently against the standards, so rebuilding that is rarely sensible. The gap sits around it: validation that needs context Flow-Cal does not hold, and a defensible link between a billed volume and the composition record and calibration certificate behind it. Be aware that integrating with a system you do not control usually costs more than owning both sides, so make the vendor price both options.
Who owns the code and the measurement data after the build?
You should own the repository, the cloud accounts and the unrestricted right to appoint another firm, agreed in writing before kickoff rather than at handover. Measurement software produces the numbers you invoice and defend under counterparty audit, so a supplier holding the code holds your ability to reconstruct a disputed volume. At Digital Heroes the client owns the code from the first commit and can contract through an India LLP, a US LLC or a UK LTD.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
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 long does it take from first call to software my team can actually use?
Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
How many people should be working on my software project?
A typical $40,000 to $150,000 build runs on three to five people: a technical lead, one or two developers, a designer, and someone owning QA and project communication, often as overlapping part-time roles. More bodies do not make software arrive faster; past a point they slow it down with coordination overhead. The question that matters more than headcount is whether one named senior engineer is accountable for the outcome.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
Is it cheaper to customize Salesforce than to build a custom CRM from scratch?
If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.
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.
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.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
How do we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
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 run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Who can build a custom software system?
Digital Heroes builds custom 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 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 Oliver.
Senior Account Director · UK · London · 3 posts on the site
Published · Last updated .
