How to Hire a Building Analytics and Fault Detection Development Company
Choose the firm that can tell you how it would normalise forty thousand control points across four automation vendors, not the one with the best dashboard. Judge on tagging method, false positive control and whether faults reach your maintenance queue.
On this page
Choose the firm that can tell you how it would normalise forty thousand control points across four automation vendors, not the one with the best dashboard. Judge on tagging method, false positive control and whether faults reach your maintenance queue. Expect $95,000 to $200,000 for a first release covering ingestion, normalisation, a tuned rule engine and a triaged fault queue.
You can walk a building and see whether the paint is good. You cannot walk a building and see whether its forty thousand control points mean what their names claim to mean. That is the whole risk in this purchase. The demo you sit through will show clean equipment graphics, a ranked fault list and a savings figure. What it will not show is the six weeks of work that made those graphics possible in one building, and whether that work multiplies or collapses when applied to the twenty three other sites your estate picked up through acquisition.
The category is hard to buy because the value and the effort sit in different places. Buyers evaluate rule libraries, because rules are visible and countable. Practitioners know the rules are the easy part, and that the project succeeds or fails on whether an air handler in a 1998 building can be described in the same terms as an air handler in a 2021 building. A vendor selling you rule count is selling the part you were going to get anyway.
What a building analytics development company actually does
The visible build is a queue, a chart and an equipment page. Around it sit three larger pieces of work.
First, ingestion per protocol and per vendor, including sites with no trend history at all, where a collection layer has to run for weeks before any analysis is possible. Second, normalisation and tagging: mapping every point to a meaning and every piece of equipment to the things it serves, using a shared vocabulary such as Project Haystack or Brick Schema rather than a naming convention invented for your project. Done properly this is semi automated. Name pattern clustering carries most of the load, because each commissioning contractor was internally consistent even where they disagreed with every other contractor, and a person confirms in bulk rather than point by point.
Third, and least discussed, the tuning loop. A generic economiser rule assumes an economiser strategy your plant may not run. A simultaneous heating and cooling rule assumes a reheat configuration. An engineer who investigates three findings that turn out to be design intent stops opening the tool, permanently, and no dashboard quality recovers that. So the build includes suppression windows, per site parameters and a path for an engineer to mark design intent and have the rule adjust. Twenty rules that are right beat two hundred that are noisy.
What it really costs in 2026
These bands come from Digital Heroes delivery experience across 2,000-plus projects, not from a market study.
| Project tier | Cost | Timeline |
|---|---|---|
| Proving phase on 10 to 15 representative buildings, one or two automation vendors | $40,000 to $85,000 | 6 to 10 weeks |
| First release: ingestion, normalisation and tagging, rule engine, triaged fault queue | $95,000 to $200,000 | 14 to 22 weeks |
| Full platform: cost attribution, utility reconciliation, work order integration with fix verification, portfolio reporting | $240,000 to $650,000 | 9 to 16 months |
| Site onboarding and rule maintenance after launch | Per site fee plus retainer | Ongoing |
Two line items are routinely absent from quotes. The first is point normalisation labour for the estate you actually own rather than the one you describe. Cost here scales with the number of naming conventions, not the number of buildings, so a portfolio assembled through acquisition can carry six conventions across thirty sites and cost more to tag than a hundred buildings on one standard.
The second is site network access and IT security review. Getting a collector onto an operational technology network in a corporate or institutional estate involves your IT security team, your controls contractor and sometimes a landlord, and in our experience it is more often the critical path than the software is. Ask for it as a scheduled item with an owner, because a vendor who prices it at zero has quietly made it your problem.
Signals of a strong partner
- They ask for your worst building, not your best. Anyone can connect to a modern supervisory layer. The estate value is decided by the site with serial controllers behind a gateway.
- They name a tagging standard unprompted. Haystack or Brick, with versioned mappings, means a controls upgrade that renames half a building becomes a difference to review rather than a crisis.
- They describe clustering plus bulk confirmation. Manual point by point tagging is how a project stalls at building six, and firms who have done this at scale say so without being asked.
- They talk about false positives before rule count. Suppression, per site tuning and a design intent feedback path are the difference between an adopted tool and an abandoned one.
- They insist on cost estimates with visible assumptions. A finance director will challenge any savings figure, and an estimate that shows its counterfactual and its tariff survives that conversation.
- They plan for verification after the work order closes. A scheduled re-check that reopens a fault when behaviour returns is what converts a sceptical engineering team.
- They hand you the repository and the equipment model. At Digital Heroes the client owns both from the first commit, which matters because a tuned rule set built over years is a genuine portfolio asset.
Red flags
- Automatic tagging claimed as a feature. Nobody has automated this on a real estate that grew by acquisition. A firm claiming otherwise has demonstrated on one clean building.
- The pitch is the size of the rule library. Volume is not precision, and in this category precision is what decides whether the tool is still open in month four.
- A savings number with no stated method. Estimated avoided cost and measured savings are different claims with different confidence. Conflating them is how these programmes lose credibility with finance.
- No mention of data gaps. A rule that computes runtime across a period with missing trend data returns a plausible wrong answer, and plausible wrong answers destroy trust faster than any outage.
- Network access treated as a formality. If they have not asked who owns the controls network at each site, they have not deployed into a corporate estate before.
Questions to ask on the first call
- How would you normalise forty thousand points across four automation vendors, step by step, with a human in the loop?
- Which controller generations have you actually read from, including serial trunks and gateways?
- How does an engineer tell your system that a fault is design intent, and what happens to the rule afterwards?
- Show me how you would estimate what a stuck economiser damper is costing us, and what assumptions you would print alongside it.
- How do you reconcile fault level cost estimates against the metered and billed consumption for that building?
- What happens to a fault after the work order closes, and how would we learn that a fix did not hold?
- How do you handle a site that has no trend history, only live values?
- Who owns the tagged equipment model, and in what format could we export it tomorrow?
A simple way to decide
Buy a paid discovery phase before you buy a platform. Give two candidates the same brief and the same three buildings, chosen to include your most awkward site, and require the same deliverable: a written specification listing the protocols and controller generations found, the tagging approach with a sample of the mapped model, the rule set proposed with its tuning parameters, the cost attribution method, the network access dependencies with named owners, and a phased plan with a cost per phase.
Insist that specification is yours whatever you decide next. That document is portable, it can be quoted against by anyone, and it converts a purchase decision made on a demo into one made on evidence from your own estate. Digital Heroes works PRD-first for this reason, and clients keep the written specification along with the code, verifiable through the usual public channels including D-U-N-S, Clutch and Trustpilot before you commit a budget.
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.
- The performance gap between digital and AI leaders and laggards is widening: McKinsey reports leaders pull ahead on shareholder returns, and the average maturity spread between top and bottom performers jumped ~60% (from 10 points in 2016-19 to 16 points in 2020-22), reinforcing that the returns to transformation concentrate among top performers. Source: McKinsey & Company (2023) →
- A later Nucleus Research review of analytics software ROI case studies found customers received $9.01 in benefits for every dollar spent on analytics technology, showing returns vary with deployment factors but remain strongly positive. Source: Nucleus Research (2019) →
- The share of tasks performed mainly by humans is projected to fall from 47% to 33% by 2030 as human-machine collaboration expands, with 170 million jobs created and 92 million displaced (a net gain of 78 million). Source: World Economic Forum (2025) →
- In an RCT, text-message reminders (11.7% missed) were non-inferior to telephone reminders (10.2% missed; difference not significant, within the 2% non-inferiority margin) but far cheaper - total cost EUR 230 for SMS versus EUR 8,910 for telephone over 6 months - making SMS more cost-effective. Source: BMC Health Services Research / PubMed Central (Junod Perron et al.) (2013) →
Frequently asked questions
How much does it cost to hire a building analytics development company?
A proving phase on ten to fifteen representative buildings runs $40,000 to $85,000 over six to ten weeks. A first release covering ingestion from two automation vendors, point normalisation and tagging, a tuned rule engine and a triaged fault queue runs $95,000 to $200,000 across fourteen to twenty two weeks. A full platform adding cost attribution, utility reconciliation, work order integration and portfolio reporting runs $240,000 to $650,000 over nine to sixteen months.
Why does point normalisation dominate the budget?
Because no rule can run until the software knows that a given controller point is the discharge air temperature of a specific air handler serving specific terminal units. Buildings name points inconsistently, since each was commissioned by a different contractor in a different year, and units and trend intervals vary too. Cost scales with the number of naming conventions rather than the number of buildings, which is why acquired estates are expensive to onboard.
Should we buy SkySpark or hire someone to build?
For a modest estate on one mainstream automation vendor with no unusual plant, buy. SkySpark has a capable analytics engine, and Clockworks pairs detection with an analyst service if you want findings rather than a system to run. Building becomes the better call when per point licensing gets untenable at your scale, when controllers in part of your estate have no clean connector, or when faults need to join systems those products do not reach.
How do we stop the tool being abandoned after month two?
Control false positives from the start and make findings actionable. Generic rule libraries assume sequences your plant may not run, and an engineer who investigates three findings that turn out to be design intent will stop opening the tool for good. Insist on per site tuning, suppression windows, a feedback path where design intent adjusts the rule, and a ranked queue with estimated cost rather than an unranked list of everything detected.
Who owns the equipment model if an agency builds this?
You should own the repository, the cloud accounts, the tagged equipment model and the right to appoint another firm, agreed in writing before kickoff. This matters more here than in most categories because the model and the tuned rule set represent years of encoded engineering knowledge about your specific buildings. Digital Heroes assigns all of it to the client from the first commit rather than holding it inside a licence.
How much does a custom BI dashboard cost for a small business?
For a small business, a focused first dashboard typically runs $25,000 to $60,000 when it covers 2 or 3 data sources, daily refresh, and 5 to 7 core metrics. Across 2,000+ Digital Heroes projects, budgets climb past that only when real-time data, complex permissions, or customer-facing access enters the scope. If a quote for a simple internal dashboard exceeds $75,000, ask exactly which of those three is pushing it there.
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.
Why do agencies charge for a discovery phase instead of quoting for free?
Because an accurate quote requires real work: mapping your workflows, finding the edge cases, and writing a specification, which typically takes 1 to 3 weeks and costs $2,000 to $10,000 at Digital Heroes depending on system complexity. You leave discovery owning a written spec and a fixed price you can take to any vendor, so the money is not locked into one agency. Free estimates are guesses, and the guess usually becomes your budget overrun six months later.
How do I make sure each client sees only their own data in a shared dashboard?
That is row-level security, and it must be enforced in the database or API layer, never by hiding filters in the interface. Each query carries the logged-in client's identity, and the data layer refuses to return rows outside their account, so a crafted URL or modified request cannot leak another client's numbers. Make any vendor show you exactly where that filter lives, because interface-level filtering is the most common security mistake we find when auditing dashboards built elsewhere.
When does Looker make more sense than a custom dashboard?
Looker earns its place when multiple teams keep producing conflicting numbers and you need one governed definition of every metric, because LookML enforces definitions centrally. Its pricing is quote-based, and the quotes clients bring to Digital Heroes typically start in the tens of thousands of dollars per year. Under roughly 50 users with straightforward reporting needs, that spend is hard to justify against Power BI or a scoped custom build.
How do I vet an agency or developer for a BI dashboard project?
Ask them to walk you through the data model of a past project, not a portfolio of pretty charts, because dashboard failures are almost always data modeling failures. Good answers mention specifics like star schemas, dbt, incremental refresh, and how they handled a source schema change after launch. Then ask for a fixed-scope discovery phase with a written data audit as the deliverable, so you judge their real work for a small spend before committing to the build.
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.
Will a custom dashboard stay fast once our data hits millions of rows?
Yes, if it aggregates before it displays; no dashboard should scan millions of raw rows on every page load. The standard techniques are pre-aggregated summary tables, incremental refresh, and caching, which keep typical page loads under 2 seconds even on datasets in the hundreds of millions of rows. Ask your vendor how the dashboard behaves at 10 times your current data volume; a good one gives a specific answer about aggregation, not just a bigger server.
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 owns the code, data models, and pipelines when an agency builds my dashboard?
You should own all of it, and the contract should say so explicitly: source code, data models, pipeline configurations, and infrastructure accounts in your name, with IP transferring on final payment. The trap to avoid is an agency hosting your dashboard on their proprietary platform, which quietly turns a custom build back into vendor lock-in. Digital Heroes delivers into the client's own cloud accounts and repositories by default, and any agency should agree to the same in writing.
Why do BI dashboard quotes range from $25k to $200k for what sounds like the same project?
Four variables move the price: how many data sources you connect and how messy they are, real-time versus daily refresh, permission complexity, and whether outside customers will log in. A three-source internal dashboard with daily refresh sits near the bottom of that range, while a customer-facing product with row-level security and live data sits near the top. Wildly different quotes are usually pricing different assumptions about those four things, so pin them down in writing before comparing.
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.
How many people does it take to build a custom BI dashboard?
A typical build runs with 3 or 4 people: a data engineer for pipelines and modeling, a full-stack developer for the application and charts, a part-time designer, and a project lead. One strong freelancer can handle a single-source internal dashboard, but in our experience solo builds stall once multiple integrations, permissions, and customer access are added. Team size matters less than having one person explicitly own the data model.
Do I need a data warehouse before building a custom dashboard?
Not for a small build; a dashboard reading from 1 or 2 sources can query them directly or use a plain Postgres database as its store. You want a real warehouse like BigQuery or Snowflake once you are joining 3 or more sources, keeping history beyond what source systems retain, or serving many concurrent users. Adding the warehouse costs around 2 to 4 extra weeks and is usually the single best investment in the project's future.
Who can build a custom business intelligence dashboards system?
Digital Heroes builds custom business intelligence dashboards 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 business intelligence dashboards 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 Ezra.
Senior Brand Designer · APAC · Sydney · 1 post on the site
Published · Last updated .
