Skip to content

About

A small studio that takes the whole job

Three senior people, one engagement at a time. No account layer between you and the people doing the work, and nothing handed to a junior once the contract is signed.

Mission

We exist to make small teams legible to the people they want to sell to.

Most companies do not have a design problem. They have an argument problem: nobody has decided what the company stands for, so every page, deck and ad quietly says something slightly different. Design then gets asked to fix a disagreement it was never in the room for.

reformer.agency does both halves. We settle the argument first, in writing, with the people who can approve it. Then we design and build the thing that carries it, and we stay long enough to see what it earns. Strategy without a build is a document nobody opens. A build without strategy is an expensive way to stay unclear.

The team

Who you will actually work with

The three people in every project. You meet all of them on the first call and none of them disappear afterwards.

Studio Lead

Strategy and client work

Runs discovery and holds the argument steady once it is agreed. Fourteen years across brand and product, most of it spent finding out that the brief and the actual problem are different things. Writes the positioning document and is the person who tells you when a request will cost more than it returns.

Positioning, scope, the awkward questions

Design Lead

Art direction and interface design

Owns how the work looks and how it reads, which are the same job. Comes from editorial design and treats a page as something to be read rather than decorated. Builds the design system that engineering works from and tests every interface against keyboard and screen reader before it is signed off.

Type systems, layout, accessibility

Engineering Lead

Architecture and delivery

Turns the design system into a typed codebase and defends the page budget when it is inconvenient. Sets up the content model so marketing can work unaided, and runs handover personally, because a site your team cannot change is a site that starts decaying the week we leave.

Front-end architecture, performance, handover

Values

Three things we will not trade away

01

Say the true thing early

If the budget does not match the ambition, if the identity is fine and the messaging is the problem, if the feature you asked for will not move the number you care about, you hear it in week one rather than at the end. It costs us work sometimes. It has never cost us a client.

02

Ship it, do not present it

There is a working staging site from week two and a fixed weekly review. You watch the thing get built rather than sitting through reveals. Nothing arrives at the end that anyone has to argue about, because it was all visible while there was still time to change it.

03

Leave nothing behind that needs us

Documented systems, a content model your team can run, every account and repository in your name, and a recorded handover. We would rather be re-hired for the next piece of work than retained because you cannot edit a headline without a support ticket.

Want to see whether we fit?

Send a short brief. If the work is not right for us, you will get a straight answer and a recommendation rather than a pitch.