Utility Network GIS Software: Custom Build vs Esri, Smallworld and Bentley
Buy the platform and never build a geographic system. Esri ArcGIS Utility Network, GE Vernova Smallworld and Bentley OpenUtilities are serious products and rebuilding any of them would be a decade of wasted money.
On this page
Buy the platform and never build a geographic system. Esri ArcGIS Utility Network, GE Vernova Smallworld and Bentley OpenUtilities are serious products and rebuilding any of them would be a decade of wasted money. Build only the editing and handoff layer around it, and only once your as-built lag is over 60 days and staffing has failed to move it.
What Esri, Smallworld and Bentley genuinely do well
Walk into a service centre at a mid sized electric utility and look for the rack of job folders. Each folder is a finished construction job with a marked up print, red pen over a plot that was already out of date when it printed. On a normal week that rack is three to four months deep. No software vendor caused that, and this is a category where the honest advice is unusually simple.
Esri has moved the platform to the ArcGIS Utility Network, and it is a genuinely better data model: services based editing, branch versioning, network rules, terminals, containment and structural attachment associations, subnetworks with controllers and tiers. It represents how a distribution system actually behaves rather than how it draws. GE Vernova Smallworld carries decades of utility modelling depth and remains the right platform for many operators. Bentley OpenUtilities sits comfortably where engineering and asset design matter most.
All three are serious platforms and none should be rebuilt. If you are a co-op under roughly 40,000 meters with a stable system and one geographic technician, buy the platform, buy a configured vertical solution on top of it, and spend the remaining money on field verification. We will say that plainly even though it means less work for us, and it is the right answer more often than any other on this page.
Where they stop: fifteen years of your own editing tools
Here is the workflow that decides this, and it is not mapping. It is posting a construction job.
Your editors do not use raw geographic software. They use the layer your utility built on top of it. On ArcFM Solution that means Auto Updaters firing on create and update, Favorites that place a whole assembly with one click, session and design based editing, and a pile of ArcObjects code somebody wrote in 2011 who no longer works here. In a Smallworld shop it means Magik customisations encoding the same construction standards. That layer is not decoration. It is why a new editor can place a padmount transformer correctly on their second day.
None of it survives the migration. ArcObjects is gone, replaced by the ArcGIS Pro software development kit in .NET. Auto Updaters have no direct equivalent, and the honest replacement is attribute rules written in Arcade plus server side logic, which is a different execution model with different failure behaviour. Custom traces built on the geometric network get rewritten against utility network trace configurations and subnetwork definitions. Most utilities discover they hold between 60 and 300 individual customisations, roughly half of which nobody uses and nobody dares delete.
The second thing the platform does not give you is your own workflow around branch versioning. Which jobs need engineering review before post. What happens to a version left open for eight months. How a phase correction reaches the outage system the same day rather than the same quarter. Esri gives you versions, validate topology, dirty areas and an error inspector. It does not give you a job queue with states, assignment, ageing and a validation gate that refuses to post with unresolved errors on the affected feeder.
The arithmetic: cost per editing seat against the cost to build
Do it with your own renewal. Platform cost here is named user licensing, meaning desktop editing seats plus server licensing plus any configured vertical solution, and it scales with people rather than with meters. Take your annual platform and vertical cost, divide by editing seats, and you have cost per editor. Then divide your total by the number of construction jobs posted last year, and you have cost per job, which is the number that actually matters.
Now measure the thing nobody measures. As-built lag is the number of days between a crew energising something and the model knowing about it. At most utilities we have worked with it sits between 45 and 120 days, and nobody tracks it deliberately. Multiply your lag by what it costs downstream: outage prediction calling the wrong customers, switching orders referencing a device that moved, load flow run on last winter's connectivity, joint use billing an attacher for a pole that was replaced.
The crossover is an editor count crossed with a customisation count. Under about 10 editing seats and 25 surviving customisations, configure the vertical solution and accept its workflow. Between 10 and 25 seats it depends on your lag: under 60 days, leave it alone. Above roughly 25 editing seats, or more than 50 customisations your editors genuinely use daily, the workflow layer returns more than it costs, because every one of those customisations is otherwise a conversation and a workaround repeated by each editor every week.
What a custom build actually costs, plus conversion and year two
Across the projects Digital Heroes has delivered, this category has a consistent shape. The workflow layer alone, meaning job and version management, as-built posting with validation gates, redline intake and the first two downstream exports, runs $90,000 to $200,000 and ships in 14 to 20 weeks. A full programme adding conversion tooling with repeatable error reporting, offline field capture, subnetwork exports for the outage and distribution management systems, and integration with your work management system runs $250,000 to $700,000 phased over 9 to 18 months.
Conversion runs 10 to 25 percent of build cost and in this category it reliably lands at the top. Getting from a geometric network with twenty years of accumulated compromise into a utility network that passes validate topology means resolving things the old model tolerated: devices sitting a foot off the conductor, transformers with no bank association, secondary that was never digitised, structures carrying no attachment associations, and phase attributes populated three different ways because three vendors ran three conversion projects. Run it iteratively. Load, validate, produce an error report by feeder, fix at source, reload, weekly for months, with a named person accountable for the error count falling.
Year two and after runs 15 to 20 percent of build cost annually. Here that pays for platform version upgrades, which move attribute rule behaviour, and for each new downstream consumer of the model.
What pushes cost up: the count of surviving customisations; gas alongside electric, because the pressure system and the pipeline data model are a second domain rather than a second layer; multiple operating companies with different construction standards; and the honest one, how much of your model was never verified against the field. If a third of your secondary is guessed, you are buying a field verification programme, not software.
The four situations where building wins
Regulatory fit. Your construction standards are the rules, and for gas operators the pipeline data model plus your integrity management records make the model an auditable artefact rather than a drawing. Validation that refuses to post a version with topology errors on a live feeder is the software expression of that obligation.
Scale economics. Past 25 editing seats, the cost of every editor working around a missing behaviour compounds weekly, and named user licensing does nothing to address it because the gap is workflow rather than capability.
A workflow that is your advantage. Posting speed. The measurable target is how long a technician takes to post one distribution job. If that number does not improve on the new platform, the migration was a schema exercise and your backlog will be exactly as deep in December as it was in June.
Integration sprawl across three or more systems. Count the consumers of your model: the outage system wants connectivity and customer to transformer relationships with device normal states, the distribution management system wants an unbalanced electrical model that will converge, planning wants a feeder export that CYME or Synergi Electric can read, engineering wants a common information model extract, and work management wants an asset register keyed on your equipment numbers. Each usually gets its own nightly extract, each silently drifts, and when the numbers disagree three departments defend their own copy.
How to decide in a week: measure your as-built lag
Pick fifty construction jobs completed in the last six months, chosen at random rather than by the technician who posts them. For each one, record two dates: when the crew energised it, and when the edit posted to the production model. Ninety minutes of clerical work gives you a distribution rather than an anecdote.
Then take the median. Under 30 days and your process works, so buy the platform, configure the vertical, and stop reading. Between 30 and 60 days, look at where the time sits, because if it is mostly waiting for engineering review you have a policy problem rather than a software one. Over 60 days, and especially if adding technicians has not moved it, the handoff is broken and the workflow layer is what fixes it.
Run a second count alongside it. Ask your two most experienced editors to list the customisations they use every day, independently, without conferring. Compare the lists. The overlap is your real inventory, and it is usually a third of what the full audit produces, which is the number that should be reimplemented rather than ported.
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 customisation triage with each behaviour classified, the job workflow states, the validation gates, the downstream export contracts, acceptance criteria and a fixed price. You keep that document whichever firm builds it, and it is the artefact that makes competing migration quotes comparable.
Who we are wrong for: anyone wanting a geographic platform built from scratch, and small co-ops whose real need is field verification. 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.
- The federal government spends about 80% of its IT budget on operations and maintenance of existing systems rather than on development or modernization, with many critical systems being decades old. Source: U.S. Government Accountability Office (GAO) (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) →
- Grand View Research valued the global field service management market at USD 4.43 billion in 2022 and projects it to reach USD 11.78 billion by 2030, a 13.3% CAGR, driven by growing field operations in telecom, utilities, construction and energy. Source: Grand View Research (2023) →
- Digital Champions expect to achieve about 16% in cost savings and around 15% in revenue gains from digital operations over five years; the study surveyed 1,155 manufacturing executives across 26 countries. Source: PwC / Strategy& (2018) →
Frequently asked questions
How long does a utility network workflow layer take to build?
Fourteen to twenty weeks for job and version management, as-built posting with validation gates, redline intake and the first two downstream exports. A full programme with conversion tooling, offline field capture and work management integration runs nine to eighteen months. The pilot approach matters more than the schedule: two feeders and one district through the whole loop, including a real post and a real outage system handoff.
Who owns the code and the platform configuration afterwards?
You should own the repository, the enterprise configuration and the right to hire anyone else, written down before kickoff. This includes attribute rules, trace configurations and export definitions, because those encode your construction standards rather than a vendor's product. At Digital Heroes the client owns the code from the first commit, and any firm hesitating on that point is selling a dependency rather than a system.
What happens to our ArcFM Auto Updaters during migration?
They do not come across. ArcObjects is gone and Auto Updaters have no direct equivalent, so the replacement is attribute rules in Arcade plus server side logic, which behaves differently on failure. The right response is triage rather than a port. Inventory every customisation, keep the twenty or thirty behaviours editors depend on daily, and let the rest go. Anyone promising a full port has not counted them.
Can we improve as-built posting without migrating platforms?
Sometimes, and it is worth testing before committing to a programme. If your backlog is caused by redline reconstruction and unclear review policy rather than by the data model, a job queue with states, assignment and ageing can be built against your existing environment. Measure the lag first. If the median is under 60 days, spend the money on field verification instead.
Should a small cooperative build anything around its geographic system?
Usually not. Under about 40,000 meters with a stable system and one technician, buy the platform, buy a configured vertical solution, and put the remaining budget into verifying what is actually in the field. Every option you have later gets cheaper as model accuracy improves, and no workflow layer compensates for secondary conductor that was guessed rather than surveyed.
What is the difference between the geometric network and the utility network?
The geometric network modelled connectivity as points and lines with tolerances your editors learned to work around. The utility network adds terminals, network rules, containment and structural attachment associations, and subnetworks with controllers and tiers, so the model expresses how the system is actually built and operated. It is not a schema upgrade. Tools written against the old model stop working on cutover day.
How much does conversion cost, and why is it the biggest line?
Budget 10 to 25 percent of build cost and expect the upper end. Conversion is expensive because the utility network refuses to accept compromises the old model tolerated, so every disconnected device, missing bank association and inconsistently populated phase attribute has to be resolved at source. Utilities that treat it as one cutover event fail. Utilities that run it weekly for months, with error counts falling, succeed.
Can one export service feed the outage and planning systems together?
It can, and it is usually the fix for departments disagreeing about the model. One service produces per consumer projections from the same validated topology, with a run log recording which model version produced each extract and a difference report so each team sees what changed overnight. Phase and normal state should be audited attributes, because those two fields cause more downstream arguments than everything else combined.
What happens if a technician posts a version with topology errors?
Ask every developer this question and listen carefully. The acceptable answer is that the post is blocked on the affected feeder and the downstream export does not run with an invalid model. If the answer is that the export simply runs, they have not worked with an operations group that gets paged at 2am, and your dispatchers will quietly learn to distrust the prediction again.
Should we build offline field capture before or after the posting workflow?
After. Field capture is popular and visible, but it feeds the posting workflow, and building it first means collecting redlines faster into the same backlog. Fix the handoff and the validation gates, prove the lag has moved on a pilot district, then push capture into the field. Done in that order, field capture removes reconstruction time. Done first, it simply arrives sooner at a queue.
What is the biggest mistake first-time software buyers make?
Choosing the lowest quote without asking why it is the lowest. A bid 40% under the field usually gets there by skipping tests, documentation, and code review, which are invisible in a demo and brutal to pay for later; every stalled project Digital Heroes has been asked to rescue tells some version of that story. The second mistake is signing without a written scope, which reliably turns the winning cheap quote into 1.5x to 2x the price by launch.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
If an agency builds my software, who actually owns the code?
You should own everything, assigned in writing: the contract transfers full IP to you on final payment, the code lives in your GitHub organization, and hosting runs in cloud accounts you control. The red flag is a proposal that mentions the agency's proprietary platform or framework, which usually means you are renting, not buying. Digital Heroes structures every build this way precisely so a client can fire us and lose nothing but the relationship.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
Our developer disappeared mid-project. Can another team pick up the code?
Yes, this is a routine engagement, provided the code exists somewhere you can access, so your first move is securing the repository, hosting, and domain credentials today. A takeover starts with a one to two week paid code audit that ends in one of three verdicts: continue the build, keep the design but rebuild the weak parts, or start over. Digital Heroes has inherited enough projects to say plainly that sometimes the rebuild is cheaper than the rescue, and an honest agency will tell you which one you have before taking your money.
How do I make sure custom software is secure and compliant with rules like HIPAA?
Start with the baseline every business system should have: encryption in transit and at rest, role-based access control, and audit logs. If HIPAA applies, the hosting provider must sign a Business Associate Agreement, which AWS, Azure, and Google Cloud all offer, and access controls have to be designed in from day one, not bolted on. SOC 2 certifies a company's operating practices, not a codebase, so ask vendors what they have shipped in your regulated domain rather than which logos are on their website.
Who can build a custom software system?
Digital Heroes builds custom 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 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 .
