Data & analytics

Reports your managers actually open.

01

Who it's for

You are probably here because

  • 01

    Month-end takes a week and one person holds the whole process.

  • 02

    Two systems report different revenue and both are defended.

  • 03

    A donor or regulator wants a report in a format nothing produces.

  • 04

    You have a dashboard nobody opens.

02

What's included

What you actually get.

Most organisations we meet do not have a reporting problem. They have four systems that disagree, and a person who spends three days a month reconciling them in a spreadsheet.

01

Dashboards over existing systems

Sales, stock, operations, finance.

02

Data cleanup, consolidation and migration

The unglamorous part that makes the rest possible.

03

Reporting pipelines and scheduled exports

So the report arrives rather than being fetched.

04

Warehousing

For organisations with several disconnected systems.

05

Donor and regulator reporting packs

For NGOs and schools, in the format asked for.

04

How it runs

Each stage, and what it produces.

  1. 01

    Find the sources

    Every system that holds a number someone quotes.

    Output

    A source inventory and a list of where they disagree.

  2. 02

    Clean and consolidate

    Reconcile, deduplicate, agree definitions.

    Output

    An agreed definition for each measure, in writing.

  3. 03

    Build

    Pipelines, warehouse, dashboards.

    Output

    A dashboard built with the people who will use it.

  4. 04

    Hand over

    Training, documentation, scheduled delivery.

    Output

    Reports that arrive on their own, and staff who can change them.

What you are handed

  • A written definition for every measure on the dashboard
  • Pipelines documented and scheduled
  • Training for the people who will maintain it
  • The reporting pack in the format your funder or regulator asks for

Technology

Power BIMetabaseLooker StudioPostgreSQLdbtPython
05

Proof

One project, in full.

Stock and dispatch system for a regional distributor SMEs and startups Example

Stock and dispatch system for a regional distributor

Four branches on separate spreadsheets, month-end taking a week.

One day

Month-end close

DjangoPostgreSQLM-Pesa DarajaBarcode

Four branches tracked stock in separate spreadsheets. Dispatch errors were routine, nobody could see group stock in one place, and month-end close took a week of reconciliation that one person held in their head.

One day

Month-end close

Four

Branches on one system

Single view

Group stock

Read the full case
06

Commercials

How buying this works.

Engagement
Fixed-price build, then a small retainer for changes and new reports.

Price
On request, after scope

How pricing works

What sets the price

Number of source systems, how much cleanup the data needs, and how many measures have to be agreed and defined before anything can be built.

The cleanup is almost always the largest item, and we quote it separately so you can see it.

Every project is quoted after we understand the scope. You will have a written, fixed quote before any build work begins. No open-ended billing.

07

Questions

Answered plainly.

It is the normal starting point, and it is most of the work. We quote it separately so it is visible rather than hidden in a build price.

Whichever your team will actually open. If everyone lives in Excel, a scheduled export beats a beautiful dashboard nobody visits.

Yes. Send us the template and we will build backwards from it.

You, after training, or us on a small retainer. Both are fine and we will not make the first one difficult.

Run

Get a scoped quote for your reporting

Tell us which two systems disagree and we will start there.

We reply to every enquiry within one working day.

WhatsApp us