You will always know where your project is.
Projects rarely fail on capability. They fail because some layer had no owner and the gap only became visible at the point it was expensive. Everything below exists to stop that.
In this order, on every engagement.
The numbering is not decoration — each stage gates the next, and skipping one only moves the cost later.
- 01
Discover
We sit with the people who will use the thing and map how the work actually happens — not how the org chart says it does.
- 02
Blueprint & scope
Architecture, screens and a scope you can hold us to, with the trade-offs written down rather than discovered in month three.
- 03
Build in sprints
Two-week sprints against a working build. Every Friday you see the real product, not a status deck.
- 04
Harden & launch
Load, security and edge cases before launch day, then migration and go-live with a rollback plan that exists on paper.
- 05
Operate & evolve
Monitoring, patching and the next round of changes. The system keeps working after the invoice clears.
Three commitments.
One pod, one owner
A named engagement lead from the first call to the day after launch. You never explain your project to a new person.
You see it every week
A working demo every Friday, on the real build. No black-box months, no surprise at the end.
Your code, your IP
Full source handover, documented, on your infrastructure if you want it there. No licence, no lock-in.
What a sprint actually looks like.
“Agile” on its own tells a buyer nothing. This is the shape of every two weeks you will spend with us.
- Monday, week one
Sprint planning. You set the priorities; we say what fits and what it displaces.
- Through week one
Build, with questions raised the day they come up rather than saved for a status call.
- Friday, week one
Internal review and a build you can click if you want to.
- Through week two
Build continues. Mid-sprint changes are possible and we will tell you their cost before taking them.
- Friday, week two
Demo on the real product, then a written note of what shipped, what did not, and why.
Three ways to work with us.
Which one fits is answered after discovery. Choosing up front is how a project ends up scoped to the model rather than to the problem.
Fixed scope
The requirement is genuinely settled and you need a defined thing delivered by a defined date — a site, a launch, a migration.
One price, agreed after discovery, staged against milestones.
- A dated plan
- Milestone demos
- Handover and documentation
- 30 days of post-launch fixes
Dedicated pod
The product will evolve as you learn from it, which is true of almost every platform. Scoping it up front would only be guessing expensively.
A monthly rate for a named pod. Scale up or down with a month's notice.
- A named engagement lead
- Two-week sprints
- A working demo every Friday
- Priorities you set each sprint
Retainer & managed
The system is live and needs to stay that way — yours or one you inherited from someone else.
A monthly retainer sized to the system, with response times written into it.
- Monitoring and incident response
- Security patching
- A budget of change each month
- An agreed response SLA
What we need from you.
Stated plainly, because the engagements that go wrong are almost always the ones where these were assumed rather than agreed.
One decision-maker
Someone who can settle a question in a day. Not a committee that meets fortnightly — that is where two-week sprints go to die.
Access to the people who do the work
An hour with the person who actually runs admissions, or the schedule, is worth more than a month of requirements documents written above them.
Honesty about the current mess
Every organisation has workarounds it is slightly embarrassed by. Show us those first. They are the requirements.
Attention at the demo
Thirty minutes every second Friday. Feedback at the demo is cheap; feedback after launch is not.
Let’s map your business.
Tell us how your business runs today. We will show you what it could look like with the right system behind it. We reply within one working day.
PDF · 12 pages · 5 MB