👋Hi, I am Swanand

Building is almost free.
Owning is not.

AI and modern tools make it trivial to ship code in an afternoon. But the real cost comes after: the maintenance, support, and cognitive drag of carrying features nobody actually uses.

Here I share essays on product strategy and offer open 30-minute virtual coffee chats to help founders and PMs pressure-test what to build (and what to cut).

About

A bit about me

Connect on LinkedIn →

I've spent nearly two decades building products. I've built from scratch, untangled bloated systems, and learned from plenty of mistakes along the way. I value simple solutions, straight talk, and cutting through the noise. Just like every PM, proudly a master of being a jack-of-all-trades. :)

What I care about

0-to-1 Discovery & What not to build

Finding the smallest, sharpest version of an idea before teams burn months building in the wrong direction. Validating real customer problems early, pressure-testing assumptions, and having the discipline to say no.

Taking Products Beyond Prototypes

A working demo takes an afternoon, but a demo is not a product. Getting past the perpetual proof-of-concept phase means tackling the non exciting realities: reliability, data integrity, user habits, and sustainable economics over the long run.

Sunsetting Product Zombies

Products fail less from a lack of features but more for carrying too many. I enjoy talking about Product zombies why they exist and how to live with them (or not!)

Community, Mentorship, and the Human Side of Tech

Product is ultimately about people. I founded and organize ProductTank Heidelberg (a local community of 600+ product builders and founders), and I love coaching early-career PMs to help them build strong product intuition and navigate their careers.

Outside of product

When not thinking about product, I get lost in Ancient Indian civilization. Fun fact: Acharya Pingala discovered the “Fibonacci” sequence roughly 1,400 years before Fibonacci got credit for it.

Observations

Six common traps I see teams hit

Patterns observed repeatedly across startups and scaleups. Solvable early, but increasingly painful the longer they linger.

01

Activity looks like progress

A working prototype takes an afternoon, so output feels substantial and teams grow attached. The real question, which customer outcome did this move, goes unasked.

02

A roadmap full of zombies

Features with ghost-town usage that are too small to matter and too awkward to delete. They eat maintenance, support and screen space while real priorities wait.

03

AI projects stuck in R&D

Perpetual PoC zombies that are always one model away from perfection, trapping your scarcest AI and data talent without ever reaching customer value.

04

Treating new features as the only growth lever

When adoption slows down, teams default to shipping more capabilities instead of asking why users abandon the existing ones. The result is a bloated product that does twenty things poorly.

05

Stakeholders who will not let go

Sales leans on it in the pitch, legacy code depends on it, or someone senior built it. Emotion beats data and the zombie survives another quarter.

06

Nobody to pressure-test the idea

Founders and PMs often lack a candid, external sounding board. What is missing is an experienced product peer to talk through trade-offs before engineering cycles are spent.

Recognise two or three of these in your product?

Have you run into these traps in your own teams? How did you navigate or solve them? I am always curious to hear stories from the trenches and how different teams tackle zombie features and AI trade-offs.

Essays

Essays and field notes

☕Virtual Coffee

Let us grab a 30-minute virtual coffee.

Whether you are an early-stage founder weighing an MVP trade-off, a PM dealing with feature bloat, or just want to chat product, pick an open slot that fits your schedule.

Grab a 30-min virtual coffee