</> Engagement model
No black boxes.
No surprises.
A repeatable sequence that keeps you in control and produces something reviewable at every stage. Same shape whether the engagement runs six weeks or two years.
The sequence
Five phases.
Each one ends in an artefact you can read, review and disagree with — before the next one starts.
- 01 1–2 weeks
Map the dots
A structured workshop with the people who live in the system. We chart the processes, the handoffs, the tools and where value leaks — then write it down and read it back to you. Most engagements find at least one problem nobody had named yet.
You get
- System map
- Prioritised problem list
- Scope in writing
- Costed options
- 02 1 week
Draw the lines
Technology selection, system design, data model and integration contracts. The blueprint exists before the build does, so the expensive decisions are made while they are still cheap to change.
You get
- Architecture & data model
- Integration contracts
- Delivery plan & milestones
- Risk register
- 03 4–20 weeks
Build in fortnights
Two-week sprints, each ending in working software in a staging environment and a written update. You see progress you can click. Scope flexes inside the plan; the cadence does not.
You get
- Working release each fortnight
- Written sprint update
- Test suite & CI pipeline
- Living documentation
- 04 1–3 weeks
Connect & cut over
Integration, data migration and a go-live window chosen to minimise risk — rehearsed, reversible, and with reconciliation so you can prove the old and new systems agree.
You get
- Migration & rollback plan
- Reconciliation reports
- Runbooks
- Launch checklist
- 05 Ongoing
Scale & sustain
Observability, cost tuning, and a roadmap for what comes next. Thirty days of cover are included after go-live; beyond that we stay on as much or as little as you need.
You get
- 30-day post-launch cover
- SLOs & alerting
- Cost review
- Quarterly roadmap
Cadence
The rhythm you
can expect.
Predictable communication is a feature. You should never have to ask where a project stands.
-
Weekly
30-minute check-in
Progress, blockers, decisions needed from you. Cancelled without ceremony if there is nothing to decide.
Plus an async written note either way.
-
Fortnightly
Demo & written update
Working software in staging, what shipped, what is next, and any change to the plan or the number.
Attendees anyone in your business who wants to look.
-
Monthly
Plan & budget review
Burn against estimate, scope changes, and an honest read on risk. No surprises at invoice time.
Output a one-page summary for your board or sponsor.
Your part
What we ask
of you.
Short list, but the projects that struggle are always missing one of these.
- 01
One decision-maker
Someone empowered to say yes, no, or not yet — reachable inside a day.
- 02
Access to the people who do the work
A few hours with the person who actually runs month-end is worth a month of guessing.
- 03
Honesty about constraints
Budget, deadlines, politics, the system nobody is allowed to touch. We design around real limits, not stated ones.
- 04
Feedback on the demo
Every fortnight there is something to react to. Reacting is the cheapest way to steer.
Commercials
How we price.
Discovery is always scoped and priced separately, so you can stop after it with something useful in hand.
-
01
Fixed scope
A defined outcome for an agreed number, after discovery has made the scope real. Change requests are priced openly.
Suits well-understood builds and integrations.
-
02
Sprint-based
A team at a fixed fortnightly rate with a rolling backlog you control. Stop at any sprint boundary.
Suits evolving products and platform work.
-
03
Retainer
Reserved senior capacity each month for support, improvement and the things that come up.
Suits live systems that need an owner.
Start with
the map.
Discovery is scoped separately and priced up front. If we are not the right partner after it, you still keep the map.