You’re in good company

A few of the companies we’ve worked with.

Every state, not only the ideal one

Most designs show a screen when everything goes right. Real products spend much of their time somewhere else: loading, empty, failing, full of long names, or open in front of someone using it for the first time.

We design those states with the main screens, so engineers aren’t left to guess and people aren’t left stuck.

Your bookings

No bookings yet

When you book a session, it appears here with the day, the place and who it’s with.

Your bookings

Loading your bookings

Your bookings

  • ThuConsultation with MayaHill Street · MorningConfirmed
  • FriFollow-up with SamOnline · AfternoonConfirmed
  • TueWorkshop with AnaHarbour Room · EveningAwaiting reply
  • WedCheck-in with LeoHill Street · MorningConfirmed

Your bookings

  • ThuTreatment planning with Dr Maria-Magdalena Okonkwo-FitzgeraldThe Old Printworks, Upper Floor, Riverside Entrance · MorningWaiting for the clinic
  • FriFollow-up with SamOnline · AfternoonConfirmed
  • TueWorkshop: planning the accessibility review for the new sign-up flowHarbour Room · EveningAwaiting reply
  • WedCheck-in with LeoHill Street · MorningConfirmed

Your bookings

No bookings match “Hil Stret”

Check the spelling, or search by the day or who it’s with.

Did you mean Hill Street?

Your bookings

We couldn’t load your bookings

Your bookings are safe. Check your connection, then try again.

First use. Says what will appear here, and offers the one step that gets someone started.

Loading. Holds the layout in place, so nothing jumps when the bookings arrive.

Filled. Shows what people look for first: the day, what it is, where it is and whether it’s confirmed.

Long content. Long names wrap to two lines, and the day and status stay where people expect them.

No results. Repeats what was searched, suggests a likely fix and keeps the way back one step away.

Error. Says what went wrong in plain words, reassures, and offers the next step.

{{ stSay }}

What we design

From the first research to the component your engineers reuse.

  • Product research

    Interviews, observation and your own analytics, to understand who uses the product, what they’re trying to do and where they get stuck.

    You getthe main user journeys and a prioritised list of problems worth solving.

  • UX design and prototyping

    Flows, wireframes and clickable prototypes, tested with people before anything is built.

    You geta tested prototype and the flows behind it.

  • Interface design

    Clear, accessible screens for web and mobile, designed around the content and data they’ll really hold.

    You getfinished screens for every state, ready to build.

  • Design systems

    Shared foundations for colour, type, spacing and components, in design and in code, so every team builds the same product the same way.

    You geta documented component library your designers and engineers both use.

  • Usability testing

    Sessions with the people who use the product, on the tasks that matter most to them.

    You getfindings, and the specific changes they point to.

  • Accessibility

    Designs checked against the WCAG guidelines from the start, with contrast, keyboard use and screen readers considered in every component.

    You getan accessibility review with each issue and how to fix it.

  • Redesigns

    Improvements to a product people already rely on, released in stages, so nobody has to relearn everything at once.

    You geta staged plan, and the first improvements in front of users early.

From research to release

Our engineers are involved from the first conversation, not handed a finished design at the end.

Understand the people and the work

We talk to the people who use the product and the teams behind it, look at the data you already have and map where things get stuck.

Who takes part

  • People who use it
  • Your team
  • Our designers
  • Our engineers

Sketch and test early

Rough flows and prototypes go in front of real users while changing them is still quick and cheap.

Who takes part

  • People who use it
  • Our designers
  • Our engineers

Design the detail

Screens, states, content and components, designed with the engineers who’ll build them and checked for accessibility as we go.

Who takes part

  • Our designers
  • Our engineers

Build, review and refine

We stay with the product through the build, compare what ships with the design and let how people use it decide what to improve next.

Who takes part

  • People who use it
  • Our designers
  • Our engineers

A design system your engineers will use

A design system only helps if it matches the code. We build components in design and in code together, give them the same names in both and document when to use each one.

  • Foundations for colour, type and spacing, shared by design and code
  • Components with every state and variant designed
  • Guidance with real examples of when to use each component
  • A clear way for your team to propose and add new ones

Already have a design system? We can review it, fill the gaps and help your teams adopt it.

Foundations

Colour

  • color.ink#232834Headings, focus rings and pressed buttons
  • color.accent#FA5478Main buttons and the flowing line
  • color.accent.text#D33D5CSmall coral text on white, like the label above the headline
  • color.surface.muted#F1EEEAThis band, and placeholders while content loads

Type

  • type.displaySailec BoldHeadlines and titles
  • type.bodySailec MediumBody text and labels

Space and shape

  • space.section88pxAbove and below most sections on desktop
  • radius.card20pxPanels and cards, like this one
  • size.target44pxThe smallest tap target
A sample of documentation, using this page’s own colours, type and sizes.

Designing products that use AI

AI features raise design questions of their own. How does someone see where an answer came from? What happens when the model is unsure, or wrong? How does a person step in, correct it or undo it?

We design those moments with the same care as the rest of the product, and test them with real users before launch.

AI Chatbots & Assistants AI Agents
You asked

Can I move my booking to Friday?

Answer

Yes. You can move a booking up to a day before it starts, if a slot is free that day.

3 sources Help centre, booking terms, timetable
An example of an AI answer, in a booking product we might design.

Our work

Explore our work

  • Yacht charter

    Belle Mare Yacht Charter

    Known for

    Guests plan their week by dragging stops on the chart.

    A charter planner where guests build their week on the chart, with cruising time recalculated as they go and the finished itinerary sent to the captain.

  • Art

    Galerie Nord

    Known for

    Each work shown at true size, and in AR on the collector’s wall.

    Private online viewing rooms where collectors see each work at true size, and in AR on their own wall, before they enquire.

  • Hospitality

    Serena Bay Resort & Spa

    Known for

    Every fee shown before the guest books.

    A direct booking engine with live rates for each suite and every fee shown upfront, and one login that follows the guest through their stay.

Working with your team

We can lead design on a new product, join your product team for a stretch of work or review an existing product and set out what to fix first.

Work with us as a dedicated team, on a fixed price project or a mix of both.

Compare engagement models

Need it built as well?

Web & App Development

Let’s design it better

Tell us about the product, the people who use it and where they get stuck. We’ll suggest where design would help most, and a sensible first step.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}