Building Commissioning Software: Build a Script Library, or Buy the Issue Log
The threshold is roughly 12 concurrent projects, and what it really measures is whether your test script library is an asset or a folder. Below that, with one or two agents, buy CxAlloy or Facility Grid and put the money into another engineer.
On this page
The threshold is roughly 12 concurrent projects, and what it really measures is whether your test script library is an asset or a folder. Below that, with one or two agents, buy CxAlloy or Facility Grid and put the money into another engineer. Above it, or on any healthcare, laboratory or data centre work where sampling has to be defensible, build: a first release covering the equipment register, tablet execution and issue tracking runs $55,000 to $130,000 over 12 to 16 weeks, and the script library alone runs $35,000 to $70,000 over eight to twelve weeks. Most providers reading this should buy.
When is off the shelf genuinely the right call here?
If you are a small commissioning practice running a handful of projects at a time with one or two agents, buy. CxAlloy and Facility Grid are purpose built, priced reasonably against a build, and will give you a competent issue log and checklist workflow immediately rather than in four months. The money is better spent on another engineer, and an engineer improves your delivery this quarter.
Buy also if you are an owner commissioning a single building. Your provider will bring their own tooling, and imposing yours creates friction for no benefit. What you should do instead costs nothing: make structured handover data a contract requirement, so the equipment register, test results and issue history arrive as data rather than as a binder of scanned forms. That achieves the outcome you actually want without a software project.
Both products hold an issue log competently, which is genuinely most of what a commissioning project needs day to day. Be honest about what they hold poorly before you decide anything, because that is the whole basis of the build case: a provider's own test scripts as versioned, reusable content, and the sampling strategy that decides how many of 84 identical fan coil units you actually test.
When does a custom build actually pay off?
It pays off when your script library is genuinely differentiated. A good commissioning firm's value is concentrated in it: what to test on a variable air volume box, in what order, with what pass criteria, what to do about the sequence of operations for a chilled water plant with two chillers and a bypass. That library took a decade to build and it currently lives as documents copied into each project and edited, which means an improvement made on project A never reaches project B. Turning it into structured, versioned content with pinned project instantiation stops that leak permanently.
It pays off when you run enough concurrent projects that quality depends on which agent is assigned. At that point consistency is a commercial problem, not an internal one.
It pays off on healthcare, laboratory and data centre work, where documentation requirements are heavier and sampling has to survive an owner's scrutiny. You are not testing all 84 fan coil units, and that is fine and standard. What almost never happens is recording which units were in the initial sample, how they were chosen, what failure rate triggered expansion, and what the final coverage was. Owners who have been through a bad handover care about that more than any other feature.
It pays off for owners with a portfolio who want commissioning data flowing into a maintenance system rather than arriving as files. And it pays off if you want to sell ongoing or monitoring based commissioning, which needs trend infrastructure a checklist tool does not provide.
How do they compare on the things that matter in this industry?
Five grounds, all checkable before you sign anything.
- Script against checklist. A checklist is a list of items someone confirms. A test script is ordered steps with expected values, tolerances, required evidence and a link to the specification clause or sequence of operations being verified, held at a version. Ask any developer or vendor to explain the difference. One who treats both as forms will give you a form builder, and your library stays a folder with a nicer front end.
- Sampling defensibility. Ask whether a declared initial sample can be selected by the system, whether a failure threshold is set before testing begins, whether expansion is automatic when it is breached, and whether coverage appears in the report as a documented fact. A form builder cannot express any of that.
- Issue classification at creation. A deficiency against the contract documents, a design issue needing the engineer, an incomplete installation that is simply not ready, and an operational adjustment have different owners and different resolution paths. One undifferentiated list is what turns a contractor relationship adversarial.
- Offline behaviour. Mechanical rooms and shafts have no signal. A technician who cannot record a result on the spot will write it on paper and type it up badly that evening, whichever tool you bought.
- Handover output. Whether the equipment register, test results and issue history can leave as structured data an owner's facilities team can load, or only as documents.
What does total cost of ownership look like at your scale?
A first release covering the equipment register with reconciliation between design intent, submitted equipment and what was installed, prefunctional checklists and functional test scripts executed offline on a tablet, issue tracking with classification and contractor response, and completion reporting by system and area runs $55,000 to $130,000 over 12 to 16 weeks in Digital Heroes delivery experience. A full platform adding the versioned script library with revision workflow, sampling rules, trend ingestion, certification documentation packs, an owner portal and structured handover runs $150,000 to $380,000 over 6 to 12 months.
A worked provider running about 18 concurrent projects with six agents and a library of roughly 140 documents lands at $109,000 for the first release, with 40 core scripts migrated at $12,000 of that. Trend ingestion is the expensive later component: plan on $20,000 to $45,000 for the first building including the analysis rule engine, then a recurring per site cost thereafter, because the constraint is site access and controls contractor cooperation rather than code.
Running costs are modest and easy to underestimate. Infrastructure sits at $200 to $600 a month, driven by evidence photographs and trend volume rather than user count. Support and enhancement runs 12 to 18 percent of build cost annually, and turnaround during a functional testing week matters more than the headline rate, because a tablet application that fails on the day four technicians are on site costs more than the annual fee. Then two lines nobody quotes: tablet fleet management including replacements and a device management tenancy, and a senior engineer spending a few hours a month owning the script library. Without that second one the library becomes a snapshot again within a year.
What does the hybrid look like, and when is it the honest answer?
Keep the product for the issue log and build only the script library. For a large share of providers this is the correct move and it is the cheapest thing in this guide.
The build is narrow and specific: convert the library into structured, versioned content, so a project instantiates scripts at a pinned version while the library keeps improving, and a technician who finds a wrong step or an unclear criterion sends a proposed revision back to the library owner rather than editing a copy that dies where it was found. That runs $35,000 to $70,000 over eight to twelve weeks and leaves CxAlloy or Facility Grid doing what it does well.
The other honest hybrid is owner side. Rather than building anything, write structured handover into the specification: the asset data standard agreed early, the equipment register, test results and issue history delivered as data. Agreeing that standard with a facilities team costs nothing in engineering if it happens on time, and retrofitting it near substantial completion is where handover projects fail expensively, because the deadline is fixed and the leverage has gone.
The hybrid stops working when trend review is part of your offering. Monitoring based commissioning needs ingestion, analysis rules and a link from a flagged condition into the issue lifecycle, and no checklist tool provides that.
Which should you choose, by provider size and stage?
One or two agents, a handful of projects: buy CxAlloy or Facility Grid. Nothing in this guide changes that answer.
Three to about a dozen concurrent projects with a library you consider differentiated: keep the product and build the script library alone at $35,000 to $70,000. Migrate the top forty scripts covering the equipment types that appear on every project, run a season, and let the technicians tell you what is missing. Attempting all two hundred up front converts a software project into a documentation project with a software deadline.
More than roughly 12 concurrent projects, or any healthcare, laboratory or data centre work: take the first release. Start with mechanical and controls, which carry most of the scope, and add electrical, life safety and specialty systems in phase two once the script and issue models have settled. Build offline first from day one rather than retrofitting it, because retrofitting offline costs more than building it.
Owners with a portfolio: build only if you want commissioning data flowing into your maintenance system across many buildings. For one building, specify the handover and let your provider bring their tools.
Providers selling monitoring based commissioning: build, and defer trend ingestion to phase two with one building for the first integration. You will learn more from one live site than from three months of protocol research, and you can price trend work as a per project line in your fee proposal rather than absorbing it.
Whichever route, settle code ownership before kickoff. If your library is the firm's core intellectual property, encoding it into a system somebody else controls defeats the purpose of the exercise.
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.
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- PMI's Pulse of the Profession research found organizations waste an average of roughly 9.9% of every dollar invested in projects due to poor performance - equivalent to about $1 million wasted every 20 seconds collectively worldwide. Source: Project Management Institute (PMI) (2018) →
- 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) →
- 73% of surveyed businesses now use a headless architecture (up nearly 40% since 2019), and 98% of those not yet using it are evaluating or planning to evaluate headless within 12 months, with 82% saying it makes delivering consistent content easier. Source: WP Engine (2024) →
Frequently asked questions
What does it cost to move off CxAlloy once we have years of projects in it?
The live commercial cost is small and the historical cost is the awkward part. Closed projects rarely need to move, so most providers export completion data for the record and start new work in the new system, which avoids a migration entirely.
What does not export cleanly is your script content, because scripts held as documents inside a project are copies rather than a library. Budget the conversion as content work with a senior engineer reviewing, roughly $12,000 for 40 core scripts in our experience, and treat that as the real switching cost rather than the data export.
What happens if our commissioning platform changes how it prices seats or projects?
Check the basis before you worry about the rate. Whether your product scales per project or per user determines how growth is priced, and a provider adding agents behaves very differently under the two models from one adding concurrent jobs.
The stronger protection is not commercial. A provider whose script library is structured content it owns can move platforms without losing the asset that makes it competitive. A provider whose scripts live only as documents inside a product is exposed to any repricing, because leaving means rebuilding a decade of work.
How long does a commissioning software build take?
Twelve to 16 weeks for a first release if you start with mechanical and controls, then 6 to 12 months for the full platform. Offline tablet capture has to be in the first release rather than retrofitted, since a technician in a mechanical room with no signal will use paper.
Script migration runs in parallel with a senior engineer reviewing, not at the end by whoever is free. That sequencing matters because migration is subject matter expert time rather than developer time, and treating it as a final task is how a project slips by a month.
Is CxAlloy cheaper than building our own commissioning system?
For a small practice with one or two agents, clearly yes, and a competent issue log and checklist workflow is available immediately rather than in four months.
The comparison changes when your script library is the differentiator. CxAlloy and Facility Grid hold an issue log well and hold a provider's own scripts poorly as versioned reusable content, so improvements made on one project never reach the next. Compare on the unbillable hours spent copying and re editing scripts and assembling documentation packs from scanned forms, not on seat price.
How should sampling on repeated equipment be handled?
As an explicit rule per equipment type: a declared initial sample selected by the system, a failure threshold agreed before testing begins, and automatic expansion when that threshold is breached. The report then states coverage as a documented fact rather than an assurance.
This is the feature owners who have been through a poor handover care about most, because the alternative is a certificate asserting that systems perform, backed by testing whose extent nobody wrote down. Be sceptical of anything cheap that claims to handle sampling, since a form builder cannot express a threshold or an expansion rule.
How much does trend ingestion from the building automation system add?
Plan on $20,000 to $45,000 for the first building including the analysis rule engine, then a recurring per site cost for every building after that. The reason is access rather than code: protocols differ, the controls contractor is a gatekeeper on some jobs, and each site needs its own arrangement.
Price it as a per project line in your fee proposal rather than absorbing it. It is genuinely per project work, and it is also what lets you offer monitoring based commissioning credibly, which is a different service at a different rate.
Can we build only the script library and keep our current issue log?
Yes, and for firms whose scripts are the real asset it is usually the right first move. Structured versioned content with pinned project instantiation and a proposed revision workflow runs $35,000 to $70,000 over eight to twelve weeks, and your existing product keeps doing the issue tracking it already does well.
What changes operationally is small and compounding. A technician who finds a wrong step or an unclear criterion sends a proposed revision back to the library owner, so an improvement made on one project reaches every future project instead of dying where it was found.
What is the cheapest credible version of a custom system?
Around $55,000 for a provider with a straightforward issue process, mechanical and controls only, offline tablet execution and no script migration in release one. That buys a working field system rather than a demonstration.
Below that figure, buy CxAlloy. The two questions that separate a real quote from a hopeful one are how sampling expansion works and how a test script differs from a checklist. If either answer is vague, the defensibility problem you have today will follow you into the new system at a higher price.
Should I customize Jira with plugins or just build our own tool?
If two or three Marketplace apps close the gap, stay on Jira, since it starts around $8 per user per month and the apps ride on top. The trap is that cloud apps are licensed for every user on the instance, so in Digital Heroes audits a 200-seat Jira with three or four paid apps plus a ScriptRunner consultant often lands at $30,000 to $50,000 a year. At that run rate a custom tool scoped to your actual workflow pays for itself in two to three years and ends the plugin upgrade treadmill.
How long does it take to build custom project management software?
Plan on 12 to 16 weeks for a working first version and 6 to 9 months for a mature platform; those are typical Digital Heroes delivery timelines. The schedule killers are undecided permission rules and mid-build scope additions, not the code itself. Locking the workflow map during discovery is what keeps a build inside 16 weeks.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
How do I vet a software agency before hiring them to build a PM tool?
Ask to click through a workflow tool they shipped, live rather than in screenshots, and get a reference from a client whose system has been in production for over a year. Then ask two questions that expose weak vendors: how they migrate data out of your current tool, and what their maintenance retainer covered for that reference client last quarter. An agency that has genuinely shipped project management software answers both in specifics.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
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.
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.
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.
How do I work out whether a custom project management tool will pay for itself?
Add three lines: the per-seat fees you stop paying, the consultant and plugin spend you eliminate, and the hours your team stops losing to manual status reporting and duplicate data entry. On seat savings alone, payback typically lands between years two and four, which is why Digital Heroes tells teams under about 50 seats not to build. It gets much faster when the tool replaces both a SaaS bill and a consultant-maintained Jira setup, or when a client portal becomes part of what you charge for.
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.
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 .
