We started this studio in Bangalore fifteen years ago, long before "design agency" meant much beyond making things look nice for a brochure. Since then we've worked with founders building their first product, with scale-ups trying to hold a brand together across five countries, and with enterprise teams untangling decades of accumulated complexity. A few things kept showing up across all of it, and they're worth writing down.

Good design means something different depending on who's asking

Early in the studio's life, we worked with a founder who wanted his product to look as polished as the big global players he was competing with. What he actually needed, we realized a few weeks in, was the opposite. His users were price sensitive, using patchy internet connections, often on their first smartphone. A beautifully animated, heavy interface would have worked against him, not for him. The right design decision was to strip things down, not dress them up.

Compare that to an enterprise client we worked with years later, a company whose internal tools hadn't been touched in over a decade. Employees had built an entire culture of workarounds, sticky notes on monitors, spreadsheets bridging gaps the software didn't cover. There, good design wasn't about being clever or minimal. It was about respecting years of institutional muscle memory while still making the tool usable for someone joining the company today.

Neither of these projects would have benefited from the other's approach. The lesson wasn't a specific style or trend. It was that good design is a response to a specific set of constraints, and assuming those constraints are the same across every client is the fastest way to produce something technically polished and practically useless.

Working across contexts forces a kind of honesty

Working with founders taught us to be direct, because founders rarely have the patience for anything else. If a design decision isn't going to move the needle on their actual metrics, they want to hear that plainly, not wrapped in a deck full of jargon.

Working with large, established organizations taught us a different kind of honesty, the willingness to say that a problem isn't really a design problem at all. More than once, a brief that came in as "our app feels outdated" turned out, after a few weeks of digging, to actually be an organizational problem: three teams building competing versions of the same feature because nobody owned the decision of which one should exist. Fixing the visual design wouldn't have touched the real issue.

Being honest about that, even when it means telling a client the fix isn't the one they asked for, has mattered more to how our client relationships have held up over the years than any single piece of visual work we've delivered.

What global brand work taught us about local nuance

Working with brands that operate across multiple countries, including several headquartered outside India, taught us something we didn't expect starting out: nuance travels better than polish.

A campaign built around a clever visual metaphor might land perfectly in one market and mean nothing, or worse, mean something unintended, in another. We've had to unlearn assumptions about color, humor, and even something as simple as reading direction and layout hierarchy, more times than we can count. Being based in Bangalore, working with clients across very different markets, forced us to build a habit of checking assumptions rather than defaulting to whatever felt familiar to us personally.

That habit turned out to be useful everywhere, not just for genuinely international work. Even within a single country, assuming your own context is universal is a quiet way to alienate part of your audience without realizing it.

What hasn't changed in fifteen years

Tools have changed dramatically. What we design for has changed too, from static websites to apps to dashboards to whatever comes after these. But a few things have stayed constant across every single project we've worked on, regardless of size or industry.

Clarity still beats cleverness almost every time. A client who can explain in one sentence what a product does and who it's for will almost always end up with better design than one who can't, no matter how good the agency is. And design work that isn't grounded in a genuine understanding of the people using it eventually gets found out, no matter how well it photographs in a portfolio.

Why this still matters to how we work today

None of this is meant as a nostalgia piece. It shapes how we take on new work today. When a startup comes to us, we're not trying to make their product look like the enterprise brands we've worked with. When an enterprise client comes to us with a legacy system, we're not trying to force a startup's speed and informality onto an organization that runs on different rhythms.

Fifteen years in, the biggest thing we've learned is that a good design partner isn't one with a single signature style they apply everywhere. It's one who's spent enough time across different contexts to recognize which constraints actually matter for the problem in front of them, and design accordingly. That's the version of this studio we've built, and the one we intend to keep building.