Utility Locate Ticket Management Software: Custom Build vs Irth and KorTerra
Buy Irth or KorTerra. If you own facilities in one state and take a few thousand 811 tickets a year, a product will beat a build on cost and on time to value, and we will tell you so.
On this page
Buy Irth or KorTerra. If you own facilities in one state and take a few thousand 811 tickets a year, a product will beat a build on cost and on time to value, and we will tell you so. Build once you cross roughly 100,000 tickets a year, work across several one call centres, or have already had a strike you could not defend with the records you hold.
What Irth, KorTerra, PelicanCorp and ProStar actually do well
A directional bore clips a fibre trunk on a Thursday afternoon. Within an hour the excavator's position is that the line was not marked. Your position is that it was, eight days ago. The proof is a photograph showing orange paint on asphalt with no scale, no landmark and a timestamp nobody can vouch for. Before deciding whether to build anything, understand that products already solve a large part of this.
Irth Solutions and KorTerra both handle ticket management, screening and workflow at serious volume, and for a mid sized facility owner they are the default answer. They have already done the tedious and genuinely difficult work of parsing dozens of one call centre formats, which is not something you should casually assume you will rebuild in a sprint. PelicanCorp covers similar ground with a strong international footprint. ProStar comes at it from precision capture and mapping of buried assets, which is a different and complementary angle rather than a competitor.
If you take a few thousand tickets a year in one state with one facility type, buy. The per ticket economics favour the product heavily at that scale, the one call integrations are already built, and you should not be writing software for this. Buy also if your facility geometry is not in usable condition, because no screening logic survives bad data and your correct first project is remediation of the mapping, not an application.
Where they stop: screening against facility records you know are wrong
Every dig ticket has to be answered, but most do not need a locator, because the excavation polygon simply misses everything you own. Automating that decision is the highest return feature in the whole domain, and it is the workflow packaged products model badly.
The reason is not the intersection arithmetic, which is straightforward. It is confidence. Your facility records have known accuracy problems in specific places, usually older plant and anything acquired. A ticket over a corridor mapped from paper in the 1960s deserves a wide buffer. A ticket over plant installed last year with survey grade capture deserves a tight one. Products give you a configurable global buffer, which is a blunt instrument compared with per area and per asset class confidence rules, and only you know which areas are which.
That distinction has a sharp edge. The day you auto clear a ticket and something gets hit, the log of that decision is the entire conversation, and it needs to show the geometry used, the buffer rule that fired and the version of the facility layer at that moment rather than what your mapping looks like today.
The second gap is the field record. A photograph on its own proves almost nothing. A defensible record is structured: device captured position at the moment of capture, the facility types marked and the colour used for each under the uniform colour code, meaning red for electric, yellow for gas, orange for communications and blue for potable water, the extent marked, whether the excavator had white lined the site, and offset measurements from something still present in six months, a pole, a curb line, a building corner. Two details decide claims and both are boring: those offsets, and the negative finding, meaning documenting that you marked and found no facilities in part of the dig area.
The arithmetic: cost per ticket against the cost to build
Do it with your own invoice. Ticket management here is priced per ticket received, sometimes banded, sometimes with separate charges for the field application and for each one call centre feed. Take your annual figure, divide by tickets received, and you have cost per ticket. Then divide by named users, which for a facility owner is a small damage prevention team plus locators, and you have cost per seat. The per ticket number is the one that matters, because it scales with construction activity you do not control.
Then price the other side properly. Multiply your unnecessary field visits, meaning tickets where a locator drove out and found nothing you own, by your fully loaded cost per visit. Add the staff weeks spent assembling defence files after damages. Those two lines are what a build competes against.
The crossover is a ticket count. Below about 20,000 tickets a year, buy without hesitating. Between 20,000 and 100,000 it turns on how many states and one call centres you receive from, since each is a separate rule set and a separate feed that a product covers partially. Above roughly 100,000 tickets a year the per ticket fee alone typically exceeds a build amortised over five years, and that is before you count the visits better screening removes. One further trigger overrides volume entirely: a single strike you could not defend, where the legal exposure became a board level number.
What a custom build actually costs, plus migration and year two
In Digital Heroes delivery experience, a first release covering ticket ingest from your one call centres, automated screening against facility geometry, deadline aware locator assignment and an offline field application producing structured proof of locate runs $60,000 to $140,000 over 12 to 16 weeks. A full damage prevention platform adding positive response automation, an excavator portal, damage investigation case files with claims packaging, contractor and locator scorecards and integration to your geographic and work management systems runs $150,000 to $400,000 across 6 to 12 months.
Data migration runs 10 to 25 percent of build cost, and in this category it is dominated by facility geometry rather than by tickets. Closed tickets bulk load for retention. What costs money is getting your mapping into a form the screening engine can trust, including the confidence classification by area, which is a judgement exercise with your own asset engineers rather than a transfer.
Year two and after runs 15 to 20 percent of build cost annually. Here that pays for one call centre format changes, which happen without asking your permission, state rule revisions, and mapping refreshes. A screening engine running against last year's facility layer is worse than no screening engine, because it is trusted.
What pushes cost up: the number of one call centres, since each has its own ticket format and its own positive response mechanism and some still use file drops rather than an interface; the number of states, because each is a rule set; the quality and accessibility of your facility geometry; and whether you must write back into an existing work management system rather than standing alone.
The four situations where building wins
Regulatory fit. Excavation notice law is set state by state: the notice period, how working days are counted, what a holiday does to the clock, what an emergency ticket means, how long marks stay valid, and what a remark request does. If you operate gas facilities, the written damage prevention programme required under 49 CFR 192.614 is an auditable document, and your software either evidences it or your binder does.
Scale economics. Past 100,000 tickets a year, per ticket pricing scales with excavation activity in your territory, which rises with every housing development and every fibre build. You pay more in the years you can least afford the distraction.
A workflow that is your advantage. Screening confidence by area. It is the one thing nobody can sell you because it encodes where your own records are weak, and it is where both your locator cost and your strike exposure actually sit.
Integration sprawl across three or more systems. Count them: each one call centre feed, the geographic system of record, the work management system, the field application, your claims and legal case files, and the reporting you submit into the Common Ground Alliance damage reporting programme. Once one ticket crosses three, somebody is retyping, and that somebody is the person your defence file depends on.
How to decide in a week: pull one damage claim
Take one real damage from the last two years, preferably one that went badly, and put the whole file on a table. The ticket as received, the screening decision, the assignment record, the locator's notes, every photograph, the positive response you posted and the correspondence that followed.
Then ask three questions in front of your damage prevention lead. Can you show what your facility mapping looked like on the day the ticket was screened, or only what it looks like now. Does any photograph carry an offset measurement to something still standing today. And is there a record showing where the locator found nothing rather than only where marks were placed.
Three noes means your exposure is evidential rather than operational, and no amount of routing optimisation addresses it. Then run the cheap half of the test: sample 200 tickets from last month and count how many produced a field visit that found nothing you own. That percentage, multiplied by your cost per visit, is the annual return on screening, and it usually settles the arithmetic on its own.
Then pay for a discovery phase rather than accepting a free proposal. At Digital Heroes that produces a signed product requirements document before any code exists: the screening rule model with confidence by area, the state clock definitions, the field record schema, the positive response mechanism per centre, acceptance criteria and a fixed price. You keep it whichever firm builds.
Who we are wrong for: single state operators under 20,000 tickets, and anyone whose mapping needs remediation first. 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.
- IBM frames first-time fix rate as a core field service KPI, noting the industry average sits around 80% (roughly one in five jobs needs a return visit). Correction: IBM cites best-in-class providers at 89-98%, not '85%+'. Source: IBM (2024) →
- Comparesoft reports the field-service industry-average first-time fix rate is about 80%, best-in-class providers reach roughly 90%, scores below 70% put the business at risk, and providers exceeding 70% FTFR saw customer retention around 86%. Source: Comparesoft (2024) →
- OECD research finds that digitalisation offers SMEs opportunities to improve performance, spur innovation, enhance productivity and compete more evenly with larger firms; it reports that increased use of online platforms produced significant multi-factor productivity gains in SME-heavy sectors such as hospitality and retail, while smaller firms lag in adoption due to skills, resource and financing gaps. Source: OECD (2021) →
- Workers can expect 39% of their existing skill sets to be transformed or become outdated over 2025-2030; 77% of employers plan to upskill their workforce, and 63% identify skill gaps as the biggest barrier to business transformation. Source: World Economic Forum (2025) →
Frequently asked questions
How long does a custom locate ticket system take to build?
Twelve to sixteen weeks for a first release with ticket ingest, automated screening against facility geometry, deadline aware assignment and an offline field application capturing structured proof of locate. Positive response automation, an excavator portal, damage case files and scorecards add six to twelve months. The schedule risk is usually the facility data, not the code, because screening cannot be tested against mapping nobody trusts.
Who owns the locate records and the code if we change firms?
You should own the repository, the cloud accounts and the data in writing before kickoff. Proof of locate records are litigation evidence with a useful life measured in years, so they cannot sit in a vendor account you cannot reach during a claim. At Digital Heroes the client owns everything from the first commit and can hire another firm to continue the work.
What happens if we auto clear a ticket and a facility is struck?
This is the exposure to design around before writing a line of code. Every automatic clearance must log the dig polygon, the facility layer version, the buffer rule that fired and the confidence classification for that area at that moment. With that record the conversation is about a documented decision made on the best available data. Without it, the conversation is about negligence.
Can we improve screening without replacing our ticket system?
Sometimes, and it is worth asking your incumbent first. If the product exposes an interface for ticket data and accepts a screening outcome back, a thin screening service using your own geometry and confidence rules can sit alongside it. If it does not, you are choosing between the product's global buffer and a build. Test the interface during evaluation rather than assuming it exists.
Should a small facility owner build a damage prevention system?
No. A few thousand tickets a year in one state with one facility type is squarely product territory, and a build would cost more than the problem. Spend instead on mapping accuracy, because every option you have later, product or custom, gets better as your facility geometry improves. That is the one investment that is never wasted whichever way the decision eventually goes.
What is the difference between locate ticket software and a work management system?
Ticket software receives 811 notices, screens them against your facilities, assigns them under a statutory clock, captures field evidence and posts positive response back to the one call centre. A work management system schedules and costs planned utility work against assets and crews. The clock, the screening and the evidentiary record are the parts a work management system has no concept of.
How much of the build cost goes on facility data preparation?
Budget it inside the 10 to 25 percent migration band and expect the upper end if your mapping has not been assessed recently. The work is not conversion. It is classifying areas by how much you trust the geometry, usually with your own asset engineers, so screening can be conservative where records are weak and tight where they are good. That classification is the asset the build produces.
Can an excavator portal actually reduce damages?
It can, because most excavator behaviour that leads to damage comes from uncertainty rather than indifference. Showing mark status, the marked area and a direct route to request a remark converts an adversarial relationship into a working one. It also has a second benefit that appears later: excavators who use the portal leave their own record, which is very useful the day a claim is filed.
What happens to the field application when there is no signal?
It must keep working, and the answer should be volunteered before you ask. Locators work in trenches, rural corridors and urban canyons where signal drops, so the application queues everything locally, preserves the original capture time rather than the upload time, and syncs when it can. A field tool requiring connectivity is abandoned within a month and replaced by the phone camera you were trying to retire.
Should we build routing optimisation or evidence capture first?
Evidence capture, almost always. Routing saves drive time, which is real money, but a weak field record is what turns one bad afternoon into a claim you cannot defend. Build screening and structured proof of locate first, run them for a quarter, then add deadline aware routing once you know your true clearance rate. Optimising dispatch before screening works simply moves the wrong visits faster.
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.
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 we start with an MVP or build the full field service platform in one go?
Start with an MVP that can run one real crew for one real week: scheduling, dispatch, job completion with photos and signatures, and invoicing. That slice typically costs $40,000 to $70,000 and ships in about 12 weeks, and technician feedback then decides phase two. Teams that built the full platform up front reworked 30 to 40 percent of it after field use in Digital Heroes experience, which is the most expensive way to discover what dispatchers actually need.
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.
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.
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 an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
Should I hire a freelancer or an agency for my software project?
A skilled freelancer is the right call for a single-discipline scope under roughly $15,000, like a website, a plugin, or one integration. Above that, projects need design, backend, testing, and project management at once, and a solo builder becomes the single point of failure: if they get sick or take a bigger client, your project simply stops. Agencies bill 20-40% more per hour but carry continuity, code review, and someone to escalate to, which is what you are actually buying.
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.
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 .
