Skip to content
§
§ · hiring guide

How to Hire a Gas Nomination and Scheduling Software Development Company

Sit a prospective developer next to your scheduler through one full timely cycle before you sign anything. If they cannot describe your transport, storage and supply constraints back to you afterwards, they will build a submission form.

Supply Chain Software workflow illustration for GAS Nomination Scheduling Software.
The short answer

Sit a prospective developer next to your scheduler through one full timely cycle before you sign anything. If they cannot describe your transport, storage and supply constraints back to you afterwards, they will build a submission form. Expect $80,000 to $160,000 over 14 to 20 weeks for a first release, and $200,000 to $500,000 for a full scheduling platform.

Most software is judged at leisure, over a quarter, in a review meeting with a deck. Nomination software is judged at 12:58 on a Tuesday, two minutes before the timely cycle closes, with a producer texting that a well came back on and three thousand dekatherms that were not in anybody's plan. Either the system is useful in those two minutes or it is a typing interface with a licence fee attached to it.

That is what makes hiring for this category awkward. The value of the system lives inside your own agreements, not in the software, and no vendor can demonstrate competence at modelling constraints they have not seen. Every firm will show you a nomination screen and a calendar of cycles. The part that decides whether your scheduler abandons the tool in month two is whether maximum daily quantities, fuel and lost-and-unaccounted-for retention, point rights, storage ratchets and current imbalance all interact correctly on a twenty minute deadline. You cannot see that on a call, which is why the evaluation has to be structured differently here than for ordinary business software.

What a gas scheduling software partner actually does

The visible build is the nomination workspace. Behind it sits a connector for every pipeline you ship on, each with its own behaviour profile, because the standards give the industry a shared clock and almost nothing else. Where a pipeline offers a machine interface you use it. Where it offers only a portal you automate the portal, and then you maintain that automation for as long as you use it, because bulletin boards get redesigned and nobody sends you a release note.

Then comes the work most buyers underestimate. Somebody has to read your transport, storage and supply agreements and turn them into structured constraints, including the ratcheted injection and withdrawal rights and any capacity release or asset management arrangement that changes who is nominating on whose behalf. Somebody has to design confirmation polling and cut detection, alert routing that treats a small afternoon cut as an email and an overnight operational flow order as a phone call, and an immutable submission record that stores the portfolio state each nomination was computed from. That last one is nearly free at the start and close to impossible to retrofit.

What it really costs in 2026

These bands assume you keep your gas accounting system and build the operational scheduling layer in front of it.

ScopeCostTimeline
Connectors and submission automation for three or four pipelines$50,000 to $95,0008 to 12 weeks
First release: contract and portfolio model, cycle-aware assembly, submission and confirmation capture$80,000 to $160,00014 to 20 weeks
Full platform: live imbalance, park and loan, cashout modelling, notice monitoring, month-end reconciliation$200,000 to $500,0008 to 14 months
Connector maintenance and support20 to 25 percent of build per yearRetainer

Two line items are missing from nearly every quote. The first is contract discovery. Turning agreements into constraints takes weeks of work by someone who can read a tariff and a confirmation, and shippers are routinely surprised by what their own contracts say once somebody actually reads all of them in one sitting. This is the schedule risk in almost every project of this type, and it is not engineering.

The second is parallel running. You need at least one full month including a month-end close with the scheduler maintaining the workbook alongside the new system, and it should not happen in January. That is real cost in your own people's hours and it never appears on a vendor invoice, which is exactly why it gets skipped and why the cutovers that go badly are the ones done in winter.

Budget separately for connector maintenance. A portal redesign is not a defect and treating it as warranty work will sour the relationship in the first year.

Signals of a strong partner

What distinguishes a firm that has built for a scheduling desk from one that has built integrations.

  • They draw contracts before they draw pipelines. Capacity rights, points, fuel retention and day-varying constraints on the whiteboard means they understand what a scheduler decides.
  • They admit portal connectors will break. The honest answer is monitoring, alerting and a same-day fix, not a promise of permanence.
  • They design alert routing with your schedulers. Thresholds that wake people needlessly get muted, and muted alerts are worse than none.
  • Estimated imbalance carries a confidence indicator. A team that has not thought about how to stop people treating an estimate as settled will ship a number that gets somebody in trouble.
  • They want to observe a live timely cycle. Including the part where the scheduler overrides her own plan, which is where the real logic lives.
  • Every submission is immutable with its inputs attached. Reconstructing a disputed day should be opening a record, not rebuilding one.
  • They propose starting with your highest-volume pipelines. The long tail can stay manual for a while at almost no cost.

