Find the problem
Every product starts with something that keeps going wrong — usually for us first. We sit with it long enough to know whether it is worth years, because that is the commitment a product actually is.
/ Inside PRISP
A small team in Gurugram building its own software. The people who decide what to build are the ones who write it, ship it and answer for it afterwards.
PRISP exists because the software we wanted to use kept not existing. So we build it ourselves, put our name on it, and stay with it — the engineers who choose what to build are the ones who write it and the ones who answer for it at 2am.
We build one thing at a time. That is the whole trade — depth over spread — and it is why the product keeps getting better long after the version anyone would have called finished.
Today that means Learners.Center: a browser-based platform where people learn to code by writing real code, now carrying 45 courses, 800 lessons, five playgrounds and an AI tutor that answers in thirteen languages. We run it, support it and keep shipping to it. Tomorrow there will be another problem worth the same commitment.
/ How we work
We choose the problem
No brief arrives from outside telling us what to build and when to stop.
Nobody hands us a specification. We pick what to build from what we keep running into ourselves, and we answer for whether it was worth building.
Production from week one
No throwaway prototype, because there is nobody to hand it to afterwards.
The first thing we ship is a narrow slice of the real product — tested, deployed, running against real data. Whatever we cut corners on, we are the ones who meet it again later.
We ship narrow, then stay
No launch treated as the finish line, and no version we walk away from.
A launch is where the work starts being useful, not where it ends. The interesting decisions arrive in year two, once people have shaped their week around it.
Usage decides, not opinion
No feature kept alive because somebody senior liked the idea of it.
What people actually do in the product settles arguments here. Ideas that nobody uses get removed, including the ones we were fond of.
What is actually running today, inside Learners.Center. These numbers move as the product does.
- Courses published
- Short lessons
- Career paths
- AI tutor languages
011 / 4 022 / 4 Build the narrow version
One slice of the idea, built properly rather than sketched. Real code, real data, deployed — small enough to throw away if it turns out we were wrong about the problem.
033 / 4 Put it in front of people
Usage settles the argument. We watch what people do with it, not what they say about it, and we cut the parts nobody touches — including the ones we liked.
044 / 4 Keep it alive
Launch is where the work starts being useful. Monitoring, fixes, and the changes that only make sense once people have shaped their week around the thing.