The problem comes before the technology.
We choose the stack after we understand what the business needs and what the people using it need to do.
How We WorkFIELD GUIDE / 01
From the first fit conversation to a working release
Howwe work.
No mystery process. No packages pretending every business has the same problem.
We decide the useful first version, price it clearly, build it where you can see it, and agree what responsibility looks like after launch.
Follow the processStart
The business problem
Middle
Visible working software
Finish
A controlled launch
THE PRINCIPLE
A package starts with what an agency wants to sell. A good project starts with what your business needs to change.
You do not buy a package. We shape the right first version.
THE PROCESS / 01—06
From problem to working product.
The shape changes with the project. The discipline does not: understand, focus, agree, build, prove, launch.
- 01
Fit
Start with the problem or product idea.
Explain what should be possible, what is getting in the way, and why it matters. The first decision is whether x Create adds enough value and what the sensible next step is.
A fit decision and a useful next step - 02
Define
Decide what should exist.
Clear, bounded work can move directly to a scope. Substantial work with material uncertainty begins with a paid Solution Blueprint covering users, journeys, business rules, risks, integrations, ownership assumptions, and the first useful release.
A scoped build or a Solution Blueprint - 03
Agree
Name the commercial and operating model.
The engagement order states the scope, price, payment schedule, delivery assumptions, ownership model, ongoing responsibility, usage treatment, third-party costs, and change process. Uncertainty is recorded, not hidden.
A decision-ready commercial pack - 04
Build
Watch the real thing take shape.
We work in visible stages and show progress in the product itself. You react to screens, journeys, and working behaviour rather than trying to imagine the final result from a document.
Regular working previews and direct decisions - 05
Prove
Test the journey that matters most.
Before launch, we walk through the real customer and operations journeys, check the awkward cases, test across the devices that matter, and fix the details that make software feel trustworthy.
A launch-ready product, not a presentation - 06
Launch & choose
Launch with responsibility made explicit.
After launch, the engagement follows the agreed path: a clean build-only handover, defined managed operation, or a Product Partnership for substantial ongoing responsibility. Expansion is separately scoped unless it is expressly included.
A controlled launch and a clear operating path
PROJECT-BASED PRICING
Priced individually. Explained clearly.
A landing page, a booking platform, and an operations system are not the same product. Their prices should not pretend to be.
Once the scope is clear, you receive one proposal covering the build cost, timeline, support options, and third-party running costs. No package theatre and no surprise invoice halfway through.
01
Scope
How many journeys, screens, roles, and edge cases the first release needs.
02
Complexity
The business rules, permissions, data, and decisions the product must handle.
03
Connections
Payments, messaging, CRMs, external APIs, and existing systems.
04
Running costs
Hosting and third-party services such as model usage, email, SMS, maps, and storage.
BEFORE YOU SAY YES
The proposal names the deal.
01
What the first release includes
02
What it deliberately leaves for later
03
The project price and payment schedule
04
The working timeline and decision points
05
Ownership, handover, accounts, and access
06
Managed-operation options and external costs
WORKING RULES
What does not change.
Different projects need different shapes. These rules keep the relationship understandable on all of them.
You see the work while it is still changeable.
Working previews replace long periods of silence and a dramatic reveal at the end.
Ownership matches the actual deal.
Client data and business materials remain the client's. Bespoke deliverables, reusable x Create capability, third-party rights, accounts, access, and exit obligations are stated for each engagement instead of hidden behind one universal promise.
YOUR TURN
Start a conversation