Case studyAgriculture9 min read

MilkLedger: paying thousands of dairy farmers fairly for every litre, twice a day

A dairy cooperative collected milk from thousands of farmers at village centres every morning and evening, recording quantity and fat on paper slips. Payments took weeks and disputes over quality were common. We built MilkLedger: connected milk analysers and scales at collection centres, instant SMS slips, direct payments every ten days, cattle feed and vet services, and cooperative dashboards.

18
Features shipped
4
Apps & platforms
6
Team members
20
Weeks to rollout
MilkLedger collection centre with milk analyser
MilkLedger: every litre measured, every farmer paid.
01

Paper slips at dawn

MilkLedger's chairman grew up in a dairy family. Twice a day, farmers brought milk to village centres, where secretaries measured quantity, tested fat and wrote a paper slip. Slips were lost, arithmetic errors crept in, and farmers waited weeks to be paid. Quality disputes damaged trust between farmers and the cooperative.

“Our farmers wake at four to milk their cattle. The least we owe them is an accurate slip.”

— MilkLedger's chairman
02

Mornings at the collection centres

We spent early mornings at village centres. Queues formed quickly; measuring and testing were manual; rates depended on fat and solids-not-fat, calculated with a chart. Connectivity was patchy, and power cuts were common.

What farmers needed
  • Quantity and quality measured objectively
  • An instant, accurate slip
  • Payments on time, directly to the bank
  • Access to feed and vet services
Agricultural field
Mornings at village collection centres.
03

Measured by machines, paid by the system

At each centre, a tablet connects to the milk analyser and weighing scale. Quantity, fat and solids are recorded automatically, the rate is calculated from the cooperative's chart, and the farmer gets an SMS slip immediately. Everything works offline through power cuts and syncs when connected.

Payments are calculated every ten days and sent directly to farmers' bank accounts, with deductions for feed or services shown clearly.

04

The team

Device integration and offline reliability drove the team.

1
Engagement lead

Board workshops and village rollout.

1
Product designer

Centre tablet app and farmer experience.

2
Mobile engineers

Centre app and device integration.

1
Full-stack engineer

Cooperative console and payments.

1
Data engineer

Collection data and quality analytics.

6 people in total, working as one team.

05

Decisions we made

Agreed with the cooperative board, including farmer members.

01

Manual testing or connected analysers?

  • Manual fat testing
  • Analysers connected to the tablet

Our call: Analysers connected to the tablet. Connected readings removed disputes and errors.

02

Cash or bank payments?

  • Cash at the centre
  • Direct bank payments every ten days

Our call: Direct bank payments every ten days. Regular, transparent payments built trust and records.

03

Online or offline?

  • Online only
  • Offline-first with sync

Our call: Offline-first with sync. Villages had power cuts and patchy signal.

06

Every feature, module by module

Everything that shipped for farmers, centres and the cooperative.

Collection centres
Measured by machines.
  • 01Analyser integration

    Fat and SNF read automatically.

  • 02Scale integration

    Quantity read automatically.

  • 03Rate chart calculation

    Rates from the cooperative chart.

  • 04Instant SMS slips

    Farmers receive slips immediately.

  • 05Offline operation

    Works through power cuts.

Farmers
Paid on time.
  • 06Farmer app and SMS

    Collections and payments.

  • 07Direct bank payments

    Every ten days.

  • 08Feed orders

    Cattle feed with deductions shown.

  • 09Vet service requests

    Request visits for animals.

Chilling and logistics
From village to plant.
  • 10Chilling centre receipts

    Milk received from centres.

  • 11Tanker tracking

    Routes and quantities.

  • 12Quality at chilling

    Re-testing and variances.

Cooperative
The whole network.
  • 13Collection dashboard

    Volumes by centre and shift.

  • 14Quality analytics

    Fat and SNF trends.

  • 15Payment cycles

    Calculate, approve and pay.

  • 16Member management

    Farmers and shares.

  • 17Role-based access

    Centres, chilling, office and board.

  • 18Audit trail

    Every reading and payment recorded.

MilkLedger cooperative dashboard
The cooperative dashboard: collections, quality and payments across villages.
07

Rollout

Centres were equipped and trained village by village. Farmers' trust grew as soon as they saw quality measured by the analyser and received SMS slips they could check at home.

  1. Weeks 1–2
    Discovery

    Mornings at collection centres.

  2. Weeks 3–4
    Design

    Centre app and device integration tests.

  3. Weeks 5–13
    Build

    Apps, integrations, payments and console.

  4. Weeks 14–16
    Pilot villages

    First centres equipped and trained.

  5. Weeks 17–20
    All centres

    Village-by-village rollout.

08

What we learned

Objective measurement builds trust. Machines ended quality disputes.

Work through power cuts. Offline operation was essential.

Built with
  • React Native
  • Next.js
  • NestJS
  • PostgreSQL
  • Milk analyser and scale integration
  • Offline sync
  • Bank payouts
  • AWS Mumbai
CTA Background

Building something like MilkLedger?

Bring the problem as it actually is, constraints included. You will get a straight answer on whether we are the right team.

View Our Work
AI-First Engineering
Secure & Scalable
Built to Deliver Impact
More case studies