Design systems & ongoing support
Reusable interface components, design guidelines and continued design support as your product evolves. For teams whose product has grown screen by screen and needs one system, and for products that need a designer after the launch.
What we do
- An audit of the existing interface and its inconsistencies
- Foundations: typography, colour, spacing and grids
- Components with states and variants
- Patterns for forms, tables and dense data
- Documentation for designers and developers
- New features and screens designed on the system
Deliverables
- A Figma library of foundations, components and patterns
- Guidelines with rules and examples
- Specifications and notes for the developers
- Regular design work on new features, while support continues
How we work
- 1. Audit: the current product, its screens and components
- 2. Foundations: type, colour, spacing and grids
- 3. Components: states, variants and patterns
- 4. Support: new features designed on the system, and the system kept up to date
Ways to work
- A fixed price for a defined scope: an identity, a website, the first version of a product
- Hourly work for open-ended tasks and changes
- Ongoing support for a product that keeps growing
- To start, send a brief: we talk, and you get a proposal with the scope, timeline and price
Questions
Can you build a system for a product that already exists?
Yes. Elma starts from the screens the product already has and turns what repeats into one set of components and rules.
How does ongoing support work?
Elma stays with the product after the launch and designs new features on the same system. Re:Staffy was two years of work, from the MVP to a commercial product.
Who does the work?
Elma’s own team: designers and developers led by Andrey Zhikalov, the studio’s founder and design director. The same team works on your project from the first brief to the launch.



