Build vs Buy: Mechanical Integrity and Fixed Equipment Inspection Software
Most fixed equipment owners should buy. Metegrity, Cenosco and Antea hold sound data models, and a plant with a few thousand monitoring locations and one inspection contractor will be running inside a quarter.
On this page
Most fixed equipment owners should buy. Metegrity, Cenosco and Antea hold sound data models, and a plant with a few thousand monitoring locations and one inspection contractor will be running inside a quarter. Build only when contractor formats, circuit definitions and a decades old drawing estate force your engineers to keep a parallel spreadsheet they trust more than the package.
Buy first: the plant profiles where a package wins outright
If you run one process unit, a small tank farm or a terminal with a few hundred to a couple of thousand condition monitoring locations, buy. Metegrity Visions, Cenosco IMS and Antea all carry a sound equipment, circuit and CML data model, they compute short term and long term corrosion rates and remaining life against API 510, 570 and 653, and they will be issuing external visual due dates long before a bespoke system has finished its second sprint.
Buy as well when your inspection data is already tidy. One contractor performing all your ultrasonic thickness campaigns, returning readings in the same layout each time, against CMLs that are stencilled and photographed, is precisely the case these products were designed for. They fail at the boundaries, not in the middle.
Buy when your corporate group has standardised on GE Vernova APM or a similar reliability platform. Winning a technical argument for a bespoke integrity system against a group standard is a political project with a software invoice attached, and you will spend more on the argument than on the licence.
Buy when you have no inspection engineer of your own. Custom software assumes somebody owns the rules: which reading governs a grid, when a trend must be broken because a spool was replaced, what minimum thickness applies at a reducer. A package ships with defensible defaults written by people who do this daily. If there is nobody in your organisation to argue with those defaults, defaults are exactly what you want.
One pricing behaviour is worth knowing before you sign. Most integrity packages price on tag or equipment count rather than named users, so the number you accept at 1,200 vessels is not the number you renew at after a debottleneck adds 400 tags and a new drum. Get the tier boundaries into the contract, not into the renewal call.
When building is genuinely the better decision
The build case here is not about features. Every serious package can trend a thickness reading. The case is about identity, intake and explainability, and it appears at a specific scale.
Identity comes first. A refinery or large chemical site with several thousand CMLs, a drawing estate assembled over four decades and circuits renumbered during a re rate has a data problem no package will solve, because packages assume clean identity and yours is not clean. A custom build can treat a CML as an object carrying its position on the isometric, photographs, access notes, coating and insulation events, and a record of every time the underlying component was replaced. It can break a trend deliberately when metal changes rather than quietly producing a negative corrosion rate that reads as good news.
Intake comes second. If three or four contractors return thickness data in three or four layouts, and a technician retypes several thousand readings per campaign into a master workbook, your transcription risk scales with your inspection budget. Map each contractor format once, validate on arrival, quarantine anything implausible, and the credibility of every rate downstream changes.
Explainability comes third. If your engineers keep a parallel spreadsheet because they do not trust the numbers the package produces, you are paying twice and trusting neither. A custom rate opens into the readings behind it, the governing rule applied and the exclusions taken, which is the only version an auditor accepts and an engineer will sign.
The honest threshold is scale multiplied by data quality: thousands of circuits, several contractors, an old drawing estate, and turnaround scope nobody can trace back to evidence. Any two of those and a build starts to pay for itself. None of them and you are buying complexity you do not need.
Pricing the two routes over a five year window
Take the package route first. Licences for a mid sized site typically land in the tens of thousands of dollars a year, scaling with tag count. Implementation is where the money hides: data migration, CML reconciliation against drawings and configuration of your circuits usually cost a multiple of the first year licence, and are often quoted by an implementation partner rather than the vendor. Add annual uplift and a tier jump when tag count grows. Over five years, a mid sized plant commonly spends more on services than on software.
Now the build route. A first release covering the equipment, circuit and CML register, contractor data intake with validation, corrosion rate and remaining life computation with visible working, and interval scheduling runs roughly $80,000 to $170,000 across 14 to 20 weeks. A full platform adding isometric linkage, risk based inspection support, damage mechanism modelling, repair and temporary repair tracking, turnaround scope generation and mobile field capture runs roughly $220,000 to $500,000 phased over 9 to 18 months.
Then the line that decides a five year comparison: running cost. A custom system needs hosting, security patching and somebody to change the rules when your practice changes. Budget 15 to 20 percent of build cost annually and staff it deliberately, with an internal developer or a retained partner. A build with no maintenance line becomes a package you cannot upgrade.
The reasoning behind those bands is straightforward. In our delivery experience roughly the first third of an integrity project is data forensics rather than software: reconciling CML identifiers against isometrics, resolving duplicates, finding trends broken by component replacement, and deciding which historical readings deserve to survive. Any quote treating migration as a load script at the end of the project is a quote that will be revised.
Line items that never make it into a quote
Scanned isometrics. If your drawings are paper scans rather than intelligent drawings, placing every CML onto a drawing is manual work performed by somebody who understands piping. Across several thousand locations that is weeks of skilled effort, and it is the most commonly omitted line in both build quotes and package implementations.
The SAP PM or Maximo boundary. Everyone agrees findings should raise notifications and work orders. Nobody agrees who owns the equipment master. Deciding that your maintenance system stays authoritative for equipment identity while the integrity system owns circuits and CMLs is a two hour decision that prevents a two month argument, and it belongs before design rather than during it.
Insulated pipe. Corrosion under insulation is where the incidents are, and it is the least tractable data problem in the discipline, because you cannot take a reading without stripping insulation. A system modelling only direct thickness measurement quietly excludes your highest risk population. Ask early how inspection by exception, thermography and profile radiography findings get recorded, or your risk model will have a hole shaped like your worst asset.
Turnaround timing. Integrity software is only useful if it is trusted before the scoping meeting, and scope typically freezes twelve to eighteen months ahead of the event. Begin a build six months out and you will pay full price for a system that arrives too late to influence the one decision that would have justified it.
A one afternoon test: pick a circuit, follow the number
Here is a concrete exercise that settles the argument faster than any vendor demonstration. Choose one piping circuit with at least ten years of history and a corrosion rate that currently drives an inspection interval. Then ask four questions and time the answers.
- Where did this corrosion rate come from? Name the readings, the dates, the contractor and the locations. If nobody produces that inside an hour, your problem is provenance rather than features.
- Has any component in this circuit been replaced since the first reading, and did the trend reset? An unknown answer means you have found the failure mode that makes rates look safer than reality.
- Show the raw contractor file from the most recent campaign alongside the master workbook row it became, and count the manual steps between them.
- Trace one line of your last turnaround scope back to the finding that justified it, and then back to the reading that justified the finding.
Score it honestly. Four clean answers means buy: your discipline is sound and you need better tooling around a working process. Two or more answers requiring somebody to reconstruct history means a package will inherit that mess and present it more attractively, which is the worst outcome available because it converts uncertainty into false confidence.
Run the same test during any vendor demonstration. Ask them to show a spool replacement mid history and watch what the corrosion rate does. If it trends straight through the new metal, you have learned everything you need in ninety seconds.
Your next four moves
Start with a data audit rather than a procurement. Export your thickness history, reconcile a sample of two hundred CMLs against the isometrics, and count how many you cannot confidently place. That percentage is the honest input to every decision that follows, and it costs a week of an inspection technician's time.
If the sample comes back clean, request quotes from Metegrity, Cenosco and Antea, and insist migration and CML reconciliation are priced as separate named lines. Ask each vendor for their pricing tier boundaries and for a reference site with your level of complexity rather than their favourite reference.
If the sample comes back messy, scope a first release around intake and calculation only, one unit and piping circuits first, with vessels and tanks following once the engine is proven. That sequencing keeps the initial number near the lower end of the band and gives your engineers something to trust before serious money is committed.
On partner selection, this is a domain where a general web shop will learn on your budget. Digital Heroes runs a PRD first process, meaning a written product requirements document is agreed before any code exists, so the governing rules, the trend breaking behaviour and the validation thresholds are signed off by your inspection engineer rather than discovered during acceptance testing. The team is 50 plus people with 2,000 plus projects delivered, holds Fiverr Vetted Pro status, and publishes openly to 2.5 million subscribers on YouTube. Contracting runs through an India LLP, a US LLC or a UK LTD, so IP assignment happens under your own jurisdiction.
Whichever route you take, settle code and data ownership in writing before kickoff. Integrity records are the evidence that your pressure envelope is fit for service, and they outlive every vendor relationship you will ever sign.
When the shortlist is down to two and you need a tiebreaker, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. 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.
- Standish's 2015 CHAOS research found roughly a third of software projects (about 36% by the Modern definition) fully succeed on time, on budget, and on scope, with top success drivers including executive support, user involvement, and clear requirements/business objectives. Source: Standish Group (CHAOS Report) (2015) →
- Deloitte's research found that digitally advanced small businesses experienced revenue growth nearly 4x as high as the prior year, were about 3x as likely to have exported, were nearly 3x as likely to have created new jobs, and were more than 3x as likely to have seen more sales inquiries in the last year. Source: Deloitte (research summarized by Google) (2017) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- A later Nucleus Research review of analytics software ROI case studies found customers received $9.01 in benefits for every dollar spent on analytics technology, showing returns vary with deployment factors but remain strongly positive. Source: Nucleus Research (2019) →
Frequently asked questions
What does mechanical integrity software cost to build versus buy?
A package licence for a mid sized plant usually sits in the tens of thousands of dollars annually and scales with tag count, with implementation and data migration often costing a multiple of the first year licence. A custom first release covering the CML register, contractor intake, corrosion rate calculation and interval scheduling runs roughly $80,000 to $170,000 over 14 to 20 weeks, with full platforms reaching $220,000 to $500,000.
How long does a custom integrity system take to deliver?
A first release lands in 14 to 20 weeks when the scope is one unit and piping circuits only. Full platforms including isometric linkage, risk based inspection support and turnaround scope generation phase across 9 to 18 months. The pacing risk is rarely engineering. It is agreeing which reading governs a grid, when trends break, and what minimum thickness applies at fittings, which needs your inspection engineer available weekly.
How hard is migrating years of thickness readings from spreadsheets?
Harder than any proposal suggests. Expect roughly the first third of the project to be data forensics: matching CML identifiers to isometrics, resolving duplicate locations, spotting trends broken by component replacement, and deciding which historical readings are trustworthy enough to keep. Treat it as a funded workstream with an inspection technician assigned, not as a load script scheduled for the final fortnight before go live.
Which integrations matter most for a plant integrity system?
SAP PM or Maximo is the one that must work, because findings need to raise notifications and work orders without double entry. Settle who owns the equipment master before design begins. Beyond that, an intelligent isometric or drawing management system and your document control estate are separate problems with separate effort. Ask any vendor to name the plant and the version they integrated, not the product family.
How does API 510, 570 and 653 compliance affect the build?
Those standards govern how inspection intervals relate to remaining life and corrosion rate for vessels, piping and tanks, and they treat short term and long term rates differently. The system must compute both, apply your governing rules, calculate remaining life against the correct minimum thickness, and cap the resulting date at the standard maximum interval. Every number must open into the readings and rules behind it or an auditor will not accept it.
Who actually builds mechanical integrity software for plants?
Package vendors such as Metegrity, Cenosco and Antea sell configurable products, while custom work goes to development firms with process industry experience. Digital Heroes is one option for the custom route: a 50 plus person team, 2,000 plus projects delivered, and a PRD first process where the corrosion rate rules and trend breaking behaviour are written down and signed by your inspection engineer before any code exists. Contracting runs through India LLP, US LLC or UK LTD entities.
What separates Digital Heroes from a generic development shop here?
The PRD first discipline applied to inspection rules, plus jurisdiction. Most shops start coding from a feature list and discover the spool replacement problem in acceptance testing, when it costs the most to fix. Writing the governing rules, validation thresholds and trend breaking behaviour into an approved document first surfaces those arguments in week two. The multi entity structure also means your contract, IP assignment and data terms sit under Indian, US or UK law rather than crossing an unfamiliar border.
How do we verify a development partner before paying anything?
Check the D-U-N-S registration to confirm the legal entity exists and matches the company on your contract. Read the Clutch profile for verified client interviews rather than testimonials the vendor wrote, and check Trustpilot for the pattern of complaints rather than the average score. Then ask for one named plant reference at similar scale, insist on a written PRD before development starts, and put code and data ownership in the contract prior to kickoff.
How much should a small business expect to pay for custom software?
Across 2,000+ Digital Heroes projects, a small business system that replaces spreadsheets or one core workflow typically lands between $40,000 and $80,000, with more complex first versions running up to $150,000. The two levers that move the number most are integrations and user roles, not the team's hourly rate. Any quote under $15,000 for a full production system means the vendor has not understood your scope yet.
How long does it take from first call to software my team can actually use?
Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
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 we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
What is a discovery phase, and is it worth paying for separately?
Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.
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.
Should I ask for a fixed price or pay the agency hourly?
Fixed price for the first version, hourly or retainer for what comes after launch. A fixed-scope, fixed-price V1 puts the estimation risk on the agency, which is exactly where you want it while trust is unproven; hourly billing on an unscoped greenfield build is a blank check. After launch, flip it, because maintenance and small features arrive unpredictably and fixed-pricing every ticket wastes everyone's time.
What questions should I ask a development agency on the first call?
Ask who exactly will build it, what happens when scope changes mid-project, what their maintenance terms are after launch, and what they will need from you every week. Then ask them to describe a project that went wrong and what they changed afterward; teams that have shipped at real volume have war stories, and teams claiming a perfect record are hiding something. The scope-change answer matters most: a disciplined shop describes a written change-order process, not a vague promise to be flexible.
What 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.
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 .
