From product brief
to production in 12 weeks.
A hands-on product, design, and engineering team for funded startups with a real release to ship.
Recent product builds.
Building a public price layer for India’s rental market.
Building Tirch’s end-to-end commerce engine.
How twelve weeks move.
- WEEKS 01–0201
Scope the release.
Decide what ships and what does not.
- WEEKS 03–0502
Design the core flows.
Resolve the product before polishing the edges.
- WEEKS 06–1003
Build the product.
Review working software every week.
- WEEKS 11–1204
Launch and hand over.
Ship, observe, stabilise, and leave a clear next move.
The 12-Week
MVP Build.
One hands-on product, design, and engineering team owns a sharply scoped release from the first decision to production.
The twelve weeks begin after scope and commercial terms are agreed. Anything that cannot responsibly fit is surfaced before kickoff.
The people in the room stay on the work.
Userhood was built around a simple operating decision: product design and engineering should share the same release, the same constraints, and the same accountability.
The founders remain involved in product direction and delivery. The wider team is compact by design, so context does not disappear between a sales conversation and the build.
Kriti
Co-founder · Design and Product Engineering
Ashwin
Co-founder · Product and Experience
Twelve weeks
from now,
what is live?_
If the problem is real, the decision-maker is in the room, and the first release can be sharply scoped, we can turn the next twelve weeks into a working product.