Brainforge Knowledge

implementation-plan-template

4 min read

Implementation Plan: [Service Name]

Purpose: Week-by-week phases, milestones, and dependencies for this offering. Used in SOW scope sections, kickoff decks, and to populate Linear milestones. Service line: [AI | Data | Strategy & Analytics] Subservice: [e.g. Data Platform] Delivery model: [fixed-scope | T&M | retainer | hybrid] Last updated: [Date]

At a Glance

PhaseNameDurationKey outputGate
Phase 0[e.g. Audit / Discovery][e.g. 1–2 weeks][e.g. Gap report, scope agreed]Client sign-off
Phase 1[e.g. Pilot / Build][e.g. 3–4 weeks][e.g. Working pilot, validation]Stakeholder demo
Phase 2[e.g. Scale / Handoff][e.g. 4–8 weeks][e.g. Rollout, runbooks, training]Acceptance sign-off

Total duration: [e.g. 8–14 weeks]
Effort (rough): [e.g. Managing Lead 20h · Senior Engineer 80h · PM 16h]

Prereqs Before Kickoff

  • [Prereq 1 — e.g. Client provides data warehouse access]
  • [Prereq 2 — e.g. SOW signed, kickoff scheduled]
  • [Prereq 3 — e.g. Stakeholder contacts confirmed (technical + business)]

Phase 0 — [Name]

[One line: what this phase proves or produces.]

Duration: [e.g. 1–2 weeks]
DRI: [e.g. Delivery Lead]

Week-by-week

WeekActivitiesDeliverable
Week 1[e.g. Kickoff, access setup, data audit][e.g. Access confirmed, audit begun]
Week 2[e.g. Gap analysis, scope validation][e.g. Gap report, updated SOW if needed]

Milestone: [Phase 0 milestone name]

  • Output: [e.g. Discrepancy report, data map, gap analysis]
  • Gate: [What must be true before Phase 1 begins — e.g. “Client reviews and approves scope; Brainforge confirms feasibility”]
  • Dependencies: [e.g. “Client warehouse credentials”, “Access to ad platform accounts”]

Phase 1 — [Name]

[One line: what this phase builds or demonstrates.]

Duration: [e.g. 3–4 weeks]
DRI: [e.g. Senior Engineer + Delivery Lead]

Week-by-week

WeekActivitiesDeliverable
Week 3[e.g. Core build, pipeline setup][e.g. Initial pipeline running]
Week 4[e.g. Integration, first validation run][e.g. Validation report v1]
Week 5–6[e.g. Iteration, edge cases, demo prep][e.g. Pilot complete, demo ready]

Milestone: [Phase 1 milestone name]

  • Output: [e.g. Working pilot, validated against client data]
  • Gate: [e.g. “Stakeholder demo completed; client approves moving to Phase 2”]
  • Dependencies: [e.g. “Phase 0 sign-off”, “Client team available for weekly check-ins”]

Phase 2 — [Name]

[One line: what this phase finalises, scales, or hands off.]

Duration: [e.g. 4–8 weeks]
DRI: [e.g. Senior Engineer + PM]

Week-by-week

WeekActivitiesDeliverable
Week 7–8[e.g. Rollout, additional channels/use cases][e.g. Expanded coverage]
Week 9–10[e.g. Documentation, runbooks][e.g. Runbook v1, training materials]
Week 11–14[e.g. Training, support window, close-out][e.g. Trained client team, sign-off]

Milestone: [Phase 2 milestone name]

  • Output: [e.g. Full rollout, runbooks, trained client team]
  • Gate: [e.g. “Client acceptance sign-off; support window complete”]
  • Dependencies: [e.g. “Phase 1 sign-off”, “Client stakeholders available for training sessions”]

SOW Copy Block (Pasteable)

Paste into the SOW to keep timeline and scope language consistent.

Timeline: [X–Y weeks total across [N] phases.]

Phase 0 — [Name] ([duration]): [One-sentence scope.]

Phase 1 — [Name] ([duration]): [One-sentence scope.]

Phase 2 — [Name] ([duration]): [One-sentence scope.]

Client responsibilities: [e.g. Provide access within 3 business days of kickoff; designated point of contact for weekly check-ins; timely review of deliverables (SLA: 5 business days).]

SOW ↔ project plan (per client)

When to use: After the SOW is signed and before Linear tickets are cut. This is not the offering-level phase plan above — it is the client-specific bridge: initiatives, projects, client-visible milestones, technical approach, and sign-offs.

Canonical template: Copy sow-project-plan-template.md into Notion or knowledge/clients/{client}/resources/sow-project-plan.md per engagement. Keep this implementation-plan file focused on offering phases and week-by-week delivery; avoid duplicating the SOW ↔ plan sections here so one source stays current.

Atomic chain (offering → execution): Playbook §8.2 — Full Atomic Chain in standards/PLAYBOOK_DEVELOPMENT_PLAN.md — Service Line → Subservice → Offering → Phase → Deliverable → Ticket.

Retro / Update Log

After each engagement using this plan, record what changed so the canonical stays current.

DateEngagementWhat changed
[YYYY-MM-DD][Client name][e.g. Phase 1 extended to 6 weeks due to access delays; added access prereq checklist]

Graph View