Red flags

  • A quote that prices all your pipelines identically. Connectors differ enormously depending on whether a pipeline offers a machine interface or only a portal.
  • No mention of confirmations or cuts. A system that submits and stops watching leaves you discovering a cut on the invoice.
  • Imbalance presented as a settled figure. Operational estimates and post-allocation accounting numbers are different objects and conflating them is a costly habit to build in.
  • A cutover planned for the heating season. Anyone proposing to retire your scheduler's workbook in December has not carried the risk of a missed timely deadline.
  • Connectors retained as a vendor service. This is the piece suppliers most often try to keep, and it is exactly where dependency gets expensive.

Questions to ask on the first call

  1. Draw our contract model. What sits on a transport agreement besides a capacity number and a point list?
  2. How would the system propose an allocation when a well comes back on after the timely cycle has closed?
  3. Which pipelines have you connected to, and which of those were portal automation rather than a machine interface?
  4. What happens when a submission silently fails at 12:55 and nobody notices?
  5. How do you model storage with ratcheted injection and withdrawal rights tied to inventory level?
  6. How is an estimated imbalance presented so nobody treats it as a settled number?
  7. How does an overnight operational flow order reach a human, and who decides the routing rules?
  8. If a pipeline disputes a scheduled quantity from four months ago, what exactly can we open?
  9. Who owns the repository, the connector code, the infrastructure accounts and the credentials?

A simple way to decide

Do not choose from proposals. Buy a paid discovery phase from your strongest candidate, two to four weeks, priced up front, on the condition that it produces a written specification you own outright and can take anywhere.

That specification should contain the contract and portfolio model expressed against your actual agreements, the pipeline connector list with the mechanism named for each, the allocation logic and how overrides are recorded, the imbalance estimation approach with its confidence treatment, the alert routing rules, the parallel run and cutover plan with a shoulder month named, and a fixed price. Circulate it to your shortlist. If the returning quotes sit close together, the scope is real; if they scatter widely, the specification just told you which firms had been guessing.

Digital Heroes writes that document before any code exists as standard practice, and contracts through an India LLP, a US LLC or a UK LTD so intellectual property assigns under the law your counsel already works in. The delivery history is verifiable through D-U-N-S, Clutch and Trustpilot rather than a slide.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. 48% of private companies cite integration with legacy systems or technical debt as a top obstacle to realizing the full value of their digital and AI investments (behind data quality/availability at 72% and gaps in AI fluency or technology talent/leadership at 53%). Source: Deloitte (2026) →
  2. 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) →
  3. 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) →
  4. ITIF's 2025 report documents that SMEs operate at roughly 60% of large-firm productivity in advanced economies (citing McKinsey), that CRM platforms deliver a 25-40% improvement in customer retention and a 15-30% boost in sales, and that digital advertising returns about $8 in profit per dollar spent on Google Search and Ads. Source: Information Technology and Innovation Foundation (ITIF) (2025) →
FAQ

Frequently asked questions

How much does it cost to build custom gas nomination software?

A first release covering the contract and portfolio model, cycle-aware nomination assembly, automated submission to your main pipelines and confirmation capture runs $80,000 to $160,000 over 14 to 20 weeks. A full platform adding live imbalance tracking, park and loan, cashout modelling, notice monitoring and month-end reconciliation runs $200,000 to $500,000 across 8 to 14 months. Connector maintenance typically runs 20 to 25 percent annually.

What is the biggest schedule risk on a gas scheduling project?

Contract discovery, not engineering. Somebody has to read every transport, storage and supply agreement and turn it into structured constraints, including ratchets, fuel retention, point rights and any capacity release arrangement. Shippers are frequently surprised by what their own agreements say once all of them are read in one sitting. Budget weeks for this and treat any vendor who skips it as underquoting.

