Purposeful, or not at all
An animation should direct attention, reinforce the story or make something clearer. If it's doing none of those, it's just a delay.
Design that gets people where they're going
UX and UI, from the shape of a page down to the state of a button. The same team designs it and builds it, so what gets drawn is what ends up live.
What we design
Visual direction
Mood boards and style exploration first, so we agree the feel of it before anyone spends a fortnight on a homepage. Cheap to change at this stage, expensive later.
A design system
Typography, colour, spacing and a component set that scales — so the twentieth page belongs to the same site as the first, and your team can add pages without ringing us.
The templates that matter
Homepage, service page, case study, listing. Everything else assembles from the component set.
Motion and interaction
Animation that guides the eye and paces the story. Every bit of it has to earn its place, and that's what keeps a site feeling current four years on.
Accessibility from the first wireframe
Contrast, type size, focus states and interaction patterns checked in Figma before anything is coded. A fraction of the cost of fixing it after launch.
Prototypes you can click
The journeys that carry the most weight get built as something you can click, in Figma or as real pages in a browser. You try the thing itself weeks before anyone writes the code for it.
From blank canvas to sign-off
Everything happens in Figma or in real pages in a browser, on live links you can open whenever you like. Some ideas are quicker to understand when you can click them, so those get built rather than drawn.
Two or three rounds of refinement on the key pages before development starts, and formal sign-off at the end of it. Nothing should be a surprise later.
Stage 1
Direction
Mood boards and style exploration, until we agree a direction. Everything after this is built on top of it, so it's worth the time.
Stage 2
Foundations
Type scale, colour, spacing and the component set. The rules that make everything after this quick.
Stage 3
Templates
The key pages, designed properly and reviewed together, with motion and interaction designed alongside them from the start.
Stage 4
Handover
Component library documented, every state specified, and the developers who will build it already in the conversation. Design and build aren't separate companies here.
Interactivity that survives the novelty
Every brief asks for something interactive. Most interactive things get used once and then date badly. The trick is picking the one or two ideas that earn their keep, and building those properly.
Designed to be built
Designers and developers are on the same project from the first wireframe, reviewing each other's work as it goes. Every idea in the file survives the trip into code.
Accessible by default
Motion respects reduced-motion settings, contrast passes WCAG 2.2 AA, and every state has a visible focus style. All of it checked in the design file, so it arrives in the build already right.
Axter
550%
increase in engagement rate after a redesign and rebuild.
Arts University Bournemouth
99%
accessibility score, and the top-ranked UK university website for it.
Transparency International
500,000+
pageviews in 24 hours at the Corruption Perceptions Index launch.
Frequently asked questions
Yes, and it usually speeds things up. The type scale, the palette and the photography rules come straight across into the interface. Where a guideline was written for print and doesn't survive contact with a screen, we'll say so and suggest the digital equivalent.
Yes, and we do it regularly. You get a documented component library with every state specified and the interaction behaviour written down, so another team can build straight from it without ringing us to ask what a hover is supposed to do.
Constantly. Work lives on live links — Figma for the design files, real pages in a browser where clicking through explains it faster than a flat frame. Formal reviews happen at direction, foundations and templates.
Two or three on the key pages, which in practice is enough because the direction is already agreed by the time we get there. If something genuinely isn't working we'll keep going — we're not counting.
We art-direct rather than shoot. We'll specify what the site needs, brief it properly and bring in people we trust, or work with a team you already use.
Let's get your site
where it should be
Get in touch with us with a bit about what you're needing, and we'll get back to you to kick things off to see how we can help you
Got it. We'll be back to you soon.
One of us will read it properly and reply — usually the same working day. In the meantime, there's more of the work to look through: