Shape the first useful release
An idea that needs a clear starting point.
Proposed outputs to agree
- A problem statement and intended audience
- A prioritised first-release scope
- A proposed delivery approach and explicit assumptions
Work with the studio
Build the right thing.
Then build it well.
We help a small number of partner teams turn a real problem into a useful product. Start with the audience and constraints, agree the scope, and keep the evidence visible as the work progresses.
Three ways to work together
Design and build
A defined problem that needs a working product.
Proposed outputs to agree
- Agreed journeys and interface designs
- Engineering against a reviewed scope
- Testing, launch preparation and handover materials
Improve what already exists
A team with a product that needs focused support.
Proposed outputs to agree
- A review of the current product and constraints
- A prioritised improvement backlog
- Agreed engineering support and measurement
These describe possible engagements, not fixed-price packages. Cost, timeline, ownership, support and acceptance criteria are agreed in writing before delivery begins.
Our own products, clearly labelled
A closer look at how we build
Owned product · Payments · Product engineering
Invoicing that starts with how a business gets paid
Read the product story
Owned product · Finance workflows · Exception handling
Make payment exceptions visible instead of hiding them
Read the product story
Owned product · Native applications · Privacy-led design
Treat private memories as the user's own data
Read the product storyThese are internal product narratives, not client testimonials. We do not invent customer outcomes.
Know what happens next.
- 01Share the problem and your current situation.
- 02Discuss fit, constraints and a useful starting scope.
- 03Agree responsibilities, terms and acceptance criteria.
- 04Build, review and prepare a clear handover.
What an enquiry does not do
Sending a brief does not reserve capacity, sign a contract or authorise us to access your systems. Ongoing maintenance, hosting and support are separate unless the agreed engagement includes them.
A short, honest brief is enough to begin. Do not send production passwords or customer data.
Create a brief without an account