Design
Web Design
The design of a site people visit to decide something. Interfaces people return to daily are UI/UX design, and that is a different discipline with a different measure of success.
Web design decides how a marketing site looks, reads and is structured, before anyone writes code. The Nexclick designs against your real content rather than placeholder text, checks contrast rather than eyeballing it, and hands over editable source files you own outright.
Is this you?
What usually prompts the call
- Your site looks dated next to competitors and it is affecting first impressions.
- The design was signed off on preference and nobody can explain why anything is where it is.
- The layout falls apart the moment a real product name runs to three lines.
- It looks fine on a designer’s monitor and awkward on a phone in daylight.
What we do
The actual deliverables
Things that appear on an invoice, not adjectives.
- Discovery grounded in the commercial goal
- What this site must achieve, for whom, and how it will be judged. Written down, so later reviews test against something other than taste.
- Information architecture and wireframes first
- Structure agreed while changes are cheap. Reordering a wireframe takes minutes; reordering a designed and built page takes days.
- Design against your real content
- Actual headlines, actual product names, actual copy lengths. Layouts designed around ideal placeholder text fail on contact with a real business.
- Contrast and accessibility measured, not judged
- Every colour pairing checked against WCAG 2.2 AA, focus states designed, target sizes verified. Retrofitting this costs several times what designing it in does.
- Responsive design from 320px upward
- Designed at mobile width first and expanded, rather than designed wide and squeezed. Most UK traffic arrives on a mid-range phone.
- A component set rather than a stack of pages
- Reusable sections so pages you have not designed yet can still be built consistently. This is what stops a site drifting six months after launch.
- Handover of editable source files
- Figma files with layers named and components organised, plus exported assets. You can take them to any designer, including one who is not us.
Checklist
Review a design against this, not against taste
Design reviews collapse when they become arguments about preference. These are answerable questions. Use them on any design you are asked to approve, ours included.
- 01Is it obvious within three seconds what this business does and for whom?
- 02Is there exactly one primary action visible in the first screenful?
- 03Does the layout survive your longest real headline and product name?
- 04Does body text measure at least 4.5:1 against its background — checked, not judged?
- 05Does the primary button colour pass contrast against its own text?
- 06Is any meaning conveyed by colour alone?
- 07Are interactive targets at least 44 by 44 pixels on mobile?
- 08Has a focus state been designed, or is it left to the browser default?
- 09Does it work at 320px width without horizontal scrolling?
- 10Does it survive 200% browser zoom without content being lost?
- 11Are line lengths under about 70 characters in body copy?
- 12Is anything centred that runs longer than two lines?
- 13Do images have a designed empty state for when the client has no photo?
- 14Is there a designed state for errors, loading and empty results?
- 15Are the fonts licensed for web use, and is that licence in writing?
- 16Could a developer build this without asking a question the file does not answer?
How it works
Step by step, with timeframes
Timeframes are typical rather than guaranteed, and they assume we get account access and approvals when we ask.
- 01Week 1
Understand
Commercial goal, audience, constraints and what has already been tried. Plus a look at competitors, largely to establish what to avoid.
- 02Week 1–2
Structure
Sitemap and wireframes, signed off before visual work begins. The stage that saves the most money and the one clients most want to skip.
- 03Week 2–5
Design
Key templates first, then the rest, with two structured review rounds. Feedback gathered against the agreed goal rather than as general impressions.
- 04Week 5–6
Systemise and hand over
Components documented, assets exported, files organised, with a walkthrough for whoever builds it.
What you get
Reporting and ownership
- A shared Figma link from day one — you watch it develop rather than waiting for a presentation.
- Measured contrast ratios documented, not an assurance that it looks fine.
- A component set so pages designed later stay consistent with these.
- Editable source files, organised and named, transferred to your ownership.
- A short written note of the design rules, so your team can apply them without asking.
Tools and platforms
- Figma
- WCAG contrast checkers
- Real device testing
- Session recordings from the existing site
- Font licensing verification
Timeline
How long this actually takes
Five to six weeks for a marketing site. Two structured review rounds are included, which is enough when feedback is consolidated — projects that overrun are almost always ones where six stakeholders commented separately and contradicted each other. We ask for a single named decision-maker for exactly that reason. One honest note: design cannot fix a proposition nobody understands. If the difficulty is that the business has not decided what it stands for, a redesign will make that confusion look more expensive rather than resolving it, and we will say so.
Pricing model
Fixed-price project
Fixed price by template count, quoted after a short discovery call. Build is priced separately, and you are free to take the design elsewhere.
Questions
Web Design questions
How is web design different from UI/UX design?
Web design is for marketing sites — how it presents, what it communicates, whether it converts a visitor who is deciding. UI/UX design is for products and applications people return to repeatedly, where efficiency matters more than persuasion. Different measures of success, so we run them as separate services.
Do we need to have our content written first?
Ideally yes, and realistic drafts are enough. Designing against placeholder text produces layouts that break on real copy — a headline that runs to three lines instead of one, a product name twice the expected length. Where content is not ready, we design against a realistic worst case rather than an ideal.
How many revisions are included?
Two structured rounds at each stage. In practice that is sufficient when feedback is consolidated by one person. Projects that spiral are the ones where several stakeholders comment separately and contradict each other, which is why we ask for a named decision-maker up front.
Can we take the designs to another developer?
Yes. You get editable Figma files with layers named and components organised, plus exported assets. That is deliberate — a design handover that only its author can build from is a lock-in, and it is not how we work.
Will you use our existing brand?
Yes, and we will raise anything with a genuine problem — a logo illegible at small sizes, a palette failing contrast at every weight — with the evidence. Whether to address it now or work within it is your decision, made knowing the constraint.
What if we do not like the first design?
Then we go back to the brief and establish which agreed goal it fails, rather than iterating on impressions. Usually the disagreement is traceable to something not settled at discovery. That is a useful finding, and it is why the discovery output is written down.
Last reviewed 28 July 2026.
Tell us what you are trying to fix
A 20-minute call, no pitch deck. The Nexclick will tell you what we would do, roughly what it costs, and whether we are the right people for it.