§ 00

Capabilities

Designing brands. Building products. Engineering growth.

Nine disciplines, run by one senior team. This is not a menu — it is how the studio works, written down. Read it and you should understand how we think, not just what we sell.

Studio Discipline: Brand, Product & Engineering
Reference: 1904-CAP-001
Volume: Vol. 02
Disciplines: Nine
Updated: 2026

§ 01

The Approach

Connected systems,
not isolated services

Companies rarely have a brand problem, a product problem and an engineering problem. They have one problem that shows up in three places. A repositioning that never reached the interface. A design system the codebase does not implement. A website nobody can update without a developer.

Handing those to three separate suppliers produces three defensible pieces of work and one incoherent company. We run the disciplines together, in one team, because the interesting decisions live in the seams between them — and the seams are exactly what gets lost in a handover.

Strategy that never reaches production is a document, not a decision.

Studio principle — 1904REF: CAP-INTRO-01

§ 02

Index

Nine disciplines,
one methodology

Engage one, several, or the whole practice. Most engagements begin at 01 and run the sequence; some start halfway through because the earlier work is already done.

Brand Strategy

Clarity before craft.

DIS-01

Brand Identity

A system, not a logo.

DIS-02

Digital Product Design

Interfaces that hold up under use.

DIS-03

Design Systems

Consistency as infrastructure.

DIS-04

Web Experiences

The most public thing you own.

DIS-05

Engineering

Design, held to its word.

DIS-06

Motion & Interaction

Movement that carries meaning.

DIS-07

Content Systems

Structure that outlives the page.

DIS-08

Growth & Optimisation

The work after the launch.

DIS-09

§ 03

The Disciplines

DIS-01 — DIS-09

DIS-01

Brand Strategy

Clarity before craft.

Most brand problems present as design problems. A logo that never feels right, a website that will not settle, a deck that says six different things to six different rooms. Almost always the cause sits upstream: nobody has decided what the company is for. Strategy is where that decision gets made — deliberately, in writing, before a single pixel is committed to it.

FIG. 01

Brand Strategy

Includes

Market & competitive research
Positioning
Naming
Messaging frameworks
Brand architecture
Stakeholder workshops
Audience definition

When you need it

Entering a new market or category
Two companies becoming one
A product portfolio nobody can explain in one sentence
Growth that has outpaced the original story

Outcomes

A position you can defend in a board meeting
Language the whole company uses the same way
A brief that makes the design phase shorter, not longer

Deliverables

Strategy document
Positioning statement
Messaging matrix
Naming rationale
Competitive audit
Workshop synthesis

Related work

Mealport

Food & Grocery Commerce · 2025

A-01

FIG. 02

Brand Identity

DIS-02

Brand Identity

A system, not a logo.

An identity is judged on its thousandth application, not its first. We design the rules that hold at that scale — how the type behaves at 11px and at 200px, what happens when the photography is bad, which colour carries the meaning when the layout has room for only one. The mark is the smallest part of the work and usually the last part we make.

Includes

Visual identity
Logo systems
Typographic systems
Colour systems
Art direction
Brand guidelines
Packaging
Social & marketing assets

When you need it

The identity predates the company you now are
Every new asset needs a designer to look right
Sub-brands have drifted beyond recognition
Investing in a website the current brand cannot carry

Outcomes

An identity that survives contact with real content
Non-designers producing on-brand work unaided
One visual language across every surface

Deliverables

Logo suite & lockups
Type scale & pairings
Colour system with contrast ratios
Grid & layout principles
Photographic direction
Brand guidelines
Asset library

Related work

OmniRelay

Enterprise Infrastructure · 2026

B-01

DIS-03

Digital Product Design

Interfaces that hold up under use.

Products are not judged in a portfolio. They are judged on a Tuesday afternoon by someone doing their job for the ninth time that hour. We design for that person — the repeat visit, the error state, the slow connection, the edge case that turns out to be a third of the traffic. Delight is welcome, but it is downstream of not wasting anyone's time.

FIG. 03

Interfaces that hold up under use.

Includes

UX strategy
User research
Information architecture
User flows
Wireframing
High-fidelity interface design
Interaction design
Accessibility
Design QA

