Every journey in the enterprise was designed around a constraint that no longer holds.
Foundation Cycle is Mitochondria's co-innovation programme for medium-large and enterprise businesses: a structured set of sprints that reimagines your customer journeys, workflows, and operating cycles, and closes with your organisation aligned on exactly what to build, and why.
The question "where does AI fit in this process" concedes the process.
Foundation Cycle begins one level down, at the constraint the process was designed around, and redraws the journey as it should exist now. AI is the operating condition of the redraw, never a feature placed into the old drawing. The customer journeys, internal workflows, and operating cycles an organisation runs today encode decisions made when reading was slow and senior judgement could only be where the senior was standing.
For the organisation, this is the difference between a faster version of the journey it already runs, and the journey it would design today if it were starting from the world as it is. The first is an optimisation, available from any vendor. The second is a redraw, and it requires the redrawing and the building to sit in the same hands, so that nothing is lost between the map and the system.
The journey, drawn for the constraints that actually hold.
A journey built around lapsed constraints accumulates stages, handoffs, and waiting. The redraw removes the stages that existed only to ration scarce attention, runs in parallel what once queued, and keeps human judgement exactly where it carries weight.
Examined, redrawn, agreed.
A Foundation Cycle moves through three movements. Each produces what the next works from, and the cycle closes with the organisation aligned on the future state and the programme that builds it.
The working sessions
Discovery runs in working sessions with your leadership group, in the room, with your people. The sessions are structured around the questions a redraw has to answer: what an agentic operation makes possible, why the back end is mapped before anyone draws screens, how the work that follows should be judged. Your organisation's operational truth, its constraints, exceptions, and undocumented judgement, surfaces in the session, and the map drawn there becomes the basis of everything that follows.
The redraw
Customer journeys, workflows, and operating cycles are reimagined end to end, designed for the constraints that actually hold today. Every journey that warrants rebuilding is redrawn. The front end of each remains an open question until the redraw answers it: conversational, button-led, voice, or a brand-led application. The real subject is the agentic foundation underneath, and direction is proven as it forms, through working demonstrations your leadership can see and challenge.
The alignment
The cycle closes with a single, shared picture of the future state: what gets built, in what order, on what architecture, and what each build requires. Every build is then scoped and commissioned on its own capability requirements.
A cycle ends in clarity.
The cycle is engineered to produce clarity at speed: the journeys demonstrated along the way, and everyone aligning with a picture of what gets built and why.
The future state, agreed
A single picture of the reimagined operation, examined and agreed by your leadership, with the reasoning that produced it on record.
The mapped back end
Systems, interfaces, constraints: the things nobody in the building could previously describe in one place, now described in one place.
Working demonstrations
The redrawn journeys demonstrated against your context through the cycle, seen and challenged by the people who will own them.
The build programme
The sequence, the scope, and the requirements of each build, written at the close of the cycle and ready to commission.
Run with the discipline a board would expect.
The cycle is governed the way serious transformation programmes are governed: a clear baseline, stage-gate reviews, and value tracked from the first sprint. People behaviour is treated as an engineering surface on both sides of the journey: the brand's register held with customers, and adoption built into the way the system works with your teams.
A year's reimagination, earned one cycle at a time.
Every sprint ends at a gate, and the cycle ends with the build programme defined. What follows is scoped only from the cycle's outputs: each build commissioned in the sequence the roadmap sets. For organisations planning a full reimagination, the arc runs nine to twelve months, with the Foundation Cycle as the first quarter and every engagement after it earned on the record of the one before. By the final gate, the organisation holds a complete account of what was rebuilt, what it cost, what it returned, and how every decision along the way was made.
For leadership teams that intend to set the pace.
Foundation Cycle is built for organisations of sufficient scale that the journeys in question carry material value. It asks three things of the client: a senior sponsor with the authority to convene the leadership group, a journey the organisation feels genuine pain on, and your own people in the room for the working sessions.
The programme closes in an agreed, build-ready picture of the future state. Organisations looking for a speculative proof of concept, or for a recommendations deck, will find the structure unaccommodating. That structure is what protects the organisations the programme is for.
Worth asking.
Is this a consulting engagement?
A consultancy closes with recommendations. Foundation Cycle closes with your leadership aligned on the future state and a build programme specified to the point where development can be commissioned with confidence. The people who run the sessions are the people who architect what follows, and, where you choose, build it, so nothing is lost between the thinking and the making.
Does the cycle include development?
No, by design. The cycle includes working demonstrations, and it specifies the builds; development is commissioned from what the cycle specifies, each build scoped on its own requirements. Keeping the two apart protects both: the discovery is never bent toward a predetermined build, and no build is priced before it is specified.
What happens if we stop after one cycle?
Then you stop, holding the agreed future state, the mapped back end, the demonstrations, and a build programme you can act on with us or without us. Every cycle ends at a gate, by design, and the model assumes nothing beyond the cycle in progress.
Who needs to be in the room?
The senior sponsor, the leadership group for the journeys in question, and the people who hold the operational truth: the ones colleagues actually ask when something is unclear. The sessions are working sessions, and what surfaces in them shapes everything built afterwards. Absence is the only reliable way to lose value from the cycle.
Is there a discovery phase before the cycle begins?
Discovery is the cycle's first movement and the most valuable work in it; it is priced as such. The map, the architecture, and the build programme are deliverables of the paid cycle. A working session precedes the engagement, where the candidate journeys and the scope take shape.
How does this relate to Mitochondria's products?
The cycle decides what gets built; the product family is what the builds that follow draw on. Where a redrawn journey calls for capabilities Mitochondria has already productised, development moves faster and inherits the governance posture those products carry. Where it calls for something new, the foundation is designed for the journey at hand.
What does it cost?
The cycle is a fixed fee, set against the scope of the journeys in question. The builds that follow are scoped and priced individually. Specifics are shared in the working session.
Begin with a working session.
A session with your leadership group, in person wherever possible: the candidate journeys surface, and the cycle takes shape.