There’s no point where thinking stops and building starts.
A small example: an illustrative brief, not a clientThe problem: new customers keep dropping out in their first month.
A welcome tour for new customers.
Six small changes. None of them a tour.
This is a small example. On every project we aim to build the best thing possible, and we test as many ideas as it takes to get there.
A prototype tells you something a conversation can’t.
A technical constraint can change what the product should even do. An assumption that felt solid in week one can look shaky by week three, once there’s something real to react to.
So we don’t lock in a plan and then execute it.
We keep deciding as we go, because the work keeps teaching us things worth deciding on. Business, product, systems and engineering perspectives stay in the room for the same reason, not signed off once and filed away.
For you, that means the brief you start with and the thing you end up with won’t be identical.
That’s not a failure of planning. It’s what happens when the plan is allowed to learn something.
AI changes how much of this is practical.
Testing an idea by making part of it gives you something concrete to learn from. AI makes that much easier to do repeatedly, within the time and budget of a real project.
A small, senior team can investigate more routes, test more assumptions, prototype more ideas and iterate further before expensive decisions become difficult to undo.
That doesn’t mean less care per decision. It means more decisions get tested against something real.
We use AI across the whole of the work, from research and design to prototyping, code and testing. We’re not loyal to one model or platform. We use the best of what’s already out there. When what’s needed doesn’t exist yet, we make it.
More chances to catch a wrong turn while it’s still cheap to fix.
What to expect.
The thinking carries on while we build. What you’re agreeing to is clear from the start.
It usually starts with you getting in touch. From there it can be a call, a paid discovery, a prototype or a proposal, depending on what you’re bringing us.
A scope and a cost, so you know exactly what you’re deciding on.
Small projects are a fixed price. Larger ones are usually a fixed price in phases. Some work suits time and materials or a retainer.
Small changes can usually be absorbed within the project cost. A bigger change means we look again at the scope and the cost.
That depends on the project: support, hosting, an ongoing retainer, or a handover to your own team.
Bring us a specification, a problem, or an opportunity. We’ll work out what it needs, and take it through to working technology.