Orvitt
A relationship management platform built end to end in 10 days.
Where they were stuck.
Orvitt existed as a conviction and a Notion doc. The founders knew what it needed to do — a relationship management platform for people who find CRMs too transactional and notes apps too unstructured — but they had no product, no timeline, and no clear path to having one.
The standard approach would have been a discovery phase, then wireframes, then a design sprint, then a development sprint, then a beta. That timeline runs four to six months and costs accordingly. For a two-person team at the idea stage, it's effectively a no.
The actual constraint wasn't resources. It was speed. Every week without a live product was a week they couldn't learn anything real. They needed something in front of users that worked — not a prototype, not a beta with caveats, a real product.
What I built.
I scoped the MVP to the one thing the product had to do exceptionally well: let someone capture a relationship context in under thirty seconds and resurface it at exactly the right moment. Everything that didn't serve that core interaction got cut.
Design and build ran in parallel, which is only possible when the person making the design decisions is also making the build decisions. There's no handoff cost, no revision cycle between disciplines, no waiting for one track to unblock the other.
The data model was the hardest decision and the most important one. Relationship management products fail when the data model doesn't match how people actually think about relationships. I spent the first two days on that structure — the rest of the build followed from it cleanly.
By day seven, the core interaction was working. Days eight through ten were reliability, edge cases, and the onboarding flow. The onboarding flow is where most products lose people in the first session; it got as much attention as the core features.
The product shipped on day ten. Not 'shipped to beta users.' Shipped to real users, with real pricing, with payment processing live.
What happened.
Orvitt was live and taking real payments on day ten. The founders had a product they could show, a URL they could share, and actual users within the first week of launch.
$10,000+ MRR within the first few weeks. That number matters not just as a revenue figure but as proof that the scoping was right — people paid for the thing we built, which means we built the thing people would pay for.
The 10-day timeline became part of the product story. In a category full of tools that have been in development for years and still feel unfinished, 'built in 10 days and generating revenue' is a differentiated narrative. It also set a pace expectation with the founders about what's possible when the constraints are right.
Got something like this?
Send it over.
I'LL GET BACK TO YOU IN A FEW HOURS.