← All case studies
Case study 05 · Water Treatment · One product, eight firms

Eight water-treatment dealers, one service-reporting platform, live in 19 days.

Water-treatment dealers all run the same visit: an engineer tests the cooling tower or boiler, writes readings on a log sheet, and someone types them into Excel and a Word report days later. AquaServe is that workflow, finished once and dropped into eight firms.

Between 29 June and 17 July 2026, Pioneer Engineering and Om Enterprises (Pune), Micro Chem (Salem), Water Whizz (Ahmedabad), FeedAqua and Bellway Consulting (Greater Noida), Goa Trading & Technical Services and S P Chemicals (Sangli) each went live on their own branded portal — one application, no forks.

Clients
8 water-treatment dealers
Industry
Water Treatment · Service & Chemicals
Location
Gujarat, Maharashtra, Tamil Nadu, Goa, Uttar Pradesh
Workflow
S · Site-visit reporting
19 days

From the first two dealers going live to the eighth — 29 June to 17 July 2026.

124 clients

End-customer plants being reported on across the eight portals by September 2026.

104,542

Readings from one dealer's five years of daily Excel logs, imported so history did not start from zero.

What every dealer gets · 8 pieces
01

A branded portal on their own subdomain — logo, colours, letterhead and email from-name — provisioned by one script, not a code fork.

02

Phone-first visit entry: client → plant → system → sample → parameter, checked live against control limits, with photos attached on site.

03

Auto-calculated values the engineer used to work out by hand — Langelier index, cycles of concentration, chiller approach.

04

Three report types on one visit record: water analysis, chemical stock, corrosion monitoring.

05

PDF on the dealer's letterhead or Excel with a report sheet and a raw-data sheet, grouped per contact person so one plant contact gets one report per date.

06

Sent from the dealer's own mailbox, with the visiting engineer as the reply-to address.

07

Five roles from platform admin down to lab analyst, and a role-aware in-app manual: 15 walkthroughs and 10 written references.

08

Tenant isolation proved by a 192-check test suite that runs before every release.

01 — The challenge

The same slow report, written eight different ways.

A dealer's engineer visits a plant, tests the water, and fills a paper log sheet. Back at the office the readings are typed into Excel, a report is built in Word, and it goes to the customer by email — days later, with illegible handwriting, copy errors and no trend history along the way. Every one of the eight firms had its own version of this, and none of them had the size to build software for it.

The trap for a small dealer is obvious: a custom build is too expensive for one firm, and a generic SaaS tool does not know what a cooling-tower control limit is.

02 — What we built

One application, eight portals, no forks.

AquaServe is the visit workflow from our first client's report portal, rebuilt as a multi-tenant product. Each dealer is one row in a provisioning script — subdomain, logo, brand colour, letterhead, mailbox — so onboarding is a run, not a project. Two dealers went live on 29 June, three on 9 July, two on 17 July, then S P Chemicals and a ninth on the same platform since.

A feature asked for by one dealer is resolved one of three ways: shipped to everyone, switched on for that dealer alone, or refused. Coupon photographs and discharge pressure went to all nine tenants the day after an engineer asked on WhatsApp; a Boiler Running Days column asked for at 12:50 was live for that one dealer at 13:08. Nobody waits for a release train.

03 — The results

A dealer network that ships together.

By mid-September 2026 the eight portals report on 124 end-customer plants with 53 working users and roughly 1,900 visits logged. One dealer's five years of daily Excel logs — 1,309 visits, 104,542 readings — were imported so their customers' trend graphs started with history instead of a blank page.

Because it is one application, every dealer got the COD parameter, the stock-report editor and the control-limit column picker in the same week they were built. That is the economics of a productised workflow: the eighth dealer costs a fraction of the first, and all eight get better at once.

Before · After
A water-treatment dealer's service reporting: before vs after AquaServe
Metric Before After
Where readings are captured Paper log sheet, re-typed later On the phone at the plant, validated live
Report assembly Excel then Word, by hand Generated PDF or Excel on the dealer's letterhead
Trend history None, or scattered files Every reading kept, graphed per plant
Rolling out to a new dealer A new build each time One provisioning run

Run a dealer network on one workflow?

If eight firms do the same job eight ways, that job is a product. Tell us which one.

Book a meeting →