Construction Handover and Asset Data Software: Buy Zutec, or Build the Validation Rules Engine?
Count your owners, not your projects.
On this page
Count your owners, not your projects. If you hand over to one or two clients a year, or to owners who never issue a structured asset information requirement, buy Zutec or Operance and stop there: a validation engine that enforces rules nobody has written is expensive theatre. The threshold is three or more owners whose requirements genuinely conflict, with at least one package already rejected and retention held over it. At that point the rules engine is your commercial position and it should not sit in someone else's account. A first release runs $50,000 to $110,000 over 10 to 16 weeks, and a multi owner platform typically lands near $168,000 over about seven months.
When is off the shelf genuinely the right call here?
Buy if you deliver one or two projects a year, if the same owner takes all of your work, or if your owners do not issue a structured asset information requirement. Operance is well pitched at the residential and golden thread end and costs a fraction of any build. Zutec is the sensible purchase for structured handover at scale. Bentley AssetWise is aimed squarely at large asset owners rather than contractors, which matters mainly when your client is the one specifying the tool you must submit into.
Buy if your real problem is that serial numbers are never captured on site. That is a process failure, and software will make it visible without fixing it. An asset installed in month four carried its serial on a label that somebody photographed, or did not. No platform recovers a photograph that was never taken. Fix the site routine, run it inside a product for two seasons, and revisit this page after that.
Buy while nobody internally owns handover data. A build needs a digital delivery lead with authority to author validation rules and argue with an owner about what counts as a maintainable asset. Without that person, you get a well engineered system with nothing enforced through it.
The test: take the asset information requirement from your next three clients and lay them side by side. If the differences are naming and a handful of attributes, configuration will hold.
When does a custom build actually pay off?
Start with the money already sitting still. Retention on a rejected package, priced at your cost of capital for the months it stayed unpaid, is a real number your commercial team can produce this week. So is the weeks of a digital delivery lead's time spent reconciling asset tags at the end of the last two jobs. Those two figures usually do more to settle the argument than any demonstration.
Then add the number almost nobody totals. Defect costs during the liability period that belonged to a subcontractor and were absorbed because nobody could find the warranty inside a 900 page operation and maintenance manual. That spend is spread across job cost codes and has never been added up, and when it is, it is often the largest line in the case.
Beyond the arithmetic, three structural signals matter. The first is conditional validation. Owners write rules like nineteen mandatory attributes on mechanical plant and four on everything else, or a warranty start date that must fall inside the construction period. Configuration screens express lists and required fields. They do not express conditions, so the condition ends up as a note somebody checks by hand.
The second is owner variety. Each additional owner is a classification set, a tag pattern, an attribute matrix by asset type, a document naming convention and a target import format. Four owners means four of each held at once, in both the validation layer and the export layer.
The third is submission reality. Your data holders are subcontractor site managers with a spreadsheet, a camera roll and an email account, and a system that asks them to complete a form per asset will be ignored.
How do they compare on the things that matter in this industry?
Every product in this category will demonstrate an asset register and a document library. These are the places they differ, and a digital delivery lead can check each one during a trial.
- Who authors the validation rules. Ask whether your own team can write and version a rule without a release from the vendor, and whether rules can differ per project and per owner. If rules are fixed by the product, every new client becomes a support ticket on someone else's queue.
- Conditional logic depth. Take your most awkward owner rule to the demonstration and ask for it to be configured live. Attribute matrices that vary by asset type are where configurable templates reach their ceiling.
- The import dry run. The real acceptance test is not a valid Construction Operations Building information exchange file, it is whether the package loads into the owner's computerised maintenance management system. Ask whether the tool can generate the owner's import file and prove it against a copy of their structure before handover, since Maximo, Planon and Archibus each expect a different hierarchy of location, system and asset.
- Subcontractor submission path. Ask to see a spreadsheet in a subcontractor's own column order accepted and mapped, plus a folder of certificates and data plate photographs ingested. Adoption is the whole return here, and adoption follows the path of least resistance.
- Warranty at asset level. Ask whether warranty start, duration, warrantor, conditions and claim process live on the asset record, and whether a defect in the liability period routes to the responsible subcontractor. This is the feature that pays the contractor rather than the owner, which is why products aimed at owners tend to be thin on it.
- Provenance and versioning. On higher risk buildings the Building Safety Act 2022 duty to hold accurate, current and accessible information and hand it to the accountable person raises the bar on who submitted what and when. Ask what the evidence trail looks like, not whether the box is ticked.
- Data portability. You retain these records for years. Ask what leaves with you, documents included rather than just the register.
What does total cost of ownership look like at your scale?
From Digital Heroes delivery experience the bands track data variety rather than contract value. A contractor turning over one large hospital and a contractor turning over four modest schools can land in the same band.
A first release runs $50,000 to $110,000 over 10 to 16 weeks: the asset register modelled against one owner's requirements, subcontractor submission by spreadsheet upload with column mapping and document attachment, the validation rules engine, and one export mapping with a dry run against a copy of the target structure. A fuller platform adding warranty and defect tracking, several owner profiles, maintenance regime authoring and an owner portal runs $130,000 to $220,000 over 6 to 8 months. Model federation, direct write into the owner's maintenance system and full golden thread evidence scope take it to $220,000 to $300,000 over 8 to 10 months.
A representative multi owner build lands around $168,000 across roughly seven months, with three owner profiles, warranty tracking and a portal, and deliberately no model linkage or direct write. Additional owner profiles beyond the first two run about $9,000 each, because the first forces the abstraction and the second breaks it, after which profiles become configuration rather than code.
Anything under $50,000 buys a document library with a spreadsheet attached, which is what your folder structure already is. If a quote omits the rules engine, the quote is for something else.
Running cost is 15 to 25 percent of build cost per year, so $25,000 to $42,000 on that example. Three handover specific costs sit on top. Storage, because drawing sets, photographs and hundreds of scanned certificates per project are retained for years rather than deleted at final account. Owner profile upkeep, because owners change their requirements and their maintenance system, and each change has to happen before the next handover rather than during it. And support concentration, because this system is quiet for months and then carries your entire commercial position for three weeks.
What does the hybrid look like, and when is it the honest answer?
The hybrid worth taking seriously here is narrower than in most categories, and it is the right shape for a lot of contractors. Keep a bought platform as the document repository and the owner facing package, and build only the validation and mapping layer in front of it.
In that arrangement the build owns three things: subcontractor submission in whatever format the subcontractor already has, the rules engine that rejects a bad record in ninety seconds while the site team is still on site, and the export mapping with a dry run per owner. Everything else stays where it is. A subcontractor uploading 300 records learns that 41 fail and exactly why, in month four rather than at practical completion, and only clean data reaches the platform you bought.
That split works because validation is where handover actually dies, and validation is the part most tied to your specific clients. Repository, viewing and owner access are commodity functions that vendors do competently and cheaply.
There is a second hybrid worth naming. Build warranty and defect tracking on its own, against your asset register, even where the owner's specification never asks for it. It is not a handover deliverable, it is a contractor protection, and it is often the fastest paying part of the whole category.
The hybrid stops being honest when the bought platform cannot hold what your owners require. If you already export from it to fix records before submission, layering a third thing on top will not help.
Which should you choose, by operator size and stage?
One or two projects a year, or one repeat owner: buy Operance or Zutec. Spend the difference on a site routine that photographs every data plate at installation, because that is where your rejections actually originate.
Three or more owners, no package rejected yet: buy, and run one project deliberately as a measurement exercise. Log every reconciliation hour and every rejected record with its reason. That log is the specification if you later build, and it costs you nothing but discipline.
Three or more conflicting owners with a rejected package behind you: build the first release at $50,000 to $110,000, scoped to one live project and its real owner requirement. Resist the generic engine on day one. It should be extracted from the second and third project, because an abstraction designed before you have met two conflicting owners will be generic in the wrong dimensions.
Contractors absorbing defect costs in the liability period: build warranty tracking early regardless of where you land on the rest. It attributes cost to the party who owes it, and that is a commercial recovery rather than a reporting feature.
Anyone delivering higher risk buildings under the golden thread duty: scope provenance and versioning as their own line before design rather than after, because it touches every write path in the system rather than sitting in one module.
Whichever way you go, settle code and data ownership in writing before kickoff. Handover systems outlive the projects that funded them.
If you would rather someone argued with your brief than agreed with it, Digital Heroes starts every engagement with a signed specification covering the data model, permissions and acceptance criteria, which is what keeps a fixed price fixed. 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.
- 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) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- 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) →
- In a McKinsey global survey of 1,259 respondents, only about 20% said their organizations excel at decision making, and just 37% said their organizations' decisions were both high quality and high in velocity. Source: McKinsey & Company (2019) →
Frequently asked questions
What does it cost to move off Zutec or Operance mid programme?
The register data exports without much drama. The expensive part is documents and their links to asset records, so ask before renewal whether certificates, photographs and drawing sets leave with their asset associations intact or as a flat folder.
Time the move between projects rather than during a handover window. A migration that lands in the three weeks when the system carries your commercial position is the one situation where switching cost becomes a retention problem rather than an inconvenience.
What happens if our handover platform changes its per project pricing?
Per project or per unit fees compound quietly, because your exposure rises with the work you win rather than with any decision you make about software. Model three years against your project pipeline rather than reacting to a single renewal.
The more useful hedge is owning the validation rules and owner profiles, since those represent the accumulated knowledge of what each of your clients will accept. A repricing then becomes a decision about where documents are stored, which is a commodity question.
How long does a handover build take before we can run it on a live job?
Ten to 16 weeks to a first release you can put on a real project. Engineering is rarely the constraint. The schedule risk is agreeing what counts as a maintainable asset for each owner, which is a contractual determination rather than a technical one and needs the owner in the room.
Contractors who arrive with a written asset information requirement from their client and a current tag convention move noticeably faster than those where that knowledge lives in one person's head.
Is Zutec good enough if we deliver to three different owners?
It may be, and the way to find out is to take your three owners' requirement documents to a demonstration and ask for the most awkward rules to be configured live. Attribute matrices that vary by asset type, and conditions such as a warranty start date that must fall inside the construction period, are where configurable templates reach their ceiling.
If those rules configure cleanly, buy. If they end up as a note somebody checks by hand, you have found the boundary and you now know what a build would be for.
Do we really need model linkage in the handover system?
Almost certainly not in the first release. Asset records that reference a drawing and a location are useful, and no owner has rejected a package for lack of model linkage. It is one of the largest lines in the category and delivers none of the commercial protection.
The engineering is also harder than it looks, because models get reissued after you extracted from them and object identifiers are not always stable across a reissue. Leave it until an owner asks for it in writing.
Can we make subcontractors submit data properly during construction?
Only by accepting what they already have. Take their spreadsheet in their column order with a mapping step, take folders of certificates and data plate photographs, and do the reconciliation in software rather than demanding it from a site manager.
The lever that changes behaviour is fast rejection with a reason. Three hundred records uploaded and 41 failures explained in ninety seconds gets fixed that week. The same 41 failures found at practical completion get argued about instead.
Where does document extraction earn its cost, and where does it not?
Reading commissioning certificates and data plate photographs into structured records is the clearest win, because those documents are semi structured and arrive in volume exactly when you have no people spare. Manufacturer, model and serial off a plate, and asset reference, date and result off a certificate, are reliable reads.
Deciding which items count as maintainable assets is not an extraction job. That determination is contractual and has to be agreed with the owner in writing, whatever any tool proposes.
Should we build warranty tracking if the owner never asked for it?
Yes, and it is often the fastest paying part of this category, because it pays the contractor rather than the owner. Warranty is asset level data with a start, duration, warrantor, conditions and claim process, and once it sits on the asset record a defect during the liability period routes to the responsible subcontractor.
Without it you spend month fourteen searching a 900 page manual for a rooftop unit and frequently absorb a cost that belonged to a supplier. Total that across your last two liability periods before deciding it is optional.
What does a $50,000 custom software budget actually buy?
One core workflow done properly: 10 to 15 screens, two or three user roles, a couple of integrations, an admin panel, and automated tests, delivered in roughly 12 to 14 weeks. What it does not buy is that workflow plus a mobile app plus AI features plus five more integrations. The discipline of picking the one workflow that matters is what separates $50,000 projects that ship from $50,000 projects that stall at 70% complete.
Should we build an MVP first or go straight to the full system?
MVP first, for almost everyone: ship the single workflow that carries the business value in 10 to 16 weeks, learn from real users, then fund phase two from evidence instead of guesses. The caveat is that an MVP is a small version of a well-built system, not a badly built version of a big one; the data model must already support what comes next. An agency that cannot tell you what they deliberately left out of your MVP has not designed one.
Couldn't I just build my app in Bubble or another no-code tool instead of hiring an agency?
For validating an idea with real users, yes, and we tell clients that honestly. The walls come later: Bubble apps cannot be exported as code to run anywhere else, performance drops on complex data operations, and usage-based pricing climbs as you grow. A meaningful share of Digital Heroes custom builds are rebuilds of no-code MVPs that proved the business worked, which is the system operating as intended: validate cheap, then build the version that scales.
What should I have ready before I contact a development agency?
Three things, none of them technical: a one-page description of the problem in your own words, a list of the tools and spreadsheets the new system must replace or connect to, and a must-have versus nice-to-have split of features. Add a budget range, even a wide one, because it changes the conversation from fantasy to engineering. You do not need a formal specification; producing that is what a discovery phase is for.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
If an agency builds my software, who actually owns the code?
You should own everything, assigned in writing: the contract transfers full IP to you on final payment, the code lives in your GitHub organization, and hosting runs in cloud accounts you control. The red flag is a proposal that mentions the agency's proprietary platform or framework, which usually means you are renting, not buying. Digital Heroes structures every build this way precisely so a client can fire us and lose nothing but the relationship.
Will an app built for 10 users survive growing to 500?
Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.
Will custom software work with the tools we already use, like QuickBooks and Stripe?
Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.
Does the tech stack matter, and which one should I ask for?
It matters less than agencies imply, provided it is boring. A mainstream stack, something like React or Next.js on the front end, Node.js or Python behind it, and PostgreSQL for data, means thousands of developers can maintain your system if you ever change vendors. Apply one test: ask how hard it would be to hire a replacement developer for the proposed stack, and walk away from anything built on an agency's in-house framework.
How do I work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
Can 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.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from James.
Senior Copywriter · New-york · 14 posts on the site
Published · Last updated .
