How we work
From discovery to an SLA.
We'd rather build AI than talk about it. Eight steps take you from getting to grips with your operations to a system running on the shop floor, with a project brief you approve before the quote, a go/no-go at every phase, and software that's yours at the end.
Eight steps, no surprises.
Every step has a clear outcome. You always know where you stand and what you walk away with.
Discovery & scoping
You get
A sharp picture of your operations and a clear scope, with the biggest win up front.
We start on the shop floor, before any quote. We get to know your process, your systems and your people, work out where time or margin is leaking, and agree together what's in and what's out.
- We look at how the work actually happens, not how the process reads on paper.
- Where the day-to-day friction sits, and where AI genuinely helps.
- Scoped together, focused on the highest value rather than tackling everything at once.
Design & prototype
You get
A design and prototype that show how the solution works.
Talking about software is tricky; seeing it is far easier. We put together a design and a prototype so you can shape the direction early, while it still costs nothing to change.
- Shape the direction early against something you can use, rather than a document.
- A design built around how your people actually work.
- Assumptions tested before we build anything at scale.
PRD
You get
A signed-off PRD covering scope, modules, assumptions and schedule.
The PRD is the full specification of what we build, written down and signed off before we begin. Scope, modules, assumptions and schedule are all on paper, so we build towards a fixed target rather than a moving one.
- Scope and modules, spelling out what we will and won't build.
- Assumptions written out plainly so they can be checked.
- Sign-off before a line of code is written.
Building in phases
You get
Working software with each phase, owned by you and free of lock-in.
We build in short phases against the PRD. You see something running early and grow it step by step, rather than waiting months for one big launch.
- A first working result early, then more from there.
- Wired into your existing ERP, TMS, MES or customs software.
- The code, the data and the system all belong to you.
Testing: go / no-go
You get
A tested phase with a considered go or no-go decision.
At the end of each phase we test it against day-to-day reality. We only carry on once you give the go; if it's a no-go, we put it right first. That keeps you in control.
- A considered go/no-go at every stage, so nothing moves ahead on faith.
- Tested in your actual operations, not just on paper.
- You keep the reins and the risk stays small.
Delivery
You get
A working system in production, delivered and yours to keep.
We take the solution live in your operations and hand it over cleanly. Working software that earns its keep day to day, well clear of any report left to gather dust in a drawer.
- Live in production, well past the demo environment.
- A clean handover with proper documentation.
- Software that runs alongside your people.
SLA & support
You get
An SLA covering monitoring, support and continuous improvement.
Going live is only the start. Under an SLA we carry on monitoring, supporting and building, so the system keeps working in production and grows with you.
- Monitoring and support that keep it running.
- Building out into new processes, guided by the results.
- A partner that scales with your operations.
In short
The scope is settled before the price.
The project brief sets out exactly what we build and why: the scope, the modules, the assumptions and the schedule in broad strokes. It's the substance of the proposal, kept apart from the price, and we sharpen it together with you until it's right.
The commercial quote, with price, milestones and terms, only follows once the project brief is agreed. So you know exactly what you're getting up front, and any talk about money rests on a target that has already stopped moving.
Once the quote is signed, we work the project brief up into a full PRD: the functional blueprint that has us ready to build.
Scope & modules
What we will and won't build, broken down into modules.
Assumptions
What we're taking as given, written out so it can be checked.
Schedule
The phasing in broad strokes, from build through to go-live.
Get started
Start with a conversation.
First we get to grips with your operations. After that you'll know exactly what we'd build and what it would cost, before a single euro changes hands.