The work, written down.
Notes on what we've built, the decisions behind it, and why. We write when we've worked something out, not on a schedule. It is an archive, not a running log.
Start here puts the posts grounded in something specific first: our own products, a named place, or a cited source. The shorter studio notes follow, newest first. Stories come out of Trinetra and Urban Hood. Blog posts are shorter notes on how we work.
Why we still build our own apps while taking client work
Most studios stop building their own products the moment client work pays the bills. We think that's exactly when you should keep building them.
The case for building where you live
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.
Why we chose hyperlocal over broad reach for Urban Hood
We could have built a generic community app for everywhere. We built one for one neighborhood instead.
What connectivity constraints taught us about offline-first design
Most products treat a spotty connection as an edge case. We think that's backwards for anywhere outside a handful of tech hubs.
Designing for Nashik, not a generic Indian market
"The Indian market" isn't a design brief. It's an excuse to skip the hard part.
Why we built Trinetra
Nashik hosts one of the largest gatherings on earth. That's where the idea for Trinetra actually started.
How we think about pricing a project
Cost depends on scope, integrations, and how much is still unknown. Here is how we get from your idea to a real number.
Red flags when hiring a product studio
The warning signs usually show up before the contract, not after. Most founders just don't know to look for them yet.
What a good studio engagement actually looks like
Most studio engagements fail quietly, in the gap between what was promised and what was actually communicated. Here's how we try not to.
What 'ship and tend' really means after launch
Launch day is the easiest part of the process to get right and the easiest one to mistake for the finish line.
The unglamorous work before the first pixel
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.
Why we cut scope before we design anything
Most teams design first and cut scope when the deadline forces them to. We do it in the other order, on purpose.
Notice, Focus, Craft, Ship: how we actually run this
Four words won't tell you how a studio actually works. Here's what each one means when the deadline is real.
Next step
Have something to build?
Tell us about the idea, the deadline, or the mess you’re in. We read every message and reply ourselves.