No tender, no day-rate,
no surprises.

We spend time with the people who’ll actually use the thing, not just the people who’ll pay for it. We map the workflow, the data, the tools you already use and the constraints nobody’s written down. The output is a written report covering what we’d build, what we’d leave alone, what we’d integrate with, and what it’ll cost.

What you bring

• Time from two or three of the people who do the work
• Read access to whatever spreadsheets, docs and systems exist
• One stakeholder empowered to answer questions

What you get

• A written, signed-off scope
• A fixed price for phase ③
• A go / no-go decision — you can stop here

We translate the diagnostic into a buildable spec: data model, screens, integrations, permissions, deployment plan. You see wireframes; you see the database schema in plain English; you see exactly what month-one through month-three of the build looks like.

The principle

You sign off the spec before we write production code. Nothing gets figured out on the fly, and nothing is allowed to surface as an unexpected cost at week six.

A senior engineer takes the spec and builds it. Weekly demos, with real users on real data inside the first three weeks rather than at the end. The default stack is the one we run our own products on (Laravel, Livewire, Tailwind and PostgreSQL on Azure or AWS), unless there’s a specific reason to vary.

What “done” means

• The whole spec, deployed, on UK infrastructure
• Tested with your data, by your team
• Documented — runbook, schema, integration points
• Handover session with whoever’ll administer it

We migrate the data and run the new system in parallel with whatever it’s replacing for one full cycle of your work, whether that’s a quarter, a month or a single campaign. The old system is then retired properly, with a handover note. The parallel run is the part that quietly determines whether the project sticks or reverts; we don’t skip it.

We host the system, monitor it, patch it and evolve it. There’s no separate support team to hand off to; the engineer who wrote a bug is the one who fixes it at 3pm on a Tuesday. Most of our clients have been with us for five years or more, and we expect that pattern to continue.

What’s included

• UK Azure or AWS hosting, monitored 24/7
• Security patches, dependency updates, framework upgrades
• UK office-hours support, named contacts
• Quarterly roadmap conversation
• Up to a defined budget of evolution work each month

What costs extra

• Major new features (treated as a small "build" engagement of their own)
• Out-of-hours incident response if you want it