Delivery Methodology & SOPs¶
🎯 This is the operational version of the Engagement Path defined in Company Strategy → Business Model — the step-by-step "how," not just the "what."
Stage-by-Stage SOP¶
| Stage | Entry criteria | Standard steps | Exit criteria (deliverable) |
|---|---|---|---|
| Discovery | Signed NDA / initial call held | Problem framing call, stakeholder list, current-process notes, feasibility check | Discovery notes doc + go/no-go decision |
| Assessment | Discovery complete | Data readiness check, opportunity list, ROI assumptions, risk flags | Opportunity assessment doc, prioritized |
| Pilot | Assessment accepted by client | Fixed scope doc, success metrics agreed, 2–6 week build, weekly check-in | Working pilot + evaluation against agreed metrics |
| Build & Integrate | Pilot validated | Architecture doc, milestone plan, testing plan, staging environment | Production-ready system, deployed |
| Deploy | Build accepted | Rollout plan, monitoring set up, rollback plan, access handover | Live in production, monitored |
| Support | Deployed | Retainer scope, SLA, monthly report cadence | Ongoing — reviewed quarterly |
Cross-Stage Rules¶
- Every stage ends with a written deliverable, even if short — no verbal-only handoffs.
- Every engagement has a single internal owner accountable for delivery, regardless of team size.
- Scope changes are logged in writing before work starts, not after.
- No stage starts without the previous stage's exit criteria signed off (by client, or internally if no client sign-off applies).
Internal Project Checklist (per engagement)¶
- Kickoff notes documented and shared internally
- Success metrics agreed and written down
- Repo / workspace set up following naming and access conventions
- Status update sent on agreed cadence
- Handover / support doc written at project close