Skip to content
AslanWay
ENKO

Process

Consulting and build, as one sequence.

Five phases from first workshop to handover. Each has a fixed purpose, a named deliverable and an exit criterion that can stop the programme — including the first one.

  1. 01Diagnose2–4 weeks
  2. 02Frame2–3 weeks
  3. 03Prove6–12 weeks
  4. 04Build & scale3–12 months
  5. 05Transfer & runContractual, from month one

The five phases

01

Diagnose

Typical duration
2–4 weeks

Establish, in your own financial terms, what the opportunity is worth and what stands between you and it. We are equally willing to conclude that the programme should not go ahead.

What you get

  • Quantified value map tied to your financial statements
  • Current-state architecture and constraint register
  • Research findings with verbatim evidence
  • A go / no-go recommendation with the reasoning shown
02

Frame

Typical duration
2–3 weeks

Convert findings into a plan someone can be held to: target architecture, dependency-aware sequencing, a funding case, and a first slice scoped tightly enough to reach production this quarter.

What you get

  • Target architecture and architecture decision records
  • Three-horizon roadmap with an explicit dependency graph
  • Costed investment case and commercial model
  • First-release backlog, estimated and ready to start
03

Prove

Typical duration
6–12 weeks

Replace opinion with evidence. In week one we deploy something trivial all the way to production so that environments, credentials, security review and deployment approval surface while nothing is at stake.

What you get

  • A working vertical slice live in production
  • CI/CD pipeline, automated tests and observability
  • Measured results against the baseline agreed in Frame
  • A revised estimate for the rest of the roadmap, informed by actual velocity
04

Build & scale

Typical duration
3–12 months

Extend from the proven slice to the full scope without losing the delivery rhythm — adding journeys, segments, channels and sites while the platform hardens underneath.

What you get

  • The full scope in production, released incrementally
  • Tested disaster recovery and documented recovery objectives
  • Architecture decision records and system documentation kept current
  • Accessibility conformance verified in the pipeline
05

Transfer & run

Typical duration
Contractual, from month one

Make our exit a plan rather than an event. The transfer is written into the contract at kickoff: named roles, dated milestones, and a fee that steps down as each function moves to your team.

What you get

  • Dated capability transfer plan with named owners on both sides
  • Runbooks, on-call rotation and rehearsed incident process
  • Continuously maintained audit evidence pack
  • A client team that has been reading and reviewing the code for months

What runs through every phase

  • One team, one accountability line
  • Production from week one
  • Your engineers are in the squad
  • Every phase can end the programme
  • Cadence over heroics
  • Say the difficult thing early

Have a programme that has stalled between slideware and shipping?

Start the conversation