Cathodic Protection Management Software: Build or Buy at Your Rectifier and Test Point Count
The line is roughly 150 rectifiers or 1,000 test points, and more importantly whether hardware from more than two manufacturers is already in the ground.
On this page
The line is roughly 150 rectifiers or 1,000 test points, and more importantly whether hardware from more than two manufacturers is already in the ground. Below that, on one monitoring vendor and one state's rules, buy the portal and keep a disciplined spreadsheet, because a build would cost $55,000 to $120,000 to reach the same compliance position. Above it, where a third of your readings are walked and no single portal sees the whole programme, the register has to be yours. Most single system operators sit below the line. Most multi state gas distribution utilities sit above it.
When is off the shelf genuinely the right call here?
If your programme runs on one manufacturer's hardware and fits that manufacturer's data model, buy the portal. American Innovations is the most complete offering in this category and covers a standardised fleet properly. MOBILTEX CorTalk, Abriox and Elecsys build strong remote monitoring units with portals designed around their own hardware, and the units themselves are good. For an operator with 30 rectifiers and 200 test points, read by the same two technicians every year under a single state's rules, that subscription plus a well kept spreadsheet carries the compliance programme. We would say so before quoting.
Three conditions make buying the right answer, and they travel together. First, one dominant monitoring vendor, so the portal sees most of your readings rather than a slice. Second, a high remote monitoring ratio, because every rectifier that reports itself removes a field visit and a data entry error path. Third, a portal that already produces the exception list and the interval report your regulator has accepted in the format they accept it.
If all three hold, the money is better spent on more remote monitoring units than on software. Expanding telemetry coverage shrinks the manual programme, which is the expensive half of any build. Operators who plan a telemetry expansion should sequence it before a software decision rather than after, because it can move them from one side of this line to the other.
What buying does not do is prove that your whole compliance programme is complete across assets the vendor did not manufacture, including the large share with no sensor at all. That is a configuration ceiling, not a criticism of the hardware. These platforms are device first by design.
When does a custom build actually pay off?
Build when proving compliance costs more effort than achieving it. In our delivery experience that point arrives through one of four specific conditions, not through asset count alone.
- Mixed telemetry already installed. Hardware from more than two manufacturers means no portal covers the fleet. One vendor samples at a fixed hour, another gives you both on potential and instant off on a synchronised interrupter cycle, a third reports rectifier output only, and timestamps arrive in three time conventions.
- A large walked programme. If 3,000 test points are read on annual routes with a voltmeter, the portal sees perhaps a third of your readings. The remaining two thirds are the ones that break intervals.
- Several rule sets. Operating across state lines, or across regulated transmission, distribution and unregulated assets such as tank farms, means different intervals and criteria applying to different asset classes in one fleet.
- Readings feeding the capital plan. When a test point drifting across three consecutive surveys has to sit next to leak history on the same pipe segment, you need the corrosion record joined to your geographic information system. No monitoring portal owns your geographic information system or your leak history.
There is a fifth trigger that is less about workflow. Records of these tests must be retained for as long as the pipeline stays in service under 49 CFR 192.491, which for buried steel is effectively permanent. History held in a portal you may stop paying for is a real exposure, and it is the least discussed part of this decision.
How do they compare on the things that matter in corrosion control?
On interval logic, portals track their own units well. The rule in 49 CFR 192.465 imposes two constraints at once: six rectifier inspections each calendar year and gaps not exceeding two and a half months. A technician who reads on January 5 and again on March 25 has satisfied the count and broken the gap. A system that models the applicable rule per asset, computes a last legal date and routes from that date catches this. A count based tracker does not, and neither does a portal covering only part of the fleet.
On reading fidelity, both approaches can be correct, but a build lets you define one reading object carrying source, measurement method, reference electrode, instrument and calibration date. The protection criteria in Appendix D of Part 192 are written against a saturated copper sulfate half cell, so the raw value and the electrode both need storing, with conversion at evaluation time rather than on ingest. Convert on the way in and the original evidence is gone.
On spatial context, this is the clearest split. A reading of negative 780 millivolts is a fact about a segment of coated steel with a vintage, a coating, a casing and a neighbouring foreign line, not a fact about a test station. Segment linkage is what turns a reading into a work plan and into an argument for replacement capital under Subpart P.
On deficiency handling, portals raise alarms. A case with an owner, a clock, a cause code and a hard rule that it cannot close without a verification reading meeting criterion is a different object. The cause codes are the quiet payoff after a year, when failures start clustering by manufacturer or by contractor.
On data portability, an owned register means changing monitoring hardware becomes a procurement decision rather than a migration project.
What does total cost of ownership look like at your scale?
Build costs run in three bands. A reading register with an asset list, recorded readings, interval clocks and a compliance summary is $30,000 to $55,000. A first production release adding remote monitoring feeds, offline field capture on route sheets, automatic criteria evaluation, an exception queue and remediation closeout is $55,000 to $120,000 and ships in 10 to 14 weeks. A full platform adding segment linkage, close interval and coating defect survey handling, interference coordination and annual reporting is $150,000 to $400,000 phased over 6 to 12 months.
Inside those bands, specific lines drive the number. Each remote monitoring vendor onboarded adds $6,000 to $12,000, and older units in a fleet often predate their own vendor's current interface. Segment linkage to your geographic information system adds $18,000 to $32,000. Survey data handling adds $15,000 to $28,000. Manual route management with sequencing and offline capture adds $12,000 to $20,000.
A worked example: a gas distribution utility with 420 rectifiers, two thirds remotely monitored across two vendors, and 3,100 test points read on annual routes by four technicians. Discovery and interval rule mapping $8,000, two vendor feeds $18,000, manual capture with offline route sheets $16,000, criteria evaluation and exception queue $15,000, remediation with interval closeout $14,000, segment linkage $13,000, historic migration and annual report output $11,000. Total $95,000.
Annual running cost is the part quotes omit. Plan on a support retainer of 12 to 18 percent of build cost, hosting and reading retention of $3,000 to $8,000, rule and criteria changes of $5,000 to $12,000, and synchronisation with your geographic information system of $4,000 to $10,000. Vendor onboarding recurs as units are replaced. Note that the monitoring vendor's per unit subscription continues either way, so it is not a saving you can claim against a build.
What does the hybrid look like, and when is it the honest answer?
Buy the hardware and the portals, build the thin register that sits above them. This is the right answer more often than either extreme, and it is what most of our corrosion control work actually is.
The portals keep doing what they are good at: collecting from their own units, alarming on their own thresholds, holding the vendor relationship. The layer you own does four things they structurally cannot. It holds one reading record across every source including paper. It computes the interval clock per asset against the rule that applies to that asset class. It runs the exception queue and the deficiency case to closure with a verification reading. And it keeps your history where a vendor change cannot strand it.
Scoped that way, the build starts at the $30,000 to $55,000 register band rather than at a platform price. Prove the feed, the criteria evaluation and the exception queue on your dominant vendor first, then add the second. Keep close interval survey work with the contractor for now, at $15,000 to $28,000 it is the easiest line to defer and it is usually commissioned in campaigns anyway. Leave repair execution in the work management system where crews already sit. The exception queue is the valuable part, not the work order.
Add segment linkage in a second phase once the reading record is trustworthy. That sequencing matters, because linking a reading history you do not yet trust to a pipe network model produces confident nonsense.
Which should you choose, by operator size and stage?
Under 50 rectifiers, single state, one vendor. Buy. Use the portal, keep the spreadsheet, spend the difference on telemetry. A build here is an expensive route to a compliance position you already hold.
Roughly 50 to 150 rectifiers, one dominant vendor, growing manual programme. Buy, but start documenting where the portal is blind. Specifically, count what share of your readings it never sees. When that share passes a third, the decision has already changed even if the asset count has not.
Above 150 rectifiers or 1,000 test points, two or more manufacturers installed. Build the register. Take the $55,000 to $120,000 first release, start with rectifiers and critical bonds only because they carry the tightest interval on the smallest asset count, and let each route move across as it comes due.
Multi state operators, or anyone whose asset list disagrees with their geographic information system after acquisitions. Build, and budget for reconciliation as discovery work measured in weeks. This is the item most often underestimated, and it is not a software problem.
Anyone whose corrosion data needs to argue for replacement capital. Build the full platform, phased. At that point the system stops being a compliance chore and becomes an input to the capital plan, which is the only version of this investment that pays back beyond avoiding findings.
If you would rather someone argued with your brief than agreed with it, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- ServiceTitan's KPI guide cites an average first-time fix rate near 80% (90% ideal) and describes strong technician-utilization rates as falling in the 60-80% band, with average travel time typically 30-60 minutes depending on service-area size. Source: ServiceTitan (2026) →
- 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) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- McKinsey argues software developer productivity can be measured by combining system-level metrics (DORA and SPACE) with its own outcome-oriented approach, which it reports deploying across nearly 20 tech, finance, and pharmaceutical companies - a claim that sparked significant debate in the engineering community. Source: McKinsey & Company (2023) →
Frequently asked questions
What happens to our reading history if we switch remote monitoring vendors?
If the history lives in the vendor portal, it stays there. Records of these tests must be retained for as long as the pipeline remains in service under 49 CFR 192.491, which for buried steel is effectively permanent, so a portal you stop paying for is a serious problem. Holding readings in your own register with vendor adapters on the edge turns a hardware change into a procurement decision rather than a migration project. Ask any prospective vendor for a full historical export in a documented format before you sign.
What if our monitoring vendor changes its per unit subscription pricing?
Per unit subscriptions continue whether you build or buy, because they are attached to the hardware rather than to the software layer. What changes is your position. If the portal is also your compliance register, a price change is a negotiation you cannot walk away from without losing your record. If you own the register and the portal is one of several feeds, you can move a tranche of units to another manufacturer at replacement time. Onboarding that new vendor costs $6,000 to $12,000, which is the real price of that option.
How long does it take to build cathodic protection compliance software?
A first production release ships in 10 to 14 weeks when your asset list is reliable and you are integrating one or two telemetry vendors. A reading register alone is faster. A full platform is phased across 6 to 12 months. The schedule risk is almost never the software. It is reconciling the corrosion asset list against your geographic information system, which on systems that have been through acquisitions takes several weeks of genuine investigation before anyone can say which test station protects which segment.
Is American Innovations enough, or do we need to build?
American Innovations is the right answer if you standardise on their hardware and your programme fits their data model. The limitation is structural rather than a quality gap: the platform is device first, so it reports accurately on its own units and is not built to prove completeness across assets it did not manufacture, including the ones with no telemetry. It also does not hold your geographic information system or your leak history, so correlating a drifting test point with corrosion leaks on a segment stays manual. Mixed fleets across several states are where the build case becomes clear.
How much does it cost to switch off a portal and onto our own system?
The switching cost is mostly data, not code. Budget $6,000 to $12,000 per monitoring vendor for the feed adapter, plus historic reading migration, which in a 400 rectifier programme runs around $11,000 alongside the annual report output. The hidden cost is interval continuity: a test point read in March under the old process and April under the new one still has to show unbroken interval history. Migrate the open interval state first, then move each route as it comes due, which spreads the change across a season.
Can we run vendor portals and a custom register at the same time?
Yes, and that is the recommended shape. The portals keep collecting from their own units and holding the hardware relationship. Your register normalises every source into one reading object, computes the interval clock per asset, runs the exception queue and holds the permanent record. Scoped that way the build starts in the $30,000 to $55,000 band rather than at platform prices. Prove it on your dominant vendor before adding the second.
At what point does a spreadsheet stop being good enough?
When one person can no longer hold the programme in memory. Practically that is above roughly 150 rectifiers or 1,000 test points, or when hardware from more than two manufacturers is installed, or when you operate across more than one state rule set. The specific failure a spreadsheet cannot catch is the two constraint interval rule in 49 CFR 192.465, where an asset can satisfy six readings in a calendar year and still break the two and a half month gap. Sorting by date shows that as compliant.
Should close interval survey data be in the first build?
Usually not. Close interval and coating defect survey data are dense spatial datasets with their own interpretation rules, costing $15,000 to $28,000 to handle properly, and they are typically commissioned as contractor campaigns with their own deliverables. Keep them with the contractor while you get periodic readings, criteria evaluation and the exception queue working. Bring them in during a later phase once the reading record is trustworthy enough to align them against.
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 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 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.
Will custom field service software scale if we grow from 10 technicians to 100?
Yes, when it is architected for growth from day one, and scale is where custom wins because cost per technician falls as you add crews instead of rising with every seat license. The real scaling work is operational: multi-branch dispatch, role permissions, and roll-up reporting, which usually arrives as a phase two costing 30 to 50 percent of the original build. State your three-year headcount plan in the first scoping call so the data model supports branch two before branch two exists.
What 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.
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.
We're outgrowing Jobber. Should we move up to ServiceTitan or build our own?
Move to ServiceTitan if the problem is missing features on a standard residential trades workflow, because migrating between products is far cheaper than building. Build custom when the problem is fit: multi-day commercial jobs, subcontractor crews, or pricing rules that neither Jobber's Grow plan (about $199 per month billed annually, up to 15 users) nor ServiceTitan models cleanly. In Digital Heroes scoping calls, about half the teams asking this question turn out to need an integration or add-on rather than a new platform, so name the exact workflow gap before committing either way.
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.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
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 Mason.
Product Designer · Sydney · 1 post on the site
Published · Last updated .
