Structure
Agree the pages, hierarchy and journeys through the site.
What are you working on?
A sentence is enough — we will work out the rest together.
The structure and visual design of a website, ready for your development team. If you want Noemo to design and build the whole site, choose a business website or an e-commerce project.
The core of this engagement. We agree the exact scope in your project plan.
Agree the pages, hierarchy and journeys through the site.
Design the agreed templates and their mobile layouts.
Define reusable elements and their interaction states.
Organize the design files and explain the decisions to the build team.
Every engagement runs through the same moves, and you always know which one we are on.
The pages, what each one is for, and the order a reader meets them in.
Real words, real images, and every state a screen actually has.
A file your team can build from, with spacing, type and behaviour written down.
Work this has already carried. All of it is live, and all of it is still ours to keep running.

It mattered to us that the site shows video rather than talking about it. Noemo turned the portfolio into a clear system, prepared every file for the web and took on the technical side. Projects open fast and look as good on a phone as on a big screen.

A manager used to start every call by explaining what we supply. Now the client usually arrives with a category, a voltage range and a real question. Noemo made the site a working tool, not just a nice business card.
Nothing here was chosen because it is fashionable. Each one is on the list for something it does that the alternative does not.
One file, one source of truth, and you are inside it from the first week. Nothing gets unveiled — you watch the screens arrive and leave comments where you are looking.
03 toolsA design that cannot be built is a drawing. Components are published as something a developer can open and run, so both halves read one source.
04 toolsWe test on the devices your users actually hold, and accessibility is checked while the screens are drawn rather than audited once at the end.
04 toolsUsing something we have not listed? Say so on the call — half of what we know arrived because a client was already on it.
You click the thing before we have finished drawing it. Opinions are cheapest while changing your mind still is.
Your developers get named components with rules, not a folder of pictures to interpret on their own.
Design QA is inside the fee, so what ships is what was agreed rather than an approximation of it.
Still deciding? Half an hour on a call is usually enough to know either way.
“It mattered to us that the site shows video rather than talking about it. Projects open fast and look as good on a phone as on a big screen.”
The questions that arrive by email anyway. If yours is not here, ask it on the call.
Not in this service. If you want the build too, that is a business website or an e-commerce project.
A Figma file with components and the rules written into it, rather than a folder of flat images.
That is the whole deliverable. We answer their questions during the build without charging for it.
We design with real structure and placeholder text we have written ourselves. Never lorem ipsum.
Start with a 30-minute call. The scope, the fee and the dates go into a project plan before any work begins.
Tell us what you are building. If it is a fit you will have an offer — and if not, we’ll tell you upfront.