Services
Four ways to work with the studio, in the order a project usually takes them. Each starts by questioning the brief, and each ends with something you can read, try or run.
An analysis of your brief
For anyone deciding whether to build
Before anything is built, we question the brief, test what it assumes against the evidence, and write up what we found: the problem behind the ask, the parts it splits into, and a first test you can run without software. It arrives in a private room on this site.
What this includes: An analysis of your brief
- Each assumption in the brief tested against public research and your own material
- The problem, as the evidence states it, in writing
- The problem in parts, with how long each has to last
- Questions only you can answer, and a test to run before any build
Good for: An analysis of your brief
- A concept that is still early
- A board, a funder or a partner who wants to see the thinking before the spending
- Deciding whether to build at all
A working version for your pitch
For consulting firms
You bring the client’s problem and the date of the pitch. We build a working version on realistic data, so the room sees the answer working. We can build it under your firm’s name.
What this includes: A working version for your pitch
- Questioning the brief with you until the real problem is clear
- A working version on realistic data, ready for the meeting
- White-label: built and presented under your firm’s name
- The record of how it was checked, and what was left out
Good for: A working version for your pitch
- A pitch or proposal with a fixed date
- A client who needs to see it before they believe it
- Firms without an in-house product team
Product, design and engineering for a decision
For teams who need tailored software in any sector
When a decision depends on software that doesn’t exist yet, we build the version that answers the question first, then the parts that have to last.
What this includes: Product, design and engineering for a decision
- Discovery and decomposition sessions on your brief
- A working version for the people who decide
- Engineering for the parts that have to last, starting with the data model
- Accessibility and contrast checked on every screen
Good for: Product, design and engineering for a decision
- A funding or go/no-go decision
- Replacing a spreadsheet process with a tool people trust
- Teams who need a product partner for a few months
A build that has to last
For teams who need software built, and kept running
When the decision is made, we build the product: the web app, the data behind it and the services around it, engineered to be kept, with the checks and their record in the code.
What this includes: A build that has to last
- Design, engineering and the data model from one team
- Accessibility and contrast checked on every screen
- Tests, deploys and the record of how it was checked
- A handover your own people can run, or a team that stays on
Good for: A build that has to last
- A working version that proved itself and now has to last
- A product with a team of one, or none
- Software a consulting firm delivers under its own name