Services  /  03  Apps

Software people return to.

Mobile apps, web apps and internal platforms — designed around the job someone is trying to finish, and built to a standard that survives its second year.

Disciplines
Discovery · UX · UI · Front-end
Typical engagement
12 – 24 weeks, then iterative
Works well with
Digital strategy, Brand
01 The problem Why products get heavier and worse

Every feature you ship is a promise to maintain it.

Products rarely fail on a single bad decision. They accumulate: a feature for one client, a workaround for one release, a screen nobody owns. Two years in, the roadmap is mostly repair work and the interface is a museum of old priorities.

We design for the job, not the request. That means saying no on the record, keeping the surface area small, and building a system your engineers can extend without asking us first.

02 What we do Eight disciplines
01

Product discovery

User research, jobs-to-be-done and opportunity sizing. What to build, what to drop, and what to prove before committing budget.

02

UX architecture

Information architecture, flows and states — including the empty, error and edge cases most projects discover far too late.

03

Interface design

Interfaces with a point of view: clear hierarchy, honest affordances, and enough craft that people trust what they are looking at.

04

Design systems

Tokens, components and usage rules, delivered in Figma and in code so design and engineering share one source of truth.

05

Mobile apps

iOS and Android, designed to platform conventions rather than against them, with the accessibility work done as standard.

06

Web apps & platforms

Dashboards, portals, marketplaces and internal tools — the dense, data-heavy screens where design discipline matters most.

07

Prototyping & testing

Working prototypes in front of real users early, so the expensive assumptions fail cheaply.

08

Front-end engineering

Production front-end build, or close partnership with your engineering team — reviews, specs and a design system they will actually use.

03 How an engagement runs Four phases
01

Discovery

Users, stakeholders, constraints and the existing product. We come back with the problems worth solving, ranked, with the evidence attached.

2 – 4 weeks

02

Define

Architecture, core flows and a prototype of the riskiest journey — tested with real users before anything is committed to a roadmap.

3 – 5 weeks

03

Design & build

Interface design and design system in parallel with engineering, shipped in vertical slices so something real is usable early.

8 – 16 weeks

04

Ship & iterate

Launch, instrumentation, and a cadence of research and release. The roadmap is revised against behaviour, not against the original plan.

Ongoing

04 What you leave with

Scope varies with build arrangement — we design, or we design and build.

  • Research findings & opportunity map
  • Product principles
  • Information architecture
  • Core user flows
  • Interactive prototype
  • Usability test findings
  • Full interface design
  • Design system (Figma & code)
  • Accessibility documentation
  • Engineering handover & specs
  • Front-end implementation
  • Analytics & instrumentation plan
— Start a project We reply to every enquiry within one working day

Tell us what you need to grow.

Whether it's a full rebrand or one stubborn conversion problem, the first conversation is the same: what are you trying to move, and by when?