When you need it

Users complete the task but complain about it
Support keeps answering the same question
Scope has outgrown the original interface
Building a first product and only getting one shot

Outcomes

Fewer steps between intent and completion
Support load that falls instead of tracking growth
An interface engineering can build without guessing

Deliverables

Research findings
Flow diagrams
Annotated wireframes
Interface designs, all states
Interactive prototype
Accessibility specification
Design QA report

Related work

TurkishWears

Fashion & E-commerce · 2025

C-01

DIS-04

Design Systems

Consistency as infrastructure.

A design system is not a component library. It is an agreement about how decisions get made, with the library as evidence. The value shows up in what stops happening: the fourth button variant nobody sanctioned, the three-day debate about spacing, the redesign that has to start from zero. Built properly, it makes the right thing the easy thing.

FIG. 04Token → Component → Page

Includes

Component libraries
Design tokens
Documentation
Governance & contribution models
Developer handoff
Versioning & release
Adoption support

When you need it

Two teams have built the same component twice
Design and code have quietly diverged
Onboarding a designer takes a month
A rebrand would mean touching every screen by hand

Outcomes

One source of truth, design through production
New screens assembled rather than drawn
Brand changes that propagate instead of repeating

Deliverables

Token architecture
Component library
Usage documentation
Contribution guidelines
Figma & code parity audit
Migration plan

Related work

CrediBE

FinTech · 2026

D-01

DIS-05

Web Experiences

The most public thing you own.

A website is read by people deciding whether to take you seriously — often in under a minute, often on a phone, often on a connection you did not design for. So the craft has to survive compression. We build sites that load fast, read well, and stay editable by the people who actually have to keep them current after we leave.

FIG. 05

Web Experiences

Includes

Marketing & corporate websites
Landing pages
Interactive experiences
CMS integration
Performance engineering
SEO foundations
Accessibility
Analytics instrumentation

When you need it

The site describes a company you no longer are
Every content change needs a developer
Traffic arrives and leaves without converting
Load times are costing you the first impression

Outcomes

A site the marketing team can run themselves
Performance that holds on a mid-range phone
Search and social surfaces that render correctly

Deliverables

Responsive design across breakpoints
Production build
CMS schema & editor training
Performance budget & audit
SEO & metadata implementation
Analytics setup

FIG. 06

DIS-06

Engineering

Design, held to its word.

We engineer our own design work. That removes the negotiation that usually happens after handoff — the one where the interaction gets simplified, the spacing drifts, and the thing that shipped is a reasonable approximation of the thing that was approved. It also means the design was checked against reality while it was still cheap to change.

Includes

Frontend development
Backend & API development
Next.js and React
Flutter
Headless architecture
Third-party integrations
Performance optimisation
Deployment & CI
Maintenance

When you need it

The build never quite matches the design
A prototype has to become a production system
The stack has become the reason things take long
Nobody owns the code after the agency leaves

Outcomes

What shipped is what was designed
A codebase your own team can pick up
Infrastructure sized to the actual load

Deliverables

Production application
Architecture documentation
Test coverage
CI/CD pipeline
Handover & walkthrough
Maintenance window

Related work

Mealport

Food & Grocery Commerce · 2025

A-01

DIS-07

Motion & Interaction

Movement that carries meaning.

Motion earns its place by explaining something — where a panel came from, what is still loading, which element the eye should follow. Animation that exists to demonstrate that animation is possible makes an interface slower and, eventually, annoying. We set the rules once, in a system, so that every transition on the product agrees with every other one.

FIG. 07

Movement that carries meaning.

Includes

Motion systems
Micro-interactions
Product animation
Brand motion
Scroll-driven sequences
Transition choreography
Reduced-motion handling

When you need it

The interface feels abrupt between states
Animation was added per screen with no rules
A brand needs to move as well as sit still
Motion is hurting performance or accessibility

Outcomes

Transitions that orient rather than decorate
One timing language across the product
Motion that respects reduced-motion preferences

Deliverables

Motion principles
Easing & duration scale
Animated component specs
Production implementation
Reduced-motion variants

Related work

CrediBE

FinTech · 2026

D-01

DIS-08

Content Systems

Structure that outlives the page.

