source: .forge/discovery/meeting-notes/2026-07-22-kickoff-deck.md · generated — edit the markdown, not this file

Empire Teas CRM — Kickoff Deck (transcription)

Date: 1 September 2026 (kickoff meeting, Colombo) Source: Altrium-Empire-Teas-CRM-Kickoff.pptx — the client kickoff presentation Purpose: A faithful, slide-by-slide markdown transcription of the kickoff deck so its content is readable, searchable, and diffable inside the harness without opening the .pptx.

How to read this. Every slide’s text is reproduced as shown. The deck is an image-based export (each slide is a rendered image), so this is a transcription, not an extract. Where a reviewer note appears in a > blockquote, that text is not on the slide — it flags a point to check against a more authoritative source. On any disagreement, the issued client pack (.forge/client/) and the PRD/architecture win over this deck.


Slide 1 — Title

  • Eyebrow: ALTRIUM × EMPIRE TEAS
  • Title: CRM project kickoff.
  • Subtitle: Aligning scope, delivery and the decisions that unlock Week 1
  • Footer: 1 September 2026 | Colombo

Slide 2 — Agenda: “Align the team for a fast start”

# Item One-liner
01 Shared outcome What success looks like for Empire Teas
02 Delivery scope (no sub-caption on the slide)
03 Delivery plan How the two phases overlap through December
04 Ways of working UAT, acceptance, decisions and change control
05 Week 1 inputs Access, data and owners required by 4 September
06 Actions Decisions, owners and immediate next steps

Reviewer note: item 02 Delivery scope is the only tile without a one-line sub-caption; the other five have one.


Slide 3 — “A tea industry CRM will replace Pipedrive”

Intro: A single tenant platform for daily selling, tea export workflows and controlled AI assistance owned and operated in Empire Teas’ AWS environment.

# Card Detail
01 Run sales in one place Accounts, contacts, two pipelines, activities, email, search, dashboards and verified Pipedrive migration.
02 Embed tea workflows Samples, quote readiness, product briefs, certification checks, export checklists and weekly bulk pricing.
03 Add AI with human control Reviewable drafts and assistance through Amazon Bedrock. AI never sets prices or sends autonomously.

Slide 4 — “Delivery is organised into two acceptance phases”

Phase 1 — Core CRM + tea workflows

  • Core records, pipelines, tasks, email and dashboards
  • Pipedrive migration and parallel run
  • Samples, quotes, product briefs and certification controls
  • Product catalogue and Tea Room managed weekly pricing

Phase 2 — AI + parity + capture

  • Human reviewed AI triage, drafting and briefings
  • Calendar/contact sync, saved views and bulk actions
  • Structured ERP handoff and admin custom fields
  • Trade show capture app with controlled CRM feed

Slide 5 — “Meet the Altrium delivery team”

As shown on the slide:

# Role Name(s) Owns
01 Project Lead Thilina Abeyrathna Delivery coordination, project cadence, actions and escalation.
02 Solution / Technical Lead Tharinda Rajapaksha Architecture, security, integrations and technical decisions.
03 Delivery Team Dinil Gamage, Biseni Perera Experience design, development, QA, migration and handover.

Slide 6 — Timeline: “Sign-off is targeted for 15 December”

Marker Milestone Sub-note
1 Sep Kickoff Foundation begins
18 Sep Foundation Platform baseline
23 Oct Core CRM usable Parallel run starts
06 Nov Phase 1 UAT Capture checkpoint
08 Dec Phase 2 UAT Final UAT begins
15 Dec Sign-off Target acceptance

Reviewer note — dates to reconcile against the issued .forge/client/project-timeline.md. Kickoff (1 Sep), Foundation (18 Sep) and Sign-off (15 Dec) match the issued schedule. The three middle markers do not:

  • “23 Oct — Core CRM usable / Parallel run starts” — the issued timeline puts Core CRM usable + parallel run start at Fri 9 Oct (Phase 1 complete = Fri 30 Oct); 23 Oct matches neither.
  • “06 Nov — Phase 1 UAT / Capture checkpoint” — Phase 1 UAT runs 2–13 Nov; the capture descope checkpoint is Fri 13 Nov, not 6 Nov.
  • “08 Dec — Phase 2 UAT / Final UAT begins” — feature-complete is Fri 27 Nov (not shown on the slide) and Phase 2 UAT runs 30 Nov–15 Dec; final UAT begins ~30 Nov, not 8 Dec.

The issued timeline is the source the client holds; slide 6 should be reconciled to it.


Slide 7 — “Short feedback loops protect the fixed-price plan”

# Step Detail
1 Demonstrate Supplier shows completed scope against written criteria.
2 Review Empire Teas has five Business Days for consolidated feedback.
3 Correct Valid reproducible defects are fixed and resubmitted.
4 Accept Unaffected items remain accepted; silence or production use may deem acceptance.

Slide 8 — “Week 1 depends on seven Empire Teas inputs”

Banner: Preferred completion date: Friday 4 September 2026

Level Client input Owner Unblocks
Critical AWS management account, admin delivery role IT Cloud environments + AI
Critical Pipedrive export or administrator access Sales / IT Migration design
Critical Tea Room and Executive access decisions Sales leadership Permission model
Critical Microsoft 365 approval, test users and shared inboxes IT Email + calendar sync
High CRM and capture-app domains plus DNS access IT URLs + email delivery
High Product-to-certification mapping sample QC Certification checks
High Weekly buying standard prices and cost samples Tea Room Pricing + margin logic

Reviewer note: this table matches .forge/client/dependencies.md (the seven development-blocking client inputs) — same items, order, owners, unblocks, and the 4 September preferred date. The fuller detail behind each row (for explaining them live) is in dependencies.md.

Reviewer note (added 2026-09-13): the first row — “AWS management account, admin delivery role” — is superseded. Under the Managed Cloud Infrastructure & Hosting SOW (ET-002), Altrium owns and runs AWS and bills Empire monthly, so no AWS account is handed over by Empire (AD-O-10 resolved; see ../../client/aws-sow.md and ../../design/environments-and-identity.md). The slide text is preserved as delivered on 1 September.


Slide 9 — “A simple cadence keeps decisions moving”

Frequency Forum Purpose Core participants
Weekly Project working meeting Progress, upcoming work, actions, decisions and RAID review Project leads + workstream leads
Weekly Written status update Completed work, next week priorities, decisions and key risks Altrium Project Lead
As needed Workstream sessions (no purpose text on the slide) Relevant specialists
By milestone Demo and UAT sessions Demonstrate scope, confirm criteria and consolidate feedback Business testers + project leads
Monthly Steering Committee Milestones, material risks, scope, commercials and escalations Executive sponsors + project leads

Callout: Escalations do not wait for the next scheduled meeting; material issues are raised promptly through the named project leads.

Reviewer note: the Workstream sessions row has an empty Purpose cell on the slide.


Slide 10 — Closing

  • Eyebrow: NEXT
  • Title: Aligned and ready to deliver…
  • Accent line: Questions, Discussion and alignment
  • Body: We are ready to build a CRM designed around how Empire Teas sells, prices and serves its customers
  • Footer: Project kickoff | 1 September 2026

Generated from .forge/discovery/meeting-notes/2026-07-22-kickoff-deck.md by .claude/lib/render-docs-html.js. Markdown is canonical.