The studio

The people who would be on your project.

Not a directory. Who owns which decision, how a brief gets assigned to a pair, and how to reach one of them without going through a form.

Get in touch Open roles
The studio

Who you would be working with.

Everyone here works on the projects. There is no account layer between you and the people doing the work.

Sarah Mitchell

Sarah Mitchell

Founder & CEO

Sits in the first interviews and stays on the project through build, so the scope and the thing that ships are decided by the same person.

James Chen

James Chen

Creative Director

Draws against real content and every state it can be in, including the ones nobody asks for.

Emily Wilson

Emily Wilson

Technical Director

Writes the front end from the same tokens the design uses, so the two cannot drift apart after handover.

Michael Torres

Michael Torres

Strategy Director

Runs the assessment phase: interviews, a read of what customers already say, and the written position the scope comes from.

How the studio is organised

Six decisions, and who owns each one.

Titles do not say much. What a title should tell you is which decision that person is allowed to make on their own, and who has to be in the room when it is made.

rule

What is in scope — strategy

What the project covers and what it deliberately does not. Owned by whoever ran the assessment, because the reasoning lives in the interviews. It does not change without them in the room.

palette

Which route we take — creative

Two or three directions are explored properly and one is chosen. Owned by the creative director and decided with you present, not presented to you a week later.

code

What gets built and where — technical

Which parts are custom, which platform holds them, and what should not be built at all. Owned by the technical director, and the answer is sometimes no.

flag

Whether a phase is finished — the pair

Owned by the two people doing the work rather than by the date in the plan. A phase that is not done is said to be not done in the demo it was due.

block

Whether we take the work — founder

Whether a project is one we should take, and whether something asked for mid-flight is a change or a correction. Answered in the week it is asked.

move_up

When you take it over — handover

Owned by the technical director and settled by your team shipping a change while we watch, not by a document being signed.

1

One person reads it first

Whoever would run the assessment reads the brief. There is no triage meeting and no qualifying call between you and them.

2

The names come before the number

The proposal says which two people would do the work. If they are not free until a date, the proposal says the date instead of hiding it in a start window.

3

The pair stays for the phase

Nobody is quietly moved onto another project mid-phase. If someone has to change, you are told why in the demo rather than finding a new face in the call.

4

The pair runs the demo

Every week, from the people who made the thing. No status deck, and nobody presenting work they did not do.

You are on a live project in the first week, on a small piece of it, with the person who owns that piece sitting next to the work. Nobody spends a fortnight reading documentation before they are allowed to touch anything.

What you do

  • Ship one change to something real and watch it go out
  • Sit in a client demo without having to say anything in it
  • Read the theme tokens and the field naming conventions, because everything else assumes them

What we do

Somebody is responsible for you by name. If you are stuck for a day that is our failure to notice rather than yours to report.

You own a piece of a phase end to end: you decide how it is built, you show it in the weekly demo, and you answer the question the client asks about it. Owning a small thing completely teaches more than helping with a large one.

What you do

  • Take one component or one template from draft to shipped
  • Present it yourself in the demo
  • Write the handover note for the part you built

What we do

We review the work rather than the hours. A review is a conversation about the decisions, in writing, that you can disagree with.

By the first full project you are half of a pair, which means your name is in the proposal and you are in the room when the direction is chosen. Whoever designs a thing here builds it, so the pair is a designer and an engineer who both stay to the end.

What you do

  • Run your half of a phase and call it finished or not finished
  • Sit in the assessment interviews rather than reading the summary
  • Take the handover session for the part you built

What we do

You are not moved off a project to cover another one. If that has to happen it is said out loud to you and to the client.

Getting hold of someone

Ask for a person by name.

The contact form is read by a person, not a routing rule. Put a name from this page in the message and the reply comes from them. Once a project starts you have the pair directly, the weekly demo is with the people building the thing, and there is nobody in between whose job is to relay it.

Send a message How a project runs
Two people working through a project together

Yes. The proposal names them, and if they are not available until a date it says the date rather than a start window. A change of person mid-project is told to you in the demo it happens in.

No. The people on this page are the people on the projects. The weekly demo is run by the pair building the work, and the answer to a question about a decision comes from whoever made it.

Ask. If they are free and the work suits them the answer is usually yes. If they are not free you get the date rather than a substitution you were not told about.

The other half of the pair keeps the work moving and the demo still happens. A phase gate moves rather than the quality of what lands on it, and the new date is said in the demo rather than discovered later.

Sometimes, for a discipline a project needs and we do not do every week. When it happens the person is named to you the same way anyone else is, and they sit in the demos rather than behind them.

Yes. Send the work rather than the CV and say which of the decisions above you would want to own. The open roles and what each of them pays are on the careers page.

Hiring

Want to work here?

The open roles say what they pay and what the first three months are. If none of them fit, send the work anyway and tell us what you would want to own.

Every role lists what it pays before you apply

  • check_circle You work on the projects, not on a pitch deck
  • check_circle Whoever designs a thing builds it
  • check_circle You ship something real in the first week
View open roles Send a message

Send the work rather than the CV, and say which decision you would want to own.