Structural Monitoring Software: Custom Build Versus Supplier Platforms
Buy, if one supplier instruments one site. Their platform will do the job and a build is money taken from instrumentation.
On this page
Buy, if one supplier instruments one site. Their platform will do the job and a build is money taken from instrumentation. Build once three or four suppliers are installed on the same job, once trigger regimes are negotiated separately with each asset owner, or once your monitoring engineer is assembling the joined view in a spreadsheet every Tuesday.
What the off-the-shelf products actually do well
A deep basement excavation next to a Victorian terrace and eleven metres from a live rail tunnel. Prisms read by an automated total station, MEMS tiltmeters on the party walls, vibrating wire piezometers in the ground, crack gauges across existing damage, precise levelling along the track. Four suppliers. Four portals. Before deciding to replace any of that, be clear about what each one is good at.
Worldsensing and Senceive do the hard physical part genuinely well: rugged wireless nodes, battery life measured in years, gateways that survive a construction site and radio links that work in a basement. Trimble 4D Control is strong on the geodetic side, handling automated total station data with the reference stability and correction handling that is a discipline of its own. Leica GeoMoS sits in the same territory with a long track record. Maxwell GeoSystems and Vista Data Vision both offer data management that goes wider than one supplier's hardware.
Each supplier ships a platform, and each platform is competent inside its own boundary. If your project has one supplier, one instrument array and one asset owner, use theirs. A build at that scale takes money out of the instrumentation budget, and more instruments beat better dashboards every time. We say that to contractors regularly and lose the work.
Where they stop: a trigger level is not a threshold
People outside the discipline assume a trigger level is a number. In an asset protection agreement it usually is not, and that is the workflow the products model badly.
A real regime may be cumulative movement since a defined baseline, plus a separate rate of change over 24 hours, plus a different set of values for a different construction stage, plus a distinction between movement toward the asset and away from it. Different assets on the same site carry different regimes because they were negotiated with different owners at different times. Supplier platforms offer thresholds, and thresholds are a fraction of what your agreements actually say.
Baselines compound it. A baseline is established over a period before works start and may legitimately be reset after a defined event, such as a preloading stage or an instrument reinstallation. Every reset must be recorded with its justification at the time, because an asset owner reviewing the record later will ask why a baseline moved, and a satisfactory answer needs to have existed then rather than been constructed afterwards.
Then the failure mode that actually bites. On a Tuesday the monitoring engineer opens the weekly report and sees that a tiltmeter on the north party wall crossed amber the previous Thursday. Five days gone, two excavation stages dug. The conversation with the asset protection engineer is not about the reading, it is about why nobody telephoned, and the answer, that the alarm went to an email address on a supplier portal configured by an engineer who has left, is not an answer anybody accepts. There is no combined live view because assembling one is a person's job, and people work Monday to Friday while ground movement does not.
The arithmetic: per instrument per month against a build
Supplier platforms and data management products in this space are priced per instrument or per channel per month, usually bundled into the instrumentation and monitoring subcontract so nobody sees the line separately. Ask for it separately.
Suppose it is $8 an instrument a month. An array of 600 instruments across four suppliers is $57,600 a year, and on a five year programme that is $288,000, paid whether or not anyone can see the instruments together. A build at $100,000 with $20,000 a year of support is $180,000 across five years, about $36,000 a year. The crossover sits near 375 instruments held for five years, and near 190 if your quote is $16 a channel a month.
Two adjustments that matter more than the rate. High frequency instruments, such as continuous vibration or strain, are often priced differently and change the storage and query design on the build side too, so price them separately on both. And if you run several projects, the per-instrument fee repeats per project while a build amortises across the portfolio, which is why contractors with three or more concurrent jobs reach the crossover far sooner than the instrument count alone suggests.
The number neither quote contains is the one that decides it. A works stoppage after a red breach, or an asset owner losing confidence in your record, costs more in a fortnight than the software costs across the programme.
What a custom build actually costs
A first release runs $70,000 to $150,000 and ships in 12 to 18 weeks. That covers multi-supplier ingestion adapters, a normalised reading model with baselines and corrections, a configurable trigger engine handling absolute, cumulative and rate of change conditions, data quality checks with a communications watchdog, and escalation with acknowledgement.
A full platform adding construction activity correlation, automated reporting in each asset owner's expected layout, portfolio views across projects and instrument lifecycle management runs $180,000 to $450,000 over 6 to 12 months.
Data migration is 10 to 25 percent of the build, and here it is historical readings plus the baselines behind them. Bringing readings across without their correction history and baseline references produces a chart that looks right and cannot be defended, so the migration is a reconciliation exercise instrument by instrument. Where geotechnical data arrives in the AGS data transfer format, that part is cheaper, and where it arrives as four spreadsheet conventions it is not.
Year two runs 15 to 20 percent annually: a new supplier on the next contract, a changed reporting layout for a different asset owner, additional instrument types, and the trigger regime revisions that follow every stage change.
What pushes cost up: the count of supplier integrations, since each protocol, application interface and file format is real work and some suppliers cooperate more than others. Automated total station data, with its geodetic corrections and reference stability handling. Alarm delivery beyond email, particularly voice escalation with confirmed delivery. And the number of asset owners with their own report formats, several of whom still want a signed document.
The four situations where building wins
Regulatory and contractual fit. Trigger levels exist because a third party agreed to let you excavate next to their asset on conditions. Breaching amber means an agreed response under a trigger action response plan. Breaching red usually means works stop and somebody senior explains themselves. Where the observational method under Eurocode 7 is being applied, the monitoring record is the mechanism by which the design is confirmed, not a report about it. A build makes the agreement executable rather than filed.
Scale economics. Past roughly 375 instruments on a five year programme, or sooner across a portfolio of concurrent projects, the arithmetic has turned.
A workflow that is your advantage. Correlating your own works with the monitoring record is the example, and no supplier will ever build it. Excavation stage changes, pile installation, dewatering rates, prop installation and removal, and significant plant movements, timestamped against the instrument traces. An engineer who can say the step change on tiltmeter 14 coincides exactly with prop removal at grid line C, and that the response settled inside the predicted envelope, is having a different conversation with the asset owner than one presenting a graph with no context.
Integration sprawl across three or more systems. Four suppliers, a survey contractor, your programme schedule and your reporting obligations. The normalised reading model, meaning instrument, channel, timestamp in one timezone convention, raw value, corrected value, applied corrections, baseline reference and quality flag, is most of the project, and everything downstream is straightforward once every reading means the same thing.
How to decide in a week
Take last month's data from your live site and run two exercises with your monitoring engineer beside you.
First, pick the most recent amber breach and reconstruct the timeline: when the reading was taken, when it was processed, when an alarm was raised, which address it went to, when a human acknowledged it, and what the agreed response required. Write the elapsed hours at each hop. Second, take an instrument that stopped reporting for more than six hours and find out how long it took anyone to notice.
- If acknowledgement happened inside the agreed period and silence was noticed the same day, stay on the supplier platforms.
- If the breach was found in a weekly report, build the trigger engine and escalation first.
- If nobody noticed a dead instrument, the communications watchdog is your first feature and it is cheap.
- If the joined view exists only in a spreadsheet somebody rebuilds weekly, that person is your single point of failure.
Then commission a paid discovery phase rather than accepting a proposal. At Digital Heroes that is two to three weeks producing a signed product requirements document covering the reading model, every supplier interface named individually, the trigger regimes transcribed from the agreements, the escalation paths and the acceptance criteria. You keep the document whether or not you hire us, and it makes three quotes comparable.
Who we are wrong for: a single site with one instrumentation supplier and one asset owner. Use their platform, spend the difference on more instruments, and revisit this when the second supplier arrives. We are more than fifty specialists with over 2,000 projects delivered, verifiable on Clutch, Trustpilot, Fiverr Vetted Pro and by D-U-N-S number. Our own products, ShopScore, HeroCheckout and Section Vault, are commerce and documentation tools rather than geotechnical ones, so judge us on delivered client work. Our India LLP, US LLC and UK LTD entities mean intellectual property assigns under your own law. You meet the named engineers before signing.
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.
- 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) →
- 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) →
- The EY survey of 508 payroll professionals at U.S. companies with 250-10,000 employees quantifies the direct and indirect cost of payroll inaccuracy, reinforcing the ROI case for payroll automation; the study is the original source of the frequently cited $291-per-error figure. Source: BusinessWire / EY (Ernst & Young) (2022) →
- SMS reminders that stated the specific cost of the appointment to the health system reduced missed appointments in Trial One, with the DNA (did-not-attend) rate falling from 11.1% (control) to 8.4% (specific-costs message) - an odds ratio of 0.74 (95% CI 0.61-0.89), i.e. roughly a 24-26% relative reduction - at no additional cost. (Trial Two replicated this at an 8.2% DNA rate.). Source: PLOS ONE (Hallsworth et al.) (2015) →
Frequently asked questions
How much does custom structural monitoring software cost?
A first release covering multi-supplier ingestion, the normalised reading model with baselines and corrections, a configurable trigger engine, data quality checks with a communications watchdog and escalation with acknowledgement runs $70,000 to $150,000 over 12 to 18 weeks. A full platform adding construction activity correlation, asset owner reporting and portfolio views runs $180,000 to $450,000 across 6 to 12 months. Historical migration adds 10 to 25 percent.
How long does it take to bring four suppliers into one view?
Twelve to eighteen weeks for the first release, but the pacing item is supplier cooperation rather than code. Some publish a documented interface and answer within a day, others send a comma separated file on a schedule and take three weeks to reply. Name every supplier in the specification with the interface each one offers before pricing, because an uncooperative supplier can add a month on its own.
Who owns the readings, and what happens at the end of the job?
You should own the database, the repository and the cloud account from the first commit. Monitoring records support a contractual position with an asset owner and may be examined years after the works finish, so retention outlives every supplier contract. Ask each instrumentation supplier, before signing their subcontract, how you export the complete corrected record including correction history rather than a chart.
What happens if an instrument stops reporting overnight?
Silence deserves its own alarm and it is the failure most often missed. A system that only alarms on values will stay quiet while half an array is dead, so an instrument that has not reported for a defined period should raise a communications alert separate from the movement queue. In our builds this watchdog is usually the first feature that earns trust from the monitoring team.
Can we build only the trigger engine and keep the supplier portals?
Yes, and it is a sensible first phase. Ingest readings from each supplier, normalise them, and run your negotiated regimes against them with escalation and acknowledgement, while leaving configuration of the nodes themselves where it is. Construction correlation, portfolio views and automated reporting can follow. What you cannot phase is the reading model underneath, because everything downstream depends on it being right.
Should a single site with one supplier build anything?
No. One supplier, one array and one asset owner is the clearest buy case in this category. Their platform will hold thresholds, produce charts and send alarms, and the money is better spent on additional instruments, which reduce uncertainty far more than software does. The build case begins with the second supplier, the second asset owner or the second concurrent project.
What is the difference between a threshold and a trigger regime?
A threshold is a single number compared against a reading. A trigger regime, as written into an asset protection agreement, may combine cumulative movement since a defined baseline, a rate of change over a set period, different values per construction stage, and a distinction between movement toward and away from the asset. Different assets on one site often carry different regimes because they were negotiated separately.
How do we stop false alarms from destroying confidence in the system?
Put data quality between ingestion and alarming rather than after it. Range checks, rate of change plausibility, cross checks against neighbouring instruments that should move together, reference and backsight stability checks on total stations, and gap detection. A reading that fails quality checks should raise an instrument health alert, never a movement alarm, and those two queues must stay separate or people mute both.
Can we correlate monitoring data with our construction programme?
That is the highest value feature and no supplier platform will build it. Timestamp excavation stage changes, pile installation, dewatering rates, prop installation and removal, and significant plant movements, then show them against the instrument traces. It converts the meeting after every breach from an argument into a finding, and it is usually what an asset protection engineer remembers about working with you.
What are the alternatives if a build is not funded yet?
Three things help immediately. Transcribe every trigger regime from the agreements into one written table, because that is the specification and it currently lives across several documents. Redirect every supplier alarm to a monitored distribution list owned by a role rather than a person. And log baseline resets with justification in a shared record, since that is the item an asset owner will question first.
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.
Is Tableau worth $75 per user per month, or should we build our own dashboard?
If you have analysts who explore data visually all day, Tableau Creator at $75 per user per month earns its price, and Viewer seats at $15 keep the total reasonable for a small team. The math flips once you have hundreds of viewers or need dashboards inside a customer-facing product, because per-seat pricing scales with your audience while a custom build does not. Run the 3-year seat cost before deciding; that horizon usually makes the answer obvious.
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.
Should I embed Power BI or Tableau in my SaaS product, or build custom charts?
Embed first if you need analytics inside your product within weeks, but treat it as a bridge rather than the destination. Embedded licensing meters your customer traffic, so your analytics cost grows with your user count, and the look and feel never fully matches your product. In Digital Heroes projects, SaaS teams usually switch to custom charts built in React with a library like ECharts or Recharts once analytics becomes a selling point instead of a checkbox.
How small can the first version of my software be and still be worth building?
One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.
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.
What do I need to prepare before contacting an agency about a dashboard project?
Bring three things: a list of your data sources with who controls access to each, the 5 to 10 recurring decisions the dashboard should support, and examples of the reports or spreadsheets it will replace. That package lets an agency quote in days instead of weeks, and in our discovery work it cuts the audit phase roughly in half. You do not need wireframes or a technical spec; a good agency produces those with you.
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.
What are the most common mistakes companies make on dashboard projects?
The four we see most: designing charts before modeling the data, cramming 30 metrics onto one screen so nothing stands out, letting every team define revenue slightly differently, and skipping data quality checks so the dashboard confidently displays wrong numbers. The wrong-numbers failure is the fatal one, because a dashboard loses trust once and never fully earns it back. Spend the first weeks on metric definitions and data quality, not on colors.
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.
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
Published · Last updated .
