How Much Does Public Works Software Cost in 2026?
A custom public works work order and asset platform runs $60,000 to $400,000, and the single decision that moves the number most is whether the field application has to work offline. A connected-only mobile app is a few weeks of work.
On this page
A custom public works work order and asset platform runs $60,000 to $400,000, and the single decision that moves the number most is whether the field application has to work offline. A connected-only mobile app is a few weeks of work. An offline-first app where two crews edit the same asset in a river valley for six hours and both sync at 4pm needs a real conflict resolution design, and that requirement alone typically adds a quarter to the first release. Departments that can genuinely rely on cellular coverage should say so early, because it is the cheapest scope reduction available to them.
The bands a public works build falls into
A focused first release runs $60,000 to $130,000 and ships in 12 to 16 weeks. That covers unified intake across every channel with classification and deduplication, the asset register with two-way Esri sync, offline-capable mobile work orders, and a dispatch board that stamps ward, basin and snow route automatically at creation.
A full platform runs $150,000 to $400,000 phased over 6 to 12 months, adding fleet and equipment, inventory and parts, the citizen portal with status tracking, preventive maintenance scheduling against real crew capacity, an event mode for declared disasters, and finance integration.
Below roughly $50,000 you are buying a form and a list. The tell is whether the proposal treats geography as data on the record or as a map layer on a screen. If ward, council district, pavement section, sewer basin and snow route are not stamped on every work order by spatial join at creation, the council question about response times in Ward 3 will still take a week to answer, which is the reason most departments start this project in the first place.
What drives a public works build up
Four things dominate.
- Offline-first mobile. The single biggest multiplier. A sync engine that survives two crews editing the same asset offline, with an explicit conflict resolution rule rather than last write wins, is genuine engineering. If a developer answers that question with last write wins, the estimate is wrong as well as the design.
- The state of your geodatabase. Esri integration cost scales with how clean your layers are. If assets lack stable identifiers or carry duplicates, budget a reconciliation phase before anyone writes application code. Doing it afterwards costs more and produces a system your crews stop trusting.
- Finance integration. Connecting to Tyler Munis, Springbrook or Workday is a knowable cost, but only after your finance team commits to a chart of accounts and activity code mapping in writing. That conversation reliably takes longer than the code.
- Utility scope. If you are a combined utility and want alarm-to-work-order from a supervisory control system, that is a separate project rather than a feature.
What keeps the number down
Fix asset identifiers before kickoff, not during. A reconciliation pass with your geographic information systems analyst is unglamorous and it moves the whole project down a band, because every integration downstream depends on a stable identifier existing.
Decide honestly whether you need full offline or degraded offline. Many departments need work orders and close-out forms to queue when signal drops, not full editing of the asset register in the field. That narrower requirement is materially cheaper and covers the real case.
Keep close-out short. Three fields and a photo gets filled in at hour fourteen of a main break. Eleven fields does not, and the data you never collect is the reason the geodatabase drifts.
Phase the citizen portal. Accessibility conformance is a requirement rather than an option, which makes the portal a real piece of work, and it delivers nothing until intake and dispatch are already reliable.
A worked example that adds up
A 60 staff department across four divisions, roughly 8,000 work orders a year, assets in an Esri geodatabase, finance on Tyler Munis. Here is release one, line by line.
- Discovery plus asset identifier reconciliation with the geographic information systems analyst: $15,000
- Unified intake queue: phone, email, portal, text and council forwards normalised, with extraction of category and location, geocoding against your own street centerline file, and deduplication within a distance and time window: $22,000
- Asset register with two-way feature service sync and a review queue for field discoveries: $24,000
- Offline-first mobile work orders with explicit conflict resolution and short close-out forms: $30,000
- Dispatch board with automatic spatial stamping of ward, council district, basin and snow route, plus distinct reported, entered, assigned, on site and closed timestamps: $16,000
That totals $107,000 and ships in about 15 weeks. Phase two adds fleet and equipment at $28,000, inventory and parts at $20,000, the accessible citizen portal with status tracking at $26,000, preventive maintenance scheduling with routing against trailing actual crew hours at $32,000, event mode with the fields a federal reimbursement claim requires at $18,000, and Tyler Munis integration at $30,000. Phase two is $154,000, taking the platform to $261,000 over roughly ten months.
Note that offline mobile is the largest line in release one at $30,000. That is not padding, it is the item that decides whether crews use the system at all. A department that can genuinely rely on coverage everywhere would spend around $14,000 there, taking release one to roughly $91,000. Answer that question honestly before you scope, because a connected-only application in a service area with dead ground produces paper work orders again within a month.
How the spend phases
Discovery and data reconciliation come first and are around 14 percent of release one. Two decisions have to close before build starts: a stable asset identifier scheme agreed with your analyst, and the chart of accounts and activity code mapping agreed in writing with finance. In our delivery experience the timeline risk in public works is almost never code, it is waiting on those two conversations.
Release one bills across 12 to 16 weeks. Go live one division at a time rather than department wide. Streets first is usually right, because the volume is highest and the failure modes surface fastest. Run the old intake path in parallel for a month so nothing arrives only in a channel nobody is watching.
Phase two should track budget cycles rather than a continuous run. Event mode is worth pulling forward if your season is approaching, because the fields a reimbursement claim needs have to be captured during the event and cannot be reconstructed afterwards from photographs and memory.
The ongoing costs nobody quotes
Plan 15 to 20 percent of build cost per year, roughly $39,000 to $52,000 on a $261,000 platform. Esri schema changes, mobile operating system updates and finance system upgrades account for most of it.
Hosting is modest for a department of this size, typically low hundreds of dollars a month, but add device costs if crews need rugged tablets and add the cellular plans for them. Those are capital and operating lines your finance director will ask about and they are not in the software quote.
Records retention is the cost that surprises people. Work orders are public records, a records request will land, and storage plus the retrieval workflow are real. Build the retention rules in rather than discovering them the first time a request arrives.
Then the internal owner. Somebody has to approve the field discovery queue into the geodatabase and maintain the classification list. That is part of the analyst's role, perhaps two days a month, and where it goes unassigned the discovery queue fills up and the loop you paid to close reopens.
Comparing a build against your current renewal
Do the arithmetic before the next renewal. Take the annual licence, add the consultant you retain to maintain configurations, add the fully loaded cost of the foreman rekeying paper work orders every morning, and add any reimbursement you have written off because the documentation could not be produced. Compare against $261,000 plus roughly $45,000 a year.
Then test the incumbent on ground you can verify. Ask whether the integration will write field discoveries back to your geodatabase or only read from it. Ask what happens to a work order edited offline by two crews. Ask for a full export of work orders, assets and attachments in a form another system could load, and what it costs. Ask how many custom fields and reports you are currently maintaining, because that count is a direct measure of how far the product sits from your operation.
The decisive signal is simpler than any of that. If you are paying for a tool and still running the real operation on a whiteboard or in Excel, the tool never fit, and another configuration cycle will not change it.
When buying beats building
If you are a department under about 25 staff with a single division, do not build. Cityworks or Cartegraph will serve you properly, and $107,000 spent on crew time and equipment returns more. The same applies if your county or state has standardised on one of them and getting an exception means two years of procurement and information technology negotiation you will lose.
Do not build if your asset data is genuinely bad. Custom software will not clean it. It will render bad data faster and more expensively. Fix the data, then revisit the question in a year.
Do not build if the real problem is that nobody uses the system you already have. A new system resets the adoption clock rather than solving it, and the second failure is harder to fund than the first.
Build when your operation is structurally unusual: a combined utility, a shared services agreement with neighbouring townships, a snow operation that is 40 percent of your winter, or an internal fleet shop that bills other departments. Off-the-shelf tools are built for the median department, and every year you spend configuring around that gap is a year you pay for software to make the job harder.
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. Nothing about that commits you to the build.
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) →
- Large companies globally have captured, on average, only 31% of the expected revenue lift and 25% of the expected cost savings from their digital and AI transformations - a significant gap between expected and realized value. Source: McKinsey & Company (2023) →
- Bersin by Deloitte research found organizations that use HR technology and employee-centric design to build a flexible, empowering workplace are more than 5 times more effective at improving employee engagement and retention than their peers, and 2.5 times more likely to reach 'high-impact' status by leveraging HR for digital transformation. Source: Bersin by Deloitte (2017) →
Frequently asked questions
What does custom public works software cost in total?
A focused first release covering unified intake with deduplication, the asset register with two-way Esri sync, offline mobile work orders and dispatch runs $60,000 to $130,000 and ships in 12 to 16 weeks in Digital Heroes delivery experience. A full platform adding fleet, inventory, a citizen portal, preventive maintenance scheduling, event mode and finance integration runs $150,000 to $400,000 over 6 to 12 months.
For a 60 staff department handling 8,000 work orders a year, a realistic all-in figure is around $261,000 across ten months.
What is the annual running cost?
Budget 15 to 20 percent of build cost per year, roughly $39,000 to $52,000 on a $261,000 platform, covering Esri schema changes, mobile operating system updates and finance system upgrades.
Add lines your software quote will not include: rugged tablets and their cellular plans, storage and retrieval for public records retention, and about two days a month of your analyst's time approving field discoveries into the geodatabase.
How long does it take to build?
Twelve to 16 weeks for a first release, then phased work over 6 to 12 months. The timeline risk is rarely engineering. It is waiting on a stable asset identifier scheme from your geographic information systems analyst and a chart of accounts mapping from finance, both of which should close before build starts.
Go live one division at a time, streets first, with the old intake path running in parallel for a month so nothing arrives only in a channel nobody is watching.
Is Cityworks or Cartegraph cheaper than building?
Yes, and for a department under about 25 staff with one division they are the right answer. Both are capable products with real Esri integration.
Test them on verifiable ground before renewing: whether the integration writes field discoveries back to your geodatabase or only reads from it, what happens when two crews edit the same asset offline, what a full export of work orders, assets and attachments costs, and how many custom fields and reports you currently maintain. That last count measures how far the product sits from your operation.
Why is offline mobile the most expensive part?
Because a sync engine that survives two crews editing the same asset offline for six hours and both syncing at 4pm requires an explicit conflict resolution design, not a setting. In our worked example it is $30,000 of a $107,000 first release.
If a developer answers the two-crews question with last write wins, both the design and the estimate are wrong. Many departments can narrow the requirement to queuing work orders and close-out forms rather than full field editing, which is materially cheaper and covers the real case.
Can we reduce cost by cleaning up our asset data first?
Yes, and it is the highest-return preparation available. Esri integration cost scales directly with whether assets carry stable, unique identifiers, and every downstream integration depends on that.
Run the reconciliation pass with your analyst before kickoff. Doing it during the build costs more and produces a system crews stop trusting. If your data is genuinely bad, fix it and revisit the build question in a year, because custom software will render bad data faster rather than repair it.
What does event mode cost and is it worth it?
Around $18,000 in the worked example. It changes intake, dispatch layout and close-out requirements for the duration of a declared event, groups requests by geographic cluster, and silently carries the fields a federal reimbursement claim needs: equipment code, operator, equipment and labour hours, location and disposal site.
It is worth pulling forward if your season is approaching, because those fields have to be captured during the event. Departments that reconstruct several hundred storm events afterwards from photographs routinely lose reimbursable cost they genuinely incurred.
Will it integrate with ArcGIS and Tyler Munis, and what does that add?
Both are standard. Esri integration runs through the feature service interface and should be two-way so field discoveries flow back rather than only reading down. Tyler Munis is around $30,000 in the worked example.
The Munis figure holds only if finance commits to a chart of accounts and activity code mapping in writing first. That conversation reliably takes longer than the code, so start it before you sign anything.
Do we own the code if a city hires a developer?
Only if the contract says so explicitly, with a repository handover clause and named transfer conditions. Many agencies sign language that quietly leaves the vendor holding the code, which means changing vendors requires rebuilding. At Digital Heroes the client owns the code from the first commit.
Have your city attorney confirm the assignment clause and the handover mechanism before signing rather than at go-live, and make sure the cloud accounts are in the city's name.
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.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
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.
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.
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 many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
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 Ben.
Senior SEO Strategist · New-york · 5 posts on the site
Published · Last updated .
