There is no price list on this page, and that is deliberate. What a data platform or an internal application costs depends entirely on what has to be in it, and an average pretending to be a quote helps nobody. What you get instead is a fixed scope and a fixed number, agreed before anything starts.
Sample data, fictional company
Most projects are one of these. A few are two of them in sequence — a platform build, then the portal that sits on it — and that is scoped as two engagements rather than one open-ended one.
When the problem has a name. A report that eats a week every month, a dashboard that needs building properly, a process that should be running on a schedule instead of on somebody’s Tuesday.
When reporting is not the problem — the thing underneath it is. Numbers that disagree, sources nobody has joined, pipelines nobody can review.
When the tool does not exist off the shelf — or analytics have to be delivered outside Power BI, to your team or to your own customers, under your own brand.
When you already have a team and need another pair of hands that understands data — working inside your repositories, your conventions and your review process.
Not sure which one this is? Describe it in a few lines and we will tell you — including if the answer is “none of these yet”. Start a project →
Support is not unlimited work, and pretending otherwise only causes an argument later. This is the line, agreed before the retainer starts.
You approve the scope and the number before anything starts. If the scope changes we requote, in writing — the number never moves quietly.
Code, data, accounts and documentation are yours. Everything runs in your tenancy, on your subscriptions.
We sit with whoever will run it and explain it in plain English, then leave written notes they can use later.
Anything that breaks in the first month after handover, we fix. It is part of the engagement, not an upsell.
It is rarely the thing people expect. The dashboard is the easy part; getting trustworthy data into it is the work.
One clean database is quick. Six systems, three spreadsheets and an inbox is the part that takes the time — not the dashboard on the end.
If the same customer is spelled four ways, that gets fixed before anything can be trusted. We will tell you at the audit stage if this is you.
A tool for two analysts is not the same build as a portal fifty people log into with different permissions.
Hourly billing makes you pay for our learning curve and puts us on opposite sides of every decision. A fixed number means you can approve the work on its merits, and it is our problem if it takes longer than we thought.
Where the work is open-ended by nature — ongoing engineering alongside a team you already have — that is an Embedded Engineering engagement instead, with capacity agreed by the month. Pretending that shape of work can be fixed-priced would just produce a number neither of us believed.
Because the honest answer to “what does a data platform cost” is that it depends on what has to be in it, and a published figure is an average pretending to be a quote. Six systems and three spreadsheets is a different build from one clean database, and the dashboard on the end is the cheap part of both.
What you get instead is a number for your scope, in writing, before anything starts — usually within a day or two of the first conversation. If you need a rough order of magnitude before committing to a call, say so in your first message and you will get one.
We stop and requote that piece. Small additions usually get absorbed; anything that changes the shape of the build gets its own number before we touch it. You will never get an invoice you have not already agreed to.
Almost always, yes. Most engagements start with what you already pay for — Microsoft 365, Google Workspace, your CRM, your accounting system. We only recommend new tooling when the existing stack genuinely cannot do the job.
Open-ended research and anything where nobody can say what “done” looks like. If that is the situation, take the audit first — that is exactly what it is for.
The audit is paid up front. Build sprints are split — half to start, half on handover. Retainers are billed monthly in advance. Bank transfer or card, and you get a proper invoice either way.
Usually within one to two weeks. Tell us your deadline in the first message and we will say honestly whether it is realistic before you commit to anything.
Yes — completely. You own the code, the dashboards, the pipelines and the data. Everything is handed over with documentation and a walkthrough, and nothing is locked to us. If you never speak to us again after handover, what we built keeps running.
Client data remains within the agreed project infrastructure and the approved third-party services we name before the build starts. Access is granted on a least-privilege basis, credentials are kept outside source code, and data-handling requirements are agreed in writing before implementation.
We are deliberately not claiming your data never leaves your systems: real builds touch hosted databases, third-party APIs and sometimes a model provider, and which ones is a decision you make at scoping rather than discover afterwards. Security & engineering practices sets out the whole thing, including what we do not claim.
AI-assisted development helps accelerate delivery. It does not replace the engineering practice around it: architecture decided before code, version control, review, testing, secrets kept out of repositories, and a deployment you can roll back. Every one of those still happens, and the quality bar does not move because the typing got faster.
AI-assisted development is part of how we work, not the product we sell. What you are buying is the architecture, the reliability and the finished system: something that runs unattended and that somebody other than us can maintain. How fast it got written is our problem to manage, not a feature on the invoice.
Every engagement includes a support window after handover, and anything that breaks inside it we fix as part of the work. After that, an optional monthly retainer covers fixes, monitoring and minor changes — the line between a minor change and a new piece of work is set out above, and anything past it is scoped and quoted before we start.
Plenty of clients take no retainer at all. Nothing we hand over needs us on a schedule, and if it does then it was not finished.
Describe the problem in a few lines. You will get a real reply within one business day telling you which engagement fits and roughly what it costs — not a brochure.