Content modelled as pages cannot be reused, translated, or restructured without being rebuilt. Content modelled as structure can. We design the schema first — what a thing is, what it is made of, what it may reference — and let the layouts read from it. That is the difference between a site you edit and a site you fight.

Includes

Sanity CMS implementation
Content architecture
Reusable content models
Editorial workflows
Roles & permissions
Preview & publishing
Migration from legacy systems

When you need it

Publishing requires a developer
The same copy is maintained in four places
Localisation is on the roadmap
The CMS shapes the design instead of serving it

Outcomes

Editors publishing without a deployment
Content reused across surfaces, authored once
A model that absorbs new page types

Deliverables

Content model & schema
Studio configuration
Editorial documentation
Preview environment
Migration scripts
Editor training

FIG. 09

Growth & Optimisation

DIS-09

Growth & Optimisation

The work after the launch.

Launch is the point at which you start learning, not the point at which the work concludes. The assumptions that survived the design process now meet actual users, and some of them will not hold. We stay on to find out which ones, and to make the small corrections that compound — the kind that never justify a redesign but quietly account for most of the gain.

Includes

Performance audits
Conversion optimisation
Analytics & instrumentation
Usability testing
Iterative UX improvement
A/B testing
Continuous design support

When you need it

Traffic is healthy and conversion is not
Analytics are installed but never read
The roadmap is set by opinion rather than evidence
The site has drifted since launch

Outcomes

Decisions argued from data, not seniority
Compounding gains instead of periodic rebuilds
A team that knows what to measure next

Deliverables

Audit & findings
Instrumentation plan
Test roadmap
Iteration cycles
Performance reporting
Quarterly review

§ 04

Methodology

How the disciplines
connect

Each stage exists to hand something specific to the next. When a stage is skipped, the one after it starts by inventing what it was owed — which is where most of the cost and nearly all of the incoherence comes from.

Strategy

Hands on

A position and a brief

Identity

Hands on

A visual language

03 · 04

Product Design

Hands on

Interfaces and a system

05 · 06

Engineering

Hands on

A working product

07 · 08

Launch

Hands on

Motion and content in place

Growth

Hands on

Evidence for the next cycle

Strategy

A position and a brief

Identity

A visual language

03 · 04

Product Design

Interfaces and a system

05 · 06

Engineering

A working product

07 · 08

Launch

Motion and content in place

Growth

Evidence for the next cycle

§ 05

Process

How great work
actually happens

Discover

Define

Design

Build

Launch

Support

Discover

Deep research into your business, users, and competitive landscape. We establish the foundation before a single pixel is placed.

Duration1–2 wks

Define

Strategic alignment on direction, architecture, and success criteria. The brief that guides everything that follows.

Duration1 wk

Design

Visual direction, system thinking, and high-fidelity prototypes. Every detail considered, every decision documented.

Duration4–8 wks

Build

Precision engineering with quality assurance at every stage. Code that performs as beautifully as it looks.

Duration4–12 wks

Launch

Staged deployment, performance monitoring, and a smooth handoff that sets your team up for independence.

Duration1–2 wks

Support

Ongoing evolution, iterative improvement, and strategic counsel as your product and brand grow.

DurationOngoing

§ 06

Why 1904

What the studio is
actually good at

R-01

Systems thinking

We look for the rule behind the request. Solving the instance takes an afternoon; solving the pattern means the request stops arriving.

R-02

Craftsmanship

The unglamorous parts get the same attention as the hero shot — empty states, error copy, the third breakpoint, the print stylesheet nobody asked about.

R-03

One senior team

The people in the pitch are the people on the work. Nothing is handed down to a junior bench once the contract is signed.

R-04

Business-first design

Every decision is argued from what it does for the company. Taste is the method, not the justification.

R-05

Engineering awareness

We design knowing what it costs to build, because we are the ones building it. Nothing is approved that cannot ship.

R-06

Long-term partnership

Most of our work is for companies we have already worked with. The second engagement is where the compounding starts.

§ 07

Engagement

Ways to
work together

The disciplines above do not change with the contract. What changes is how the team is held — for a defined outcome, for a standing commitment, or as counsel to the people already doing the work.

ENG-01