Propane Delivery Software: Custom Build vs ADD Systems and Tank Utility
Buy, and keep what you already run. Under about six bobtails with a mostly will-call base, ADD Systems or Cargas plus tank monitors is the right spend, and nothing custom repays itself.
On this page
Buy, and keep what you already run. Under about six bobtails with a mostly will-call base, ADD Systems or Cargas plus tank monitors is the right spend, and nothing custom repays itself. Building starts to pay when you pad every schedule to avoid run-outs, when after-hours calls go to voicemail, and when years of delivery history has never answered a question.
What the off-the-shelf propane products actually do well
It is a Tuesday in January, a cold snap dropped fifteen degrees below the forecast your delivery schedule was built on, and by ten in the morning three keep-full accounts have run dry while a bobtail comes back to the yard 700 gallons short. Before you commission anything, understand that most dealers should not build. The back office you already pay for is doing its job.
- ADD Systems and Cargas Energy are the systems of record for fuel dealers, and they are good at the part that keeps you legal and paid: pricing tiers, budget plans, degree day tracking, taxes by jurisdiction, driver settlement and the delivery ticket itself.
- Blue Cow Software serves the same market and is worth a look if you are replacing an ageing back office rather than adding to one.
- Tank Utility, Otodata and Wesroc give you live tank levels on the tanks you have paid to monitor, which is real information nobody had ten years ago.
- ServiceTitan and Jobber handle the service side, appliance work and installations, competently enough that rebuilding them is a waste of your money.
If you run four or five trucks, most of your base is will-call, and you are not padding the schedule to sleep at night, stop here. Configure what you own and put the money into another truck or another technician.
Where they stop: a forecast that runs you dry and drives you empty at once
Legacy fuel systems schedule off a K-factor, a per-customer burn rate multiplied against heating degree days. It is a sound idea that goes stale quietly. Most dealers set the factor once and never retune it, so a customer whose usage changed throws the estimate off in both directions: too loose and the tank runs out, too conservative and you burn a truck run topping off a tank sitting at 55 percent.
The cost of a run-out is not one delivery. Under NFPA 58, the Liquefied Petroleum Gas Code adopted in most states, an interruption of service means a technician performs a leak check on the system before it goes back into service, and every appliance gets re-lit. That is an afternoon of a technician's time, not a top-up, and the customer spent a cold morning taking a competitor's call.
ADD holds years of delivery records. Tank Utility holds live levels on a third of your tanks. Neither closes the loop, because the routing that ships with these tools optimises the stop rather than the day, and nobody is asking the question that matters: which tanks will actually run out this week, and how do I fill them in one full truckload instead of three half-empty ones.
The second place they stop is the phone. Winter demand does not respect office hours, and an answering service cannot see whether the caller is keep-full or will-call, cannot tell a genuine no-gas emergency from a routine order, and cannot book anything. The third is the conversion quote. An oil-to-propane conversion is the most valuable estimate you write and the one most likely to die in the queue during the exact months it is worth the most.
Underneath all of it sits a decade of deliveries, tank sizes, pricing tiers and payment histories that has never answered a question. Which customers are quietly drifting to a competitor. Which routes lose money every time they run. Which will-call accounts move enough gallons to be worth converting to automatic delivery. The canned reports cannot tell you, because that data was structured for billing rather than for decisions.
The arithmetic: monthly licence cost versus the cost to build
Fuel back offices are priced per user or per truck, with modules for routing and mobile delivery, and tank monitoring is priced per tank per month plus hardware. Both are reasonable. Neither is where your money actually goes.
Put the real numbers side by side for one heating season. Count your run-outs and price each at the emergency fill plus a technician's afternoon for the leak check and re-light. Count the gallons of unused capacity on trucks that came back short. Count the after-hours calls that went to an answering service and the customers who never came back. Count the conversion quotes that sat three days and lost. Those four numbers are the case, and in most dealers they are larger than the entire software spend.
The crossover in this category sits near 12 to 18 bobtails, or roughly 8,000 delivery accounts, whichever arrives first, and it moves earlier if your monitored fleet is small. Below that line, more monitors and a properly retuned K-factor will get you most of the way, and that is the cheaper answer. Above it, each additional truck multiplies the cost of a bad forecast while the licence line stays flat, which is when a build starts winning on arithmetic rather than enthusiasm.
What a custom build actually costs
A focused first release covering the forecasting and routing engine plus one automation runs $50,000 to $120,000 and ships in 10 to 16 weeks. A full operations layer adding dispatch intelligence, an after-hours voice agent, quote follow-up, review generation and the analytics model runs $150,000 to $350,000 phased across 6 to 12 months, released in working pieces rather than a single launch.
Data migration runs 10 to 25 percent of the build here, and propane sits at the top of that band for one specific reason: getting clean history out of a closed back office is often the hardest single piece of the work. ADD Systems has a thin integration surface, and the delivery records you need were structured for billing rather than for decisions. If your monitors are split across Tank Utility, Otodata and Wesroc, that is three interfaces to normalise rather than one.
From the second season onward, plan on 15 to 20 percent of the build cost a year. The recurring lines here are back office upgrades that change an export, monitor vendors changing their interface, and retraining the burn rate model after each season, which is genuinely valuable rather than maintenance overhead. Add hosting, which is small.
The four situations where building wins
- Regulatory fit. Anything that answers your phone carries a safety script that is not negotiable: the smell-of-gas question, leave the building, call from outside, escalate to a human. Routing has to respect bobtail capacity and hours of service rules for drivers holding a commercial licence with hazmat and tank endorsements. A generic booking flow that treats a gas emergency like an appointment is dangerous rather than merely wrong.
- Scale economics. Trucks multiplied by heating season days is the arithmetic above, and every truck you add raises the cost of a stale forecast.
- A workflow that is your competitive advantage. If you win keep-full accounts because you never run a customer dry, the forecast is the business. Renting a generic approximation of it is the expensive option.
- Integration sprawl across three or more systems. The fuel back office, two or three monitor vendors, a service platform, and whatever answers the phone at night. Five boundaries, and the failures all live at one of them.
None true means buy. One true usually means keep the back office and build only the narrow layer that leaks money.
How to decide in a week
Run the cold snap post-mortem rather than another demonstration.
- Day one. Pull every run-out from last season. For each one, write down the emergency fill cost and the technician hours spent on the leak check and re-light.
- Day two. Pull the gallons returned to the yard on those same days. That is the capacity you paid for and did not deliver.
- Day three. Pull every after-hours call from the answering service log and check how many of those customers are still with you.
- Day four. Pull every conversion quote from last season that never closed, and check how many were followed up within 48 hours.
- Day five. Ask your back office vendor, in writing, exactly how you get delivery history out and on what schedule.
If days one to four total less than the cost of a first release, buy monitors and retune your K-factor instead. If day five gets a vague answer, price the integration work before anyone quotes you a platform.
Then pay for discovery instead of collecting free proposals. Digital Heroes runs a paid discovery phase that ends in a signed product requirements document covering the forecasting approach, the back office integration contract, the safety script and acceptance criteria. You own that document whether you build with us or hand it to another firm.
We are wrong for you if you want your back office replaced, if you need someone at your yard every week, or if you run under six trucks on a mostly will-call base, where more monitors is simply the better buy. What we are is more than fifty specialists with over 2,000 projects delivered, and the team you meet is the team that builds it. We build and run our own products, ShopScore, HeroCheckout and Section Vault, so our architects live with their own decisions on their own revenue, and our India LLP, US LLC and UK LTD entities mean intellectual property assigns under your own law. Check us on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S before the call.
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.
- 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) →
- SMS reminders that stated the specific cost of the appointment to the health system reduced missed appointments in Trial One, with the DNA (did-not-attend) rate falling from 11.1% (control) to 8.4% (specific-costs message) - an odds ratio of 0.74 (95% CI 0.61-0.89), i.e. roughly a 24-26% relative reduction - at no additional cost. (Trial Two replicated this at an 8.2% DNA rate.). Source: PLOS ONE (Hallsworth et al.) (2015) →
- 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) →
Frequently asked questions
How long does it take to build propane dispatch and forecasting software?
Ten to sixteen weeks to a first release covering the burn rate model, run-out prediction and routing, assuming the back office integration is settled early. A full operations layer takes six to twelve months, phased so each piece goes live as it finishes. The single biggest schedule risk is data access, so get written confirmation of how history leaves your back office before anyone starts.
Who owns the code and the forecasting models if a firm builds this?
You should own the repository, the cloud accounts in your company name, the trained models and the data pipelines, settled in writing before kickoff. At Digital Heroes the client owns the code from the first commit. The model matters as much as the code, because it is trained on a decade of your own deliveries and it improves every season you keep it.
Should we just add more tank monitors instead of building software?
For many dealers that is the right first move and it is cheaper. Monitors give you truth on the tanks you meter, and truth beats a stale estimate every time. The limit is economics: metering an entire residential base rarely pays. A forecast trained on your own delivery history covers the unmetered tanks, which is why the two approaches work better together than either alone.
Can we keep ADD Systems and build on top of it?
Yes, and that is the shape we recommend. ADD stays the system of record for pricing, taxes, billing, driver settlement and compliance, which it does well. The build reads history and account data, decides who needs gas and in what order, and writes results back. Replacing a fuel back office to fix dispatch is a much larger project wearing your problem as a disguise.
What is the difference between a K-factor forecast and a tank monitor?
A K-factor is an estimate: a per-customer burn rate multiplied against heating degree days, useful across an entire base but only as accurate as the last time somebody retuned it. A monitor is a measurement on one tank. Monitors are better and cost more per tank. The practical answer is monitors on your highest risk and highest volume accounts, and a retrained model everywhere else.
Can software safely answer after-hours propane calls?
It can, provided the safety sequence runs first and always. The smell-of-gas question, instruction to leave the building and call from outside, and immediate escalation to an on-call human are not optional and should be written into the specification before any conversation design happens. Everything else, meaning account lookup, will-call orders and scheduling, sits behind that gate rather than beside it.
What happens when the model predicts a run-out and gets it wrong?
Both directions matter and they cost differently. A false alarm costs a stop you did not need. A missed run-out costs an emergency fill, a technician afternoon for the leak check and re-light, and possibly a customer. Set the model to be deliberately conservative on high risk accounts, review misses weekly, and retune after each season, because a model nobody reviews drifts exactly like the K-factor did.
How do we handle monitors from three different vendors?
Normalise them behind one interface of your own, so the rest of the system never knows which vendor a reading came from. Each vendor exposes different fields, update frequencies and failure behaviours, and a stale reading treated as current is worse than no reading. Include a staleness rule that downgrades any tank to forecast-only when its monitor has not reported inside an expected window.
Should a dealer with four trucks build anything custom?
Almost certainly not. At that size the money is better spent on monitors for your riskiest accounts, a proper K-factor review, and one person owning the schedule. Custom software becomes an annual cost you notice. Revisit the question when you pass roughly twelve trucks, when you acquire a second yard, or when your after-hours losses become a number you can actually count.
What happens to our history if we later switch back office systems?
This is the argument for owning the pipeline. If the build already extracts and stores your delivery history in a warehouse you control, a back office change becomes a new source connector rather than a lost decade. If everything lives inside the vendor system, you inherit whatever export they offer on the way out. Ask that question during procurement, not during the migration.
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.
At what point does it make sense to switch from ServiceTitan to custom software?
The switch usually pencils out once your ServiceTitan bill passes roughly $75,000 a year and your team still maintains workaround spreadsheets beside it. ServiceTitan keeps pricing quote-only, and the quotes owners share in Digital Heroes scoping calls run several hundred dollars per technician per month on annual contracts, so a 30-technician shop can spend a full custom build's budget every 12 to 18 months in fees. If ServiceTitan fits your workflow cleanly, stay; the case for custom is a workflow the product forces you to bend.
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.
Is Housecall Pro enough for a growing HVAC or plumbing company, or do we need custom software?
Housecall Pro holds up well to roughly 10 to 20 technicians on standard residential jobs, with its Essentials plan listing around $129 per month for up to five users. The ceiling appears with commercial work: multi-visit projects, progress billing, equipment service history, and inventory are thin, which is when owners start managing the business in exported spreadsheets. Use the spreadsheet count as your signal: three or more recurring workarounds mean the tool no longer fits.
Can I get my customer and job history out of ServiceTitan or Jobber if we switch to custom software?
Yes. Jobber and Housecall Pro both provide CSV exports of clients, jobs, and invoices, and ServiceTitan data comes out through its API and report exports, though attachments and full audit history take extra work. Budget 2 to 4 weeks of migration effort inside the project for cleaning, mapping, and verifying records, and run both systems in parallel for at least two billing cycles before cutting over.
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.
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 Reyansh.
iOS Lead · Delhi · 1 post on the site
Published · Last updated .
