What does your data problem cost you?
Every engagement starts with a fixed-price assessment focused on one costly problem. You get the evidence, method, and a clear recommendation on what, if anything, to do next.
At a retail group, a six-week assessment identified an estimated $40,000 in monthly savings, primarily through analysis of idle warehouse capacity and overlapping cloud pipelines.
TRIGGERS
Who this is for and when it makes sense
A data problem has become too costly, risky, or important to leave unresolved. Six situations where an assessment is worth considering:
New leadership needs a baseline
A new CTO, CDO, or CFO needs a clear view of the costs and risks in the platform they inherited.
The bill has increased
Platform costs have risen, but the team cannot identify which workloads or decisions caused the increase.
The platform has outgrown its design
Data volumes grow, queries slow down, and decisions made for a smaller platform continue to drive cost.
A legacy platform must be replaced
A migration is planned, but its cost, scope, integration effort, and reporting risks have not been measured.
A regulatory deadline
An upcoming regulatory, audit, or resilience deadline creates urgency, but the gaps on the data side are not yet clear.
Lost confidence in the numbers
After an outage or reporting error, teams verify data manually and business decisions are delayed.
TWO ENTRY OFFERS
Where to start?
The right starting point depends on the evidence you need and the access available.
Diagnosis
Best if you cannot grant data access yet
The process:
Team interviews and an architectural review. No production data access is required to start.
Deliverables:
A documented cost and impact baseline
Pricing:
Fixed fee, fully agreed before we start
Measurement pilot
Best if data access is available right now
The process:
Hands-on engineering work on a targeted slice of your data, hosted entirely inside your own cloud.
Deliverables:
A working proof your team can run and verify
Measured results and a documented calculation method
Measured results and a documented calculation method
Pricing:
Fixed fee, fully agreed before we start
We only recommend further work if the evidence justifies it
The decision may be based on cost, risk, operational impact, or feasibility. If the findings do not justify further work, we say so and stop there. Your commitment is limited to the agreed scope and fixed price of the current stage.
MEASUREMENT
What we calculate and what we require from you
We measure the time between an event and the action taken, then estimate the business cost attributable to that delay. We use evidence from your process and make the assumptions behind the calculation explicit.
We need: event logs and one example that already cost you something.
Decision window
We measure the hours spent on manual data processing and apply agreed labor-cost assumptions. We document what may be automated and what still requires human judgment.
We need: a conversation with the people who actually build those reports.
People's time
We measure the time spent reconciling conflicting data and assess the impact of decisions made with the wrong version.
We need: two reports showing different values for the same metric.
Numbers mismatch
We map cloud spend to the workloads, queries, teams, and processes that can be identified from the available billing and usage data.
We need billing and usage history for the agreed scope. We confirm the required read-only access before starting
Platform bill
We measure the time, infrastructure, and repeated preparation work caused by data that is not ready for AI models. We also identify the gaps that must be closed before production.
We need: the AI use case, its data sources, and the current preparation process.
Unprepared data for AI models
Rules that apply to every line above
We use available system data, documented assumptions, and evidence supplied by your team. Consumption and performance data come from your environment. Labor costs use agreed rates or estimates. External benchmarks include their sources and years, so your team can review the calculation methods.
SECURITY
Your data stays with you
We work inside your cloud
On your permissions and your accounts. Production data does not leave your organisation.
Production access depends on the agreed scope
We start with interviews and an architecture review, using production data only if the agreed scope requires it.
We work under an NDA
The scope of access is agreed up front, before the stage starts.
Security requirements are checked before the proposal
If your security requirements affect the proposed scope or delivery model, we say so before the engagement starts.
PROCESS
Four steps from call to decision
The call
In the first call, we define the problem to assess and determine the appropriate starting point.
Access
The schedule starts once the inputs and access agreed for that stage are available. Diagnosis can start without production data access. Where access approvals are required, the time needed to obtain them is counted separately.
The work
Diagnosis typically takes 2 to 4 weeks. A Measurement pilot typically takes 3 to 6 weeks and includes hands-on work on a selected slice of your data.
Findings and recommendation
You receive the findings, calculation method, priorities, and a recommendation on whether further work is justified.
What does this stage not cover?
The Measurement pilot tests the proposed approach on a selected sample; full rollout is part of a separate implementation. Diagnosis is a separate, fixed-price engagement, and its findings do not depend on whether you commission implementation. Support is scoped separately after rollout.
Frequently asked questions
We have a strong IT team. What would you do?
We work with your IT team on the defined problem, adding the specialist capacity and outside perspective required by the scope. Architectural decisions are made with them, not around them.
Will we be dependent on you afterward?
The evidence, calculation method, and documented findings stay with your team. For a Measurement pilot, your team also receives a working proof it can run and verify.
What does it cost?
Each assessment is a fixed-price engagement. The scope and fee are fully agreed before we start.
What is the difference between the Diagnosis and the Measurement Pilot?
Diagnosis uses team interviews and an architectural review, with no production data access required. A Measurement pilot includes hands-on work on a targeted slice of your data inside your own cloud.
What stays with us once you are done?
You receive the findings, calculation method, priorities, and a recommendation on whether further work is justified. Any implementation or support is scoped separately.
Start with one costly problem.
We measure its cost and define the scope through a fixed-price assessment, then recommend what, if anything, should happen next.