Bridge Inspection Management Software: Build or Buy?
The threshold is roughly 300 structures, and below it the answer is almost always buy or stay put.
On this page
The threshold is roughly 300 structures, and below it the answer is almost always buy or stay put. A county with 40 bridges inspected under a state contract where the state carries the national inventory submittal should build nothing at all: ask for your inspection data back annually in a usable format and keep a good spreadsheet. Above 300 structures the decision turns less on count than on contractor mix, because three consultant firms filing reports as PDFs in three house styles is what turns re keying into a standing annual cost and quietly injects rating inconsistency into your dataset. At that point a first release runs $70,000 to $150,000 over 12 to 18 weeks, and most agencies should stop there for a full inspection cycle before going further.
When is off the shelf genuinely the right call here?
If the state performs and submits your inspections, buy nothing. Small counties in that position have no compliance exposure to instrument and no data to manage. Request your inspection records back each year in a usable format, keep a spreadsheet of structures and due dates, and preserve the option to build later. That request costs nothing and is the single most useful thing a small owner can do.
If you already run AASHTOWare Bridge Management successfully and your staff know it, keep it. It is genuinely comprehensive on the management side: element data, deterioration modelling, benefit cost analysis and programme optimisation. Agencies whose programme fits its model and who have people fluent in it are better served improving around it than replacing it. Replacement only becomes a serious conversation when the configuration effort to make it match your programme keeps exceeding the value it returns.
If your problem is inspection collection and report production rather than programme management, Bentley InspectTech is the product built for that and it is why so many consultant inspection teams run it. Buy it if what you need is a better report out of a better form.
Esri Field Maps and Survey123 deserve an honest note rather than a recommendation. Agencies reach for them because the geospatial side is excellent and the licence is often already paid for. What you get is forms and points. There is no structure domain model, no element quantity logic across condition states, no interval rules and no submittal validation, so the improvised version works for a season and then becomes a data problem. Use it to map assets, not to manage a compliance programme.
When does a custom build actually pay off?
Build when the seams between products have become your compliance risk. That is the honest description of this market: a heavyweight management system, an inspection collection tool and a mapping platform, with most agencies running at least two plus spreadsheets to fill the gaps.
Specifically, build when two or more of these hold. You own several hundred structures or more. Multiple consultant firms submit to you in incompatible formats and a technician re keys condition ratings weeks later. Your interval determinations under the National Bridge Inspection Standards are not documented anywhere a reviewer could read them, so the due date on a structure is the output of a decision that lives in an engineer's memory. The annual submittal under the Specifications for the National Bridge Inventory is a manual reconciliation exercise. Or you cannot produce a condition trend per element to justify your capital programme to elected officials.
The figures, from Digital Heroes delivery experience. A first release covering the structure register, interval determination and scheduling with compliance alerts, an offline element level field application carrying your own element set, and consultant submission runs $70,000 to $150,000 over 12 to 18 weeks. A full structure management platform adding submittal generation with item level validation, load rating and posting records, scour evaluation history, deterioration trending on your own data and candidate project generation runs $200,000 to $450,000 phased over 9 to 15 months. Specialised inspection types, meaning underwater and non redundant steel tension member routines, add $40,000 to $120,000 and belong in a defined phase rather than assumed into scope.
How do they compare on the things that matter in this industry?
Your element set. This is the largest single swing factor and the thing products configure rather than solve. Every state extends the national element set to cover what it actually owns: specific joint types, coating systems, culvert configurations, historic truss details. Each added element is a form definition, condition state definitions, validation and a reporting treatment. Some agencies now carry more locally defined elements than standard ones, and the configuration ceiling is exactly where the fight happens.
Offline field capture. Inspectors work under bridges, in valleys and off a snooper truck with no signal. The application has to load the previous inspection so the inspector starts from last cycle's element quantities rather than a blank form, tie photos to specific elements and defects rather than a folder, and resolve a conflict when two people edited the same structure while offline. If it is slower than paper, inspectors keep using paper.
Quantity consistency across cycles. If inspector A records 1,200 square feet and inspector B records 1,150 two years later because they measured differently, your deterioration model reads that as improvement. Carrying quantities forward and requiring a reason for a change is a control, not a feature, and it decides whether network level trending is defensible.
Submittal as a data contract. Items changed in the move to the newer specifications, new items appeared, and some coded values no longer mean what they meant before. Validation before submission, plus a record of exactly what was submitted each cycle, puts you in a different position during a compliance review than regenerating the file and hoping.
Structure identity over time. A bridge gets widened, renumbered, transferred between owners and has its superstructure replaced. If the inspection is the primary record rather than the structure, you orphan history the first time an identifier changes, and you lose both the condition trend and the load rating chain.
What does total cost of ownership look like at your scale?
A worked example. A department of transportation district responsible for 640 structures including 190 culverts, an element set extending the national set by about 70 elements, three consultant firms performing roughly 40 percent of routine inspections, and records running back to the late 1970s.
First release: structure register $24,000, interval determination and scheduling with alerting by inspection type $22,000, element configuration mechanism plus loading the national set and 70 agency elements $34,000, offline field application with photo capture, sketching and defect notes $39,000, consultant submission portal with validation and acceptance workflow $26,000, migration of the current cycle plus reconciliation of renumbered structures $19,000. That is $164,000 over about seventeen weeks.
Phase two adds submittal generation with item level validation at $52,000, load rating and posting linkage at $29,000, scour evaluation history at $21,000, deterioration trending at $46,000 and candidate project generation with funding scenarios at $58,000, taking the programme to about $370,000 across fourteen months.
Running costs are where agencies get caught. Support and enhancement at 15 to 20 percent of build cost, so $56,000 to $74,000 a year on that programme. Media storage at $6,000 to $20,000 a year and rising, because element level inspection with photographic evidence generates a great deal of data every cycle and the retention obligation on a structure record is effectively permanent. Element and form updates at $8,000 to $25,000 per revision, because older data has to remain interpretable under the definitions in force when it was collected. Submittal format changes at $5,000 to $18,000 per event. And inspector training at $4,000 to $12,000 a season, which is the line that protects every deterioration curve you fit later.
What does the hybrid look like, and when is it the honest answer?
The hybrid here is well established and it is the right answer for a large share of agencies: keep AASHTOWare Bridge Management as the system of record and build only the offline field inspection application that feeds it. You get your own agency developed elements on the form, previous cycle quantities carried forward, photos tied to elements at capture time, and an application inspectors will actually use, without replacing a management platform your staff already know and without touching your submittal path.
That targeted build sits in the lower half of the first release band, typically $60,000 to $110,000 depending on element count, and it addresses the specific complaint most agencies voice about the incumbent. Ship it before an inspection season rather than during one. An inspector asked to learn a new field application in July under a bridge will not adopt it, and a failed field rollout costs a full year because the next honest opportunity is the next season.
The second hybrid worth considering is consultant submission alone. If your own crews are fine and the pain is three firms filing PDFs, build the submission portal with validation at their end and acceptance at yours, at roughly $26,000 to $40,000, and leave everything else where it is. The first firm onboarded takes longer than the other two combined, so budget calendar time even though the software cost is small.
The hybrid stops being honest when your interval logic, load rating chain and submittal reconciliation all live outside the incumbent anyway. At that point you are maintaining a management platform that manages very little, and the full build is the cheaper answer over five years.
Which should you choose, by operator size and stage?
Under 100 structures, inspected and submitted by the state. Build nothing. Request your data back annually in a usable format. Keep a spreadsheet with structures, inspection types and due dates.
100 to 300 structures, own crews, no consultant mix. Buy, or extend what you have. A build at this scale rarely repays itself. If the field form is the complaint, price the targeted field application before anything larger.
300 or more structures, or any count with two or more consultant firms. Build the inspection core at $70,000 to $150,000. Start with routine inspections on your own structures with your own staff, decide early whether culverts are in phase one because they often make up a third of the register, and add specialised inspection types in phase two.
Large district or statewide programme with a capital committee to answer to. Phase to the full platform at $200,000 to $450,000, but do not build deterioration modelling and programme prioritisation until two clean cycles of element data have been collected inside the system. A funding scenario is only as defensible as the condition history behind it.
Whichever route you take, own the repository, the database and the cloud accounts. Inspection records are permanent public safety records that can become discovery material after an incident, so they cannot sit inside a vendor controlled account.
When you are ready to turn this into a specification, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The average developer spends more than 17 hours a week dealing with maintenance issues such as debugging and refactoring, and about four of those hours on 'bad code' - waste that equates to nearly $85 billion annually worldwide in opportunity cost. Source: Stripe (2018) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- The EY survey of 508 payroll professionals at U.S. companies with 250-10,000 employees quantifies the direct and indirect cost of payroll inaccuracy, reinforcing the ROI case for payroll automation; the study is the original source of the frequently cited $291-per-error figure. Source: BusinessWire / EY (Ernst & Young) (2022) →
- Criteo's Global Commerce Review found retail apps convert at 18% versus 4% on mobile web (roughly 4.5x), and travel apps convert at 20% versus 6% on mobile web (about 3.3x). Source: Criteo (2017) →
Frequently asked questions
What does it cost to move off our current bridge inspection system?
The licence is rarely the obstacle. The cost is the inventory: decades of records coded under earlier element definitions, attached to structures that have since been renumbered, widened, replaced or transferred to other owners. Reconstructing a clean history is investigation work rather than a data load, and it ran $19,000 in a 640 structure example that covered only the current cycle plus reconciliation.
The practical route is to migrate the current cycle first, because that is all you need to schedule the next inspection correctly, then work backwards only as far as your trending genuinely requires.
What if our software vendor changes pricing or the licence model?
The exposure worth watching is not the annual figure but the configuration you have accumulated inside the product: your agency developed elements, your form layouts, your validation rules. That is real engineering effort that lives in someone else's system, and it is what makes a move expensive regardless of price.
Ask what an export contains before your next renewal. Element definitions, condition state history, photographs with their element associations, and the submittal record for each cycle should all come out in a documented format. If photographs come out as an unassociated folder, that is a material exposure independent of price.
How long does a bridge inspection build take, and when should it go live?
Twelve to 18 weeks for the inspection core, then 9 to 15 months in total if you go on to the full structure management platform.
The timing rule matters more than the duration: ship before an inspection season, never during one. Inspectors learning a new field application in July under a bridge in the heat will not adopt it, and a failed field rollout costs a year because the next honest opportunity is the next season. Plan backwards from your season start date.
Should we replace AASHTOWare BrM or build alongside it?
If it runs well and your staff know it, build alongside. The targeted project is an offline field inspection application carrying your own element set that feeds it, typically $60,000 to $110,000, which addresses the complaint most agencies actually have without disturbing your submittal path.
Replacement becomes worth discussing when configuration effort to match your programme keeps exceeding the value returned, when consultant submissions still arrive as PDFs, or when your interval logic, load rating chain and submittal reconciliation all live outside it anyway. At that point you are maintaining a management platform that manages very little.
How do we stop consultant firms injecting inconsistent data?
Give them a submission route with validation applied at their end and a review and acceptance step at yours, with rejections returned carrying specific reasons. That is roughly $26,000 to $40,000 as a standalone piece and it replaces PDF reports arriving by email and being re keyed weeks later.
Then control quantity consistency: carry the previous cycle's element quantities forward as the starting point and require an explicit reason when a total changes. Without that, a small measurement difference between two inspectors reads as condition improvement in your deterioration model.
Are culverts worth including in the first release?
Usually yes, and the decision needs making early. Agencies treat culverts as second class structures because they are less visible, then discover they make up a third of the register and carry their own forms and interval rules.
Deferring them changes the element configuration effort noticeably and means running two scheduling processes side by side for a year, which is exactly the kind of parallel process that produces a missed interval. If they are a third of your inventory, put them in phase one.
Can we start small and expand later?
Yes, and you should. Start with routine inspections on your own structures with your own staff, adopt the national element set first, and add your agency elements incrementally once the extension mechanism exists, because at that point adding one is configuration rather than development.
Leave load rating where it is initially. Rating is specialist work done in specialist tools, and linking the resulting record to the structure is enough at first. Consultant workflow and specialised inspection types belong in phase two, once the core loop has survived a real inspection cycle.
When is deterioration modelling worth building?
Only after two clean cycles of element data have been collected inside the system. It runs roughly $46,000, plus about $58,000 for candidate project generation and funding scenarios, so it is not the expensive part. The prerequisite is the expensive part.
A funding scenario presented to a capital committee is only as defensible as the condition history behind it, and a commissioner asking why a specific bridge in their district ranks where it does deserves an answer that traces back to individual inspection findings rather than a curve fitted to national defaults.
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.
How do I know when spreadsheets are no longer enough to run my operations?
Replace the spreadsheet once more than three people edit it, versions travel by email, or a single broken formula could cost real money. Other reliable signals: staff keep personal shadow copies, month-end reporting takes days of manual assembly, and nobody can say who changed a number or why. In Digital Heroes discovery calls the tipping point is almost always a specific expensive error, a mispriced quote, a missed order, or payroll built on a tab someone sorted wrong.
Should we build the whole internal tool at once or start with an MVP?
Start with a version that fully replaces one workflow, ship it in 4 to 6 weeks, and let real usage set the roadmap. Internal tools have a captive audience, so you learn within days which features matter, and across Digital Heroes projects roughly a third of initially requested features never get built once staff work with version one. Phasing also spreads the spend: a $40,000 vision becomes a $15,000 phase one that starts paying for itself while phase two is scoped.
Is a custom internal tool secure enough for HR records and financial data?
A properly built custom tool is generally safer for sensitive data than the shared spreadsheet it replaces, because you get role-based access, audit logs, encrypted storage, and the ability to cut one person's access instantly. Ask the agency specifically for encryption in transit and at rest, permissions down to the field level, and an audit trail showing who viewed or changed each record. If HIPAA, GDPR, or SOC 2 expectations from enterprise clients apply to you, raise it before the quote, because compliance features add real scope.
At what point does Retool cost more than building a custom tool?
The crossover usually lands between 25 and 50 daily users. At Retool's published Business rates of $50 per standard user and $15 per end user monthly, a 40-person deployment with a typical seat mix runs roughly $9,000 to $15,000 per year, every year, while a comparable custom tool built once for $20,000 to $30,000 carries no per-seat fees and costs about 15 to 20 percent of the build price annually to maintain. On a three-year horizon, custom comes out ahead for most growing teams in Digital Heroes engagements.
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.
Should we build our internal tool in Retool instead of hiring developers?
Retool is the right choice if someone on your team is comfortable with SQL and JavaScript and the audience is a handful of technical users, because a basic CRUD dashboard comes together in days. Hire developers when non-technical staff will use the tool daily, when the logic goes beyond forms sitting on a database, or when per-seat pricing stings, since Retool's Business tier lists at $50 per standard user per month. A pattern Digital Heroes sees often: companies arrive after a year on Retool with a tool nobody can maintain because the one person who built it has left.
What should I prepare before contacting an agency about an internal tool?
Bring the spreadsheet or document you run the process on today, a list of everyone who touches the workflow and what each person does, and one sentence describing the outcome you want. You do not need wireframes or a technical spec; a 30-minute screen-share of the current process beats a 20-page requirements document. Decide your rough budget band and name a single internal decision-maker, because projects without one take noticeably longer in Digital Heroes experience.
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.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
Is a freelancer or an agency better for building an internal tool?
A solid freelancer works for a single-workflow tool under roughly $10,000, if you accept that one person holds all the knowledge. An agency earns its premium once the tool spans departments or integrations, because you get a developer, a designer, and a project manager plus continuity when someone leaves or gets sick. The hidden freelancer cost appears 18 months later when you need changes and the original builder has moved on, a rescue situation Digital Heroes is hired for regularly.
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.
Who can build a custom internal tools system?
Digital Heroes builds custom internal tools 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 internal tools 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 Ryan.
Senior UX Designer · APAC · Sydney · 3 posts on the site
Published · Last updated .
