Why we still build our own apps while taking client work
Many studios stop building their own products the moment client work pays the bills. We think that's exactly when you should keep building them.
Studio
How we build, what our own apps teach us, and how we work with clients.
Follow via RSSMany studios stop building their own products the moment client work pays the bills. We think that's exactly when you should keep building them.
Studio
We didn't set out to build two apps. We set out to fix a gap we felt ourselves living in, and the products followed.
Studio
We could have built a generic community app for everywhere. We built one for one neighborhood instead.
Our products
Launch day is the easiest part of the process to get right and the easiest one to mistake for the finish line.
How we work

"The Indian market" isn't a design brief. It's an excuse to skip the hard part.
Our products

Nashik hosts one of the largest gatherings on earth. That's where the idea for Trinetra actually started.
Our products
Most products treat a spotty connection as an edge case. We think that's backwards for anywhere outside a handful of tech hubs.
How we work
Most studio engagements fail quietly, in the gap between what was promised and what was actually communicated. Here's how we try not to.
How we work
Cost depends on scope, integrations, and how much is still unknown. Here is how we get from your idea to a real number.
Pricing
Every product we build starts with work that produces no visuals at all. Skip it and every later decision is a guess dressed up as a choice.
How we work
The warning signs usually show up before the contract, not after. Most founders just don't know to look for them yet.
How we work
Four words won't tell you how a studio actually works. Here's what each one means when the deadline is real.
How we work
Most teams design first and cut scope when the deadline forces them to. We do it in the other order, on purpose.
How we work