Web design, drawn to be built.
Most design goes wrong at the handover, when a drawing meets the person who has to make it real. We skip that step. Alexandra draws the screens, Dmitrii builds them, and the two of them sit at the same table.
Four things, every project
The same deliverables whether the project is a five-page site or an app with an admin panel behind it. The size changes; the list doesn't.
Product and interface design
Every screen the product needs, drawn at the size people will actually use it. Not a mood board and not a homepage mockup: the empty states, the error states, the long forms and the boring admin screens that decide whether the thing is usable on a Wednesday.
Design systems and tokens
Colour, type, spacing, radius and shadow defined once as named values, so the fortieth screen looks like the first one without anyone policing it. This site runs on exactly that, and so does everything we hand over.
Clickable prototypes
Real screens wired together so you can move through the flow before any of it is built. Finding out a step is wrong costs an afternoon here. Finding out after it ships costs a sprint.
Responsive and accessible by default
One layout that works from a phone to a wide monitor, with contrast, focus states and keyboard paths handled while the screens are being drawn rather than patched in afterwards.
The drawing and the build are the same job
A design that nobody has to build can promise anything. It can assume the list is always short, that the name always fits, that the image is always there. Then it reaches a developer, who finds out otherwise and quietly changes it, and the thing you approved is not the thing that ships.
Because the person drawing it knows what the database can return, that gap closes before it opens. Empty states get designed because we know the list starts empty. Loading states get designed because we know the request takes time. It is a short list of small things, and it is most of the difference between a product that feels considered and one that feels close.
See how we build it, or read the four phases a project moves through.
Things people ask before starting
Can we hire you for design only?
Yes. You will get the screens, the prototype and the design system as files your own developers can build from. Most people come to us wanting both halves, but the design on its own is a real thing we sell.
Who actually does the design work?
Alexandra, every time. There is no junior doing the first pass and no one else to hand it to. She taught herself design and went through Google’s UI/UX certificate, and she draws every screen we ship.
Do you redesign existing products, or only new ones?
Both. An existing product is often the easier brief, because the hard questions have already been answered by people using it. We start by finding out what they work around.
Do you work with clients outside Vancouver?
Yes. We are based in Vancouver and we work on Pacific time, which overlaps a normal working day across North America. The work itself happens over a shared staging URL, so where you are rarely matters.
Have something worth building?
Tell us what you have in mind. A half-formed idea is plenty to start with. We take one project at a time, so the two of us read and answer every note ourselves.