A design system studio in Bangalore, building the shared foundations product teams ship on, wherever they are.
Layer One was started by Aniket Pandey after six years inside design systems teams: first at IBM in Bangalore, then leading the CARS24 design system through a rebrand across three countries, and now on the design systems team at JPMorgan Chase.
The same problems came up everywhere. Teams didn't need another component kit. They needed decisions that hold across products, a way to run the system without becoming a bottleneck, and a reason for people to use it. That's the work Layer One exists to do, and it's the only work we do.
Experience from
founder
Aniket Pandey
Founder, Layer One. Bangalore, India.
A designer who has spent most of his career on design systems, and who is comfortable close to code. He runs office hours, workshops and mentoring for designers new to systems, and writes about governance and tokens.
JPMorgan ChaseSenior Designer, Design Systems, 2025–now. Patterns used across the company, an AI workflow that drafts new patterns, and tools that check design files and code against the system.
CARS24Design Systems Lead, 2024–25. A system for 60+ designers and 100+ engineers across 10+ products; new palette and tokens for the rebrand; governance; pattern library. System Architect Award.
IBMUX Designer, 2021–24, Bangalore. Built and launched design systems for products used worldwide; contribution process, releases and training.
what we do
- Design system audits01
- Token architecture02
- Colour systems and accessibility03
- Core component libraries04
- Multi-brand and multi-market theming05
- Pattern libraries06
- Documentation07
- Governance and contribution models08
- Design and engineering workflows09
- Design system checks and tooling10
- Team workshops and training11
- Adoption measurement12
How each engagement works, step by step: design system services.
how we work
- Small and senior. The person on the first call does the work.01
- We work in your Figma files and your repository, not in a separate deck.02
- Every engagement starts with an audit, so we fix what matters first.03
- Weekly demos and written decisions, so nothing is a surprise.04
- Fixed prices and fixed timelines. No hourly billing.05
- We leave documentation and a governance model your team can run alone.06
working with teams worldwide
Bangalore is where we're based, not where we stop. Most of the systems behind this studio served products in several countries, and studio engagements run remotely with teams anywhere.
- United States8–10am Eastern is 6:30–8:30pm in India. We keep those hours free for calls and reviews.
- UK and EuropeMost of your morning overlaps our afternoon, so a daily check-in is easy.
- Gulf and Middle EastAlmost the whole working day overlaps. Experience with Arabic and right-to-left systems.
- Asia-PacificSingapore and Australia afternoons overlap our morning; India is home.
- Contracts and paymentFixed prices in US dollars, invoiced from India, with a written scope before any work starts.
- Async by defaultWeekly demos, written decisions and a shared channel, so progress doesn't depend on meetings.
invitation
Founding partners, 2027.
We're choosing three teams to be Layer One's first studio partners. You get 20% off any engagement and a senior team that treats your system as its flagship. We get to publish what we build together.


