Digitising a two-site automotive service business, end to end
Over five years, I moved an authorised Michelin partner from notebooks, Tally entries and WhatsApp threads to connected customer records, invoicing and reporting across two locations and ~30 staff.
Digital Transformation and Customer Engagement Lead · Mast Service Station · Jan 2019 – Sep 2024
The work
I had no handed mandate here, only full accountability for whether the changes actually stuck. They had to survive daily service pressure, staff routines and customer expectations. This study covers the operational layer: customer records, service history, POS and CRM workflows, invoicing, reporting, standard operating procedures, and the follow-up routines built on top of them. (The customer-facing identity this system served, across brand, website and Instagram, is covered in its own case study.)
The logic ran one direction: implement systems first to free up operational workload, then reinvest the freed capacity in things the business never had time for.
I treated the business like a service journey, where staff processes, records, and customer communication had to support each other.
What made it complex
The challenge was not one isolated website, marketing, or system problem. It was the overlap between customer experience, digital visibility, service operations, staff routines, records, reporting, and follow-up.
A customer could discover the business, make contact through WhatsApp or phone, arrive at one of two locations, receive a service, and return months later. The business needed its records and internal processes to stay connected across that full journey.
The work had to connect counter staff, service staff, accounts, owners and customer-facing touchpoints across two locations without interrupting daily walk-in operations.
"My job was to make the invisible work visible: the bookings, the service history, the follow-ups. I built the system the business needed to run without holding it all in one person’s head."
Approach
I used a practical improvement rhythm: observe the current experience, identify where customers or staff were losing time or information, improve the relevant touchpoint or workflow, record the interaction properly, follow up where there was a service or retention opportunity, and turn useful improvements into repeatable routines.
I mapped the service transaction lifecycle from enquiry to visit, invoice, record update, follow-up and repeat engagement, then used that map to decide where digital records and reminders would reduce friction.
The aim was not to introduce technology for its own sake. It was to make the business easier to discover, easier to use, and easier to operate.
A major source of avoidable effort was the billing and filing handoff: manual bills moved between people before being entered separately into Tally. Moving invoicing into the POS-supported workflow reduced duplication and made records easier to retrieve.
One example of the rhythm end to end: recording data points like average monthly driving at the time of visit, so reminder calls and messages for servicing and replacement went out on the customer's schedule, not on guesswork.
The questions that ran the day
How the service system connected
The work was not one isolated website, Instagram, record-keeping, or process task. Each part supported the same service journey.
Customers needed to discover the business, understand the service, make contact, receive the service, be recorded properly, and have a reason to return. Behind that, an operating layer connected WhatsApp, customer records, reporting, and SOPs to keep the journey consistent.
What the work enabled
Repeat-customer visits up 15% over two years, per POS data.
A loyalty programme taken up by 1,000+ customers.
Customer history retrievable in one click at the counter; digital receipts offered alongside paper.
Follow-up became routine: data points captured at the time of visit fed scheduled reminder calls and messages for servicing and replacement.
Customer history, Vyapar invoicing and follow-up consolidated into daily workflows across both locations; staff routines made repeatable through SOPs and handover notes.
Avoidable manual effort down an estimated 25–30% (my estimate — from mapping transaction lifecycles: a sale used to move by hand from the counter to accounts to filing; integrated records removed those handoffs).
Sales, delivery and stock updates became easier to reconcile because the POS-supported workflow created a clearer record of what had moved, what had been billed and what still needed follow-up.
Key takeaways
Service transformation does not happen through tools alone. It happens when customer-facing touchpoints, operating routines, records, communication, and staff habits start working together.
A better website cannot fix an unclear service process. A customer database cannot create value if records are not maintained. A retention idea cannot work without ownership and follow-up.
That lesson still shapes how I approach product and transformation work today: improve the whole service system, not only the visible interface.
The systems were never the point. The hours they freed were reinvested into capturing customer data at the counter, producing content to a standard operating procedure, and the feedback and reminder calls that kept customers coming back. Transformation that only removes work is half finished; the other half is choosing what the business does with the capacity it gets back.
"The customer sees the service. The business runs on the system behind it."