The Team
Four people. One sprint.
No committee, no roadmap theatre. A small crew in Bengaluru, India building the tool we wanted to use — and running it on itself.
The Dreamer
It started as a whiteboard rant about ceremony — the standups nobody needed, the boards nobody read. Somewhere between the third rewrite and the first real sprint, the rant turned into a product with a schema, a cooldown timer, and a strong opinion about what a team actually needs. Still sketches the next thing before the current one ships.
The Closer
Lives in the last ten percent — the part everyone else already calls done. Chases the edge cases, the empty states, the error that only shows up on a slow connection at 2am. If a feature is in your hands, it's because it survived a review that assumed you'd try to break it.
The Craftsman
Notices the four pixels of misalignment, the transition that's forty milliseconds too slow, the label that reads fine until you actually think about it. Believes the gap between a tool people tolerate and one they trust is a hundred small decisions nobody is supposed to see — and makes all hundred.
The Catalyst
Breaks things on purpose so production never gets the chance. Writes the test that fails first, stages the deploy that flushes out the assumption, asks the 'what if two people do this at once' question before it becomes a support ticket. Chaos, but scheduled.
How we work
We run the product on the product.
One active sprint. A cooldown before the next. Every change on the record. If a rule feels strict in the app, it's because it felt strict for us first.