Our standard: every site we build loads in under 2.5 seconds on mobile data.

Analyze

Data, analytics & M&E dashboards

Analytics installed properly, dashboards that answer a real question, and monitoring-and-evaluation reporting built for the people who have to submit it.

Indicative
On scope
Typical timeline3–10 weeks
Deposit50% to start
Source codeYours at handover
SupportCare Plan from KES 14,000/mo
Discuss a project

Who this is for

You have data and you still cannot answer the question. The numbers exist in four systems, the quarterly report is assembled by hand, and nobody is quite sure the two versions agree.

An NGO reporting to a donor

Indicators defined once, calculated from live data, and exported in the donor’s own format.

A county department

The figures the assembly asks for, current, rather than rebuilt from scratch each quarter.

A firm that cannot see its pipeline

Where enquiries come from and which of them convert, so marketing spend is decided on evidence.

An organisation with three systems

One set of numbers everybody agrees on, instead of three that nearly match.

What you get

A measurement plan first

The questions you need answered, written down, before a single chart is built.

An indicator framework

Each number defined once: what it counts, what it excludes, and who owns it.

Dashboards people use

Built for the person who has to act on it, not for a screen in reception.

Scheduled exports

The donor or board report generated on a schedule, in the format they insist on.

Cookieless web analytics

Privacy-respecting by default, so the site needs no consent banner.

Documentation

How every figure is derived, so the answer survives the analyst leaving.

How the build runs

Each stage ends with something you can open, and a decision you have to make. No month of silence.

  1. 01

    Question setting

    What decisions the data has to support. Anything that supports no decision is not built.

    1 week
  2. 02

    Indicator definitions

    Each number written down and agreed, including the awkward edge cases.

    1 week
  3. 03

    Instrumentation

    Collecting what is missing, and correcting what is being collected wrongly.

    1–3 weeks
  4. 04

    Dashboards and exports

    Built, reviewed against a period you already have reported, and corrected.

    2–4 weeks
  5. 05

    Handover

    Training, documentation, and ownership of every account.

    1 week

What we need from you

Three things, and a project runs on time.

Most delays are not technical. They are a decision nobody was able to make, or data nobody could find.