Should the developer automate pipeline portals or wait for machine interfaces?

Automate the portals, and budget for maintenance. Where a pipeline offers a machine interface you use it, and where it does not you drive the portal and accept that a redesign will break the connector. That is maintenance, not warranty, and getting that expectation into the contract prevents a bad first year. Ask for monitoring and alerting so a silent submission failure never sits unnoticed before a deadline.

When should we cut over from the scheduler's workbook?

In a shoulder month, after at least one full month of parallel running that includes a month-end close. Never during the heating season. The parallel period costs real hours from your own people and never appears on a vendor invoice, which is why it gets cut and why winter cutovers are the ones that go badly. Write the parallel run into the plan as a dated deliverable.

Who should own the pipeline connectors after the build?

You should, along with the repository, the infrastructure accounts and the credentials, agreed in writing before kickoff. Connectors are the component suppliers most often try to retain as an ongoing service, and that is precisely where the dependency becomes expensive when you want to change firms. Ask about ownership in the first conversation rather than at contract stage.

How long does it take to build custom supply chain software?

Plan on 10 to 14 weeks for a first production release covering one or two core workflows, and 6 to 9 months for a full platform spanning procurement, inventory, and fulfillment. Digital Heroes ships most supply chain MVPs in about 12 weeks with a 4 to 6 person team. Integrations are the schedule risk: each ERP, EDI, or carrier connection typically adds 2 to 4 weeks of build and testing.

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.

Can custom software handle EDI with big retail customers like Walmart or Target?

Yes, and this is one of the most common reasons distributors go custom, because retailer scorecards penalize late or malformed documents. The typical build covers EDI 850 purchase orders in, 855 acknowledgments, 856 advance ship notices, and 810 invoices out, usually through a network like SPS Commerce or TrueCommerce rather than raw AS2. In Digital Heroes builds, onboarding your first major retailer adds 4 to 8 weeks and $10,000 to $25,000, with each additional trading partner far cheaper once the pipeline exists.

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.

Is custom supply chain software cheaper than SAP over five years?

For small and mid-size operations it usually is, because SAP costs compound through licensing, implementation partners, and per-user fees, while custom costs are front-loaded. SAP Business One's published list price has run roughly $3,200 per professional user as a perpetual license plus annual maintenance near 20 percent, and the S/4HANA proposals Digital Heroes clients share are typically in the hundreds of thousands before any customization. A $60,000 to $100,000 custom build with 15 to 20 percent annual upkeep often costs less by year three for a 10 to 30 user company, and you stop paying per seat as you hire.

How much does a custom warehouse management system cost to build?

A custom WMS typically costs $40,000 to $120,000 for a single-warehouse operation, and $120,000 to $300,000 once you add multiple sites, wave picking, and labor tracking. Across Digital Heroes WMS builds, the biggest cost drivers are scanner-based workflows, real-time inventory sync with your ERP, and the number of picking strategies you need. A pilot covering receiving, putaway, and picking for one warehouse is the cheapest credible starting point.

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 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.

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.

How fast does custom supply chain software pay for itself?

Most operations see payback in 12 to 24 months, faster when the system replaces manual data entry or per-user SaaS fees. Measure it concretely: hours of double entry removed, error and mis-ship rates, inventory carrying cost, and the license fees you stop paying. One recurring pattern from Digital Heroes projects: a distributor spending 60+ staff hours a week re-keying orders between systems can often justify a $50,000 build on labor recovery alone within the first year.

What does it cost to maintain custom supply chain software each year?

Budget 15 to 20 percent of the original build cost per year, so roughly $9,000 to $12,000 annually on a $60,000 system, covering hosting management, dependency updates, bug fixes, and small enhancements. Across its maintenance contracts, Digital Heroes sees supply chain systems need more upkeep than typical web apps because carrier APIs, EDI specs, and ERP versions keep changing underneath them. Hosting itself is usually minor, often $100 to $500 per month for a mid-size operation.

Who can build a custom supply chain software system?

Digital Heroes builds custom supply chain 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 supply chain 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.

Keep reading

Published · Last updated .

Online now

Hi there. How can we help you today?

Reply