How to Hire a Building Commissioning Software Development Company
Hire the firm that can explain, without prompting, how a functional test script differs from a checklist. That single distinction decides whether your library becomes a versioned asset or a nicer form builder.
On this page
Hire the firm that can explain, without prompting, how a functional test script differs from a checklist. That single distinction decides whether your library becomes a versioned asset or a nicer form builder. Expect $55,000 to $130,000 for a first release covering the equipment register, prefunctional checklists, functional scripts on tablets and classified issue tracking, in twelve to sixteen weeks.
Six weeks before substantial completion, everything reduces to a single number: how much of the mechanical system has actually passed functional testing. The unusual thing about commissioning software is that this number is contested by four parties before it even exists. The commissioning agent says seventy percent. The mechanical contractor says everything demonstrated has passed. The controls contractor says half the tests could not run because the sequences were not loaded. Nobody is lying. They are counting different denominators, and the software you buy either settles that or joins the argument.
The category is hard to buy because a commissioning provider's real inventory is not a workflow, it is a script library built over a decade and currently living in Word documents. Improvements made on one project never reach the next, because each project copies and edits its own version. Any developer can build you an issue log. Very few will understand that turning that library into versioned, reusable, testable content is the actual product, and that a form builder with a good interface leaves you exactly where you started.
What a commissioning software development company actually does
The visible build is a tablet app and a dashboard. Underneath sit four pieces that decide whether the system holds.
The equipment register comes first, and it is not a data import. It is a living reconciliation between design intent from the mechanical schedules and controls points list, submitted equipment, and what was actually installed, with the source of each entry recorded. Equipment gets substituted through submittals, three units disappear in a value engineering exercise, tag numbers change between design and shop drawings. Two parties counting different registers will never agree on a completion percentage, which is why this unglamorous piece is the largest single source of disputed numbers on a project.
Then the scripts. Structured steps with expected values, tolerances, required evidence and a link to the specification clause or sequence of operations being verified, held at a version so a project instantiates a pinned copy while the library keeps improving. Technician feedback returns to the library owner as a proposed revision rather than a private edit.
Then sampling, which is the judgement nobody records. You are not testing all eighty four fan coil units. A defensible system declares the initial sample and how it was chosen, sets the failure threshold before testing begins, expands automatically when the threshold is breached, and states final coverage in the report as a fact. Finally, issue classification: a deficiency against contract documents, a design issue needing the engineer, an incomplete installation and an operational adjustment have four different owners, and lumping them into one list is what turns contractor relationships adversarial.
What it really costs in 2026
These bands come from Digital Heroes delivery experience rather than a published survey.
| Project tier | Cost | Timeline |
|---|---|---|
| Single project pilot: register, checklists and one script family on tablets | $25,000 to $50,000 | 5 to 8 weeks |
| First release: register with reconciliation, prefunctional and functional scripts offline, classified issue tracking, completion reporting | $55,000 to $130,000 | 12 to 16 weeks |
| Full platform: versioned script library, sampling rules, trend ingestion and analysis, certification packs, owner portal and handover output | $150,000 to $380,000 | 6 to 12 months |
| Library curation, new equipment families and support | Retainer | Ongoing |
Two line items are almost always missing. The first is migrating your existing script library. This is content work rather than engineering, it requires your senior commissioning people rather than the developer's, and everyone underestimates it, including us on the first pass. A hundred equipment families each carrying a decade of accumulated conditions is weeks of structured authoring, and it is the reason a project slips while the software sits finished.
The second is genuine offline capture. Mechanical rooms, shafts and roof plant have no signal, and a technician who cannot record a result where they are standing will write it on paper and transcribe it wrong that evening. Offline first has to be in the first release rather than retrofitted, and it carries real cost in conflict handling when two people record against the same equipment.
Signals of a strong partner
- They distinguish a script from a checklist in the first meeting. Ordered steps, tolerances, required evidence and a link to the specification clause, held at a version. If both are forms to them, you get a form builder.
- They ask who owns the library. A revision workflow with a named owner is what stops fifty projects quietly forking your intellectual property.
- They design sampling as a rule, not a note. Declared initial sample, threshold agreed before testing, automatic expansion, coverage stated as a fact in the report.
- They classify issues at creation. Four categories with four different owners, with the failing test step and its acceptance criterion attached so the contractor sees exactly what was expected.
- They ask about your handover obligations early. Agreeing an asset data standard with the owner's facilities team at kickoff is what stops a maintenance system handover collapsing near completion.
- They have ingested building automation trends on a live building. Naming the system and how the data was obtained is a different answer from claiming an integration.
- They put the repository and the library in your accounts. Digital Heroes hands both to the client from the first commit, which for a provider whose scripts are the firm's core asset is the entire point of building.
Red flags
- Retest treated as optional. Anything closed without a linked retest is how a punch list reaches four cycles and the schedule absorbs six weeks.
- Trend ingestion described as a simple connection. Protocols and site access differ per building. Anyone calling it simple has not done it on a live project.
- Offline as a phase two item. It cannot be retrofitted cleanly, and the moment technicians revert to paper the data quality problem you were solving returns intact.
- A single flat issue list. If deficiencies, design issues, incomplete work and operational adjustments share one queue and one owner, the software will generate disputes rather than resolve them.
- Reluctance to put library ownership in writing. Encoding a decade of scripts into a platform somebody else controls is the opposite of what you set out to achieve.
Questions to ask on the first call
- How does your model represent a functional test script differently from a prefunctional checklist?
- How does a project pin a library version while the library keeps improving between projects?
- Walk me through sampling expansion on eighty four identical terminal units when the third one fails.
- How does the equipment register reconcile design intent, submitted equipment and installed equipment?
- Which four categories does an issue fall into at creation, and who owns each?
- What happens when two technicians record results against the same equipment offline, on the same afternoon?
- Which building automation systems have you pulled trend data from, and how did you get access?
- How would our test results and equipment data reach an owner's maintenance system at handover?
- Who holds the repository, the cloud accounts and the script content, from which day?
A simple way to decide
Do not pick from proposals. Buy a paid discovery phase from your two best candidates and require the same deliverable from each: a written specification covering the equipment register model, the script structure with two of your real scripts converted as worked examples, the sampling rules, the issue taxonomy with routing, the offline and sync design, the trend ingestion approach for one named building, the handover data standard, and a phased plan with a cost per phase.
Insist the specification is yours regardless of who builds. Two converted scripts will tell you more about a developer than any portfolio, because that is where the difference between a form and a test script becomes visible. Digital Heroes works PRD-first and assigns the specification and the code to the client from the first commit, contracting through India, US and UK entities so the intellectual property in your library assigns under your own law.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- 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) →
- The Standish Group 1995 CHAOS Report found only 16.2% of software projects fully succeeded; success varied sharply by size, with large-company projects succeeding about 9% of the time versus far higher rates for small projects - best treated as an industry survey, not an audited dataset. Source: Standish Group (1995) →
- This analysis cites IDC research that companies lose 20-30% of revenue annually to inefficiencies caused by data silos, Gartner's estimate that poor data quality costs organizations at least $12.9 million per year on average, and a Salesforce benchmark that 80% of IT leaders say data silos hinder digital transformation - illustrating the business case for integrating systems. Source: Cherry Bekaert (citing IDC, Gartner, Salesforce, DATAVERSITY) (2024) →
- The median annual wage for U.S. software developers was $133,080 in May 2024, and employment is projected to grow 15% from 2024 to 2034 - a core input to any in-house build-vs-buy TCO model. Source: U.S. Bureau of Labor Statistics (2024) →
Frequently asked questions
How much does custom commissioning software cost to have built?
A single project pilot covering the register, checklists and one script family runs $25,000 to $50,000 over five to eight weeks. A first release adding register reconciliation, offline functional scripts, classified issue tracking and completion reporting runs $55,000 to $130,000 across twelve to sixteen weeks. A full platform with a versioned script library, sampling rules, trend ingestion, certification packs and handover output runs $150,000 to $380,000 over six to twelve months.
Is CxAlloy good enough, or should we hire a developer?
CxAlloy and Facility Grid are purpose built and the right answer for a small practice running a handful of projects with one or two agents. Building starts to make sense when your script library is genuinely differentiated and you want it versioned rather than copied into each project as Word files, when quality depends on which agent is assigned, or when you commission healthcare, laboratory or data centre work where sampling has to be defensible.
What is the hardest part of the project to schedule?
Migrating the existing script library. It is content work rather than engineering, it consumes your senior commissioning people rather than the developer's team, and a hundred equipment families each carrying a decade of accumulated conditions is weeks of structured authoring. Projects routinely slip here while the software sits finished. Budget it explicitly, assign a library owner, and start converting scripts before the build reaches its final phase.
Why do commissioning issue logs turn adversarial with contractors?
Because everything lands in one list. A deficiency against the contract documents, a design issue that needs the engineer, an incomplete installation that is simply not ready, and an operational adjustment have different owners and different resolution paths. Classify at creation, attach the failing test step and its acceptance criterion so the contractor sees exactly what was expected, and require a linked retest before anything can be closed.
Who owns the script library if an agency builds the platform?
You should own the repository, the cloud accounts and the script content itself, agreed in writing before kickoff. This matters more for commissioning providers than for most buyers, because the library encoded into the system is your firm's core intellectual property and the reason you are building rather than buying. Digital Heroes assigns code and content to the client from the first commit, with contracting entities in India, the US and the UK.
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.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
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.
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.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
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 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 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.
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.
Can a solo freelancer build project management software, or do I need an agency?
A strong freelancer can deliver a single-team internal tracker in the $15,000 to $25,000 range. Once you need role-based permissions, real-time updates, several integrations, and someone on call after launch, you need a 4 to 5 person team, because those features cross design, backend, and QA at once. The bigger freelancer risk is continuity: one person on vacation becomes an outage in your delivery pipeline.
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.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
Can a custom project management tool double as a client portal?
Yes, and this is one of the strongest reasons to build. Guest access is where Asana, Monday, and ClickUp frustrate agencies: permissions are coarse, client editing rights can require paid seats, and the whole experience carries the vendor's branding. A custom portal shows each client only their projects, under your brand, with approval buttons wired to your real workflow, and unlimited client logins cost you nothing per seat.
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 Eleanor.
VP Client Services · UK & EU · London · 1 post on the site
Published · Last updated .
