Architect, then HCI, then product. London.
Idesignproductsforthemessypart: whereAI,behaviour,andcomplexsystemsmeet.
An architect's training, four-plus years across agency and product design, an MSc in Human-Computer Interaction from Nottingham, and a drawing hand that never went digital-only. I bring research craft to messy product problems, then turn the insight into design decisions backed by evidence.
Currently building Bloooom at Zaltt, and open to the right UX research, product design, and service design work.
Now
Zaltt is my studio: architecture, visualisation, and software, made where the physical and digital meet. Its first product is Bloooom, a local AI server that lets an architecture practice's whole design team visualise ideas in their own style, with nothing ever leaving their building.
Why a designer builds infrastructure: because the practices that need AI most are the ones whose NDAs forbid the cloud version of it. Design is deciding where the server goes, too.
Selected work
Service design at enterprise scale, AI product design under academic rigour, a self-initiated product, and years of agency delivery. Three are written up in full; open any of them.
Agency UX · Ecour Studio
Led UX across 10+ projects: research, interaction design, and delivery. Two design awards, 35% client conversion improvement, and a 30% average engagement lift across the portfolio. Client work sits under NDA; happy to walk through it on a call.
Process
Three habits, carried from architecture into product. They are boring on purpose; the drama belongs in the outcome.
I design at three altitudes: the organisation, the journey, then the screen. Screens drawn before the system is understood are decoration. This is the architect in me; you survey the site before you draw the door handles.
Explore the problem broadly before committing to one framing, then explore answers broadly before committing to one design. Most bad products skipped the first diamond: a beautiful answer to the wrong question.
Every design decision points at something: an interview, a test, a number. Then it ships, gets measured, and the loop runs again. Taste starts the argument; evidence ends it.
About
I trained as an architect in India, and kept noticing that the hardest problems were never the buildings. They were the people using them, and the tools everyone suffered along the way. That question took me to an MSc in Human-Computer Interaction at Nottingham, and from there into product.
Architecture, cooking, and interfaces are one discipline to me: constrained material, a decision about how to treat it, and a result a stranger lives inside. I still render by hand. I make espresso badly but with growing conviction. And I believe the maker should disappear into the work, which is why my studio is named after salt.
Roles, research collaborations, commissions, or a conversation about local AI in the built environment.