Skip to content

—Services · Build

Product & UI Design.

Pretty screens that never become a site are not a product. We design against the components we actually build.

01The usual mess

Pretty screens that never become a site are not a product.

Someone spent a month in Figma. Engineering rebuilds half of it. Marketing pastes a longer headline and the layout falls over. Empty states were never drawn.

If the first screen could belong to another firm after you hide the logo, the work did not do its job.

02What we do

We design against the components we actually build.

Calm type, a real grid, one job per section. Brand where it matters; quiet elsewhere. No card soup. No purple theatre.

The designer sits with the people writing the site. What you sign off is what goes live — not a file that dies in the handoff.

Energy Coast UTC website

03How the job runs

From a messy brief to screens that ship.

  1. 01

    The call.

    What people must do, in what order. Cover in place before we open a file.

  2. 02

    The system.

    Type, colour, spacing — matched to how the site will actually be built.

  3. 03

    Real copy.

    Key screens with your words, not lorem, including the awkward long ones.

  4. 04

    Polish and hand to build.

    Hover, focus, loading, empty, a phone in a car park. Then we stop guessing. Specs go to the same team. You do not buy a second interpretation.

04Who it is for

Who this is for.

Teams launching a new product surface, refreshing a marketing site, or needing a UI system that will not fight the codebase six weeks later.

  • New product and marketing sites

  • UI systems for ongoing delivery

  • Redesigns tied to a real build sprint

  • Brands that need presence without visual noise

05What changes

What you walk away with.

Ship-ready design

Layouts and components that survive the handoff into code.

One design lead

Your design lead works with the engineers who build — so rework stays rare.

A coherent system

A system your next feature can inherit without reinventing the grid.

07Pricing

What this costs.

A design sprint to get flows and surfaces shippable, embedded design alongside a build, or a focused UI pass on what you already have.

01Most chosen

Design sprint.

From £5,500

per engagement

Flows, interface system and the key surfaces, specced against real components.

Scope a design sprint

Get this from as little as £138 per month with Flexi-Pay over 24 months.

Based on a 40% deposit, then the balance across 24 months. Indicative, excluding VAT. Flexi-Pay terms. Terms and conditions apply.

02

Embedded design.

From £3,750

per month

A designer in the same team as the engineers, shipping surface by surface.

Talk embedded design
03

UI polish pass.

From £2,250

per engagement

Tighten type, spacing and states on an existing product — not a full redesign.

Scope a polish pass

Get this from as little as £56 per month with Flexi-Pay over 24 months.

Based on a 40% deposit, then the balance across 24 months. Indicative, excluding VAT. Flexi-Pay terms. Terms and conditions apply.

Compare

Ticks are in the fee. Crosses are not. A higher plan keeps every tick from the plan to its left, then adds the rows below.

What is included in each plan
Included01Design sprintFrom £5,50002Embedded designFrom £3,75003UI polish passFrom £2,250
Discovery
Product flows and information architecture✓✓✓
System
Type, colour and spacing system✓✓✓
Key surfaces at every breakpoint✓✓✓
Hover, focus, disabled and empty states✓✓✓
Delivery
Implementation-ready specs✓✓✓
Accessibility pass on the agreed set✓✓✓
Design review with engineers✓✓✓
Engagement
Named designer for a fixed sprint✓×✓
Designer embedded month-to-month×✓×
Polish / rescue pass on agreed surfaces××✓

Retained Service

It’s cheaper to partner up.

One-off engagements are fair on their own — and they add up. A monthly retainer unlocks named capacity across Build, Growth and Care for less than stacking those services as separate projects.

See Retained Service

Fixed for the agreed scope once discovery is done. Ranges depend on surface count, integrations and how much of the data model already exists. Excludes VAT.

Next step

If the first viewport could belong to another brand after removing the nav, the branding is too weak. We design so yours holds.

Bring a URL or a file. We will say whether the screens can actually ship.