DESIGN
WEBSITE DESIGN
- 100+ projects
- from 3 days
- ready for development
Site design built as a system: grid, typography, button and form states, layouts for every screen. Handed over so the build matches the design instead of approximating it.
WHO IS IT FOR?
Three situations where design is needed separately from development
- .01
YOU HAVE DEVELOPERS AND NO DESIGN
The team is in place, the stack is chosen, the job is clear — what is missing is the design. It goes to one freelancer, then another, and each draws it their own way: different spacing, different buttons, different logic in the forms. That then settles into the code: what was not a system in the mockups will not become one in the build. Every new page is assembled from scratch instead of being put together from parts that already exist.
- .02
THE SITE WORKS BUT LOOKS CHEAPER THAN THE PRODUCT
Functionally everything is in order; visually it is a template bought three years ago. The product is premium, the price is premium, the first impression is not. It costs most where the decision takes seconds: a client compares you with a competitor on a single screen and leaves before reading as far as your advantages.
- .03
THERE ARE MOCKUPS AND DEVELOPMENT WILL NOT TAKE THEM
The design is drawn beautifully, and the moment it reaches the build the questions start: what happens on hover, what on an error, what if there is three times more text, how does this behave on a tablet. Half the decisions get made by a developer on the fly. The result drifts from the picture and nobody is at fault: the mockup described the ideal case, and development needs all the others.
WHAT'S INCLUDED
We do not build below this line
- - A review of the brief and the references.01
- - Structure and a prototype.02
- - Custom design, never a template.03
- - Grid, typography, colour.04
- - States for elements and forms.05
- - Layouts for every device.06
- - Source files and handover to development.07
- - Revisions after delivery.08
- THIS IS THE FLOOR, NOT A PACKAGE
Everything listed ships in every project — even the simplest and cheapest one. There are no stripped-down versions.
- DESIGN THAT SURVIVES DEVELOPMENT
We write the code ourselves — so we know where a mockup falls apart in the build. States, long text, empty screens and errors are described before a developer has to ask.
- THE LIMIT ON REVISIONS IS AGREED BEFORE WE START
How many rounds are included and what counts as a new task is settled at the beginning. It is the only way to keep the work from turning into an endless “let us try one more option”.
WHAT'S INSIDE
EVERY PROJECT LOOKS LIKE ITSELF
We do not take ready-made assemblies and we do not bend a business to fit somebody else’s grid. The design is built for the job from scratch: its own composition, its own typography, its own rhythm, its own motion. Which is why no two of our projects look alike — open the portfolio and compare them yourself. With studios that work from templates every project is recognisable from the first screen, and the client notices that too.
DESIGN THAT SURVIVES DEVELOPMENT
A beautiful mockup and a working site are not the same thing, and the difference surfaces during the build: what happens on hover, what on an error, what if there is three times more text, what on a tablet. We write the code ourselves — so we know where a mockup falls apart, and we describe it before a developer has to ask. Whether we build it or your team does, the result will match the picture rather than approximate it.
A SYSTEM, NOT A PILE OF PICTURES
Grid, typography, colour, states, components — built once and reused. A new page is then assembled from parts that already exist rather than drawn again: that is what separates a project you can keep developing from one you will be rebuilding in six months. Plus everything that usually gets forgotten: empty screens, loading, errors, long text, and how all of it looks on the smallest phone there is.
BEAUTIFUL AND FAST IS ONE JOB, NOT TWO
Heavy animation, 3D, a scroll-driven sequence — all easy to draw and hard to keep light. It is usually paid for in speed: the site impresses in a demo and takes four seconds to load for the client. We design the effect and its implementation together — what the browser has to compute, what loads later, what switches off on a weak device. A heavy scene and a slow site are not the same thing, and the second is not compulsory.
CATEGORIES
Three levels of scope. Yours is the one you recognise yourself in
A LANDING PAGE OR A SITE
WHEN IS THIS YOUR CASE?
One page or a small site: a landing page, a promo, a company site of a few sections. The whole base build: a review of the brief and the references, structure and a prototype, custom design, grid and typography, states for elements and forms, layouts for every device, source files and handover to development. Nothing stripped out — just without the extras you do not need yet.
A MULTI-PAGE PROJECT
WHEN IS THIS YOUR CASE?
There are many pages and they differ: a store with a catalogue and a product page, a corporate site with business lines, a service with a client account. Mockups alone will not carry that — you need repeatable components that new pages can be assembled from without new design. A design system with a component library, every state and edge case, several languages, motion and interface behaviour, documentation for development.
DESIGN THAT WINS AWARDS
WHEN IS THIS YOUR CASE?
The brief is not “make it good” but “make it memorable”: a product launch, a rebrand, a project meant to land in the round-ups and on the industry sites. A visual idea of its own rather than an assembly of trends, a scroll and transition sequence, 3D and interactive elements, animation and micro-interactions worked through in detail. We think separately about keeping it fast in development: a heavy scene and a slow site are not the same thing.
FAQ
Answers to the most popular questions
From $1.000 for a landing page or a small site to $5.000 and up for a project with a visual idea of its own and heavy animation. The figure depends on the number of unique screens, on whether it needs a design system with components, and on how far the animation is taken. After the first call you get a plan with the scope broken down by stage rather than a guess.
A landing page or a small site, from 3 days. A multi-page project with a design system, 1–3 weeks. A project with a visual idea of its own, from 2 weeks. Most of the time goes not into drawing but into agreeing the direction: the sooner that is settled, the shorter the whole project.
The limit is settled before we start: usually two rounds at the direction stage and two on the final mockups. Revisions inside the chosen direction are part of the work. Changing direction after it has been signed off is a new task with its own timeline and price. That is not rigidity but a way of keeping the project from becoming an endless search for options that you end up paying for.
We work in Figma. What you get is a file with the mockups, the components, the styles and a description of the states, and access to it stays yours permanently. Plus everything development needs: exported images and icons, fonts, a description of the animation. If your own team is building it, we hand over on a call and answer questions as they go.
Yes, that is a normal arrangement — we do a share of projects exactly that way, for companies with their own team and for other studios. We write code ourselves, and that changes the quality of the handover: the mockup is put together knowing how it will be implemented. None of which ties you to our development.
Then it makes more sense to order the project as a whole — design is already part of development and does not need pricing separately. It comes out cheaper and faster: nothing has to be handed between teams, and the awkward points get settled on the spot rather than over email. If you have landed on this page but what you need is a turnkey site, look at the development section, where it is described in full.
We build the structure and the logic of the pages. You supply the substance: descriptions, prices, terms, advantages. We can write the copy from your materials; that is quoted separately. Design on real copy and design on “Lorem ipsum” are different things: in the second case the layout nearly always comes apart once the content goes in.
You do. The files, the rights and every asset are handed over with the project. Any designer can carry on with them — we put the file together so that someone who did not draw it can find their way around.
A normal situation, and the process allows for it. We show the direction before the mockups — at the stage where redoing it is cheap, not after every page has been drawn. If none of the directions fits, we work out why: usually the brief was understood in two different ways, and that is far better to discover at the start.