Skip to main content
ELSTAT

Statistics • Discovery • Evidence • Policy

Evidence that holds when the decision is questioned

We design surveys, build composite indices, and turn raw data into numbers whose methodology can be opened, checked, and reproduced.

Platforms we run

Methodology should not stop at the report. We run it as a system that keeps working.

PERSADA — Kab. Madiun

A regional analytics and data integration hub: development programmes, public finance, and agency performance in one view.

HTML · Chart.js · ApexCharts · Leaflet

HAMID RAUNG — Kab. Bondowoso

Holistic, Adaptive, Monitoring, Integrative Dashboard — an analytical workspace for tracking regional programmes and budgets.

HTML · Leaflet · Chart.js

IPU Platform

Computation and visualisation of a business competition index across survey data from 38 provinces.

Next.js · FastAPI · PostgreSQL · Docker

AKB — Atlas Kesempatan Berusaha

An atlas of sector structure and competitiveness analysis across Indonesia.

HTML · D3 · Nginx · Docker

ELSTAT Survey

Structured field data collection, from form design through quality control.

ODK · PostgreSQL · Docker

Platform

Selected work

The honest way to judge a research team is to read what it has produced.

All case studies
Local governmentYear: 2026

One performance and budget view for two district governments

Built a regional performance monitoring framework once, then deployed it in two districts with different sector structures and priorities: PERSADA in Madiun and HAMID RAUNG in Bondowoso.

HTML · Chart.js · ApexCharts · Leaflet
Public sector regulatorYear: 2025

A business competition index across 38 provinces

Built a national composite index from a cross-province survey, then moved the whole computation off spreadsheets and onto a platform that can be re-run every cycle.

Next.js · FastAPI · PostgreSQL · Docker

How we work

Every engagement goes through the same four stages. No stage gets dropped because of a deadline.

  1. 01

    Sharpen the question

    Establish which decision is waiting on the result, and which number is actually needed to make it. This stage routinely cuts the initial scope in half.

  2. 02

    Design before collecting

    Sampling design, indicator definitions, and the analysis plan are written and agreed first. Once the data is in, the method can no longer be chosen neutrally.

  3. 03

    Compute and validate

    Computation runs as reproducible code, cross-checked against an independent source, and stress-tested against the assumptions doing the most work.

  4. 04

    Hand over so it gets used

    Results are handed over in a form your team can run: methodology documentation, the code, and where warranted the platform that runs it.

Have a question that needs a defensible answer?

Tell us the context. If the question is not sharp yet, sharpening it is the first part of the work.

Start a conversation