Dilith Dinesh
Product operator at the boundary between
customer reality and product systems.
Three clicks. You're either very bored or very thorough. Either way — hello.
I translate what breaks in the field into
capabilities that scale.
Currently: Customer Product Manager at Zuper —
built the roofing vertical from zero.
Zuper · Field Service Management · B2B SaaS · Built the roofing vertical from 0 to 1 · Chennai
Most product teams learn about customer problems through tickets, NPS scores, and quarterly reviews.
I've spent two years inside the operational layer — sitting with contractors, mapping how they actually collect money, watching where workflows break before anyone files a bug report.
That proximity changes how I think about product decisions. Not every problem needs a feature. Not every feature request is the actual problem. The real work is finding the gap between what people say they want and what would actually help them.
That's the kind of product thinking I'm building toward.
Work
Not success stories. Decision logs.
ZUPER · FIELD SERVICE · VERTICAL BUILD
The Roofing Vertical
The roofing vertical at Zuper didn't exist. No architecture, no repeatable process, no foundation for the product to grow on. I built it — from first discovery call to cloneable system.
Read the case study →
ZUPER · FIELD SERVICE · PRODUCT JUDGMENT
The Stopgap That Knew Its Place
Roofing customers needed booking before the product roadmap was ready. I built the interim solution — and designed it to be replaced.
Read the case study →
Writing
Product teardowns, field notes, and frameworks
from the boundary between operations and product.
JAN 2026 · TEARDOWN
What B2B SaaS Can Learn From India's Fastest-Growing Mobility App
Rapido nailed the habit loop. But they're still optimizing for the ideal user — not the actual one.
Read →
DEC 2025 · TEARDOWN
How Spotify Turned Usage Data Into an Annual Identity Ritual
Most imitators copy the format. They miss the emotional architecture underneath.
Read →
Projects
Things I built because the problem
was real enough to solve.
2026 · REACT 18 · TYPESCRIPT · SUPABASE
Iris
I work across four devices. Every day I need to move something between them — a screenshot, a file, a link. Every existing solution added friction I didn't want. So I built one.
2025 · B2B SAAS · LOVABLE
Pulseboard
A colleague asked what I'd been working on lately. I blanked. Not because I hadn't done enough — but because scattered work doesn't accumulate into a narrative on its own. So I built one.
If you're building something that needs this
kind of thinking — let's talk.