Completions and Commissioning Management Software: When SmartPlant or WinPCS Is the Right Buy and When Tag Count Forces a Build
Tag count sets the floor and contractor count sets the price.
On this page
Tag count sets the floor and contractor count sets the price. Below a few thousand tags with one delivery 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. Above roughly 50,000 tags, or once several contractors claim progress against shared scope, readiness stops being computable by hand and a build starts to pay. If you already run the Hexagon engineering stack, buy SmartPlant Completions and stop there.
When is off the shelf genuinely the right call here?
Three products carry real credibility in this category and each wins for a different reason. Hexagon SmartPlant Completions is the heavyweight, and if your project already runs the Hexagon engineering stack the native tag register integration is a genuine advantage that should weigh heavily, because that is where most completions data problems start. WinPCS has been used on serious projects for a long time and is well understood by commissioning people who have worked internationally. Wood GoTechnology hub2 comes with the process knowledge of a company that does this work, which shows in the model.
Buy, and stop reading here, if this describes your project:
- A brownfield tie in or a small unit with a few thousand tags rather than tens of thousands.
- One delivery contractor, so one permission model and one progress claim conversation.
- A construction window measured in months, where a custom build would not be ready in time.
- An engineering register that is essentially stable through construction.
- A commissioning team who already know one of the packaged products.
That last point is worth more than a feature comparison suggests. A system your commissioning contractor's people can use on day one saves weeks of training, and weeks of training during commissioning are project weeks.
A second case for buying at any size. If the owner has not settled the certification hierarchy, meaning mechanical completion, ready for commissioning, commissioning complete and handover with the required check sheet sets and punch categories for each, do not commission software yet. Changing that mid build is the single most expensive avoidable rework in this category, and it is a decision no developer can make for you.
When does a custom build actually pay off?
Thursday morning, twenty people, one question: can subsystem 2340 be energised on Monday. The electrical contractor says his scope is complete. The instrument contractor says four loops are outstanding, two of them waiting on a valve the mechanical contractor says was installed last week, with a photograph to prove it. The commissioning engineer has a fortnight old spreadsheet showing 87 percent of check sheets complete and nobody can say which 13 percent, or whether any sit inside the boundary as it was redrawn in March. An hour later the decision is deferred to next Thursday. The hour is not the cost. The week is.
Build when two or more of these are true:
- More than roughly 50,000 tags, so per discipline spreadsheets cannot be reconciled by hand.
- Several contractors claiming progress against shared scope, where one subsystem draws tags from four commercial packages.
- Handover date sitting on the critical path to first production, where a week of deferred decisions costs more than the software.
- Brownfield work inside a live plant, where completions has to interact with permit to work and isolation.
- A requirement for the completions system to reach into the owner's maintenance, document and cost systems, which packaged products treat as out of scope.
The underlying reason general project software fails here is structural. A construction management system tracks progress against a work breakdown structure. Completions tracks status against a tag, and a single subsystem pulls tags from piping, electrical, instrument and mechanical scopes sitting in different contractors' packages. Progress at 92 percent against the work breakdown structure tells you nothing about whether any subsystem is complete, because completion is not linear across a boundary.
How do they compare on the things that matter in this industry?
Tag register as a live feed. Ask what happens when engineering deletes a tag that already has signed check sheets against it. The answer you want involves a revision trail, a superseded state and a report of affected records. A one time export taken at the start is wrong by month three, and the Thursday argument is often about equipment designed out in April that is still on somebody's outstanding list.
Automatic check sheet assignment. A new instrument tag should have its check sheets within the hour, assigned by tag type and discipline from a centrally maintained library. Any process where a coordinator assigns them manually falls behind the drawings by week six, and once it does the outstanding list stops reflecting reality.
Boundary versioning. Subsystem boundaries change during a project. Ask how a boundary change affects a completion percentage reported to the owner last week. If there is no answer, readiness numbers move without explanation and nobody trusts them again.
Offline field execution. A technician on the fourth floor of a structure with no signal for six hours either records on the device or records on paper for someone to key later. What you need is durable local storage, a sync queue, conflict resolution on a check sheet two people touched, and assigned work visible while offline. The keying backlog is exactly where completion status goes stale.
Contractor segregation. Each party needs its own scope visibility, its own signature authority set and its own progress view, and none should see another's commercial position. This gets messy in a single tenant configuration, and the interesting cases are the shared ones where a subsystem spans four scopes.
What does total cost of ownership look like at your scale?
On the build side, from Digital Heroes delivery experience, a first release runs $100,000 to $220,000 over 14 to 22 weeks. That buys a live tag register feed, system and subsystem boundaries defined against it, an automatically assigned check sheet library, offline field execution on tablets, and a readiness percentage per subsystem that replaces the meeting. A full platform adding punch list management with blocking categories, the certification hierarchy, handover dossier generation, contractor access control, progress claim reconciliation and asset handover into the maintenance system runs $280,000 to $650,000 over 8 to 14 months.
A worked greenfield plant with one train, roughly 65,000 tags and four delivery contractors priced out like this: discovery with the certification hierarchy agreed in writing $16,000, live tag register feed with revision trail $30,000, subsystem structure with versioned boundaries $26,000, check sheet library with automatic assignment $24,000, offline field execution $34,000, readiness view with outstanding items named against the responsible contractor $14,000, contractor access control $18,000, and migration of open items from per discipline spreadsheets $11,000. That totals $173,000. A single contractor project of similar tag count lands nearer $125,000 for the same functional scope. Adding punch management, the full certification hierarchy, continuous dossier generation, progress claim reconciliation and asset handover takes the same project to roughly $430,000 to $540,000 across the following three to four quarters.
Dossier generation is $40,000 to $80,000 within the full platform phase. Infrastructure runs $600 to $1,800 a month during peak field activity, driven almost entirely by photographs attached to check sheets. Support and enhancement runs 12 to 18 percent of build cost annually. Budget separately for the tablet fleet, because site conditions destroy devices and a project running three hundred check sheets a day cannot wait a fortnight for a replacement, and for contractor onboarding, which recurs with every mobilisation.
On the buy side, the honest comparison for most mid sized projects is not an enterprise licence. It is spreadsheets and a coordinator. Price the deferred decision, the coordination labour across four disciplines, the keying backlog measured in days behind the register, and the overtime when the dossier is assembled in the last weeks by people working weekends.
What does the hybrid look like, and when is it the honest answer?
There is a narrow option that suits projects already running a packaged tool and it is the one most mid sized projects should consider first. Build the readiness layer alone: consume check sheet and punch data from your existing system and join it to subsystem boundaries and the live tag register. That runs $45,000 to $80,000 over eight to twelve weeks and does not touch field execution.
It answers the one question the weekly meeting cannot, which is whether a specific subsystem is ready and exactly what is outstanding inside its boundary. If your packaged tool captures check sheets adequately and your problem is that nobody can compute readiness across a boundary, this is the proportionate spend and it leaves your field process alone.
The other hybrid worth naming is scope sequencing on a full build. Adopt your existing check sheet library rather than redesigning it during the project, since your commissioning team already has forms that work and 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 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.
Which should you choose, by operator size and stage?
Find your row and act on it.
- Brownfield tie in, a few thousand tags, one contractor, three month window. Do not build. A packaged tool or a disciplined spreadsheet with one clear owner is proportionate.
- Any project already on the Hexagon engineering stack. Buy SmartPlant Completions. The native tag register integration addresses the exact place most completions data problems start.
- Commissioning contractor whose people already know WinPCS. Buy it. Day one usability is worth more than a feature comparison, and training time is project time.
- Mid sized project on a packaged tool where readiness is the only real complaint. Build the readiness layer at $45,000 to $80,000 and leave field execution alone.
- Fifty thousand tags or more with several contractors on shared scope. Build the first release at $125,000 to $173,000 depending on segregation, and phase punch, certification and dossier work behind it.
Two conditions apply to every build row. Be live while check sheets are still being executed, because a completions system introduced at handover is an expensive data entry exercise, and get tablets into the field on a trial subsystem by around week fourteen rather than at go live. And settle ownership before kickoff: the repository, the cloud accounts and every completions record should be yours in writing, because the dossier is a permanent asset record for a plant that will run for decades while the software was built for a project with an end date.
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.
- Across 1,471 IT projects the average cost overrun was 27%, but one in six projects was a 'black swan' with an average cost overrun of 200% and a schedule overrun of nearly 70%. Source: Harvard Business Review (Bent Flyvbjerg & Alexander Budzier, University of Oxford) (2011) →
- Across more than 5,400 IT projects studied by McKinsey and the University of Oxford BT Centre, large IT projects ran on average 45% over budget and 7% over schedule while delivering 56% less value than predicted. Source: McKinsey & Company / University of Oxford (BT Centre for Major Programme Management) (2012) →
- Salesforce's field-service research (State of Service / field service trends, survey of 5,500+ service professionals) found that 74% of mobile workers report increasing workloads and 47% say appointments don't go as planned due to customer miscommunication, unaccounted-for parts, or insufficient appointment lengths and travel times. (The separate claim that admin tasks consume ~30% of a technician's hours is NOT supported by the report - the seventh-edition data instead states technicians spend about 18% of working hours, ~7 hours/week, on admin, and only ~32% of time interacting with customers.). Source: Salesforce (2024) →
- 88% of customers say good customer service makes them more likely to purchase from a brand again in the future, quantifying the direct revenue link between support quality and retention. Source: HubSpot (2024) →
Frequently asked questions
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. On a multi billion dollar project the configuration effort is proportionate.
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 is disproportionate, or where the system must reach into the owner's maintenance, document and cost systems.
What does it cost to migrate off our current completions system?
Migration here means open items only, and in a representative build it was $11,000. Closed check sheets can stay in the spreadsheets or the legacy tool and be attached as records rather than re-keyed.
The larger switching consideration is timing rather than money. Moving mid construction means running two sources of truth through at least one certification cycle, so plan the changeover against your construction calendar and not against a software release date.
What if our vendor raises licence costs or prices every change separately?
Licensing here commonly scales with tags or users, so model it at your project's peak tag count rather than today's, and remember a second train reprices the whole arrangement. Interfaces and changes being quoted separately is normal in this category and not unreasonable, since each really is site specific work.
Price the queue, not just the quote. If an interface you need lands after handover, it did not exist for the project it was bought for. Owning the readiness layer and the tag register feed converts a large part of that queue into work you can schedule yourself.
How long does a completions system take, 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.
How much does contractor data segregation add?
In a representative build 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, signature authority set, progress view and 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 is offline field execution the largest line in the first release?
Because it cannot be approximated. In a representative build 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 in a meeting about next Monday.
Can we build only the readiness view and keep our current tool?
Yes, and for mid sized projects this is often the right answer. 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.
It does not touch field execution and it answers the one question the weekly meeting cannot: whether a specific subsystem is ready to energise and exactly which blocking punch items and outstanding tests sit inside its boundary, with the responsible contractor named against each.
Is progress claim reconciliation worth paying for?
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.
I run a 15-person business. Is there a cheaper option than a full custom project management build?
Yes: a custom layer on top of a tool you already pay for. Digital Heroes ships client dashboards, automated reporting, and workflow glue built on the Asana and ClickUp APIs for $8,000 to $20,000, which fixes the specific gap without replacing the whole tool. A full custom platform rarely makes sense below roughly 50 seats unless the software faces your own customers.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
Who owns the code when an agency builds my project management software?
You should, in full, and the contract must say so: work-for-hire language with all intellectual property assigned to you on final payment. Watch for agencies that license you their platform or framework, because that quietly turns your custom tool back into a subscription you cannot leave. Digital Heroes assigns full ownership and delivers into a GitHub organization the client controls; treat anything less as a red flag.
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.
What should the first version of a custom project management tool include, and what should wait?
Version one is the painful workflow plus the basics: tasks, projects, permissions, and one integration, shippable in 12 to 16 weeks. Everything that feels essential but is not should wait: Gantt views, custom report builders, native mobile apps, and public API access all belong in version two, once real usage shows what matters. Teams that run the MVP for a quarter before expanding consistently spend less and drop features that looked critical on paper.
What should I have ready before I contact a development agency?
Four things: an export from your current tool, a list of the specific workflows it fails at, screenshots of the spreadsheets you use as workarounds, and your integration list with a budget range. Buyers who arrive with those cut discovery from two or three weeks to days, and that time comes straight off the invoice. You do not need a formal spec document; a good agency writes that with you.
We're paying for 250 Monday seats. Would building our own tool be cheaper?
Cheaper only if you hold the tool for three years or more. 250 seats on Monday's Pro tier at about $19 per user per month is roughly $57,000 a year, while a custom platform costs $120,000 to $200,000 to build plus 15 to 20 percent annually to run, so cash break-even sits around year three. Building wins if you also gain workflow fit and unlimited seats; if Monday fits fine and you only dislike the invoice, negotiate an enterprise contract instead.
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.
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.
Is custom software more secure than off-the-shelf SaaS?
Neither is secure by default; security tracks the practices of whoever builds and operates the system, not the model. SaaS gives you the vendor's certifications and patching but puts your data in a shared multi-tenant platform on their terms, while custom gives you full control over data residency, access rules, and compliance requirements like HIPAA, with the responsibility sitting with you and your agency. Before hiring anyone for a system holding sensitive data, ask for their security checklist: encryption at rest and in transit, an OWASP Top 10 review, role-based access, and a penetration test before launch.
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
More from Aanya.
Senior Frontend Engineer · Next.js · Delhi · 2 posts on the site
Published · Last updated .
