No prices published yet, and there is a reason for that — it is the first thing below.
Why there are no prices here. We quote after seeing a sample, not before. Scope, exclusions, revisions and timeline are written down with the quote, and the quote does not move unless the scope does. We would rather publish the boundary than a number we could not stand behind — a rate set before we understand our own delivery times is a guess dressed as a commitment, and it is the buyer who pays for it later.
Quick Fix
One workbook, one conversion, or one defined batch of records.
A single file, cleaned or converted, checked and handed back.
Included
Cleaned or converted file in Excel or CSV
Duplicate check and format standardisation
A note listing anything unreadable, missing or ambiguous
Not included
Analysis or interpretation of the data
A repeatable process — this is a one-time output
Dashboards, charts or reporting layers
What we need from you
The source file, or one representative page of it
The column layout you want out, if you have one
Revisions
Two rounds, where a round means corrections against the agreed scope — not new requirements.
Timeline assumes
Assumes a legible source and a record count agreed before we start. An unreadable scan or a batch larger than quoted resets the estimate.
What moves the quote
Record, page or row count · Source quality — a clean export costs a fraction of a shadowed photograph · Number of distinct layouts in one batch · Whether duplicates have to be resolved or only flagged
A manager who needs a specific question answered, once, properly.
Clean data, defined KPIs, and a findings document that names what to do next.
Included
Prepared and sense-checked data
Written KPI definitions
Pivots, charts and the supporting workbook
A findings document with ranked recommendations
Not included
An interactive dashboard
A refresh mechanism — this answers a question at a point in time
Ongoing updates
What we need from you
The question, written as a question
The data that might answer it
The decision that follows, and who makes it
Revisions
Two rounds on the findings document, plus corrections to any figure that fails reconciliation.
Timeline assumes
Assumes the data can answer the question. We check that first and will tell you if it cannot before you commit.
What moves the quote
Number of questions in scope · Number of separate data sources to reconcile · How much cleanup the data needs before analysis can start · Whether the findings also need a deck
Sales, stock, finance or leadership visibility that several people share.
An Excel or Power BI dashboard, with the KPI definitions and refresh written down.
Included
Dashboard in Excel or Power BI, at an agreed page count
Filters, drill-downs and period comparison
KPI definition document
Refresh, sharing and access guide
A handover walkthrough
Not included
Power BI licences — bought by you, directly from Microsoft
Tenant administration or gateway infrastructure on your network
Embedding into your own application
Preparing the data each period
What we need from you
Data sources and two periods of real data
The KPI list, or a current report we can derive it from
Who needs access, and your licensing position if Power BI
Revisions
Two rounds against the agreed page and KPI list. Adding a KPI after sign-off is a change request.
Timeline assumes
Assumes stable, accessible sources. If the refresh depends on a system we have not confirmed we can reach, that confirmation happens before the estimate stands.
What moves the quote
Number of report pages and KPIs · Number of data sources and how much modelling they need · Excel versus Power BI · Whether scheduled refresh and access design are in scope
Recurring reporting where the manual work should stop being manual.
A workbook that refreshes instead of getting rebuilt, with the steps documented.
Included
Rebuilt template with Power Query, formula redesign and a data model where it fits
Refresh proven against two periods of data
A one-page refresh guide written for a non-author
A training session for the person who will run it
Not included
VBA or macros by default — assessed against your sample and your IT policy first
Integration with systems or APIs we have not confirmed we can reach
Multi-user editing, locking or version control
Running the refresh for you — that is Managed Refresh
What we need from you
The current workbook and a walkthrough of the manual steps
Two periods of source data
Your Excel version and whether macros are permitted
Revisions
Two rounds, plus a fix for any refresh failure found during the agreed support window.
Timeline assumes
Assumes the source arrives in a consistent shape each period. A source that changes shape needs stabilising before automation is worth buying.
What moves the quote
How many manual steps are being replaced · How stable the source format is · Excel version and macro policy constraints · Length of the post-handover support window
A reporting pack that works, and nobody with time to run it.
We run the cycle — intake, refresh, QA, delivery — on a fixed cadence.
Included
The refreshed pack on the agreed date, every period
A QA note recording what was checked
An issue log carried period to period
A named escalation route
Not included
Unlimited change requests — a defined allowance is included, larger changes are quoted
Fixing source data that arrives broken; we flag it and pause rather than guess
Cover outside agreed support hours
What we need from you
A data drop by the agreed cut-off, in the agreed format
One named contact who can answer a query inside the cycle
Revisions
A defined number of small changes per period, agreed at the start of the engagement.
Timeline assumes
Assumes the cut-off is held. A cadence that slips every period costs more to manage than it saves, and we will say so rather than absorb it.
What moves the quote
Cadence — weekly costs more than monthly · Number of sources to be reconciled each cycle · Size of the included change allowance · Support hours and escalation expectations
Including the ones with answers that cost us something to publish.
How many revisions are included?
Every package states its own allowance, and it is on the package card rather than buried in terms. A revision means a correction against the scope we agreed. A new requirement is a change request, priced separately — we will always tell you which one we think it is before doing the work, not after.
What affects the price, and why are no prices published?
What affects it: volume, source quality, the number of separate sources, how much cleanup is needed before the real work starts, and whether a refresh mechanism is in scope. Why nothing is published: this is a new practice, and a rate published before we understand our own delivery times would be a number we could not stand behind. We quote after seeing a sample, and the quote does not move unless the scope does.
How long does it take?
We give a date with the quote, once we have seen a sample — not before. Any estimate given without seeing the data is a guess, and guesses on this kind of work are wrong in one direction. Every package states what its timeline assumes, so you can see what would move it.