Stage 1 · Running on spreadsheets
Data Foundations Sprint
A small, low-cost cloud data platform that replaces the manual reporting cycle with automated pipelines and one agreed set of KPIs.
Usually 10–100 staff with no data team. Reporting sits with a finance or operations lead. The founder, MD or finance director signs off.
Typical duration4–6 weeks
Discuss this offeringWhere you are
Reporting is manual exports, Excel and copy-paste. Month-end takes days and nobody agrees on the numbers.
Signs you're here
- Key reports are built by hand every week or month
- The same KPI gives different answers depending on who you ask
- One person is the only one who knows how the report works
What usually gets in the way
- The real data is in personal spreadsheets, each with its own layout and its own manual fixes
- Some systems have no API, or the vendor charges extra for data access
- Departments define the same KPI differently, and agreeing one definition is a political decision as much as a technical one
- The one person who knows the reports is also the busiest person in the business
One trusted set of numbers, refreshed automatically, that leadership uses to run the business.
What I'll do
- Source audit: where the data really comes from and who owns it
- Right-sized cloud warehouse on the platform that suits your team
- Automated loads from your core systems and spreadsheets
- Agreed definitions for your 5–10 most important KPIs
- A first dashboard built on the governed model, not on the raw exports
You get
- Working pipelines and warehouse
- KPI definitions document
- Executive dashboard
- Runbook and handover
What you'll need to provide
- A named owner with 2–4 hours a week
- Admin or export access to each source system
- KPI definitions decided within an agreed timeframe
- Copies of the reports you produce today
Not included
- Cleaning years of historical data by hand. Anything that can't be fixed automatically gets flagged and scoped separately
- Replacing your CRM, ERP or finance system
- Software licences (bought in your name, so you own them)
Risks, and how I manage them
- The dashboard gets built and nobody uses it. Replace one report people already depend on, designed with the people who chair the meeting where it is used.
- People keep editing spreadsheets by hand and break the loads. Locked input templates or simple forms, with validation that flags bad rows instead of failing silently.
- Nobody in-house can maintain the platform after handover. Managed services and a deliberately small toolset, a written runbook, and optional light-touch support.
- Typical duration
- 4–6 weeks once access is in place. Getting logins and exports sorted often adds 1–2 weeks at the start
- How we measure success
- Hours of manual reporting removed each week · Report refresh moved from manual to scheduled · One agreed figure per KPI
- Running costs after go-live
- Indicatively £50–£500 a month for cloud and BI licences at this size. It mostly depends on how many people need report access.
- What changes for your team
- Someone needs to own the KPI definitions and handle new report requests, about half a day a week. Without an owner, the spreadsheets drift back in.
- When this isn't the right fit
- Businesses that run almost entirely on one system with good built-in reporting. Its native reports are cheaper than a platform.
Done before: Centralised reporting that cut one regular data retrieval from 5 hours to 10 minutes.