Every engagement runs on the same plumbing: work arrives through Kai threads, executes inside Ark intents, and is documented on Project Hub. Four core roles sit on top of that pipe, each fully agentic, with optional Implementation Consultants where scale calls for extra delivery muscle.
Three roles face the customer directly. The Solution Lead designs and scopes what gets built; the Agentic Consultant gets it executed; the Product Expert makes the customer able to run it themselves. The Engagement Lead carries delivery and governance underneath all three.
Kai threads are the front door for all work. Ark intents are the boundary every piece of execution runs inside. No work happens outside the pipe.
The roles do not change between phases. The seating does. The Solution Lead takes the front seat in Foundation and hands it to the Engagement Lead for delivery, who augments with Implementation Consultants as required.
Design, scope and proving the solution with the customer.
Delivery, governance and taking the solution live.
Every live engagement placed into the model as it stands today. The highlighted cell is the front seat for that engagement's current phase. Seats are mapped from the June resource snapshot; names marked TBD are being confirmed.
| Engagement | Phase | Solution Lead | Engagement Lead | Implementation Consultant | Product Expert | Agentic Consultant |
|---|---|---|---|---|---|---|
| A+R | Foundation | Grace heavy support: Ivan + Tómas | Grace Aquiva · PM support: Anna F (Aquiva) | Sebastian Aquiva | Lindsay Christabel as backup | Ragnar Alex as backup |
| TTC | Foundation | Ragnar | Petar | Monika | Shared pool Diego's team | Ragnar |
| TTC | Delivery | Ragnar | Petar or new hire brought in | Monika | Marijana | TBD |
| GRJ | Delivery | Frankly partner | Frankly partner + Tracy internal | Frankly partner | Shared pool + Neil | TBD |
| Bunnik | Delivery | Anita | Anita | — | Karen + Caine | TBD |
| Belmond | Delivery | Ivan | Danny | Neil | Sam 50% | TBD |
| Intrepid TM | Delivery | Caine | Benoit with Janet | Stjepan | Stjepan + Kenneth | TBD |
| Tauck | Hypercare | Kristijan | Stephen | Denis K / Tomislav H | Product team | TBD |
| Armstrong | Live | — | — | — | Shared pool Diego's team | Ragnar Edge |
| PLX | Incoming | TBD | TBD | — | TBD | TBD |
| No engagements match this filter. | ||||||
Programme and portfolio oversight (Tracy, Janet, Stephen, Danny) folds into the Engagement Lead seat or sits at portfolio level; confirmed per engagement. Partner-held Engagement Lead seats require an internal pairing per the governance rule above.
Kai is open to the whole engagement for questions and triage. Execution is different: work only becomes real inside an Ark intent, and only the Agentic Consultant drives that.
Questions, triage, context, status. No permission needed, no queue. This is how work gets shaped before it becomes an intent.
Kai responds directly on the channel: answers, investigation, prioritisation. Anyone can trigger this, including the customer.
Requests that change something become Ark intents. Only the named Agentic Consultant executes them, inside the intent boundary, with a human accountable for the result.
The same four roles on two axes: whether the role primarily faces the customer or the system, and whether it builds the engagement or sustains it.
Design and scope. Decides what is built and shapes it into Ark intents. Scope content on Project Hub. Foundation-heavy.
Executes through Ark within intent boundaries. Named per channel, on the calls.
Training and enablement. Requests execution via Kai and Ark sweeps.
Delivery and governance: timing, budget, forecasts. Takes the solution live from Phase 2. Project management section on Project Hub. Optionally supported by 1 to 2 Implementation Consultants.
All execution flows through Kai threads and Ark intents regardless of which role originates it. Partner Engagement Leads are always paired with an internal equivalent. Implementation Consultants are an optional addition where engagement scale calls for parallel delivery and testing capacity.