How Much Does Completions and Commissioning Software Cost in 2026?
Custom completions and commissioning software runs $100,000 to $650,000, and the line item that moves the number most is how many contractors need genuinely separate access to the same subsystem data. A single delivery contractor means one permission model and one set of screens.
On this page
Custom completions and commissioning software runs $100,000 to $650,000, and the line item that moves the number most is how many contractors need genuinely separate access to the same subsystem data. A single delivery contractor means one permission model and one set of screens. Four contractors who must each see their own scope, sign their own check sheets, and never see another party's commercial position turns every query into an authorisation question and every report into a per organisation variant. That is not a settings page, it is a design constraint that touches the whole system. A first release with the tag register feed, subsystem structure, check sheet library and offline field execution runs $100,000 to $220,000 over 14 to 22 weeks. Multi contractor segregation plus brownfield permit interfaces is what takes a project to the top of the $280,000 to $650,000 band.
The bands a completions build falls into
The first release band is $100,000 to $220,000 over 14 to 22 weeks. That buys a live tag register feed from the engineering registers rather than a one time import, system and subsystem boundaries defined against that register, a check sheet library assigned automatically by tag type and discipline, offline field execution on tablets, and a readiness percentage per subsystem that replaces the argument in the Thursday meeting.
The full platform band is $280,000 to $650,000 over 8 to 14 months. That adds punch list management with categories that block certification, the full certification hierarchy through mechanical completion and ready for commissioning, handover dossier generation, contractor access control, progress claim reconciliation against signed check sheets, and the handover of asset data into the maintenance management system.
There is a narrower option that suits projects already running a packaged tool. The readiness layer alone, consuming check sheet and punch data from your existing system and joining it to subsystem boundaries and the live tag register, runs $45,000 to $80,000 over eight to twelve weeks in our delivery experience. It does not touch field execution. It answers the one question the weekly meeting cannot.
What drives a completions build up
Contractor segregation is the first driver. Each additional party with strict data boundaries adds an authorisation dimension to every record, a separate progress claim view, a separate signature authority set, and a separate onboarding process for their people and their devices. It is not linear in contractor count either, because the interesting cases are the shared ones: a subsystem whose tags span four scopes.
Brownfield interfaces are the second and they are frequently underestimated. Completions inside a live plant has to interact with permit to work, isolation and the operating authority's own procedures, and packaged products treat that as out of scope for a reason. Modelling a check sheet that cannot be executed until a permit is live, and a permit that cannot close while a test is in progress, is genuine engineering.
Scale in trains and sites is the fourth. A second train is not a copy, because it brings its own subsystem structure, its own certification sequence and a portfolio view somebody will want across both. Certification hierarchy churn is the fifth and the cheapest to avoid: if the owner has not settled the hierarchy before the build starts, you will build it twice.
What keeps the number down
Agree the certification hierarchy with the owner before the first line of code. Mechanical completion, ready for commissioning, commissioning complete and handover, with the required check sheet sets and punch categories for each, written down and signed. Changing this mid build is the single most expensive avoidable rework in the category.
Adopt your existing check sheet library rather than redesigning it during the project. Your commissioning team already has forms that work and that inspectors accept. Digitising them is cheap. Rewriting them while also building the system doubles the review burden and delays the field.
Keep the dossier out of release one but design the data for it from day one. Certificates, check sheets, test records and vendor documents must all be attachable to a subsystem from the first week even if the generator comes later, because retrofitting those associations costs far more than capturing them. Use one device standard across the field too, since mixed tablet fleets cost more in support and training than the hardware saving is worth.
A worked example that adds up
A greenfield process plant, one train, roughly 65,000 tags, four delivery contractors with commercially separate scopes, engineering registers in a system that publishes on request rather than continuously, construction completion about seven months out.
- Discovery, including the certification hierarchy agreed in writing with the owner and the subsystem breakdown strategy: $16,000
- Live tag register feed with revision trail, superseded states and reporting of records affected by an engineering change: $30,000
- System and subsystem structure with versioned boundaries and visible impact of a boundary change on completion percentage: $26,000
- Check sheet library with automatic assignment by tag type and discipline, and a maintained central template set: $24,000
- Offline field execution on tablets with signatures, photographs, queued sync, conflict handling and assigned work visible offline: $34,000
- Readiness view per subsystem with outstanding items named against the responsible contractor: $14,000
- Contractor access control with per organisation data segregation across every record and report: $18,000
- Migration of existing check sheet records and punch items from per discipline spreadsheets: $11,000
That totals $173,000, in the middle of the first release band because four contractors need segregation from day one. A single contractor project of similar tag count lands nearer $125,000 for the same functional scope.
Adding punch management with blocking categories, the full certification hierarchy with generated certificates, continuous dossier generation, progress claim reconciliation and asset handover into the maintenance management system takes that project to roughly $430,000 to $540,000 in total across the following three to four quarters.
How the spend phases
Discovery is three to four weeks and around 9 percent of the first release. The deliverable that matters is the certification hierarchy signed by the owner and a worked subsystem breakdown for two real subsystems, including one that spans all four contractor scopes.
The tag register feed carries roughly 17 percent across weeks two to nine. Ask a developer what happens when engineering deletes a tag that already has signed check sheets against it. The right answer involves a revision trail, a superseded state and a report of affected records. A developer who has not thought about it will build an import that silently orphans data, and you will spend the Thursday meeting arguing about equipment that was designed out in April.
Check sheets and field execution together take roughly 33 percent, weeks six to eighteen, and the tablets need to be in the field for a trial subsystem by around week fourteen rather than at go live. A technician on the fourth floor of a structure with no signal either records on the device or records on paper, and the keying backlog is exactly where completion status goes stale.
Subsystem structure and readiness reporting are another 23 percent and are what the project team actually buys. The single most valuable screen is the one saying this subsystem is ready to energise except for these three blocking punch items and these two outstanding loop tests, with the responsible contractor named against each. The last 17 percent covers access control and migration, and migration here means open items only. Closed check sheets can stay in the spreadsheets and be attached as records.
The ongoing costs nobody quotes
Infrastructure runs $600 to $1,800 a month during peak field activity for a project of this size. Photographs attached to check sheets are the dominant storage cost and they scale with tag count and inspection intensity rather than with users.
The tablet fleet is a real line. Site conditions destroy devices, and a project that runs three hundred check sheets a day cannot wait a fortnight for a replacement. Hold spares and budget the replacement rate.
Engineering register changes never stop until the project does. Every design change ripples into check sheets, punch items and readiness numbers, and that reconciliation is a standing operational cost rather than an incident. Contractor onboarding recurs for the same reason: new parties join, subcontractors change, and each needs accounts, signature authority mapping, device provisioning and training, so budget it per mobilisation rather than once.
Support during commissioning is not the same as support during construction. Ask specifically about cover across night shifts and weekends in the commissioning window, because that is when the system is load bearing and a failure delays energisation rather than paperwork.
Comparing a build against your current renewal
Put it on one page against the actual alternative, which for most mid sized projects is not an enterprise licence, it is spreadsheets and a coordinator.
Start with the deferred decision. If your weekly readiness meeting sends twenty people away without a decision, price that at twenty salaries for the hour plus the week of slippage it usually implies. On a project where handover date drives first production, a week is not an administrative cost.
Then count the coordination labour. The completions coordinator assembling status from four disciplines, the document controller chasing signed originals, the planner reconciling contractor claims against a percentage nobody can evidence. Multiply by fully loaded cost across the construction and commissioning window.
Then price the keying backlog. Paper check sheets typed in later mean your readiness number always describes last fortnight, so ask your commissioning manager how many days behind the register runs and what that has cost in re-inspection. Then price the dossier. If handover documentation is assembled in the last weeks by people working weekends, you know what that overtime looks like and what a delayed handover certificate costs against the operating date.
Set that against a build whose cost stops when the project does but whose data outlives it, because the dossier is a permanent asset record for a plant that will operate for decades.
When buying beats building
Do not build for a brownfield tie in with a few thousand tags, one contractor and a three month construction window. A packaged tool or a disciplined spreadsheet with one clear owner is proportionate, and a custom system would not be finished before the work is.
Buy Hexagon SmartPlant Completions if your project already runs the Hexagon engineering stack. The native tag register integration is a genuine advantage and it addresses the exact place most completions data problems start. On a multi billion dollar project the configuration effort is proportionate.
Buy WinPCS if your commissioning contractor's people already know it. A system your field team can use on day one saves weeks of training, and that familiarity is worth more than a feature comparison suggests. Wood GoTechnology hub2 is a sensible choice if its structural opinion about how completions should work matches your owner's certification hierarchy, because you will be adapting to it either way.
Build above roughly 50,000 tags, when several contractors claim progress against shared scope, or when handover date sits on the critical path to first production and a week of deferred decisions costs more than the software. Build also when the completions system must reach into the owner's maintenance, document and cost systems in ways the packaged products treat as out of scope, or when licensing and configuration for an enterprise product is disproportionate to a mid sized project, which is precisely why so many of them are still being run on spreadsheets that fail in the way described above.
If you want a second opinion before signing anything, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The 2015 CHAOS data (based on the modern definition of success) reports that only about 29% of software projects succeed, 52% are challenged, and 19% fail, with the three most important success skills being executive sponsorship, emotional maturity, and user involvement. Source: The Standish Group (reported via InfoQ Q&A with Jennifer Lynch) (2015) →
- 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) →
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- Across ten outpatient clinics the mean no-show rate was 18.8%, and the marginal cost of no-shows reached $14.58 million per year for those clinics, at roughly $196 per missed appointment (2008 figures). Source: BMC Health Services Research / PubMed Central (Kheirkhah et al.) (2015) →
Frequently asked questions
What is the total cost of custom completions and commissioning software?
A first release with a live tag register feed, subsystem structure, an automatically assigned check sheet library, offline field execution and readiness reporting runs $100,000 to $220,000 over 14 to 22 weeks in our delivery experience. Adding punch management, the certification hierarchy, dossier generation, contractor access control and progress claim reconciliation takes it to $280,000 to $650,000 across 8 to 14 months.
Contractor segregation and brownfield permit interfaces move the number more than tag count does.
What does it cost to run each year after launch?
Infrastructure sits at $600 to $1,800 a month during peak field activity, driven almost entirely by photographs attached to check sheets, which scale with tag count and inspection intensity rather than users. Support and enhancement typically runs 12 to 18 percent of the build cost annually.
Budget separately for the tablet fleet and for contractor onboarding, which recurs with every new mobilisation. Ask specifically about night shift and weekend cover during the commissioning window.
How long does a completions system take to build and when should it go live?
Fourteen to 22 weeks for a first release and 8 to 14 months for the full platform. The date that matters is not go live, it is construction completion. A completions system introduced at handover is an expensive data entry exercise, so aim to be live while check sheets are still being executed.
Get tablets into the field on a trial subsystem by around week fourteen rather than at go live, because device behaviour in a structure with no signal is not something you can test in an office.
Is SmartPlant Completions or WinPCS cheaper than building?
On a project already running the Hexagon engineering stack, SmartPlant Completions is usually the better economics because the tag register integration is native and that is where most completions data problems start. WinPCS wins when your commissioning contractor's people already know it, since training time is real project time.
Building tends to win on mid sized projects where enterprise licensing and configuration are disproportionate, or where the system must reach into the owner's maintenance, document and cost systems in ways the packaged products treat as out of scope.
How much does contractor data segregation add to the budget?
In the worked example it was $18,000 within a $173,000 first release, roughly 10 percent, and it also raised the cost of every screen and report built around it. Each party needs its own scope visibility, its own signature authority set, its own progress view and its own onboarding.
The expensive cases are the shared ones. A subsystem whose tags span four contractor scopes is where the permission model and the readiness calculation meet, so make sure discovery works through at least one of those in detail.
Why does offline field execution cost so much?
Because it is the largest single item in the first release and it cannot be approximated. In the worked example it was $34,000, around 20 percent, covering local storage, queued sync, conflict handling on a check sheet two people touched, signatures, photographs and assigned work visible while offline.
The alternative is paper completed in the field and typed in later, and that keying backlog is precisely where completion status goes stale. You would be paying for a system that reports last fortnight's truth.
What does dossier generation cost and can it wait?
Budget roughly $40,000 to $80,000 within the full platform phase for continuous dossier generation per subsystem, covering certificates, completed check sheets, test records and vendor document assembly.
It can wait, but the data model cannot. Certificates, check sheets and vendor documents must be attachable to a subsystem from the first week even if the generator comes later, because retrofitting those associations is far more expensive than capturing them as you go.
Can the system reconcile contractor progress claims, and is that worth paying for?
Yes, and it is one of the strongest reasons to build. When a contractor's claimed percentage is compared against signed check sheets inside defined subsystem boundaries, both parties are reading the same record and the monthly claim conversation becomes a data review rather than a negotiation.
It also changes field behaviour quickly, because signing off work in the system becomes the route to getting paid for it, which does more for data quality than any amount of training.
What is the cheapest credible version of this system?
Around $100,000 for a single contractor project with a settled certification hierarchy, an existing check sheet library adopted unchanged, one train, and an engineering register that can publish continuously. That buys the tag register feed, subsystem structure, automatic check sheet assignment, offline execution and readiness reporting.
Below a few thousand tags with one contractor and a short window, do not build at all. A packaged tool or a disciplined spreadsheet with one clear owner is proportionate, and a custom system would not be finished before the work is.
What does it cost to keep custom project management software running each year?
Budget 15 to 20 percent of the original build cost annually, so a $100,000 platform costs $15,000 to $20,000 a year to run. That covers hosting, security patches, dependency upgrades, and the item buyers forget: fixing integrations when Slack, Google, or QuickBooks change their APIs, which happens every year. Skipping the maintenance budget is how a two-year-old tool becomes impossible to upgrade.
How many people should be working on my software project?
Three to five for a typical focused build: a project lead, one or two engineers, a designer, and part-time QA, which is the standard shape across 2,000+ Digital Heroes projects. Larger platforms justify 6 to 10, but a ten-person team on a small first version usually signals bill padding rather than horsepower. What predicts success is whether a senior engineer is writing your code daily, not the headcount on the proposal.
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.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
We've outgrown ClickUp. Does that mean we need custom software?
Not automatically. First check whether ClickUp's Business tier at about $12 per user per month plus its API covers the gap, because most complaints about outgrowing ClickUp are really automation limits, not data model limits. The genuine signal for custom is structural: your work does not fit the task-in-a-list model, for example a job that must sit under two clients with separate billing at the same time. If you are paying someone monthly just to maintain workarounds, it is time to price a build.
What happens if the agency that built our project management tool shuts down?
Nothing fatal, if you set things up correctly from day one: code in your own GitHub organization, infrastructure in your own cloud account, and written deployment documentation as a contract deliverable. With those in place, any competent team can take over a standard-stack codebase in one to two weeks. Takeover disasters happen when the vendor hosted everything in accounts they owned, so verify account ownership before the first sprint, not after the relationship sours.
Can we move our existing Asana or Jira data into a custom tool?
Yes. Both expose full export APIs, and projects, tasks, comments, and assignees come across cleanly; Digital Heroes typically runs migration as a 2 to 4 week workstream in parallel with the build. The awkward parts are attachments, automation rules that must be rebuilt rather than imported, and deciding how much closed historical work to carry over. Migrate active projects fully and keep the rest as read-only archive exports.
Will a custom tool built for 50 people still work when we're 500?
Yes, if it sits on a standard stack; a PostgreSQL-backed application handles 500 concurrent users without exotic engineering, and unlike Monday or Asana, seats 51 through 500 add nothing to your license bill. What does need rework at that scale is organizational rather than technical: permission models, department-level reporting, and admin tooling. Have the agency design the data model for multi-team use on day one, even if version one serves a single team.
What security features does custom project management software need?
The non-negotiables are single sign-on, role-based permissions, encryption in transit and at rest, and an audit log of who changed what. If client work under NDA lives in the tool, custom actually improves your position, because you can run single-tenant on your own cloud account instead of shared SaaS infrastructure. You only need SOC 2 certification if you plan to sell the tool to others; for internal use, an annual penetration test is the sensible spend.
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.
Who can build a custom project management software system?
Digital Heroes builds custom project 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 project management software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
Published · Last updated .
