Facility Condition Assessment Software: Build or Buy at Your Portfolio Size
The line is roughly 3 million square feet, and it only counts if somebody interrogates your methodology.
On this page
The line is roughly 3 million square feet, and it only counts if somebody interrogates your methodology. Under about a million square feet with a stable estate, one funding source and no obligation beyond an annual number, commission a Gordian assessment on a cycle or buy Brightly Predictor and put the money into a roof. Above 3 million square feet, where you must reconcile the backlog against completed work in front of a board or a legislature, a first release runs $65,000 to $140,000 in 12 to 18 weeks. The deciding cost is almost never the survey fee. It is the decisions made from stale data in the four years between surveys.
When is off the shelf genuinely the right call here?
If you steward under roughly a million square feet with a stable estate, a single funding source and no reporting obligation beyond an annual figure, do not build. Commissioning a Gordian assessment on a cycle is a perfectly defensible way to run a small portfolio, and Gordian in particular brings a serious commercial cost library behind it, which is a genuine advantage you would otherwise have to accumulate from your own bid history over several years.
Brightly Predictor is a reasonable fit at that scale if you want a platform rather than a service, and Accruent VFA is the sensible purchase when your estate maps cleanly onto a standard building system hierarchy and your reporting need is an index rather than a reconciliation. If your buildings are buildings, your systems are ordinary and nobody is going to interrogate the methodology, a product is the cheaper answer and custom software would be an expensive way to hold 26,000 spreadsheet rows.
Buy also if you have never held a complete space and asset inventory. A condition platform sitting on an unknown estate produces a confident number about buildings you have not counted, and that is worse than a consultant deliverable because it looks like a system.
The test for buying is whether anyone downstream asks how you got the number. If the board accepts an index and moves on, buy. The build case appears when a trustee asks why the backlog rose despite thirty million dollars of spend, and only then.
When does a custom build actually pay off?
The thing worth building is the shift from finding to asset. Consultant deliverables arrive as documents plus a spreadsheet in the consultant's own schema, and the line items rarely carry a stable identifier, so matching this cycle's findings against the last cycle is a manual exercise. That means you cannot answer the most important question about your estate: what did we fix, what got worse, and what did we predict wrongly.
Make the component the permanent record and every assessment produces observations against it. Now a chiller has a history: installed 2004, assessed fair in 2019, assessed poor in 2024, repaired twice between, replaced in 2026. The Facility Condition Index is derived from that history rather than restated from scratch every five years, and the backlog updates as work completes rather than ageing quietly.
In Digital Heroes delivery experience a first release covering the asset register with component identity that survives cycles, condition and remaining life, the backlog and index engine with escalation, and a capital renewal forecast you can run scenarios against in a meeting runs $65,000 to $140,000 over 12 to 18 weeks. A full platform adding an offline capable field inspection app, two way reconciliation with your maintenance system, project bundling, funding source eligibility and board reporting runs $160,000 to $400,000 across 7 to 12 months.
Build when two or more hold: your asset classes do not exist in a product hierarchy, you must reconcile backlog against completed work publicly, you hold multiple funding sources with different restrictions, or your renewal decisions have already started diverging from the assessment because everyone knows it is out of date.
How do they compare on the things that matter in this industry?
On cost data, the products win. Gordian's commercial unit cost library is a real asset and reproducing it from your own bid history takes years. If your objection to buying is cost data, you have the argument backwards.
On hierarchy, the constraint is configuration rather than quality. Uniformat II gives a sensible classification of building systems and any credible build should map to it for external reporting and grant applications. The friction appears when your asset classes are not in the tree, so assessors put them in Other, and three years later Other is a meaningful share of your backlog and unusable for planning. Health systems with central utility plants, medical gas and a linear accelerator vault, research campuses, ports and transit agencies all hit this. So do the awkward things no product models: leased space you maintain but do not own, historic structures with restricted intervention, and steam tunnels and campus distribution that sit inside no single building.
On service life, published tables are a reasonable and defensible starting point and both routes use them. The difference is whether you can adjust per asset with a recorded reason and then compare actual replacement ages against assumed life by asset class and exposure once you have a few years of your own history. That comparison is the most persuasive evidence available in a funding hearing, and no purchased table can tell you that your 1970s residence hall roofs last 22 years and your 1990s academic roofs last 31.
On reconciliation, this is the structural gap. Products describe a moment. Your operation moves every day, and without a link from work orders and capital projects back to the components they touched, nobody can produce the bridge from opening backlog to closing backlog. That question decides funding requests, and answering it in a fortnight reads as evasion regardless of the facts.
On scenarios, a plan that cannot bundle forty roof line items into one procurement produces a list nobody can execute.
What does total cost of ownership look like at your scale?
Take a health system with 210 buildings and roughly 6.2 million square feet, two legacy consultant assessments from different firms, and Maximo in place for work management.
The first release prices at about $122,000 over 16 weeks: discovery and asset hierarchy design mapped to Uniformat II with local asset classes carried underneath $16,000, the asset register with building, system and component identity that persists across cycles plus condition capture $29,000, the backlog and index engine with escalation and service life modelling $34,000, the capital renewal forecast with four funding scenarios $24,000, and migration of two legacy assessments into one comparable history $19,000.
Phase two over the following nine months adds the offline field inspection app at $41,000, two way reconciliation with Maximo including renewal classification rules at $38,000, the backlog bridge report at $18,000, project bundling and procurement handoff at $26,000, funding source eligibility with a plan per source at $22,000, and board and portfolio reporting at $20,000. That is $165,000, taking the platform to $287,000 all in.
Running costs are 15 to 20 per cent of build cost a year, roughly $43,000 to $57,000. Hosting is the smallest part. The largest is data stewardship: someone owns the asset register, approves new asset classes, clears reconciliation exceptions where a work order could not be matched to a component, and keeps escalation assumptions current. At a large estate that is a meaningful fraction of an analyst role and it should appear in your budget with a name on it. Add integration drift when Maximo, AiM, TMA or Archibus is upgraded, any commercial cost library subscription you keep, and the physical surveys you will still commission, just less often and more targeted.
What does the hybrid look like, and when is it the honest answer?
Buy the platform, build the thin layer you actually need. For most large estates this is the sensible architecture rather than a compromise, because the two halves have different lifespans.
Concretely: keep commissioning assessments, and keep a licensed cost library if you have one. Those are services and content, and reproducing them is waste. Build the asset spine and the reconciliation layer, meaning component identity that survives cycles, a link from work orders and capital projects back to the components they touched, and the bridge report that goes opening backlog, plus escalation, plus new findings, minus completed renewals, minus reclassifications, equals closing backlog.
That layer is a fraction of a full platform and it converts every future consultant deliverable from a document into an update. Each survey then writes observations against components you already hold rather than producing a fresh spreadsheet nobody can match to the last one.
Two sequencing rules. Prove the model against a known answer before you extend it: run the new engine against last year's board number and explain every difference, because a difference you cannot explain is a finding rather than a defect and it is far better discovered privately. And take the field app in phase two. Assessors can work from a tablet form in the first release while you learn what they actually record, and building the offline app afterwards produces a better app for the same money.
Which should you choose, by operator size and stage?
Under a million square feet, stable estate, one funding source: buy. A Gordian assessment on a cycle, or Brightly Predictor if you want a platform. Spend the difference on the deficiency at the top of your list.
One to three million square feet with a standard hierarchy and a board that accepts an index: buy Accruent VFA and spend the year cleaning your space and asset inventory instead. That work makes a later build cheaper and improves the purchased platform immediately, which is a rare combination.
Three to six million square feet where reconciliation is a recurring public requirement: build the asset spine and reconciliation layer beside your existing assessment programme, starting with your top fifty buildings by replacement value and your three highest risk systems, typically roofing, primary heating and cooling plant, and electrical distribution. Use your own bid history as the cost basis in phase one and add a licensed library later once you know what the model is doing.
A health system, research campus, port or transit agency with unusual asset classes, several funding sources and multiple legacy assessments: expect the full $160,000 to $400,000 programme. Hold the migration budget separately, because consolidating deliverables from different consultants into one comparable history is the item most often underestimated in the whole project. And settle ownership of the code, the cloud accounts and the asset database in writing before kickoff, since a multi decade asset history outlives any vendor relationship.
When you are ready to turn this into a specification, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. 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 right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
- SaaS spend averaged $4,830 per employee (up 21.9% year over year), with large enterprises (10,000+ employees) spending roughly $284M annually and running about 660 apps, while organizations wasted an average of $21M annually on unused licenses. Source: Zylo (2025) →
- Per the Standish Group CHAOS 2020 report (reviewed at this URL), across tens of thousands of software projects roughly 31% end successfully, about 50% are 'challenged', and roughly 19% fail outright; small projects succeed far more often than large ones, and Agile approaches succeed at markedly higher rates than Waterfall. Source: The Standish Group (2020) →
- Only about 30% of digital transformations succeed at meeting their objectives, but getting six critical success factors in place (leadership commitment, talent, agile culture, progress monitoring, clear strategy, and a modernized platform) raises the odds of success from 30% to 80%. Source: Boston Consulting Group (BCG) (2020) →
Frequently asked questions
What does it cost to move off a condition platform later?
Ask what structured export you get of components, observations, deficiencies and cost assumptions, and test it during implementation rather than at renewal. If the platform can only produce reports rather than data, you will be recreating the register when you leave.
The larger switching cost is comparability. Any move that breaks the identity linking this cycle's findings to the last one costs you the trend, which is the whole reason the register exists. Protect component identity above everything else in a migration.
What happens if our assessment provider changes its pricing?
Assessment is a service, so the cost is per cycle and it scales with square footage and depth. That is worth modelling against the estate you expect in five years, including any campus you are about to absorb.
The protection is owning the asset register. An institution whose components, histories and escalation assumptions sit in its own system can change consultants between cycles without losing the trend, and can commission targeted surveys on the buildings that have drifted furthest rather than repeating the whole estate.
How long until we can present from a new system?
Twelve to eighteen weeks to a first release, then allow a few weeks to prove the model against your last board number and explain every difference before you present from it.
Data migration is the schedule risk rather than engineering. Consolidating assessments from different consultants into one comparable history takes real effort because the line items usually carry no stable identifier, and that work runs in parallel with the build rather than after it.
Is building cheaper than commissioning Gordian on a cycle?
Not on the survey fee alone, and if that is the only cost you carry then buying is the right answer. Gordian brings a strong commercial cost library and a defensible methodology, and for a stable estate under about a million square feet that is difficult to beat.
The build case turns on the four years between surveys: emergency replacements funded at a premium because an asset failed ahead of the list, high priority items funded for assets that were quietly still fine, and analyst weeks spent assembling board decks from exports.
How much does integrating with Maximo or Archibus add?
Reading work order history sits at the low end and is often inside a first release. Writing renewal completions back so the backlog reconciles adds roughly $25,000 to $45,000, and it was $38,000 in the worked example above.
Most of that is not the interface. It is defining and testing the rules that decide which work counts as renewal against routine maintenance, which is a policy decision your organisation has to make explicitly rather than delegate to a developer.
Can we reduce the first release and still get value?
Yes, and it is the standard advice. Start with your top fifty buildings by replacement value and your three highest risk systems, typically roofing, primary heating and cooling plant, and electrical distribution. That covers most of the money at risk and teaches the model before you scale it.
Use your own historical bid data as the cost basis initially, and bring history across at annual summary level per building rather than reconstructing every line item from three consultants working to three schemas.
What does the offline field inspection app cost?
Typically $35,000 to $45,000, and it was $41,000 in the worked example. The cost sits in local storage with photographs, conflict resolution when two assessors touch the same component, and a capture flow fast enough that assessors prefer it to paper.
Take it in phase two. Assessors can work from a tablet form in the first release while you learn what they actually record, and building the app afterwards produces a better result for the same money.
Why does the number rise when we have several funding sources?
Because a single prioritised list stops being executable. Bond proceeds, state appropriations, grant funds, auxiliary reserves and department budgets each restrict what they may fund, so the model needs eligibility rules attached to sources, a plan generated per source, and a view of what remains unfunded across all of them.
That module ran $22,000 in the worked example. Most public institutions need it, and skipping it produces plans that look complete and cannot be actioned.
Is a custom ERP cheaper than NetSuite over five years?
Often yes once you pass roughly 20 to 30 users. NetSuite is commonly quoted at $999 per month for the base platform plus about $99 per user per month, so a 30-user company spends over $200,000 on licenses across five years before paying for implementation. A custom build in the $120,000 to $250,000 range is a one-time cost, and in Digital Heroes projects annual upkeep runs 15 to 20 percent of build cost with no per-seat fees as you hire.
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.
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.
Can a custom ERP meet compliance requirements like SOC 2 or GDPR?
Yes, and often more cleanly than a shared SaaS platform because you control exactly where data lives and who touches it. The build includes role-based access control, full audit logs, encryption at rest and in transit, and data residency in whatever region your regulator requires. If you need SOC 2 attestation, tell the agency before development starts, since audit logging is far cheaper to design in than to bolt on.
Can a freelancer build an ERP, or do I need an agency?
An ERP is too wide for one person: it needs backend, frontend, database design, integrations, QA, and someone mapping your business processes. A solo freelancer can extend an existing ERP or ship one small internal tool, but full ERP builds by single developers are the most common rescue scenario Digital Heroes takes on. If budget is tight, shrink the scope to one module rather than shrinking the team below three or four people.
How do I vet an agency for an ERP project?
Ask to speak with two clients who have been running an ERP the agency built for at least two years, because ERP quality shows up in year two, not at launch. Then ask for their data migration plan, their module rollout sequence, and the named senior engineers who will be on your project. An agency that leads with screen designs instead of process mapping is a red flag for ERP work.
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.
Who owns the source code if an agency builds my ERP?
You should, in full, and it must be written into the contract as work for hire with IP assignment on payment. At Digital Heroes every client receives the complete repository, database schemas, and deployment documentation, so they could hand the system to another team tomorrow. Walk away from any ERP proposal built on the agency's proprietary platform with ongoing license fees, because that recreates the vendor lock-in you were escaping.
Who can build a custom ERP software system?
Digital Heroes builds custom ERP 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 ERP 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 .
