Build vs Buy Oil and Gas Production Allocation Software: Who Should Own the Back Allocation Math
Buy in this category unless you have a specific reason not to. ProCount, Enertia and Energy Components allocate correctly, and a conventional operator under roughly 150 wells should not rebuild them.
On this page
Buy in this category unless you have a specific reason not to. ProCount, Enertia and Energy Components allocate correctly, and a conventional operator under roughly 150 wells should not rebuild them. Build when allocated volumes must satisfy five separate systems and a person coordinates them by hand: a first release runs $90,000 to $180,000 across sixteen to twenty two weeks.
Buying is the default here, and it should be
Back allocation is regulated arithmetic with decades of packaged software behind it. Quorum ProCount is the most widely deployed field data capture and production accounting system in North American operations and it does allocation properly. Enertia integrates production accounting with the general ledger in one system, which is a genuine advantage for a smaller company. TietoEVRY Energy Components handles complex processing and ownership structures for large international operators. eLynx does field data acquisition and SCADA hosting well, and feeds allocation with clean measurement.
If you run under roughly 150 wells on simple facilities, with no processing plant contract to reconcile and no working interest partners with audit rights, buy. The packaged system will cost a fraction of a build, it comes with people who have configured a hundred of them, and your production accountant will be productive in weeks rather than months. Building in that position is spending capital to reproduce something that already exists and already passes audit.
Buy also when the honest problem is knowledge concentration rather than software. If one person understands your allocation and the fear is that they leave, the fix is documentation and a second trained accountant, not a development project. Software will not encode judgement that has never been written down, and the discovery phase of a build will simply expose the same gap at a higher cost.
One caution about the buy side that rarely appears in a quote. Allocation configuration in the major packages is specialist work, and changes tend to route through consultants at daily rates. Ask any vendor what a facility reconfiguration costs and how long it queues, because the answer is part of the total price and almost nobody puts it in the comparison.
The specific failures that justify owning the math
The build case is narrow and it is about coordination rather than calculation. The same allocated barrel has to satisfy an allocation engine, a revenue distribution system, a state production report, a working interest partner reconciliation and a reserve database. When those five things live in five places, the coordination logic between them becomes the actual job, and today that logic is a person with a spreadsheet.
The first failure is effective dating. Facilities change: a well is rerouted to a different separator, a battery ties into a new sales point, gas lift injection starts so some measured gas is recycled rather than produced. In a spreadsheet, editing the tree silently rewrites how prior months would calculate, which is why nobody reruns them. An owned system preserves the configuration that applied in June, so a June rerun in March produces June's answer rather than today's answer applied to old data.
The second is the well test. Every allocated volume traces back to a test rate, and in most operations the test register is a tab with no rule about what makes a test valid. A four hour test on a slugging well is treated identically to a stable twenty four hour test. Acceptance criteria, reject reasons, automatic test selection by rule and recorded overrides remove the most common source of royalty disputes, because you can finally answer why a well carries a given rate for a given month.
The third is the prior period adjustment. A correction should produce a new run whose output is a delta, with the originally filed month left untouched forever. Editing a closed month in place is how a correction becomes a restatement, and it is the single most common design mistake in home built allocation.
The fourth is the gas plant statement, which arrives weeks after the month, in the processor's own format, showing plant volumes, shrink, thermal reduction and product yields that will never match yours. Reconciling it is one of the few places in an operator where software finds cash rather than saving hours.
The five year cost of each path
On the buy side, count licence, implementation, annual support and the consulting line for configuration changes. A mid size operator commonly carries a packaged production accounting system plus a warehouse for analytics, because getting granular data back out for engineering usually means nightly extracts you then maintain anyway. That warehouse is part of the buy cost even though it never appears in the vendor proposal.
On the build side, a first release covering an effective dated allocation network, a governed well test register, measurement ingestion from your flow computers and a monthly allocation that reconciles to the sales meter runs $90,000 to $180,000 across sixteen to twenty two weeks. A full production accounting build adding plant settlement reconciliation, prior period adjustment handling, severance tax and state regulatory filings, and revenue and joint interest billing volumes runs $250,000 to $600,000 phased over nine to eighteen months.
Cost rises with the number of states you file in, since each defines its own production report and severance calculation. Gas processing complexity raises it further, particularly multiple plants with different contract structures. Federal and tribal leases add their own reporting obligations. Historical conversion is its own project, because loading and validating several years of prior allocations is work you will want done for the reserve database.
Cost falls sharply with a narrow first release: one state, one plant contract, and a decision to leave revenue distribution in the existing system while the allocation engine proves itself in parallel. Add fifteen to twenty percent of build cost annually for hosting, support and continued development.
What the quote leaves out
Four items. The first is parallel running. The allocation engine should run beside your current process against the same source data for two or three months while the production accountant compares outputs line by line. That is where the undocumented rules living inside the workbook surface, and it is unbudgeted labour on your side rather than the developer's.
The second is measurement data handling. Electronic flow measurement carries an expectation that the original value is preserved alongside any edit and the reason for it, consistent with electronic flow measurement practice under API 21.1. That audit trail is exactly what an examination looks at, and building it after the fact means reworking your ingestion layer.
The third is the reserve database consequence. Your allocation history is what a reserve auditor ties to, and what a bank lends against. If historical conversion produces volumes that do not match what was filed, you have created a reconciliation problem that lands in front of an auditor rather than an engineer. Validate the conversion against filed reports, not against the spreadsheet that produced them.
The fourth is discovery time on contracts. Shrink terms, thermal reduction and settlement structures live in executed processing and marketing agreements that in many operators nobody has read since the deal closed. Someone has to read them, and that someone is usually your commercial lead rather than the development team.
A single battery test
Before you commit either way, take one battery with a shared sales meter and a plant contract, and ask whoever you are evaluating, vendor or developer, to model just that battery end to end and reproduce last June to the barrel.
The exercise answers more than a proposal does. If they can reproduce a filed month using the configuration that applied at the time, they understand effective dating. If they ask what makes one of your well tests valid, they understand where allocation actually comes from. If they ask how the plant statement for that month reconciled, they understand where the money is.
Alongside that, answer four questions internally. Do you file in more than one state? Do you deliver to a gas plant under a percent of proceeds or keep whole arrangement that nobody reconciles? Has a plant restatement ever forced you to redo several months? And does your allocation math live in a workbook that only one person can explain?
Two or more yes answers, with more than roughly 150 wells, is a real build case. One yes is usually a process fix: write the rules down, train a second accountant, and negotiate a configuration retainer with your existing vendor. None means keep what you have.
Phasing, and how to interview a developer
The safe phasing is allocation engine first, everything downstream later. Run it in parallel for two or three months against the same inputs, compare outputs with your production accountant, and only make it the source once the numbers agree. Then feed volumes to your existing revenue and billing systems through an interface. Replacing revenue distribution is a separate decision with a separate budget, and doing both at once is how operators end up unable to close a month.
When interviewing, ask them to draw the allocation model on a whiteboard before you sign. You want effective dating on the network, a test record with validity rules, and an immutable run output. A team that draws wells and volumes with no notion of time validity will build you a faster spreadsheet.
Ask what happens when a June test is corrected in March, and accept only the answer that a new run produces a delta while June's filed output stays untouched. Ask whether they have handled electronic flow measurement data and what they do about edits, because preserved original with a recorded reason is the only acceptable design. Ask who owns the code, the cloud accounts and the production data, and get it in writing before kickoff, since your allocation history is evidence in royalty and partner audits for years.
Digital Heroes works from a written product requirements document before any code, which in this category means the allocation network, test validity rules and prior period behaviour are settled on paper with your production accountant. The team is fifty plus people across more than 2,000 delivered projects, holds Fiverr Vetted Pro status, and publishes to 2.5 million subscribers at Digital Marketing Heroes on YouTube. Contracting runs through an India LLP, a US LLC or a UK LTD, and the client owns the repository and the data from the first commit.
If you want that decision made properly rather than quickly, 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 keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Organizations that scaled intelligent automation report an average cost reduction of 32% (up from 24% in 2020), and respondents expect an average 31% cost reduction over the next three years. Source: Deloitte (2022) →
- Widely cited benchmarks place skilled manual data-entry error rates at roughly 0.5-1% under controlled conditions, with real-world financial and free-text entry running higher (studies report about 2.5% for structured numeric fields up to ~4.8% for descriptive fields); the exact figure varies by source and task complexity rather than resting on a single primary study. Source: Lido / industry benchmark research (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) →
- An EY survey found one in five U.S. payrolls contains errors, each costing an average of $291 to remediate, with a typical 1,000-employee organization spending roughly 29 workweeks per year fixing common payroll errors. Source: EY (Ernst & Young) (2022) →
Frequently asked questions
How much does custom production allocation software cost?
A first release covering an effective dated allocation network, governed well tests, flow computer ingestion and monthly allocation that reconciles to the sales meter runs $90,000 to $180,000 across sixteen to twenty two weeks. Adding plant settlement reconciliation, prior period adjustments, severance tax and state filings, and revenue and billing volumes takes it to $250,000 to $600,000 over nine to eighteen months. Multiple filing states and several plant contracts move the number most.
Is Quorum ProCount enough, or should we own the allocation math?
ProCount allocates properly and is the most widely deployed system in North American operations, so a conventional operator should buy. The build case appears when the same allocated volume must satisfy an allocation engine, a revenue system, state filings, a partner audit and a reserve database that all sit in different places. Many operators keep the packaged system and build only the reconciliation and reporting layer around it.
How long does implementation take and what causes delays?
A first release ships in sixteen to twenty two weeks when facility configuration and contract terms are documented. The schedule risk is almost never engineering, it is discovery: allocation rules that exist only as a formula in a workbook, shrink terms in processing contracts nobody has read since the deal closed, and well test practices that vary by field. Operators who hand over current facility diagrams and executed contracts at kickoff move faster.
Can we keep our existing accounting system and replace only the allocation?
Yes, and that is usually the right phasing. Run the new engine in parallel against the same source data for two or three months while your production accountant compares outputs, which surfaces the undocumented rules living in the spreadsheet. Once outputs agree, the engine becomes the source and feeds volumes to your existing revenue and billing systems through an interface. Replacing revenue distribution is a separate budget and a separate decision.
What happens to historical allocations when we convert to a new system?
Historical conversion is its own project, and it should be validated against what was actually filed rather than against the spreadsheet that produced it. Your allocation history is what a reserve auditor ties to and what a bank lends against, so volumes that fail to match filed reports create a reconciliation problem in front of the wrong audience. Budget the conversion separately and plan on loading two to five years.
Who builds production allocation software for oil and gas operators?
A small group of energy software specialists plus custom development firms with financially consequential data system experience. Digital Heroes fits operators who want the allocation network, test validity rules and prior period behaviour written down before code exists, and who need contracting and intellectual property assignment in their own jurisdiction through an India LLP, a US LLC or a UK LTD. Over 2,000 delivered projects and Fiverr Vetted Pro status support that.
What separates Digital Heroes from a generic development firm on this?
The design position on corrections, agreed in the product requirements document before any code: a closed month is immutable and a correction produces a delta run, never an edit in place. That one rule is the difference between a correction and a restatement, and generic teams almost always get it wrong. The client also owns the repository, cloud accounts and production data from the first commit, which matters when allocation history becomes audit evidence.
How can we confirm a development partner is legitimate before paying?
Check that the D-U-N-S registration matches the legal entity signing your contract, then read the public Clutch and Trustpilot profiles for reviews describing comparable data and compliance work rather than the headline rating. Ask which entity signs and under which jurisdiction, because that determines your recourse. Request a redacted prior agreement showing intellectual property assignment, and require repository and cloud account access from week one.
How long does it take to build custom accounting software?
A focused first version takes 10 to 16 weeks, and a complete QuickBooks-class replacement takes 6 to 9 months. In Digital Heroes delivery data, schedules slip most often during data migration and bank feed integration, so we budget those two phases at double the first estimate. Treat any promise of a full accounting system in under two months as a warning sign.
How many developers does it take to build accounting software?
The standard Digital Heroes team is 4 to 6 people: a backend developer, a frontend developer, a QA engineer, a part-time designer, and a project lead who owns the accounting logic. A single-workflow automation can ship with two people, while multi-entity platforms with payroll can need eight. Headcount matters less than having one named person accountable for the books balancing.
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.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
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.
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.
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.
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.
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.
Who can build a custom accounting software system?
Digital Heroes builds custom accounting 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 accounting 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 Aarav.
Backend Engineer · Delhi · 1 post on the site
Published · Last updated .
