An Australian software company wanted to ship a real estimating application, not another folder
of spreadsheets. They built it on Infoveave so reference cost data, calculation
logic, saved runs, and exports live on one platform. The product runs as multi-tenant SaaS for
their own customers, with inputs and outputs you can trace back when someone asks how a number was
calculated.
At a glance:
Industry: Enterprise
Platform focus: Unified Data Platform
Proof type: Quantified outcomes on a governed unified data layer
The customer needed to turn Australian construction cost reference data into something estimators could run day to day. The logic had to work across road, civil, stormwater, water, sewer, buildings, open space, and indexation, with state-based rates, regional adjustments, and pricing-year updates.
Spreadsheets were the obvious starting point and the obvious dead end. Duplicate models, formulas that drift between teams, and no clean record of what changed when a reference edition landed. They needed a platform that could:
Hold master reference data (page, state, year, unit rates) in one governed place
Run configurable calculation modules without rewriting the engine for each asset type
Save estimate runs with inputs and line-item outputs for review
Export to CSV, XLSX, and PDF with an archive trail
Operate as multi-tenant SaaS with admin, premium, and basic user tiers See how industry analytics addresses these challenges.
Ready to see Infoveave in action?
Book a personalised demo and discover how Infoveave can unify your data and drive measurable outcomes.
The solution: a domain application on the unified data platform
The product team built on Infoveave. Infoveave handles data, governance, analytics, and export patterns; they configure the domain modules, inputs, and formulas.
Reference data that admins can refresh
Reference unit rates load as lookup master data, keyed by Australian state, pricing year, and handbook page. When a new reference edition arrives, admin users upload and refresh datasets instead of editing thousands of spreadsheet cells.
Modules you can configure, not black boxes
Each infrastructure domain is a module with documented standard assumptions, user inputs (dropdowns, numeric fields, year selectors), and formulas that chain quantity, unit rate, and cost. Administrators adapt modules through a builder workflow. End users run estimates without touching the formula layer.
Saved reports and exports
Every estimate run can be saved as a report: inputs, calculated summary, and detailed line items. Users export to CSV or multi-sheet XLSX. Download history keeps archived files. Premium and admin roles get detailed breakdowns and PDF export.
Multi-tenant operations
The application deploys as multi-tenant SaaS: separate tenant environments, role tiers (admin, premium, basic), and optional client logo branding. Authentication and tenant isolation sit on the platform stack the team runs in production.
When users need to reprice or compare
Users can recalculate saved inputs against a new pricing year without rebuilding the estimate from scratch. For deeper what-if or scenario work, Infoveave What-If and scenario modelling can use the same data layer. We wrote up that pattern in our What-If modelling guide.
What changed in practice
One calculation pattern now covers eight infrastructure domains instead of eight disconnected spreadsheet models. Reference data and module definitions live in the platform, not on personal drives. Saved inputs, assumptions, results, and export archives mean reviewers do not have to piece estimates back together from email threads.
Multi-tenant deployment and role-based access let the team operate the product for multiple organisations from one foundation. They spend time on domain modules and user experience; Infoveave carries ingestion, quality, analytics, and export plumbing.
Outcomes
The team shipped a production estimating application on Infoveave: multiple infrastructure domains, state-based reference data, regional and year adjustments, and exports that hold up under review. They can refresh reference datasets, adapt modules, and onboard tenants without rebuilding the platform from scratch.
For Infoveave, the engagement is a concrete example of product builders using the Unified Data Platform to deliver domain applications in reference-data-heavy industries, with a live deployment in Australia.
What this case study is about
This story is about what Infoveave enables: reference data, configurable logic, saved runs, and exports on one platform. The customer is an Australian software company that built infrastructure estimating on Infoveave for their own B2B product.
Ready to see similar outcomes? Book a demo with the Infoveave team.
About the Authors
Infoveave Product Team is a member of the Infoveave Product and Solutions Team — specialists in Unified data platforms, agentic BI, and enterprise analytics. Infoveave (by Noesys Software) helps organizations unify data, automate business processes, and act faster with AI-powered insights.