Case study · 03Northridge Mechanical · Bangalore

A field-service company's
dispatch board,
rebuilt around the van and the customer.

Northridge Mechanical was running an HVAC and plumbing service business across Bangalore on a whiteboard, a WhatsApp group and a paper job sheet that came back at the end of the week. We replaced it with a dispatch board the office watches in real time and a technician app the crew actually opens.

Client
Northridge Mechanical
Industry
HVAC · Plumbing · Service
Engagement
Fixed-scope build + retainer
Timeline
Six weeks · Q3 2025
app.northridgehvac.in / dispatch
Operations
Dispatch
Technicians
Routes
Customers
Inventory
Invoices
Office
Bangalore
Dispatch · live service tickets
Bangalore · five technicians on the road
Tickets in queue
Moving
no backlog
Technicians
All routed
5 on the road
Same-day SLAs
On track
auto-rebalanced
RefJobTechStateETA
NR-3041AC servicing · IndiranagarArun K.En route10:30
NR-3040Boiler repair · WhitefieldPriya N.On sitenow
NR-3039Plumbing · HSR LayoutRahul M.On track12:15
NR-3038Duct cleaning · KoramangalaDeepa S.Awaiting15:45
NR-3037Heat pump · JayanagarVikram J.On track17:00
At a glance

From a whiteboard the office redrew every morning to a dispatch board the whole crew works off.

One live board, no whiteboardoffice and field see the same queue
Routes that respect the citytechnicians stop driving across Bangalore twice
Job sheets close on the vanphotos, parts, signature, invoice — before the next stop
Discovery to launch in six weeksfixed scope, fixed price
01 The problem

A service company growing faster than the whiteboard could keep up with.

Northridge Mechanical had spent fifteen years building a name in Bangalore for HVAC and plumbing work that actually got done. The craft was strong. The coordination was a daily fire drill.

Every morning the operations lead drew the day on a whiteboard from notes on her desk. Technicians took photos of it, then adjusted in a WhatsApp group as customers called and jobs ran over. Job sheets came back on paper at the end of the week, half of them missing parts used, half of them missing the customer signature. Invoices went out late. Same-day SLAs slipped because nobody could see, in one place, where the next available van actually was.

The bottleneck was not the technicians. It was the absence of a single picture of the day that the office and the field both trusted.

02 What we built

Three pieces that act like one operation.

A

A dispatch board the office runs the day from

Every ticket has one card. Customer, address, job type, history, parts notes, attached photos — all on the card, all editable, all auditable. The board re-orders itself as jobs run over and new ones come in. The operations lead stops redrawing the whiteboard.

  • Single ticket card per job
  • Live queue, auto-rebalanced
  • City view across all technicians
B

A technician app that closes the loop on the van

Each tech opens the day on their phone. Routes are ordered, addresses one tap to navigate, parts pre-listed. When a job is done, photos, parts used and the customer signature go in on site. The ticket closes on the van and the invoice queues itself before the next stop.

  • Route view with one-tap navigation
  • Photo + parts + signature on site
  • Offline-first, syncs when back in range
9:41● ● ●

My route · Today

Arun K. · Bangalore · 5 stops

AC servicing · Indiranagar10:30 · 17 min away
Next
Plumbing · HSR Layout12:15 · parts loaded
Hold
Boiler repair · Whitefield14:00 · customer notified
Set
Duct cleaning · Koramangala15:45 · access code shared
Set
Heat pump · Jayanagar17:00 · pre-call done
Set
C

A customer site that sets the right expectation

Customers book and reschedule online. They get an honest arrival window, a name and a photo of the technician on the way, and a clean invoice afterwards. The office stops fielding the same five phone calls every morning.

  • Online booking and reschedule
  • Live ETA and technician profile
  • PDF invoice with payment link
03 Six weeks, end to end

From a discovery call to a board the operations lead opens at 8am.

  1. Week 01

    Discovery

    Two days at the Bangalore office, riding along on two service calls.

  2. Week 02

    Plan

    One-page spec, fixed scope, fixed price. Signed before any code shipped.

  3. Week 03

    Build · α

    Dispatch board live for one technician as a pilot. Office ran the day from it.

  4. Week 04

    Build · β

    Technician app rolled in. Job sheets started closing on the van.

  5. Week 05

    Customer site

    Online booking and ETA pages live. Reschedule flow shipped end of the week.

  6. Week 06

    Launch

    All five technicians on the new system. On retainer the same day.

Stack

Mature, boring, well-supported.

Nothing on the bleeding edge. Everything has documentation, a community, and a future. Northridge's office can hire any competent engineer to maintain it.

Front-end
Next.js · React · Tailwind
Tech app
React Native · Expo
Back-end
FastAPI · Postgres · Redis
Routing
Mapbox · OSRM
Sync
Offline-first queue · WebSocket
Telemetry
Sentry · audit log
We had been told for years that a system like this either cost a fortune or never shipped. Tanvora delivered one in six weeks that our technicians actually open on the van. That was the part nobody else managed.
NRRohan Bhatia · Director · Northridge MechanicalBangalore
Up next

More work, ready to read.

See the matter-management build for Halverson Chambers, the tax-season cockpit for Iyer & Joshi, or the back-of-house rebuild at Soch et Latte.