UI/UX Design
Description
Design here is not decoration. It is how we agree, in public, on what is being built.
Talking about a website in the abstract almost never works. You need to see structure, then see a real interface, then change it until it matches the business. We do that in Figma: wireframes first so content and paths are honest, then visual design so you can judge the thing your customers will actually look at.
This service stands on its own. If you already have a developer — or you are the developer — we can hand off a documented Figma file and stop there. If you want us to build it, the same file becomes the contract for Custom CMS Development.
We keep iterating inside the agreed scope until the design is something you can stand behind. Unlimited rounds is not a slogan for chaos; it means we do not cut you off after two comments if the work is still inside what we scoped.
How we run this from first conversation to a locked file is written up in our design process.
What's included
- WireframesPage structure and content placement before visual style. You can argue about the product, not the shade of blue.
- Visual system in FigmaNot a stack of disconnected artboards. Type, color, components, and states that a developer can actually build.
- Brand directionIf the brand is thin, we define enough visual identity for the site to feel like one company — not a new logo for its own sake.
- Revisions inside scopeWe keep going until the file is right, as long as we are still solving the thing we agreed to solve.
The challenge
Most clients do not know what they want until they see it. That is normal. The expensive version is discovering it in code.
This stage is also where the unclear parts of the project surface — the page nobody owned, the content that does not exist, the feature that sounded simple on a call. Better here than in week five of development.
What we do
- Visualize before you commit to codeA clickable, reviewable design is cheaper than a rebuild. You see the site before it exists.
- Iterate with you, not around youFeedback is part of the work. We would rather hear “this is wrong” on a frame than on a staging URL.
- Hand off a file a developer can useSpacing, types, components, and notes. If we are not the ones building, your team should not have to reverse-engineer the intent.
Our process
- 01
Continue discovery
Goals, audience, sitemap, and content reality. If we already did a consulting session, we start from those notes.
- 02
Wireframes
Skeleton of the key templates. We check UX and information architecture before visual design.
- 03
Visual design
The real interface, with brand, type, and components. This is what you approve.
- 04
Revision rounds
Changes until it is right. Then we freeze the file so development has a single source of truth.
Why choose us
Design that developers can actually build
Pretty frames that ignore CMS fields, empty states, and real content get thrown away in development. We design for the system that will run the site.
Works as a standalone hire
You do not have to buy development from us. Many people only need the Figma work.
Fast feedback loops
You are talking to the person drawing the file, not an account manager forwarding comments.
Frequently asked questions
Yes. This service is independent. We deliver the Figma file and notes. Your developers take it from there.
Other services you might need
Project Discovery & Consulting
A free working session to decide if you need a website, what it should do, and what it will actually cost — before you spend anything.
Custom CMS Development
Your approved design becomes a real website powered by a maintainable CMS. — Payload, a Git-based option, or WordPress when that is genuinely the right tool.