Technology transformation case study
From Google Sheets to GharPar’s operating system.
How a pragmatic WordPress prototype evolved into a modular booking platform, real-time operations stack, automation engine and purpose-built ERP.
First Technical Lead
Product + Architecture
2016 onward
DOCUMENTED SCALE
30K
Registered clients reported in the 2022 Fairwork Pakistan assessment.
CURRENT FOOTPRINT
6
Cities listed in GharPar’s current FAQ.
01 / CONTEXT
A service business with a technology problem hiding inside it.
GharPar connected women seeking reliable at-home beauty services with trained beauticians seeking safer and more flexible economic opportunity.
When I joined as the first technical lead, operations lived across Google Forms, Sheets, calls, WhatsApp and team memory. Those tools validated demand, but growing volume made coordination fragile.
The real product was not appointment booking. It was operational certainty.
02 / JOURNEY
Architecture evolved only when the business earned the complexity.
2016 — Manual validation
Forms and spreadsheets proved demand before major engineering investment.
2016–17 — WordPress prototype
Coordinated customer and operations surfaces replaced fragmented intake with structured workflows.
2017–18 — Operational platform
Bookings became jobs with skill-aware assignment, schedule projection and durable customer history.
2018+ — Modular services
The proven model expanded into APIs, modern frontends, webhooks and real-time events.
03 / SYSTEM
One booking was really a graph of dependencies.
A request could include multiple services, skill requirements, duration, travel buffers, preferred technicians, equipment, products, payment context and manual exceptions.
Customer intent
Services, location, time, preferences, notes, promotions and payment context.
Orchestration
Job splitting, skills, availability, duration, travel and override rules.
Execution
Assignments, acknowledgements, state changes, support and completion.
Reconciliation
Revenue, worker share, inventory, payroll, reporting and analytics.
04 / EVIDENCE-BACKED IMPACT
Technology became an operating capability.
Public sources use different definitions, so these are milestones rather than a strict cohort series.
1,200+
Clients reported in Lahore in 2017.
10K+
Subscribers documented in the LUMS case.
30K
Registered clients reported in 2022.
The deeper outcome was a shift from person-dependent coordination toward searchable history, repeatable rules, shared operational state and extensible product boundaries.
05 / LESSONS
Scale understanding before scaling architecture.
- The spreadsheet is often the first requirements document.
- Automation should reduce routine decisions without removing accountability.
- Rewrites must inherit accumulated business knowledge.
- Reliability is a product feature.
06 / PUBLIC SOURCES
Evidence used in this case study.
NEED THIS LEVEL OF TECHNICAL OWNERSHIP?