Skip to content

Delivery Stakeholders

The decision-makers, approvers, and informed roles that the customer team and the Evospin team work with throughout a rollout. Used by the phased rollout to identify who signs off on each phase gate, by risks to assign mitigation owners, and by the launch checklist to confirm sign-offs.

Status: structure defined; names and contact paths are filled in by the customer team during phase 1 (Discovery) of ./phased-rollout.md. Every {{TBD}} is a customer-team-owned slot.

RACI summary

The four-role matrix used throughout the delivery track:

Role Definition
Responsible Does the work for the phase / decision
Accountable Owns the outcome; signs off on completion
Consulted Provides input before decisions are made
Informed Notified after the decision lands

A given person can hold more than one role, but each phase has exactly one Accountable.

Decision-makers

These roles can authorise spend, scope changes, go/no-go decisions, and contractual amendments. Sign-off from the Accountable role is required for every phase gate.

Role Customer-side ebit-side Phase gates owned
Executive sponsor {{TBD: customer-team CEO / VP / Head of Product}} {{TBD: ebit-team founder / CEO}} Discovery sign-off; GA go/no-go
Delivery lead {{TBD: customer-team PM / project manager}} {{TBD: Evospin handover engineer or PM}} Every phase transition
Engineering lead {{TBD: customer-team CTO / VP Eng}} {{TBD: Evospin Tier 3 lead}} Local-stack acceptance; Stage acceptance; Performance acceptance
Security / compliance lead {{TBD: customer-team CISO / DPO}} {{TBD: Evospin security review}} Integration acceptance; UAT (security findings); GA (compliance)
Operations / SRE lead {{TBD: customer-team SRE lead / Head of Ops}} {{TBD: Evospin Tier 3 ops}} Pilot launch acceptance; on-call go/no-go
Customer-comms / brand owner {{TBD: customer-team marketing / brand}} n/a Pilot launch (status-page wording); GA (announcement)

Approvers (per phase gate)

Each phase in ./phased-rollout.md has explicit Accountable + Consulted approvers. The matrix below mirrors the phase structure for fast lookup.

Phase R (does work) A (signs off) C (consulted) I (informed)
1. Discovery Delivery leads (both sides) Customer exec sponsor Eng + sec leads All
2. Local stack Customer engineering Customer eng lead Evospin handover engineer Delivery leads
3. Stage env Customer SRE + customer eng Customer eng lead Evospin Tier 3 Sec lead
4. Integration Customer eng + Evospin handover engineer Customer eng + Evospin Tier 3 (joint) Sec lead Delivery leads
5. Performance validation Customer SRE Customer eng lead Evospin Tier 3 Delivery leads
6. UAT Customer QA + customer eng Customer delivery lead Sec lead, customer-comms Exec sponsor
7. Pilot launch Customer SRE + customer eng Customer eng + customer ops (joint) Evospin Tier 3 Exec sponsor, customer-comms
8. GA Customer SRE + customer-comms Customer exec sponsor + Evospin exec sponsor (joint) All All

Sign-off is recorded in the ./launch-checklist.md per-phase block; on-call gates are recorded in ../handover/oncall-readiness.md §6.

Informed-only roles

These roles don't approve, but receive updates at material milestones (start of phase, end of phase, any go/no-go decision).

Role Customer-side When notified
Legal {{TBD: customer-team general counsel}} Phase 1 (contracting); phase 6 (compliance review); phase 8 (GA)
Finance / Procurement {{TBD: customer-team CFO / FinOps}} Phase 1; phase 5 (cloud spend forecast); phase 8 (run-rate)
Customer-team support / first-line {{TBD: support lead}} Phase 6 (training); phase 7 (pilot start); phase 8 (GA)
Marketing {{TBD: marketing lead}} Phase 7 (pilot — quiet launch); phase 8 (GA — public)
ebit-team customer-success owner {{TBD: ebit-side relationship lead}} Phase 1; phase 8; quarterly thereafter

Contact info template

The customer team fills these in during phase 1. Until filled, the matrix is non-operational.

Role Name Slack / email Phone (P0 only) Time zone Backup
Customer exec sponsor {{TBD}} {{TBD}} {{TBD}} {{TBD}} {{TBD}}
Customer delivery lead {{TBD}} {{TBD}} {{TBD}} {{TBD}} {{TBD}}
Customer engineering lead {{TBD}} {{TBD}} {{TBD}} {{TBD}} {{TBD}}
Customer security lead {{TBD}} {{TBD}} {{TBD}} {{TBD}} {{TBD}}
Customer SRE lead {{TBD}} {{TBD}} {{TBD}} {{TBD}} {{TBD}}
Customer-comms / brand owner {{TBD}} {{TBD}} {{TBD}} {{TBD}} {{TBD}}
Evospin exec sponsor {{TBD}} {{TBD}} {{TBD}} {{TBD}} {{TBD}}
Evospin handover engineer {{TBD}} {{TBD}} {{TBD}} {{TBD}} {{TBD}}
Evospin Tier 3 escalation {{TBD}} {{TBD}} {{TBD}} {{TBD}} {{TBD}}

The on-call escalation contact info lives separately in ../handover/escalation-matrix.md — that table is for incident response and is operationally distinct from this delivery-side stakeholder map (incident response is shorter-lived and pages people; delivery sign-off is slower-cadence and emails / Slacks them).

Cross-references