Utility Crew Callout and Dispatch Software: Custom Build vs ARCOS, Clevest and IFS
Buy ARCOS. It is the established product in this category, it does automated callout with a defensible log, and most utilities with one bargaining unit and a contract close to the common pattern should configure it rather than commission anything.
On this page
Buy ARCOS. It is the established product in this category, it does automated callout with a defensible log, and most utilities with one bargaining unit and a contract close to the common pattern should configure it rather than commission anything. Build when you run two or more agreements with genuinely different callout language, or when you are already settling grievances you cannot defend.
What ARCOS, Clevest and IFS actually do well
Wind hits at 9pm. By 11pm you need four more line crews and two service crews, and the way you get them is a dispatcher with a printed roster and a desk phone, calling people in an order your collective agreement dictates while the outage system keeps lighting up. Any product that removes that phone is worth serious money, and one exists.
ARCOS was built for exactly this. Automated callout with voice, roster rules, an overtime accumulator, crew manager and mutual assistance handling, used across a large part of the industry. It does the thing that matters most on the night, which is placing many calls in the correct order simultaneously and recording every attempt with a timestamp. If your contract language sits reasonably close to the common pattern and your main need is reliable callout with a log you can put in front of a steward, buy it. There is no prize for rebuilding a product that works.
Clevest, now inside the Schneider portfolio, is strong at field mobility and switching workflows, so it complements callout rather than answering it. IFS is a capable enterprise field service and asset platform with genuinely good scheduling optimisation, and if you are already deploying it across the utility, look at it. If you are not, opening that door for one problem is a large commitment. Oracle Field Service sits similarly.
If you run a small municipal or cooperative utility with a few dozen field staff and one crew on standby, buy nothing. A phone tree and a whiteboard is proportionate and the dispatcher knows everyone by name. Spend the money on vegetation management.
Where they stop: the clause your local negotiated and nobody else has
Callout is not scheduling. It is a rules engine whose rules were negotiated at a bargaining table and rewritten at the last one, and that is the specific workflow packaged products model badly.
Consider what varies between utilities, and sometimes between locals inside the same utility. Whether equalisation runs on hours offered or hours worked. Whether the accumulator resets annually or rolls. Whether a no answer counts the same as a decline, and how long the phone rings before it becomes one. Whether an employee on vacation is charged. Whether the list runs by district first or classification first, and what happens when a district list is exhausted. Whether a supervisor may skip the list in a genuine emergency and what documentation that requires. How crews must be composed by classification, and how apprentices count toward the ratio.
Every one of those is a clause with a grievance attached. Here is the detail people outside labour relations miss: in most agreements a decline still counts as an offer for equalisation purposes, which means the attempt log matters as much as who actually worked. So when the grievance arrives two weeks later claiming an employee was skipped, your defence is not the crew list. It is the ordered roster as it stood at 11:04pm that night, the rule set in force at that moment, and every attempt with its channel and its outcome.
A vendor product handles the common shapes and then asks you to adapt. Where the contract will not adapt, your dispatchers work around the system, and once dispatchers work around the system during a storm it stops being the record. You are back to defending a paper log with times written in pen, and you settle at the overtime rate for hours nobody worked.
The arithmetic: cost per employee against the cost to build
Run it on your own contract. Callout products are priced per employee in the callout population per month, sometimes with a separate charge for voice minutes and a separate module for mutual assistance. Take your renewal, divide by the number of represented field employees on the roster, and you have your rate per employee per month. Multiply back out at the headcount you expect in three years, because this fee scales with the workforce rather than with usage, and a storm year costs the same as a quiet one.
Then put the grievance line beside it. Count settlements paid in the last three years on callout and overtime equalisation, at the overtime rate, plus the staff hours spent assembling each defence. At most utilities nobody has ever added that up, and it is usually the larger number.
The crossover is a headcount crossed with a bargaining unit count. Under about 150 represented field employees in a single unit, buy and configure, because the rules complexity is low relative to the price. Above roughly 400 employees the per employee arithmetic alone starts favouring a build amortised over five years. But headcount is the weaker signal. Two bargaining units with materially different callout language is nearly two rules engines, and that condition moves the crossover down to around 200 employees on its own.
What a custom build actually costs, plus migration and year two
In Digital Heroes delivery experience, a first release covering the roster with overtime equalisation, the configurable rules engine, automated callout across voice, text and push with full attempt logging, and crew assembly against composition rules runs $70,000 to $140,000 and ships in 12 to 16 weeks. A full platform adding outage system integration, mutual assistance crew onboarding with lodging and guides, restoration progress with estimated restoration times, fatigue and rest tracking and storm cost capture runs $180,000 to $400,000 phased over 8 to 12 months.
Data migration runs 10 to 25 percent of build cost. Here the awkward object is the accumulator: you cannot start everyone at zero without creating an equalisation dispute on day one, so historical offered and worked hours have to come across and reconcile to whatever your stewards currently accept as the truth. Budget for that conversation, not just the transfer.
Year two and after runs 15 to 20 percent of build cost annually, and in this category it is bargaining driven. Your agreement will be renegotiated inside the life of this system. If the rules engine is configurable without a code change, that is a configuration session and a test pass. If it is not, you are paying to rebuild.
What pushes cost up: the number of bargaining units; integration depth with your outage platform, since each vendor has its own interface and its own operational sensitivity; telephony reliability engineering, because a callout system that fails during a regional event is worse than none; and human resources (HR) and payroll integration for roster truth, which is never as simple as it sounds.
The four situations where building wins
Regulatory fit. Two regimes bite. Your collective agreement, which is the primary specification, and the hours of service rules under 49 CFR Part 395 where crews drive commercial vehicles, including the utility service vehicle provision at 395.1(n) and what changes during a declared emergency. Your legal and safety teams make those determinations. The system's job is to hold hours worked and rest taken so the determination rests on real numbers.
Scale economics. Past the headcount and unit crossover above, a per employee fee that rises every time you hire is a strange way to pay for a system used a dozen nights a year.
A workflow that is your advantage. Mutual assistance is the honest example. Fifty trucks arrive on a Sunday from three states away and you need qualifications, clearances, staging, lodging, guides, daily time capture and contractor rate application. Nearly every utility runs this on whiteboards, and if your storm costs go into a recovery filing, that reconstruction is the difference between recovering the money and eating it.
Integration sprawl across three or more systems. Count them: human resources for the roster, payroll for the pay, the outage platform for demand, the mobile workforce system for assignment, telephony for contact, and your cost accounting for storm capture. Once one callout crosses three, the dispatcher becomes the integration at exactly the hour she has none to spare.
How to decide in a week: replay one real callout
Take the last significant callout you ran and try to reproduce it on paper. Ask your dispatcher and your labour relations lead to answer four questions together, in writing.
Who was on the list at the moment the callout started, in order, and can you evidence that order now. What was every attempt, its channel, its time and its outcome. Which rule was applied when the district list was exhausted. And how long did assembling those three answers take.
If it takes under an hour and everyone agrees on the result, your current process is defensible and configuration is the right investment. If it takes a day, or if two people give different answers about the order, you have already lost the next grievance and the frozen list replay is the feature worth buying or building. Then price it against your settlement history rather than against a licence.
Then pay for a discovery phase instead of accepting a free proposal. Send the callout and overtime articles from your two most complex agreements. At Digital Heroes that produces a signed product requirements document before any code exists: the rule set expressed as configuration, the roster model, the attempt log schema, telephony fallback behaviour, acceptance criteria and a fixed price. You own that document whichever way you go, and it is what makes competing quotes comparable.
Who we are wrong for: small municipals, single unit utilities whose contract fits an existing product, and anyone wanting a full enterprise field service platform. We work as India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law, you own the repository from the first commit, and you meet the named engineers before signing. More than fifty specialists, over 2,000 projects, checkable on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.
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.
- 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) →
- Salesforce's field-service research (State of Service / field service trends, survey of 5,500+ service professionals) found that 74% of mobile workers report increasing workloads and 47% say appointments don't go as planned due to customer miscommunication, unaccounted-for parts, or insufficient appointment lengths and travel times. (The separate claim that admin tasks consume ~30% of a technician's hours is NOT supported by the report - the seventh-edition data instead states technicians spend about 18% of working hours, ~7 hours/week, on admin, and only ~32% of time interacting with customers.). Source: Salesforce (2024) →
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- U.S. retailers lost an average of 1.6% of sales to shrink in FY2022 (up from 1.4% the prior year), equating to $112.1 billion in inventory losses - the benchmark case for POS-integrated loss prevention and inventory accuracy. Source: National Retail Federation (NRF) (2023) →
Frequently asked questions
How long does a custom callout system take to build?
Twelve to sixteen weeks for a first release covering the roster and accumulator, a configurable rules engine, multi channel callout with complete attempt logging, and crew assembly against composition rules. Outage integration, mutual assistance, fatigue tracking and storm cost capture add eight to twelve months. Do not plan a go live during storm season, and pick the quietest month you have for the cutover.
Who owns the callout logs if we change vendors?
You should, in writing before kickoff, including the repository, the cloud accounts and the underlying data. Callout logs are labour relations evidence and storm cost data supports regulatory filings, so neither can sit in an account you cannot reach during a dispute. At Digital Heroes the client owns the repository from the first commit and can hire any other firm to continue the work.
What happens when a grievance is filed six months after a storm?
The system should answer it by replaying the frozen list and the rule set exactly as they stood that night, not by showing today's roster. Every callout event stores the ordered list, the rules in force and every attempt with channel, timestamp and outcome. If a vendor cannot demonstrate that replay on a past event during evaluation, assume you will keep settling grievances you should win.
Can we build only the rules engine and keep our existing telephony?
Yes, and it is a reasonable first phase. The rules engine produces the ordered list and the offer sequence, and your existing voice platform places the calls, provided it can report each attempt and outcome back with a timestamp. Confirm that reporting exists before you design around it, because a telephony platform that cannot evidence a no answer leaves a hole in the record you are trying to close.
Should a small cooperative utility build a callout system?
No. With a few dozen field staff, one standby crew and a dispatcher who knows everyone by name, the rules complexity does not justify software of any kind, let alone custom software. Write your callout procedure down, keep an ordered log by hand, and spend the money on vegetation management. We turn this work away and would rather say so on the first call.
What is the difference between callout software and workforce scheduling?
Scheduling assigns planned work to available people against skills and shifts. Callout assembles unplanned crews at 11pm in a legally constrained order set by a collective agreement, where the offer itself has consequences whether or not it is accepted. Scheduling optimises for efficiency. Callout optimises for defensibility, which is why generic workforce products handle the first well and the second poorly.
How much does mutual assistance management add to a build?
Treat it as its own phase within the $180,000 to $400,000 platform band rather than as a feature. It carries crew rosters from assisting utilities and contractors, qualifications and clearances, staging assignments, lodging and meals, guide assignment, daily time capture and contractor rate application. Getting time capture right at the source is what stops invoice reconciliation becoming a six week argument in March.
Can the system publish estimated restoration times we can defend?
It can, if the estimate derives from actual crew assignment and reported restoration progress rather than from a whiteboard judgement. That means callout, assignment and outage data have to sit in one place. The benefit is not only customer communication. When a regulator asks how a published estimate was produced, an answer traceable to assignment records is a different conversation from an answer traceable to a supervisor's memory.
What happens if the telephony provider degrades during a regional storm?
Ask this question of every vendor and every developer before signing. The acceptable answer involves fallback channels, queued retries, and a dispatcher view that clearly separates attempted from delivered, so nobody assumes a person was reached when they were not. An architecture that assumes the voice interface is always available has not been designed for the only conditions in which it matters.
Should we build for one bargaining unit first or all of them?
One unit and one district's storm process first, proved in a real event, then expand. Building for every agreement at once multiplies the test surface before anybody has validated the model, and the second unit is the honest test of whether the rules engine is genuinely configurable. If adding the second agreement needs engineering rather than configuration, the design was wrong and you want to know that early.
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 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 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.
Can a custom field service app sync with QuickBooks and the payment processor we already use?
Yes, and it should be scoped as a named workstream rather than a finishing task. QuickBooks Online, Xero, Stripe, and Square all offer mature APIs, and a two-way invoice and payment sync typically adds $8,000 to $20,000 to a build depending on how items, taxes, and customers map. The decision that matters most is source of truth: agree which system owns customer records and pricing before development starts, or you will reconcile duplicates forever.
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.
Should I hire a freelancer or an agency to build my field service software?
An agency in almost every case, because a field service build spans a mobile app, a dispatch web console, a backend, offline sync, and accounting integrations, which is four or five specialties one person rarely covers. A freelancer is the right choice for a single integration or a well-scoped add-on under $15,000. The solo-built field service systems Digital Heroes inherits fail most often at handover, when the freelancer has moved on and nobody can safely modify the sync engine.
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.
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.
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 long does it take to build a custom field service app with scheduling, dispatch, and a technician mobile app?
Plan on 12 to 16 weeks for a working first release covering scheduling, dispatch, and a technician mobile app, and 5 to 7 months for a full platform with offline mode and accounting sync. Across 2,000+ Digital Heroes projects, field service timelines slip in two predictable places: underscoped offline behavior and integration testing against QuickBooks or the payment processor. Both belong in week one of planning, not month four.
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 Ria.
Hydrogen & Headless Lead · Delhi · 3 posts on the site
Published · Last updated .
