How to Hire a Propane Delivery Software Development Company
Hire on two proofs: that the vendor has pulled clean delivery history out of a closed fuel back office before, and that they will write the gas safety sequence into the specification before anything answers a phone.
On this page
Hire on two proofs: that the vendor has pulled clean delivery history out of a closed fuel back office before, and that they will write the gas safety sequence into the specification before anything answers a phone. Expect $50,000 to $120,000 and 10 to 16 weeks for a forecasting and routing engine, and plan go live for spring, not January.
Propane software gets one honest test a year and it lasts about ninety days. In September every route looks efficient and every forecast looks sound. Then an overnight low lands fifteen degrees under what the degree day model was built on, three keep full accounts run dry before lunch, each run out drags a technician through a leak check and a full re-light, and a bobtail comes back to the yard 700 gallons short because the route sent it to top off tanks sitting at 55 percent. That is the day you learn what you bought.
The seasonality is what makes this category hard to buy. A poor vendor choice does not cost you a sprint, it costs a heating season, and you cannot rehearse the failure in July. Meanwhile the two hardest parts of the work are both invisible in a sales meeting: getting a clean, repeatable delivery history out of a closed back office, and writing a phone agent that runs a regulated safety sequence correctly on the worst call of someone's winter.
What a propane delivery software company actually does
The visible build is a dispatch board and a few dashboards. Maybe a quarter of the work.
The rest starts with the forecast. A partner worth hiring reads your full delivery history out of the back office, layers in whatever live telemetry you have, adds local degree day data, and trains a burn rate per customer that retunes itself after every delivery rather than sitting on a K factor somebody set in 2019. The routing engine then clusters genuinely at risk tanks by geography against bobtail capacity and hours of service rules, and it actively suppresses the stops that do not need making, which is the half of the problem most tools ignore.
Then the phone. An after hours voice agent that identifies the caller from the account record before it speaks, runs the smell gas and evacuate sequence first, then either takes a will call order or books an emergency and pages the on call driver, writing every call back to the account so the morning office sees the night. Then the quiet revenue work: conversion quotes chased before the homeowner signs with whoever called back first, review requests fired off closed job records, and churn risk surfaced from declining gallons and slowing payments.
What it actually costs in 2026
These bands reflect Digital Heroes delivery experience in field service and fuel operations.
| Project tier | Cost | Timeline |
|---|---|---|
| Forecasting and routing engine on your delivery history, plus one automation | $50,000 to $120,000 | 10 to 16 weeks |
| Add the after hours voice agent with safety script and on call paging | $90,000 to $180,000 | 4 to 7 months |
| Full operations layer over the back office with follow up, reviews and analytics | $150,000 to $350,000 | 6 to 12 months |
| Support, seasonal model retuning and monitor interface maintenance | 15% to 20% of build per year | Retainer |
Two line items go missing from nearly every propane quote.
The first is the back office extract. ADD Systems and Cargas are closed platforms with a thin integration surface, and getting a clean repeatable feed of deliveries, tank sizes, pricing tiers and account flags is frequently the single largest task in the project. It is also often gated by your back office vendor's own change process and licence terms, which means the schedule depends on a third party who has no stake in your deadline. A quote that shows integration as one line has not asked which version you run.
The second is monitor normalisation. If your telemetry is split across Tank Utility, Otodata and Wesroc, that is three interfaces with three reading cadences, three calibration behaviours and three definitions of a low level alert, not one. And since most dealers monitor only a minority of tanks, the model has to be good on the unmonitored majority, which is a harder problem than the demo implies.
One more schedule constraint. Never plan a go live inside the heating season. Cutting over dispatch in January is how a dealer finds a routing defect on the coldest week of the year. Work backwards so the system is live and shaken out between April and September.
Signals of a partner who has done this
- They ask which back office and which version before quoting. ADD Systems, Cargas or something older changes the extraction approach entirely, and a firm that has done it will ask in the first ten minutes.
- They explain K factor and degree days back to you. If they do not already know what a keep full account is, or why a run out triggers a mandated leak check and re-light, they will build something that demos well and fails in January.
- They write the safety sequence into the specification. The smell gas and evacuate script is not a conversational nicety, and a partner who treats it as a specification item rather than a prompt has understood the stakes.
- They plan go live around the season. A vendor proposing a December cutover has never worked with a fuel dealer.
- They keep the back office as the system of record. Billing and compliance stay where they are. Anyone offering to replace it in phase one is selling you risk.
- They name what happens on a surge day. A cold snap multiplies calls and deliveries at once, and load behaviour under that spike should come up before you raise it.
Red flags worth walking away from
- A generic booking bot for the phone. A flow that treats a no heat call like a restaurant reservation is not merely weak, it is unsafe, and it should end the conversation.
- A fixed price before seeing your data extract. The extraction is the risk. A number produced without touching it is a placeholder that will be revised upward.
- They propose replacing the back office. Ripping out billing and compliance to fix dispatch is expensive, slow and puts your invoicing on a cutover date in the wrong season.
- Monitors treated as one integration. Three vendors means three interfaces. A quote that says tank monitoring, singular, has not looked at your account.
- They want to keep the trained models. The model compounds on your own delivery history. If it lives with the vendor, you are renting your own operating data back.
Nine questions for the first call
- Which fuel back offices have you extracted history from, by name, and what broke?
- How would you forecast a run out for a customer with no tank monitor and eight years of delivery records?
- What does your routing engine do with a tank at 55 percent that sits on the way to a tank at 12 percent?
- Write me the first thirty seconds of the after hours script for a caller who says they smell gas.
- How does the voice agent tell an emergency from a will call order, and when does it wake the on call driver?
- How do you handle a cold snap that triples call volume and delivery demand in a day?
- Which monitor platforms have you normalised, and how do you reconcile disagreeing readings?
- What is your proposed go live month, and why?
- Do we own the code, the trained models and the data pipelines outright, in writing before kickoff?
A simple way to choose
Never pick on a proposal alone. Buy a paid discovery phase from your two strongest candidates and require the same output: a written specification covering the extraction approach for your specific back office version, the forecasting method with how it handles unmonitored tanks, the safety script as a scripted flow, the monitor interfaces to be normalised, the go live month with reasoning, and a phased plan with costs. You pay for it, you own it, and it goes to any other firm you want to price against.
Read the two documents side by side and the choice usually makes itself. One will describe your operation back to you and one will describe software. Digital Heroes works this way as standard, writing the product requirements document before code exists and handing over the repository, the cloud accounts and the trained models from the first commit, because the asset you are buying compounds on your own delivery history and should never sit in a vendor account.
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.
- Grand View Research valued the global field service management market at USD 4.43 billion in 2022 and projects it to reach USD 11.78 billion by 2030, a 13.3% CAGR, driven by growing field operations in telecom, utilities, construction and energy. Source: Grand View Research (2023) →
- 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) →
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
- 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) →
Frequently asked questions
How much does it cost to hire a propane delivery software development company?
A forecasting and routing engine built on your delivery history plus one automation runs $50,000 to $120,000 over 10 to 16 weeks. Adding the after hours voice agent with a safety script and on call paging takes it to $90,000 to $180,000. A full operations layer over your back office with follow up, reviews and analytics runs $150,000 to $350,000 across 6 to 12 months. Extraction difficulty drives the range more than truck count.
What is the single most important thing to verify before hiring?
Whether they have pulled clean delivery history out of a closed fuel back office before, and which one. Getting deliveries, tank sizes, pricing tiers and account flags out of a platform with a thin integration surface is usually the largest task in the project, and it is often gated by your back office vendor's change process. A developer who has never done it will underestimate it and the timeline will slip.
Should we replace ADD Systems or build on top of it?
Build on top. Your back office is the system of record for billing and compliance and it does that job well. The money leaks in dispatch intelligence, the after hours phone and quote follow up, none of which it was designed for. Replacing a working back office puts invoicing on a cutover date, costs several times more, and fixes none of the problems that made you look for software.
When should a propane software project go live?
Between spring and early autumn, never inside the heating season. Cutting over dispatch in January is how a dealer finds a routing defect on the coldest week of the year, with run outs and emergency re-lights as the cost of the lesson. Work backwards from an April to September window, which usually means starting discovery in the previous winter while the pain is still fresh and staff remember the specifics.
Do we own the code, the models and the data pipelines?
You should, and it belongs in writing before work starts. Insist on outright ownership of the source, the trained forecasting models and the data pipelines, running in your own cloud accounts with no per seat lock in. At Digital Heroes the client owns all of it from the first commit. The model improves every time a truck delivers, which makes it an asset that should compound for you rather than for a vendor.
How long until a custom field service platform pays for itself compared to per-technician licenses?
For most shops the crossover lands between 18 and 36 months once upkeep is counted. A 25-technician company paying $300 per technician per month for licenses spends $90,000 a year, so a $120,000 custom build with $20,000 in annual maintenance breaks even around month 21, before counting saved dispatch hours and billing errors. Below about 10 technicians the math rarely works, and Jobber or Housecall Pro is the honest recommendation.
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.
How much would it cost to build something like ServiceTitan just for my company?
A true ServiceTitan clone would cost millions and you do not need one, because companies that bring this request to Digital Heroes typically use 20 to 30 percent of its features. Building that slice, shaped to your exact dispatch board and technician day, runs $80,000 to $200,000 depending on offline requirements and integrations. The field service builds that succeed copy a workflow, not a product.
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.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
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.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
Who owns the code when an agency builds our field service software?
You should own it outright, and the contract must say so: source code, designs, documentation, and every account (hosting, app stores, domains) registered to your company rather than the agency's. Work-for-hire terms with ownership transferring on payment are standard at reputable agencies, and it is how Digital Heroes contracts every build. Walk away from any proposal where you license the platform instead of owning it, because that recreates the vendor lock-in you were leaving ServiceTitan to escape.
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.
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 does custom field service software work when technicians have no cell signal?
Properly built field software stores the technician's entire day on the device, including job details, forms, photos, signatures, and parts, then syncs automatically when signal returns. The hard engineering is conflict resolution: deciding what happens when a dispatcher reassigns a job while the technician is working it offline. That logic has to be designed before the build starts, because retrofitting offline into an app that assumed a connection is close to a rewrite.
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.
Who can build a custom field service management software system?
Digital Heroes builds custom field service management software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other field service management software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Shaurya.
Senior React Native Engineer · Delhi · 1 post on the site
Published · Last updated .
