Product

Three products, all written out of our own fieldwork

None of these started as a product. Each started as the thing we needed on an engagement and could not buy: one for research teams drowning in spreadsheet reconciliation, one for distributors whose orders and deliveries lived in two different worlds, and one for a courier running a day of parcels out of a notebook.

A note on the names

MESRI is the organisation, Mekong Environmental and Social Research and Innovation. MESRI Data Hub is one of its products. They are often shortened the same way, so on this site the organisation is always MESRI and the product is always MESRI Data Hub or Data Hub, never just “MESRI”.

01 · The products

What each one does

MESRI Data HubField data → donor report In development

The evidence chain in one workspace. Pick a sector template, build the survey, deploy it to KoboToolbox with a QR code, sync the submissions back, validate them, chart them, and publish the report.

  • Who it is for: NGO programme teams, research teams, HR departments, anyone producing donor reports
  • Feeds on: KoboToolbox, ODK Collect, Google Forms, CSV and Excel, and paper forms keyed in by hand
  • Ends with: a validated dataset and a published report, in English or Khmer
Product site Live demo Pricing
Route PlanCall plan → delivered order Live

The distribution loop in one place. Reps follow a call plan and check in at each shop; every visit can raise a purchase order; orders group by area into delivery truck routes automatically.

  • Who it is for: Cambodian distributors and any team running reps against a route
  • Two lanes: Call Plan for sales visits, Delivery for the trucks, joined by the order
  • Ends with: a dispatched delivery route and a live picture of what happened today
Product site Live demo Pricing
Parcel Run CamboPickup request → delivered parcel In pilot

The courier's day in one place. Customers request a pickup and track by code; the office plans the stops, dispatches riders as run files, watches the run live, and reconciles the cash that comes back.

  • Who it is for: Cambodian parcel couriers and any small delivery operation running riders
  • Takes payment: KHQR prepay through Bakong or any bank app, or capped cash on delivery
  • Ends with: a delivered parcel and the day's cash reconciled against it
Product site Pricing
02 · Which one

They rarely compete for the same job

If you are not sure which applies, start here: are you trying to find something out, or to get something delivered? And if it is delivered, is it your own stock going to shops you sell to, or someone else's parcel going to their customer?

  MESRI Data Hub Route Plan Parcel Run Cambo
The job Find something out and report it credibly Get the visit made and the order delivered Get someone else's parcel to their customer
Primary user Programme, research and M&E staff Sales reps, dispatchers, distribution managers Couriers: the dispatch desk and the riders
Unit of work A survey round A day's route A parcel
Input Survey submissions, CSV, paper forms Shops, reps, a call plan Pickup requests from the public
Output Validated dataset and a published report Purchase orders grouped into truck routes Delivered parcels and the day's cash reconciled
Handles payment No Raises the order, does not take the money Yes — KHQR prepay or cash on delivery
Integrates with KoboToolbox, ODK Collect, Google Forms, Excel Runs standalone KoboToolbox, Telegram, Bakong / KHQR
Languages English & ភាសាខ្មែរ English & ភាសាខ្មែរ English & ភាសាខ្មែរ

The Data Hub and Route Plan sites both carry a full interactive demo that computes its results live — neither is a video or a “request a demo” form. Parcel Run Cambo is still in pilot, so it is shown in person rather than on the site.

03 · In common

What all three assume about the field

They look nothing alike and solve different problems, but they were written by the same people under the same constraints.

The connection will drop

Field tools that need good wifi are office tools. All three are built for the connectivity that actually exists on a provincial road, not the one in the demo.

Khmer is not a translation layer

All three ship bilingual English and Khmer, in the interface and in the output, not an afterthought bolted on for a launch.

The phone is the primary device

The person doing the work has a phone in one hand and something else in the other. Desktop is the review surface, not the working one.

Nobody re-keys anything

Every manual re-entry is a chance to introduce an error nobody will find. All three exist to remove one of those steps.

Not sure which

Describe the process that keeps breaking

Tell us where the work currently falls apart and we will point you at the right product, or tell you that neither fits and what would.

Ask us Research & advisory