811 Damage Prevention Software: Buy Irth or KorTerra, or Build Your Own Ticket Platform?
Annual ticket volume and the number of one call centres you receive from decide this.
On this page
Annual ticket volume and the number of one call centres you receive from decide this. Under roughly 20,000 tickets a year in a single state with straightforward screening, buy a managed platform such as Irth Solutions UtiliSphere or KorTerra and put the difference into locator training, which moves your damage rate more than software does at that volume. The case for building strengthens past roughly 200,000 tickets a year, at any volume across more than one one call centre, or where you manage contract locators whose performance you cannot measure. That build runs $80,000 to $500,000.
When is off the shelf genuinely the right call here?
Buy when you take a modest ticket volume in a single state with straightforward facilities. Under about 20,000 tickets a year the managed platforms handle it well and the marginal value of your own screening engine is low, because your whole territory is effectively one buffer rule. Spend the difference on locator training instead, which is the intervention that actually moves damage rates at that scale.
Irth Solutions UtiliSphere is a widely used ticket management platform in North America and it does the core job: intake from one call centres, screening, routing, positive response and reporting. KorTerra covers similar ground with ticket management, dispatch and analytics. Pelican Corp brings real depth from markets with different one call structures, which is a strength in breadth and a consideration in fit given how much North American variation is state by state. ProStar PointMan is a different animal, focused on precision location capture of facilities as they are located and installed, and it complements the others rather than replacing them.
The trade off with all of the managed platforms is the same and it is verifiable rather than a criticism. Screening logic, workflow and reporting work their way, changes to fit your operation go through their roadmap rather than yours, and pricing generally scales with ticket volume. For a single state operator at moderate volume that is a fair deal.
Buy, too, if your evidence problem is really a training problem. If locators are not photographing marks because nobody told them to, a new platform will not change that.
When does a custom build actually pay off?
Three conditions, and the third is the one operators underrate.
You receive tickets from more than one one call centre. Each centre has its own ticket format, its own response clock definition including how it counts working days and holidays, and its own positive response code set. A manager tracking four states in a dashboard built for one is going to be wrong somewhere, and an emergency ticket that inherits a routine response window is a safety failure rather than a defect.
Your ticket volume makes per ticket pricing painful. Because managed platforms commonly price in a way that scales with tickets, the build case strengthens as volume rises. At a few hundred thousand tickets a year the annual fee starts approaching a one time build plus hosting and support, and the comparison usually stops being close.
And you manage contract locators whose quality you cannot measure. If you cannot show which locator marked a site, when, and what the marks looked like before the excavation, you are settling damage claims on the excavator's version of events. That cost does not appear in the software budget at all.
Underneath all three sits the consistent gap in the managed products: ownership of your geographic information system, referred to below as GIS, as the screening source of truth, and ownership of the evidence package. Screening quality depends on buffer rules tuned against your own damage history, which requires joining ticket outcomes back to facility data you control.
How do they compare on the things that matter in this industry?
Compare these rather than feature grids, because each is checkable against your own last damage claim.
- Screening tuned by outcome. Parse the work area geometry where the centre supplies it, geocode where it does not, and buffer by facility type since a transmission main warrants a wider buffer than a service line. The part that separates a build is the feedback loop: when a damage occurs, check whether screening had cleared that ticket, and tune buffers against real outcomes over a season rather than against a setting chosen years ago by someone who has retired.
- Clock arithmetic per state. Due time computed against each state's working day definition and holiday calendar, with different handling for emergency, update, relocate, design and cancellation tickets. A single countdown across state lines is the most common way a response window gets missed at scale.
- Positive response fidelity. The response code is your legal statement. When a dispatcher submits it from a status field the locator updated at the end of the day from memory, the code and reality drift. Submission direct from field completion removes that gap.
- Field evidence. The location track of the actual locate walk, timestamped and geotagged photographs of the marks before excavation, equipment used, sweep pattern and site conditions. Photos of marks taken before the dig are the single most valuable artefact in a dispute and almost nobody captures them systematically.
- Claim assembly. Ticket text, screening decision and reasoning, dispatch record, locator evidence, positive response confirmation and as built records as one artefact. Assembling that by hand from four systems after a strike is how programmes lose recoverable money.
- Contractor measurement. Damage rate per thousand tickets by locator and area, implausibly short completion times, evidence completeness, and reconciliation of completed tickets against invoiced counts.
What does total cost of ownership look like at your scale?
From Digital Heroes delivery experience, an intake and dispatch core runs $80,000 to $160,000 over 12 to 18 weeks: ticket intake and normalisation from each centre, screening against your facility footprint with your own buffer rules, dispatch with the statutory response clock visible on every open ticket, and automated positive response submission. A full damage prevention platform runs $220,000 to $500,000 over 9 to 15 months, adding the locator mobile application with location tracking and marks photography, contractor performance scoring, damage claim assembly and cost recovery. Analytics and prevention work adds $40,000 to $110,000.
A gas distribution utility taking roughly 340,000 tickets a year across two states, with about 60 contract locators and 14 internal, lands at $129,000 for a first release over sixteen weeks and $383,000 for the whole programme across roughly thirteen months.
Running cost is 15 to 20 percent of build cost a year for support with a genuine peak season response commitment, so $57,000 to $77,000 on that programme. Add $12,000 to $40,000 for hosting provisioned to the spring peak rather than the annual average, $6,000 to $18,000 for GIS synchronisation upkeep, $5,000 to $20,000 each time a one call centre changes its format, $5,000 to $15,000 a year for locator training given contractor turnover, and $300 to $900 per locator every few years for rugged devices.
One honest caveat about payback. Building does not reduce your ticket volume, and it will not by itself reduce damages. What it does is make the response defensible and the recovery collectable, and it moves per ticket cost from a variable fee into a fixed asset. Only the second of those shows up cleanly in a budget comparison.
What does the hybrid look like, and when is it the honest answer?
There is a real hybrid here and for two state operators at moderate volume it is usually the right first move: keep the managed platform for intake and positive response, and build only the screening engine and the evidence layer.
The managed platform continues receiving tickets and submitting response codes, which is the part with regulatory plumbing attached and the part that already works. What you build is screening against your own facility data with buffers you tune against your own damage outcomes, and the field evidence and claim assembly that decides disputes eighteen months later.
That aims spend at the two things the managed products structurally do not own, and it can be delivered inside a quarter rather than across a year. It also lets you keep a locating contractor's existing field tool in phase one and take their data rather than replacing it immediately, then replace it in phase two once you know what evidence you actually need.
Be clear about the limit. The hybrid does not remove per ticket platform pricing, so if your business case rests on converting a variable fee into a fixed asset, the hybrid does not deliver it. Choose the hybrid when screening quality and claim evidence are the pain, and the full build when the fee itself is.
Which should you choose, by operator size and stage?
Under 20,000 tickets a year, single state, straightforward facilities: buy. Irth or KorTerra, configured properly, and put the money into locator training. We would tell you this before quoting anything.
Twenty thousand to 200,000 tickets, single state: buy, then instrument the decision for one dig season. Count how many damage claims you settled or abandoned for lack of evidence, and how many tickets your screening cleared that later produced a damage. Those two numbers, not a proposal, tell you whether the evidence layer is worth building.
Any volume across two or more one call centres: build at least the intake and clock layer. This is where a dashboard built for one state quietly goes wrong, and it is worth noting that the second centre is close to double the intake work while the third and fourth cost progressively less.
Past roughly 200,000 tickets a year: build, and run the arithmetic on your current annual platform spend against a one time build plus hosting and support before you renew.
Operators with large contract locator workforces: build the evidence layer regardless of volume, but defer contractor scorecards to phase two. Scores need a full season of clean data before they mean anything, and publishing unreliable scores damages the relationship you depend on during peak season.
Whatever you choose, sequence around the calendar. Get intake, screening and dispatch live before spring, because the season is the test and missing it costs a year. Add the second state only after a complete season in the first.
If you want that decision made properly rather than quickly, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. You can take that specification to any other firm on your shortlist.
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) →
- 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) →
- In an October 2025 survey of 530 small-business employers (conducted by TechnoMetrica, October 3-9, 2025), 88% reported using AI tools and 73% said those tools had been important to their competitiveness and growth over the past year, with 60% citing efficiency and productivity as the primary motivation for adoption (42% cited improving customer service). Source: Small Business & Entrepreneurship Council (SBE Council) (2025) →
- Gallup reports global employee engagement fell to 20% in 2025 (its lowest since 2020, down from a 2022-2023 peak of 23%), and estimates low engagement costs the world economy an estimated $10 trillion in lost productivity, or 9% of global GDP. (Note: this figure appears in Gallup's evergreen State of the Global Workplace page, currently reflecting the 2026 edition reporting on 2025 data.). Source: Gallup (2025) →
Frequently asked questions
Is Irth or KorTerra good enough, or should we build?
Both handle the core job well and are the right answer for a single state operator with moderate volume and straightforward screening. Under about 20,000 tickets a year the comparison clearly favours buying and we would say so.
The build case strengthens when you take tickets from several one call centres, when per ticket pricing at your volume starts to look like a build budget every year, and when you want screening buffers tuned against your own damage history using your own facility data rather than a vendor's configuration model.
What does it cost to leave a managed platform later if we build the screening layer first?
Materially less than switching cold, because the layer already holds the parts that are painful to recreate: your screening rules and their tuning history, your facility buffer configuration, and the field evidence and claim files that carry long retention obligations.
What remains is the intake adapter and positive response integration for each centre, which is contained work at roughly the cost of building them the first time. Confirm ownership of the repository, database and cloud accounts in writing before kickoff, because ticket and locate records can be subpoenaed years later.
What happens if our platform vendor changes per ticket pricing?
At low volume it is an irritation. Past a few hundred thousand tickets a year it is a budget event, because the fee scales with a number that grows every dig season and is outside your control.
Model it against your projected ticket growth rather than last year's count. A build converts that variable fee into a fixed asset plus a support retainer, which is the clearest part of the business case, and it is worth running before your next renewal rather than after.
How long does an 811 ticket platform take to build?
Twelve to 18 weeks for the intake and dispatch core, and 9 to 15 months for the full platform including field evidence, contractor scoring and cost recovery, phased so each quarter puts something into production.
Timing matters more than duration. Get intake, screening and dispatch live before spring, because the season is the real test under volume and missing it costs a full year of learning. Sequence a second state only after a complete season in the first.
How do you screen tickets against facility data accurately?
Parse the work area geometry where the one call centre supplies it, geocode where it does not, and buffer against your facility layers with rules that vary by facility type, since a transmission main warrants a wider buffer than a service line.
The part most operators skip is the feedback loop. When a damage occurs, check whether screening had cleared that ticket, and use those outcomes to tune buffers over a season. Screening tuned by outcome is the main advantage a custom build has over a configured product.
What does poor GIS data do to the project?
It does not raise the software price directly, but it lands in the same budget conversation. Screening against incomplete facility data produces confident wrong answers, clearing tickets that should have gone to a locator, which is worse than not screening at all.
Cleaning geographic information system data is a parallel workstream with its own owner and its own timeline. Screening quality also degrades quietly afterwards if the ongoing synchronisation breaks, which is why $6,000 to $18,000 a year is budgeted for keeping it current.
Should contractor performance scoring be in the first phase?
No. Scores need a full season of clean data before they mean anything, and publishing unreliable scores to a locating contractor damages the relationship you depend on most during peak season.
Build it in phase two at around $34,000, once location tracking and marks evidence are flowing and you can defend every number in the scorecard. Reconciling completed tickets in your system against invoiced counts usually pays for the reporting work on its own.
Does the locator application need to work without a signal?
Yes. Locates happen in rural corridors, basements and construction sites with no coverage, so the application must hold assigned tickets, capture location tracks, photographs and notes offline, and synchronise reliably afterwards.
Photograph capture with embedded timestamp and location has to survive that synchronisation intact, because an image whose metadata was stripped is much weaker evidence in a dispute. Ask any developer what their application does with no signal for eight hours, and treat a vague answer as an answer.
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.
Do my field technicians need a native mobile app, or will a web app work?
If your technicians ever work in weak signal, you need a native or offline-capable app, because a plain web app fails exactly where field work happens: basements, mechanical rooms, and rural routes. Cross-platform frameworks like React Native or Flutter give one codebase for iPhone and Android with full offline storage, which is how Digital Heroes builds most technician apps. A web app is the right call for the office dispatch console, where connectivity is guaranteed.
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.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
How long until a custom field service platform pays for itself compared to per-technician licenses?
For most shops the crossover lands between 18 and 36 months once upkeep is counted. A 25-technician company paying $300 per technician per month for licenses spends $90,000 a year, so a $120,000 custom build with $20,000 in annual maintenance breaks even around month 21, before counting saved dispatch hours and billing errors. Below about 10 technicians the math rarely works, and Jobber or Housecall Pro is the honest recommendation.
How 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 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.
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 Aisha.
Project Manager · UK · London · 3 posts on the site
Published · Last updated .
