Three ways to start

Most first engagements fit one of three shapes. Each has a defined length, defined outputs and a defined way of being accepted, and each is useful on its own.

Three ways to start

Solution Design Sprint

For a team that has to make a concrete architecture decision and is caught between competing options and constraints.

Length
Two weeks
Scope
One bounded design question
Format
Stakeholder workshops and independent design time
Options compared
Up to three

Read more: Solution Design Sprint

Modernization Partnership

For an organization that knows a platform or architecture has to evolve, and needs an achievable route and help keeping decisions coherent along the way.

Starts with
An initial assessment and roadmap
Then
A three- or six-month partnership
Capacity
Days reserved each month
Implementation
Owned by your team or partner

Read more: Modernization Partnership

Side by side

Infrastructure Clarity SprintSolution Design SprintModernization Partnership
ForA critical environment few people understandA decision stuck between competing optionsA platform or architecture that has to evolve
LengthTwo weeks, up to 10 working daysTwo weeksAn assessment, then three or six months
You end withA current-state diagram, a findings register and a prioritized backlogA recommended architecture, a decision and risk register, and a roadmapA roadmap kept current and decisions kept coherent
Often leads toA design sprint, documentation, or quarterly adviceImplementation readiness, or a partnershipA renewed term, or a handover

Adjusted before it is quoted

These are deliberately bounded starting points, not fixed packages. Before quoting, the scope is adjusted to the complexity of your environment, the access available, your team's readiness and the calendar.

Each offer page prints as a one-page sheet, to share with the people who will decide.