drag me
simple, at last.
Muhammad Fatheen
Chennai, India Open to Associate PM rolesSimple is the last thing a product becomes.
I’m a Product Management Intern at Zuper, a B2B field-service platform. I studied Computer Science and Engineering at Sathyabama Institute of Science and Technology, co-founded an ironing service called Wrinkl, and now spend my days finding where people get stuck and deciding what is worth building.
Case studies
3 · open one for the summarythree last miles,
one decision each
Google MapsThe last 100 metres
Maps gets the rider to the building. The handover still starts with a phone call.
Product case study
- Target user
- Delivery riders arriving at gated complexes and buildings with several entrances, and the people receiving the order.
- Pain point
- Maps ends the trip at the building, not at the right gate, so the handover starts with a phone call and a walk around the complex.
- Gap
- Maps can show where entrances are, and Address Descriptors describe the area. Neither says which entrance to use for this delivery, and delivery apps only receive a point on the map.
- Solution
- The receiver confirms the delivery entrance when they share a location. The rider is guided to that gate, and delivery apps receive it through the Maps Platform.
- North Star
- Time from arrival to handover, for the slowest 10% of deliveries
- Guardrails
- Time to share a location, wrong or unsafe entrances, and privacy reports
Inside the case
- Market sizing
- RICE
- Partner model
- A/B test design
- North Star metric
- Now, Next, Later roadmap
Chennai MetroThe ride home after a match
Paying for the metro is solved for regulars. It breaks at the busiest moment: everyone leaving a match at once.
Field teardown
- Target user
- Fans leaving a big match at Chennai Central, especially first-time riders without a ticket on their phone.
- Pain point
- At the busiest moment of the night they queue twice: at the ticket counter, then again at the gates.
- Gap
- Paying is solved for regular riders through WhatsApp and app QR tickets. Event nights are not, except for sponsored IPL rides.
- Solution
- Make the match ticket the metro ticket wherever a sponsor pays; otherwise send a "book your ride home" link with every big-event ticket.
- North Star
- Share of post-match riders who enter without visiting a counter
- Guardrails
- Failed QR scans at the gates and cost per event
Inside the case
- Queue model
- Benchmarking
- RICE
- Metrics
- Roadmap
WrinklIroning, ordered on WhatsApp
Ironing is a small chore with a large coordination cost. Could it be as easy to order as anything else?
Early-stage venture
- Target user
- Households who iron every week or need a batch at short notice, and the neighbourhood dhobi shops that would do the pressing.
- Pain point
- Ironing is a weekly chore with a coordination cost: finding a shop, arranging pickup and return, and guessing the price.
- Gap
- Quick commerce reached food and groceries, not ironing. Local shops can press fast, but none of them collect and deliver.
- Solution
- Ironing only, ordered on a WhatsApp bot, with Wrinkl handling pickup and return in booked slots and the price shown before you confirm.
- North Star
- Orders returned pressed, on time, each week
- Guardrails
- Re-press requests and delivery cost per order
Inside the case
- Field research
- PRD
- MoSCoW
- Unit economics
- AARRR funnel
- Given / When / Then
Second runner-up at IEEE YESIST12 2025. Prototype and WhatsApp bot built; the vendor trial never started, so there are no customer results to report.
Experience
4 roles
ZuperProduct Management InternJul 2026 – Present
B2B SaaS · Field service management
Software that businesses use to coordinate jobs, people, customers and operations in the field. Product changes have to respect existing workflows and the very different people who use them.
How a piece of work moves
Find where the product falls short of how customers actually work, and look into new product areas.
What comes outA written finding
Compare how others solve it, weigh the user and product trade-offs, then write requirements, UX flows, user stories and acceptance criteria.
What comes outRequirements engineers can build from
Work with product managers and engineers in Agile cycles, from discovery through to build.
What comes outTickets that say what was decided
What it has taught me
In an established product, every change lands on something people already depend on. Research earns its place when it explains a trade-off, and requirements get better when engineers and product shape them together.
Tools
- Linear
- Slack
- PostHog
- Microsoft 365
Described at a public-safe level. No internal screenshots, customer data or unreleased details.
WrinklCo-founder / Product BuilderJan 2025 – Oct 2025
Early-stage venture · Quick-commerce ironing
Could a familiar offline service become as easy to order as any on-demand service, and what has to be true behind the screen for that promise to hold?
- Owned the research, product decisions, pricing and build end to end.
- Led development of an ordering platform with a WhatsApp bot to simplify customer orders.
- Researched the market end to end: existing apps, laundromats, an equipment maker, online surveys and conversations with people in the trade.
- Spoke with local dhobi shops to set up a trial. They could offer quick service but not delivery.
- Placed second runner-up at IEEE YESIST12 2025 in Malaysia.
- The trial never started, so there are no customer or order results to report.
- WhatsApp Business API
- Postman
- Supabase
- ChatGPT
- Claude
- Gemini
TechKnotsMERN Stack Development InternMay 2025 – Jul 2025
Internship · Web development
A software internship building customer-facing web modules with the MERN stack.
- Developed and improved customer-facing web modules using the MERN stack.
- Integrated WhatsApp Business APIs for customer communication: chat, images and order updates.
- Helped with debugging, testing and bug fixing across development cycles.
- MongoDB
- Express
- React
- Node.js
- WhatsApp Business API
Chennai Publishing ServicesUI/UX Design InternMay 2024 – Jun 2024
Internship · Design
A short design internship that taught me to turn written requirements into consistent, user-focused interfaces.
- Designed web pages, company posters and digital assets in Figma.
- Iterated on UI layouts based on feedback and delivered marketing assets.
- Figma
What I practise
eight methods · click one to see where I used itno skill listed
without a receipt
Toolkit
what I reach for every weekProduct6 tools
- Figma
- Linear
- Notion
- Slack
- Microsoft 365
- Google Workspace
AI3 tools
- Claude
- ChatGPT
- Gemini
Prototype & measure3 tools
- Lovable
- Postman
- PostHog
Hello there !
- I started by building software. Then I got more interested in why things get built than in how.
- Wrinkl taught me the operational side of product. For eight months I researched, priced and prototyped an ironing service. The trial never ran, and I say so wherever it matters.
- At Zuper I work on a product people already depend on. Every change lands on an existing workflow, so research has to explain a trade-off, and requirements get better when engineers shape them too.
- I believe simplicity is a decision. Most of my work is making it.
Writing
short notes from real work · click to readLines I keep coming back to
borrowed,
but lived
“If you are not embarrassed by the first version of your product, you’ve launched too late.”
“The essence of strategy is choosing what not to do.”
“The most important thing in communication is hearing what isn’t said.”
“Your most unhappy customers are your greatest source of learning.”