Telecom Site Power Monitoring Software: Build Custom or Buy Vertiv
Buy. Under roughly 150 sites on a substantially single vendor rectifier estate, the manufacturer's own monitoring plus a disciplined battery replacement programme is the right spend, and the money is better used on strings and tank senders.
On this page
Buy. Under roughly 150 sites on a substantially single vendor rectifier estate, the manufacturer's own monitoring plus a disciplined battery replacement programme is the right spend, and the money is better used on strings and tank senders. Building starts to earn its place on a genuinely multi vendor fleet where fuel and battery spend is large and a site down event carries a contractual cost.
What Vertiv, Schneider, Eaton and Galooli actually do well
It is 2:14am and a storm line has crossed a region where you run 900 macro sites. The operations wall shows 63 power alarms. Forty are mains fail on sites with healthy strings and eight hours of autonomy, which is noise. Six are on sites whose battery string was last capacity tested four years ago. Two of those six carry a hospital's dedicated fibre and a public safety tenant, and nobody on shift can say which two.
Vertiv Environet, Schneider Electric EcoStruxure and Eaton Brightlayer present the state their own hardware reports, and inside a coherent single vendor estate they do it properly. Asset records, thresholds, alarm forwarding, trending and the reports an infrastructure manager needs are all there, and the integration to their own controllers is already done and tested against firmware you have not seen yet. Galooli is worth knowing about specifically because it was built for remote telecom sites with generators and fuel rather than for data centre halls, which is a different design starting point.
If most of your rectifiers come from one of those manufacturers, start there. A custom build would be an expensive route to a similar screen, and the difference would show up in your capital budget rather than your uptime. The same applies if your sites are grid stable, mostly battery only with no generators, and your fuel spend is negligible, because two of the three hard problems below simply do not apply to you.
Where they stop: a mixed fleet and the criticality nobody wrote down
A valve regulated lead acid string does not announce its decline. Float voltage looks perfect right up to the moment it has to deliver current, and then a string rated for eight hours gives you forty minutes. The traditional answer is a scheduled discharge test, which nobody performs at fleet scale because it means taking a live site to battery on purpose and risking exactly the outage you are trying to avoid.
The manufacturer platforms show what their hardware reports. They do not build a health opinion from your fleet's own outage history, because they have not seen your fleet's history. On an outdoor estate accumulated over fifteen years of acquisitions and build programmes, you have four rectifier families, two generator controller brands, some sites with string level monitoring and many with nothing but a shunt.
The second stopping point is criticality. Every operator eventually reaches the point where the operations centre filters power alarms because there are too many, and that is the real failure state: not a missing alarm, an ignored one. A mains fail on a site with a working generator and a full tank and a mains fail on a battery only site with a degraded string arrive looking identical. Fixing that requires site tiering that reflects your tenants, your backhaul topology and any public safety obligations, plus travel time from wherever your technicians actually are. That is commercial and organisational data, not telemetry, and no vendor can supply it.
The third is fuel. Diesel delivery usually runs on a calendar, so stable sites get topped up nearly full while storm exposed sites run dry in the week they were needed. The gap between fuel purchased and fuel that could have been burned given actual run hours is where theft lives, and on a contracted delivery estate nobody reconciles it.
The arithmetic: cost per site per month versus a build
Monitoring platforms in this category are priced per site or per monitored device per month, usually with a separate licence for the analytics tier and a per site commissioning charge. Get the three year total including commissioning onto one page and divide by your site count and twelve.
Now the build. A first release covering edge collection with store and forward, two or three rectifier and generator families, battery health scoring from opportunistic discharge, fuel burn modelling with delivery reconciliation and criticality ranked alarm triage runs $70,000 to $150,000 in our delivery experience. Amortise the midpoint over five years, add year two support at the rate below, and you carry roughly $30,000 to $37,000 a year.
At 900 sites that is $2.80 to $3.40 per site per month. At 300 sites it is $8.30 to $10.30. At 120 sites it is $21 to $26, which is why we tell small fleets to buy. Against a subscription of $8 per site per month the crossover sits near 310 to 385 sites. Against $15 it falls to roughly 165 to 205.
Neither figure decides it on its own. Put your annual diesel spend and your annual battery replacement capital on the same page. A 10 percent improvement on either, which is a conservative expectation once deliveries follow measured autonomy rather than a calendar and replacements follow risk rather than install date, is usually a larger number than the entire software line at any site count above a few hundred.
What a custom build actually costs
A first release covering edge collection with store and forward, ingest from your two or three highest count controller families, battery health scoring from opportunistic discharge, fuel burn modelling with delivery reconciliation and criticality ranked triage runs $70,000 to $150,000 across 12 to 18 weeks.
A full platform adding dispatch integration, generator preventive maintenance, spares and battery capital planning, tenant service level and outage evidence reporting and a contractor portal runs $180,000 to $450,000 phased over 8 to 14 months.
Data migration lands at 10 to 25 percent of build cost, and in this category most of it is not data at all. It is the protocol layer. Plan one to three weeks per controller family including a lab unit and a live site validation, and do not skip the lab unit, because a manufacturer's documented register map and the map implemented in a specific firmware version are not always the same document. Your first release should cover the two or three families holding most of your sites, with the long tail funded as backlog rather than treated as a launch dependency.
Year two runs 15 to 20 percent of build cost annually. The drivers are firmware vintages changing underneath you, new hardware entering the fleet through acquisitions, and the sites that need a tank sender or a shunt fitted before they can report anything at all. That last item is field capital rather than software, and it belongs in the same business case.
The four situations where building wins
- Standards and evidence fit. Your estate speaks Modbus over serial and over network transport, simple network management protocol traps from newer controllers, and DNP3 at any site inherited from a utility partnership. Battery maintenance practice follows the recommended practices published for valve regulated and vented lead acid cells, and a tenant with service credits will want outage evidence that survives scrutiny. When one telemetry stream has to satisfy engineering, finance and a contractual claim, it belongs in a system you own.
- Scale economics. Past roughly 165 to 385 sites depending on your quoted per site rate, the arithmetic above turns. Under 150 sites on one manufacturer, it does not.
- A workflow that is your advantage. Tower companies and neutral host operators sell uptime to multiple tenants with different criticality, so predicted time to site down ranked against tenant obligations is the product rather than a report. Encoding criticality tiering that today lives in someone's head is worth doing regardless of which system you end up with.
- Integration sprawl across three or more systems. Count them: rectifier controllers, generator controllers, the alarm collector, the field service scheduling system, the fuel supplier's delivery dockets and your asset register. Once three or more must agree about one site at two in the morning, the fusion layer is the product and no manufacturer sells it.
How to decide in a week
Take your last ten unplanned mains failure events across the fleet. For each one, try to produce four things: the discharge curve, the load in amps at the time, the ambient temperature, and the time to recovery. Give it a day.
Count how many of the ten you have complete. Every unplanned mains failure is a free capacity test if you captured it, so the gap between ten and your answer is the number of free tests you threw away last quarter. If you can produce eight, your telemetry is good and better analytics may be all you need. If you can produce two, the problem is collection rather than intelligence, and the first thing to fix is buffering at the edge, because backhaul drops exactly when the interesting events happen.
Run the fuel test in parallel. Take last quarter's delivery dockets for ten generator sites, and beside each one write the run hours reported by the controller and the tank level step the delivery should have produced. Any docket claiming 400 litres into a tank that rose by 220 is an exception you paid for. Any site burning fuel with no corresponding run hours is a leak or a siphon.
Third, ask your operations centre a question with a stopwatch running. Of the sites currently on battery, which will die first and which one hurts most. If the answer requires opening a spreadsheet maintained by another team, you have found the reason alarms get filtered.
If the tests point to building, take a paid discovery phase rather than a proposal. Digital Heroes runs discovery to a signed product requirements document covering the protocol inventory, the health scoring method, criticality tiering and acceptance criteria. The specification is yours to take to any other firm on your shortlist. We are the wrong partner if your fleet is single vendor and under 150 sites, because we would be selling you a build that your manufacturer already covers. We are an India LLP with US LLC and UK LTD entities so intellectual property assigns under your own law, with more than fifty specialists, over 2,000 projects delivered, a named team you meet before signing, and a public record 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.
- Timefold reports field service operations moving to automated route optimization typically see 10-25% fuel savings and 15-30% drive-time reductions, and documents a case where a global services firm cut drive time 33% and distance 43% while eliminating overtime. Source: Timefold (2025) →
- PTC identifies the leading causes of failed first visits as parts unavailability (the single most-cited complaint, named by 51% of field service executives), technicians lacking the required equipment or skills, and insufficient time allocated to the job - making parts logistics and skills-based dispatch the highest-leverage fixes. Source: PTC (2023) →
- Per the Standish Group CHAOS 2020 report (reviewed at this URL), across tens of thousands of software projects roughly 31% end successfully, about 50% are 'challenged', and roughly 19% fail outright; small projects succeed far more often than large ones, and Agile approaches succeed at markedly higher rates than Waterfall. Source: The Standish Group (2020) →
- Brandon Hall Group research on onboarding reports that done well, structured onboarding drives measurable gains in new-hire productivity, employee engagement, and retention; the page notes 41% of organizations experience greater than 5% turnover among new hires. Source: Brandon Hall Group (2024) →
Frequently asked questions
Can we detect battery degradation without scheduled discharge tests?
Yes, and it is the single highest value capability in this category. Every unplanned mains failure is a free capacity test if you capture the discharge curve, load in amps and ambient temperature, then trend it per string against rated capacity with temperature compensation. Sites that never discharge get flagged for a deliberate test precisely because they generate no data, which is a small minority worth sending a crew to.
How do we catch generator fuel theft across remote sites?
Model each site's litres per run hour from its own history, then reconcile three numbers that should agree: predicted burn, delivered litres on the docket, and the tank level step the delivery produced. A docket claiming 400 litres into a tank that rose by 220 becomes an exception before the invoice is paid. This needs a tank sender at the sites where fuel volume justifies the hardware, normally the storm exposed generator sites.
How long does it take to integrate our rectifier and generator controllers?
Plan one to three weeks per controller family including a lab unit and a live site validation. Do not skip the lab unit, because a manufacturer's documented register map and the map implemented in a particular firmware version are not always the same thing. Scope the first release around the two or three families covering most of your sites and treat the long tail as funded backlog rather than a launch blocker.
What happens to telemetry when a site loses backhaul during an outage?
This is the case that decides whether the system is useful, because backhaul drops exactly when the interesting events happen. The edge collector must buffer locally and replay on reconnect, otherwise you lose the discharge curve for every outage that mattered. Ask any prospective developer this question first. If store and forward is not in their answer, they have built for data centres rather than outdoor sites.
Can this drive field dispatch rather than just raise alarms?
It should, and that is where it stops being a dashboard. The useful output is predicted time to site down, computed from current load, battery state of health and generator status, ranked against site criticality and travel time from where your technicians actually are. That needs an integration into whatever scheduling system your field team uses, and it needs criticality tiering written down rather than remembered.
Who owns the telemetry history and the code if an agency builds this?
You should own the repository, the cloud accounts and the device credentials, written into the contract before kickoff. This matters more here than in most categories because the system accumulates years of discharge and burn history that becomes the evidence base for battery and generator capital decisions. If that history sits inside a vendor tenancy you have created a dependency you will pay to escape. At Digital Heroes the client owns everything from the first commit.
Do we need this with 120 sites on one rectifier brand?
Probably not, and we would rather say so. At that size on a coherent single vendor estate, the manufacturer's own monitoring plus a disciplined battery replacement programme is the right spend, and the money is better used on strings and tank senders. The picture changes when you cross into multiple hardware families, when generators become a material cost line, or when you carry tenants with service credits for downtime.
What is the difference between asset state monitoring and health scoring?
Asset state monitoring reports what a controller currently says: float voltage, mains present, alarm active. Health scoring builds an opinion from history, trending each string's delivered capacity against its rating across every discharge it has experienced, temperature compensated and load aware. The first tells you a site is on battery. The second tells you how long it will last and whether the string should have been replaced last year.
Can we start with fuel and add battery health later?
Yes, and for fleets with heavy generator dependence that sequence often pays back faster. Fuel modelling and delivery reconciliation need tank telemetry and run hours rather than string level battery data, so the hardware prerequisite is smaller. Battery health scoring then rides on the same edge collection and ingestion once it exists, which makes it a much cheaper second phase than it would be as a separate project.
How do we decide site criticality tiering?
Write it down with the commercial and network facts together: which tenants sit on the site, whether it is a hub carrying downstream sites or a leaf, any public safety or emergency services obligation, and what a service credit costs if it goes dark. That exercise usually takes a workshop between operations, network planning and commercial, and it is worth doing before any procurement because it changes what you are buying.
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.
What tech stack should a custom field service platform be built on?
The dependable 2026 stack is React Native or Flutter for the technician app, React for the dispatch console, Node.js or Python on the backend, and PostgreSQL with an offline sync layer on the device. Boring, widely used technology wins here because any competent team can maintain it five years from now. Be wary of an agency proposing a stack only they can staff; that is a lock-in strategy, not an engineering decision.
What does it cost per year to maintain custom field service software?
Budget 15 to 20 percent of the original build cost per year, so $15,000 to $20,000 on a $100,000 platform. That covers hosting, security patches, integration API changes, a monthly block of small improvements, and the iOS and Android updates Apple and Google ship on their own schedule. Skipping it is not a savings; the technician app needs attention every OS cycle or it eventually stops opening on new phones.
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.
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 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 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 .
