WHAT YOU GET
04 deliverables
01Working software, not a prototypeDeployed, monitored and in front of real users at the end of the first phase rather than demonstrated on a laptop.
02A senior podProduct, design and engineering in one team, with the authority to decide without escalating.
03Partner platforms where they earn itWe build on what exists when it shortens the path and write it ourselves when it does not. The choice is explained, not assumed.
04A timeline your board will believeScoped to a date, with the cuts named up front instead of discovered in month three.
HOW IT RUNS
Two-week cycles with something usable at the end of each. Scope moves; the date does not.
WEEK 01–02Frame
The users, the one job the product has to do, and the constraint that decides the architecture.
WEEK 03–08Build to a date
Usable software every cycle, in front of real users early enough that their feedback can still change it.
WEEK 09–14Harden and hand over
Performance, security review, support runbook, and the team that will own it after release.
WHERE IT LANDS
OUTCOME
Something real in front of users
Early enough that what you learn can still change what gets built.
OUTCOME
Fewer decisions deferred
A senior pod decides without escalating. In most programmes that is the exception, not the operating model.
OUTCOME
A product your team can carry
Documented, tested and staffed before we leave the building.
THE SHAPE
DURATIONTypically 14 weeks to first release.
TEAMOne pod: product, design and two to three engineers.
DELIVERYRemote, in your cloud and your CI from day one.
PREREQUISITESA named product owner who can decide scope without a committee.
LEADS INTOA resident pod for the next release.
NOT A FIT WHENThe requirement is a full platform replacement. That is a different shape of programme.
SHIP IT THIS QUARTER.
Fourteen weeks to working software, with the trade-offs named at the start rather than the end.