How Much Does Propane Delivery Software Cost in 2026?
Custom propane delivery software costs $50,000 to $350,000 in our delivery experience. A focused first release covering forecasting, routing and one automation runs $50,000 to $120,000 over 10 to 16 weeks.
On this page
Custom propane delivery software costs $50,000 to $350,000 in our delivery experience. A focused first release covering forecasting, routing and one automation runs $50,000 to $120,000 over 10 to 16 weeks. A full operations platform layering dispatch intelligence, an after hours phone agent, quote follow up, review capture and a data model on top of ADD Systems runs $150,000 to $350,000 phased across 6 to 12 months. The decision that moves the budget most is how you get delivery history out of your back office, because ADD Systems is a closed system with a thin integration surface, and a project that assumes a clean interface and finds a database extract instead will lose weeks before anyone has predicted a single run out.
The bands a propane build falls into
A dealer's quote splits into two purchases. The first stops the paradox where bobtails go out half full while tanks across town run dry: a burn rate model per customer that retunes itself on every delivery, monitor readings normalised across whichever vendors you run, degree day data layered in, and routing that clusters genuinely at risk tanks so a truck leaves full and comes back empty. That runs $50,000 to $120,000 over 10 to 16 weeks. The second purchase is everything around the truck: the after hours phone agent, quote follow up, review capture, churn scoring and route profitability. That runs $150,000 to $350,000 across 6 to 12 months.
Typical first release line items from our fuel delivery work:
- Back office data extraction: $18,000 to $28,000. A reliable nightly pull of delivery history, tank sizes, account types and pricing tiers out of ADD Systems. This is the piece that is hardest to estimate and should be scoped first, not last.
- Monitor normalisation: $6,000 to $9,000 per vendor. Tank Utility, Otodata and Wesroc are three separate interfaces with three separate reading conventions.
- Burn rate model per customer: $22,000 to $32,000. Trained on your own delivery history with local degree day data, retuned every time a truck delivers, rather than a K factor set once and never revisited.
- Routing against real constraints: $20,000 to $30,000. Bobtail capacity, driver hours of service and geography, with tanks that do not yet need a visit actively flagged out of the run.
- Dispatch view: $11,000 to $17,000. Predicted run out windows, at risk accounts and the trips the system recommends dropping.
What drives a propane build up
- Back office extraction difficulty. This is the largest unknown in the category and it is not proportional to truck count. Getting clean history out of a closed fuel back office is real engineering, and a quote that treats it as a connector is a quote that will slip.
- Monitor fleet fragmentation. Three monitoring vendors is three interfaces to normalise, not one. Dealers who inherited monitors through acquisitions carry this cost without realising it.
- The phone agent safety script. Anything that answers a call about gas has to run the do you smell gas, leave the house, call us sequence first, every time, with a hard handoff to a human on anything ambiguous. That specification and its testing is a meaningful share of the phone agent line and it is not negotiable.
- Service work alongside delivery. If technicians, appliance service and tank sets share the same dispatch, you are building two scheduling problems rather than one.
- Peak load behaviour. The system has to hold up when a cold snap multiplies call and delivery volume in a single day, and designing for that is different from designing for an average Tuesday.
What keeps the number down
- Keep ADD Systems. It is your system of record for billing and compliance and it is good at that. Building on top rather than ripping out removes the riskiest and most expensive part of the programme.
- One monitor vendor first. Normalise the fleet you have most of, and let the others arrive through the same ingestion layer afterwards.
- Start with the data model project. It is the cheapest work on the list because the history already exists, and it tells you which tanks the forecast keeps getting wrong before you build the forecast.
- One automation in release one. Pick either the phone agent or quote follow up, not both. The phone agent is the higher return and the higher specification burden.
- Manual review requests until the delivery feed is trusted. Review automation is cheap to add later and worthless if it fires off a delivery record that turns out to be wrong.
A worked example that adds up
A regional dealer running 12 bobtails and roughly 9,000 accounts, with about a third of tanks monitored across two vendors, a mixed keep full and will call base, and an answering service handling nights. First release, line by line:
- Discovery and back office extraction design: $12,000
- Nightly extraction pipeline from ADD Systems: $22,000
- Monitor normalisation across two vendors: $14,000
- Burn rate model per customer with degree day inputs: $26,000
- Routing against bobtail capacity and hours of service: $23,000
- Dispatch view with predicted run out windows: $13,000
- Dispatcher and office rollout: $6,000
That totals $116,000 across roughly 14 weeks. Phase two adds the after hours phone agent with the regulated safety script at about $52,000, quote follow up automation at about $22,000, review request automation at about $14,000, churn and will call conversion scoring at about $28,000, route profitability reporting at about $24,000 and a driver mobile delivery confirmation at about $32,000. Phase two is $172,000, taking the programme to $288,000.
How the spend phases
Scope the back office extraction first, before anything else is priced. Ask the developer to demonstrate a working pull of one month of delivery history in the first two weeks. If that proves harder than expected, you find out at the start of the project rather than in the middle of heating season, and the rest of the plan can be adjusted while adjustment is still cheap.
Then the data model work, which is the cheapest thing on the list and the fastest to show value because the history is already sitting there. It also tells you which customers have drifting K factors, which is exactly the input the forecast needs.
Forecasting and routing next, ideally landing before the heating season rather than during it. Nobody should be cutting over a dispatch process in January. Phase two follows in the shoulder season, starting with the phone agent because its specification and testing take longer than its build.
The ongoing costs nobody quotes
- Maintenance at 15 to 20 percent of build cost annually. Back office upgrades can change the extraction path, monitor vendors revise their interfaces, and the routing rules need adjusting as your fleet and territory change.
- Model retraining and supervision. A burn rate model retunes itself on delivery data, but somebody has to watch its accuracy by segment and investigate when a group of accounts drifts. That is an operations habit, not an automatic one.
- Phone agent usage costs. Voice minutes and model inference are consumption based, and they spike on exactly the nights you most need them. Budget for the cold snap, not the average.
- Monitor hardware and subscriptions. These grow as you instrument more tanks and they sit outside the software budget entirely, which is where dealers get surprised.
- Safety script review. The emergency sequence should be reviewed by whoever owns compliance in your business on a set schedule, and re-tested after any change to the agent.
Comparing a build against your current renewal
Your ADD Systems subscription is not the comparison, because you are keeping it. The comparison is against what the current arrangement costs you in operations, and there are four lines.
First, run outs. Each one is an emergency fill plus a technician doing a pressure test, a leak check and an appliance re-light before it is legal to leave. Count last season's run outs and multiply by a technician afternoon plus the emergency delivery. That is a number your service manager can produce this week. Second, wasted truck runs. Take a week of delivery records and count the fills where the tank was well above the level that justified a visit. Third, after hours calls that went to voicemail and never converted, which your answering service log will show even if your accounting will not. Fourth, quotes that went cold during the months they were worth the most.
The first and fourth numbers are usually the ones that carry a board conversation, because both are recoverable and both are already being paid for in labour and lost customers rather than in software.
When buying beats building
If you run a handful of trucks, most of your base is will call, and the routing and forecasting you already have keep up without you padding the schedule, do not build. ADD Systems plus Tank Utility monitors will serve you, and on the service side ServiceTitan or Jobber cover the technician scheduling well. Adding more monitors is also a legitimate first move, and it is far cheaper than software.
The build case appears on specific signals rather than at a revenue threshold. You are padding delivery schedules to avoid run outs and eating the wasted miles as the cost of sleeping at night. After hours calls go unanswered and you know you are losing customers you never hear from. Quotes die in the queue during the exact months they are worth most. Your K factors have not been retuned in years and nobody trusts the delivery report. Or you are sitting on years of history that has never answered a single question.
Even then, the right shape is layering rather than replacing. ADD Systems stays the system of record for billing and compliance. The custom work goes where the money actually leaks, which is dispatch intelligence, the phone and follow up. Ripping out a working back office is expensive, risky and rarely the thing that was broken.
If you want that decision made properly rather than quickly, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- IBM frames first-time fix rate as a core field service KPI, noting the industry average sits around 80% (roughly one in five jobs needs a return visit). Correction: IBM cites best-in-class providers at 89-98%, not '85%+'. Source: IBM (2024) →
- Comparesoft reports the field-service industry-average first-time fix rate is about 80%, best-in-class providers reach roughly 90%, scores below 70% put the business at risk, and providers exceeding 70% FTFR saw customer retention around 86%. Source: Comparesoft (2024) →
- An earlier SHRM benchmarking report (reflecting fiscal year 2015, published 2016) established a widely cited baseline average cost-per-hire of $4,129, illustrating how recruiting costs have climbed over time (SHRM's separate 2025 Benchmarking Report shows $5,475 for nonexecutive roles). Note: the $5,475 figure is not on this linked page; it comes from SHRM's 2025 report. Source: SHRM (Society for Human Resource Management) (2016) →
- The NRF discontinued its long-running annual shrink report, stating that a broad study of retail shrink 'is no longer sufficient for capturing the key challenges and needs of the industry' - important context that qualifies how POS/shrink benchmarks should be cited going forward. Source: Retail Dive (2024) →
Frequently asked questions
How much does custom propane delivery software cost for a dozen trucks?
A focused first release covering forecasting, routing and one automation runs $50,000 to $120,000 over 10 to 16 weeks in our delivery experience. A full operations platform layered on top of ADD Systems runs $150,000 to $350,000 phased across 6 to 12 months. The main cost driver is not truck count, it is how clean the delivery history extraction from your back office turns out to be.
Why is getting data out of ADD Systems the expensive part?
Because it is a closed back office with a thin integration surface, so the extraction is real engineering rather than a connector you switch on. Budget $18,000 to $28,000 for a reliable nightly pull of delivery history, tank sizes, account types and pricing tiers. Scope it first and ask for a working pull of one month of data inside the first two weeks, so a surprise arrives while the plan can still be changed.
What does the after hours AI phone agent cost to build?
Around $52,000 in phase two, and a meaningful share of that is specification and testing rather than build. Anything answering a call about gas has to run the do you smell gas, leave the house, call us sequence first, every time, with a hard handoff to a human on anything ambiguous. It also looks the caller up in your account data before it speaks, so it knows whether it is talking to a keep full or a will call customer.
What is the annual cost of running this alongside ADD Systems?
Budget 15 to 20 percent of build cost per year for maintenance, plus your unchanged ADD Systems subscription because the build sits on top rather than replacing it. Add consumption costs for the phone agent, which spike on exactly the nights you need it most, monitor hardware and subscriptions as you instrument more tanks, and someone watching forecast accuracy by segment rather than assuming the model minds itself.
How long does it take to ship something usable?
Ten to sixteen weeks for a focused first release. The data mining work shows value fastest because the history already exists and nobody has queried it. Aim to land forecasting and routing before the heating season rather than during it, because no dealer should be cutting over a dispatch process in January, and phase the automations into the shoulder season.
Do we have to replace ADD Systems?
No, and you should not. It stays your system of record for billing and compliance, which it does well. The custom work rides on top for dispatch intelligence, the phone agent, follow up and reviews. Ripping out a working back office is the most expensive and riskiest thing you could do here, and it is rarely the part that was broken.
How many monitor vendors can the system handle, and what does each add?
As many as you run, at roughly $6,000 to $9,000 per vendor for normalisation. Tank Utility, Otodata and Wesroc each have their own interface and reading conventions, so three vendors is three integrations. Dealers who inherited monitors through acquisitions often carry this cost without realising, and starting with the vendor covering most of your fleet keeps the first release tighter.
How do we build the business case?
Four numbers your own team can produce. Last season's run outs multiplied by the emergency fill plus the technician afternoon for the pressure test, leak check and appliance re-light. Fills from one week of records where the tank was well above the level that justified a visit. After hours calls that went to voicemail and never converted. And quotes that went cold in the months they were worth most.
When should a dealer not build this?
When you run a handful of trucks, most of your base is will call, and the routing and forecasting you already have keep up without padding the schedule. ADD Systems plus Tank Utility monitors will serve you, with ServiceTitan or Jobber on the service side. Adding more monitors is also a legitimate and far cheaper first move than any software project.
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 security and compliance does custom field service software need?
The baseline is encryption in transit and at rest, role-based access so a technician sees only their own jobs, remote wipe for lost phones, and audit logs on anything that touches money. Run payments through a processor like Stripe or Square so card data never touches your servers and the heaviest PCI burden stays with them. If your crews serve regulated sites such as healthcare or government facilities, say so in scoping, because access and documentation requirements shape the data model.
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.
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 much does it cost to build custom field service management software for a small business?
For a company running 5 to 25 technicians, a focused first version with scheduling, dispatch, a technician mobile app, and invoicing typically runs $40,000 to $80,000 in Digital Heroes delivery experience. A full platform with offline mode, a customer portal, GPS tracking, and accounting sync lands between $90,000 and $180,000. The two biggest cost drivers are offline sync depth and integration count, so pin both down in scoping and the quote holds.
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.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
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
Published · Last updated .
