Case studyEnergy & Utilities9 min read

MeterMate: ending estimated electricity bills with photo-verified meter reading

An electricity distribution utility's meter readers wrote readings in books, and many bills were estimated or disputed. Complaints clogged service centres. We built MeterMate: a meter reader app with photo capture and OCR, route planning, anomaly detection for theft and faults, spot billing on the doorstep and a consumer app for bills, payments and complaints.

19
Features shipped
4
Apps & platforms
6
Team members
22
Weeks to rollout
MeterMate meter reader app capturing a meter photo
MeterMate: every reading photographed, every bill accurate.
01

Estimated bills and angry queues

MeterMate's chief engineer described queues at service centres of consumers disputing bills. Many bills were estimated because a reading was missed; others had readings copied wrongly from a book. Some readings were never taken at all. Revenue leaked, and trust with consumers eroded.

“Every disputed bill costs us twice: once in revenue, once in trust.”

— MeterMate's chief engineer
02

On the round with meter readers

We accompanied meter readers on their rounds. Routes were fixed in paper books, meters were often in dark corners or behind locked gates, and readers had hundreds of meters to cover. There was no way to verify a reading after the fact.

Why bills went wrong
  • Readings missed and bills estimated
  • Readings copied incorrectly
  • No evidence to resolve disputes
  • Theft and faulty meters undetected
Blue-lit server rack
On the round: hundreds of meters, paper books and no verification.
03

A photo for every reading

The meter reader app guides readers along an optimised route. At each meter, the reader photographs the display, and an OCR model reads the value; the reader confirms it. Unusual consumption compared with history triggers a check on the spot. Bills are printed on a portable printer at the door and sent by SMS.

Every reading has a photo, time and location, so disputes are resolved by looking at the evidence. Consumption patterns suggesting theft or meter faults are flagged to vigilance teams.

04

The team

The OCR model and billing integration were the core technical challenges.

1
Engagement lead

Utility workshops and division rollout.

1
Product designer

Meter reader and consumer apps.

2
Android engineers

Reader app, camera and printing.

1
Backend engineer

Billing integration and operations console.

1
AI engineer

Meter OCR and anomaly detection.

6 people in total, working as one team.

05

Decisions we made

Agreed with the chief engineer and commercial department.

01

Trust typed readings?

  • Typed readings
  • Photo with OCR, confirmed by the reader

Our call: Photo with OCR, confirmed by the reader. Photos made every reading verifiable and reduced errors.

02

Bills at the door or later?

  • Bills generated centrally later
  • Spot billing printed at the door

Our call: Spot billing printed at the door. Immediate bills reduced disputes and sped up collections.

03

Where to host?

  • Public cloud
  • Utility data centre

Our call: Utility data centre. Utility policy required consumer data in its own infrastructure.

06

Every feature, module by module

Everything that shipped for meter readers, billing, vigilance and consumers.

Meter readers
Accurate and faster.
  • 01Optimised routes

    Meters in the best order.

  • 02Photo capture with OCR

    Readings read from the display.

  • 03Consumption checks

    Unusual readings verified on the spot.

  • 04Spot billing

    Bills printed at the door.

  • 05Offline mode

    Works without signal.

  • 06Meter issue reporting

    Damaged or inaccessible meters flagged.

Billing
No more estimates.
  • 07Billing integration

    Readings flow into the billing system.

  • 08Reading validation

    Photos and history checked.

  • 09Estimated bill tracking

    Why a reading was missed.

  • 10SMS bills

    Bills sent to consumers.

Vigilance
Catch theft and faults.
  • 11Anomaly detection

    Suspicious consumption patterns.

  • 12Inspection tasks

    Assigned to vigilance teams.

  • 13Evidence records

    Photos and history per case.

Consumers
Clear bills, easy payment.
  • 14Consumer app

    Bills with meter photo.

  • 15Online payment

    UPI and cards.

  • 16Complaints

    Raise and track complaints.

  • 17Consumption history

    Monthly usage charts.

  • 18Role-based access

    Readers, billing, vigilance and consumers.

  • 19Audit trail

    Every reading and change recorded.

MeterMate consumption anomaly dashboard
Vigilance: consumption anomalies flagged for inspection.
07

Rollout

One division piloted MeterMate for two billing cycles. Estimated bills fell sharply and disputes were resolved with photos. The remaining divisions followed with training for meter readers at each sub-division office.

  1. Weeks 1–3
    Discovery

    Rounds with meter readers.

  2. Weeks 4–5
    Design

    Reader app and OCR flow.

  3. Weeks 6–14
    Build

    Apps, OCR, billing and vigilance.

  4. Weeks 15–19
    Division pilot

    Two billing cycles in one division.

  5. Weeks 20–22
    All divisions

    Training at sub-division offices.

08

What we learned

Evidence ends disputes. A photo with every reading changed conversations with consumers.

Help the reader, don't just monitor them. Route planning and OCR made the job easier as well as more accurate.

Built with
  • Kotlin (Android)
  • Next.js
  • Java / Spring Boot
  • PostgreSQL
  • Meter OCR model
  • Consumption anomaly detection
  • Bluetooth bill printers
  • Utility data centre
CTA Background

Building something like MeterMate?

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