Arjun Dayal
I’m a Senior Product Designer at EverCommerce, designing for software that more than 100,000 business owners use every day. The solutions I design tend to fit within these beats:
Making the product smarter.
I own the end-to-end design of EverCommerce’s AI intelligence layer for customer service: the workflow for tagging at-risk customers and suggesting prompt replies for them, the insights that quantify sentiment and detect when customers are drifting away, and the upcoming auto-reply agent that now takes the first response on itself.
More than 6,000 business owners lean on it every month, and the ones who do reply in less than half the time they used to. I’ve made impact by bringing in new subscriptions and keeping customers who would otherwise have quietly left. Like other projects, if the solution is successful, we white-label the generic component and ship it across other adjacent products.
Fitting into what's already there.
None of that started from scratch. Most quarters, my job is to design something new and embed it in software that has been running for years, with its own patterns, its users’ habits, and engineering realities that don’t move. The AI layer lives inside those products, not beside them.
I’ve come to like that constraint, because it makes me ask what to reuse before I invent anything. I practiced this skill on my own time: a home-style meal subscription designed to live inside Uber Eats, built from its existing system, adding only what the idea really needed. It helps that I love to cook. I care about simple, tasty food, and I wanted ordering it to feel just as simple.
The foundational system is more important than ever.
Building efficiently today takes a design system that acts as the engine. I keep ours as one source across Figma variables, components and the web, maintained with Claude Code. Because Claude Code now builds prototypes and code with that system as its context, any drift gets copied straight into what ships, so keeping it accurate has become a full-time job.
Handbook is where I took the idea furthest. It’s a web app I designed and built from zero, where a variable table and a component library in Figma act as the bill of materials: every colour, size and part is declared there first, and the app is assembled from that list.
- surface
- accent
- 16body size
- 12radius
- Guide card
- Section header
- Export button
Thinking in systems, for music production.
Outside work I produce hip-hop, and I make beats the way I make interfaces so I can release new material every month. I build one master section that holds every layer, then make stripped-down instances of it for each part of the song. The layers stay linked, so changing a sound in the master changes it everywhere it’s used.↗
