Vinay Débrou
Spending your 6 months runway building the wrong-product?
You can build many versions with AI. Fast & Cheap. The hard part is judging which one will users pay for. How many users have you listened to?

Vinay Débrou
Founding Product Designer
CS, IIT Kanpur
Focus
product shaping, prototyping & testing
Experience
5 years
Based in
chandigarh / remote
Teams I have worked with
Founding teams, consumer products, crypto, health, and research.
Right before the build
You & the team are ready to build. The product is still a moving target.
I work best with technical founders who can build or are already building. The question is what should actually get built before a good engineering team turns the wrong assumptions into months of code.
The goal is not a prettier Figma file.
A reality check from your target users. A product decision you can stand behind before you ask the team to build it.
Product Craft
Once the direction is right, we make the design tight.
Before the code gets expensive
The decisions I like to make while they are still cheap to change.
Make the product clear
Turn the idea in your head into a concrete product: who it is for, what they do, and what matters first.
Test the risky part
Prototype the part you are least sure about, put it in front of people, and see what breaks before engineering does.
Give engineering a target
Core flow, states, edge cases, priorities, architecture — enough clarity that nobody is guessing what done means.
A few products I have helped figure out
Different products. Same job: make the important decisions before they get expensive.
Start here
Need help iterating to PMF?
Send me the messy version. A deck, a sketch, a Loom, a rough prototype — whatever you have. We can work out what is still unclear before it turns into months of code.
Send me the current version for a free audit→

























