This project reinforced several ideas about building and improving service products:
01 — Service products are more than interfaces.
The real experience is shaped by how product, operations and partners work together, not just by what the screens look like.
02 — Visibility can itself be a product intervention.
Making the journey more visible to customers and partners can reduce anxiety and support load, even before adding new features.
03 — User research can expose operational problems.
Talking to partners and clients, and comparing their accounts with system data, can reveal gaps that are not visible from dashboards alone.
04 — Fix foundations before optimising retention.
Retention work is fragile if core reliability and experience issues remain unresolved.
Overall, this case study is less about owning a single feature and more about contributing to a series of grounded, rapid interventions within a complex service environment.
What I learned
A longer-term assignment focused on understanding why customers were not subscribing again.
The core product question was:
Why customers weren’t subscribing again?
In practice, this investigation could not progress meaningfully. Multiple upstream product and operational breakpoints were still present, and company restructuring added further constraints.
A key learning from this work was that retention can be a downstream symptom of more fundamental experience and reliability problems. In this case, it would have been misleading to claim that retention was “solved.”
PYNC
Product Management Intern : September 2025 - December 2025
Pync was a service marketplace connecting customers with local partners for home and everyday services such as cleaning, gardening and car washing, starting with Bangalore.
I worked as one of three Product Management interns under a Product Manager, collaborating with operations and sales on partner and client journeys, service reliability and product improvements.
The Problem - Where the experience was breaking
Book → Assign → Travel → Arrive → Service
Partners were sometimes reaching customers late, creating service delays and support issues.
The core service journey looked like this:
Book → Assign → Travel → Arrive → Service
The problem sat at the intersection of customers, partners, the platform and operations. It was not only an interface problem — it involved how assignments were made, how information flowed, and how operations responded when things went wrong.
Understanding what was happening on the ground
23
7
30
partners interviewed
clients interviewed
users in total
Conversations with partners and clients helped identify journey pain points and operational friction across the service flow.
In addition to interviews, access to admin-panel and operational data helped surface discrepancies between system records and actual partner activity. For example, some partners were marked absent in the system despite actually working.
These observations were documented and escalated to the relevant teams rather than treated as issues independently solved.
The problem wasn’t only “late partners”
On the surface, the issue looked like partners simply arriving late.
Looking closer, the service journey lacked enough visibility for customers and partners to understand where the service stood at any moment.
This uncertainty showed up as questions like:
• Where is the partner?
• When will they arrive?
• Has the assignment actually happened?
The lack of clear, shared visibility created anxiety for customers, pressure for partners, and extra load for support and operations.
Decision - Three rapid product interventions
3 UX improvements implemented within 24–48 hours
01 — Partner allocation
Proposed assigning partners within a 5-km radius to reduce unnecessary travel distance and make arrival times more predictable.
02 — ETA visibility
Proposed giving customers clearer visibility into expected arrival time so they had a better sense of when to expect the partner.
03 — Partner tracking
Proposed tracking partner movement so that customers and operations had more clarity on where the partner was in the journey.
Once the key problems and interventions were identified, we focused on moving quickly.
The changes were implemented rapidly in collaboration with the relevant team, following a simple flow:
User research → Problem identified → Intervention proposed → Implemented
I contributed by surfacing observations, framing the problems, and proposing interventions, while implementation was done in partnership with the broader team. I do not claim independent ownership of the entire product or technical implementation.
These were framed as product interventions to improve service reliability and visibility, not as solutions that fully resolved every operational problem.
-
Fewer customer complaints and support issues around partner delays and arrival uncertainty.
-
Better visibility into partner location and expected arrival time, reducing uncertainty for customers.
-
Fewer issues caused by partners being delayed in traffic without clear visibility.
-
More accurate operational tracking, with partner activity better reflected in the dashboard instead of being incorrectly marked as absent.
-
Better alignment between actual partner activity and system records, improving operational reliability.
Impact - What changed
Beyond immediate service reliability work, the three Product Management interns were also tasked with supporting Pync’s expansion into other states.
This included helping to shape hiring pipelines for:
• Private chefs
• House helps
The work involved creating structure around the hiring pipeline as Pync explored expansion. However, this expansion work remained incomplete because of company restructuring, and should not be read as a finished expansion initiative.