Empire Teas CRM — Kavindu’s request for email campaigns
Date: 9 October 2026 Meeting: WhatsApp exchange, 15:51–17:07 Participants: Kavindu Anthony (Empire Teas), Tharinda Rajapaksha (Altrium) Source: the WhatsApp thread, summarised. Kavindu’s list is restated close to his wording; Tharinda’s reply is quoted as sent.
Why this file exists: it is the dated record of the client request and the answer that moved bulk email from a stretch candidate to committed Phase 2 scope (PRD Rev 57, features F37-a and F37-b).
The request
Rukshan told Tharinda that Kavindu had questions about email. Kavindu asked whether the CRM will have an email campaign option, which he remembered raising in the early meetings. Asked what he meant, he listed:
- Corporate newsletters: send monthly newsletters and track how recipients engage with them.
- Product marketing: promote the Hyson, Thurson, Akina and Ceylon Wild Harvest ranges.
- Trade fair communications: send invitations, meeting requests and follow-ups after the event.
- Customer segmentation: organise contacts by market, customer type and business requirements.
- Campaign analytics: see email opens, link clicks and engagement to judge how a campaign performed.
He listed Pipedrive contact synchronisation as well, then withdrew it.
The records show bulk sending was first raised on 9 September and confirmed as important on 16 September (2026-09-09-requirements-followup.md, PRD Rev 28), both after the proposal was accepted. The proposal places “email campaigns” among the later-phase Pipedrive add-ons and excludes “a full marketing suite”.
The answer (sent 17:05–17:07)
Phase 1: sending emails from the CRM, email templates, follow-up reminders, tagging accounts and contacts, and sending each customer their weekly prices
Phase 2: bulk email (the weekly prices to all customers at once, newsletters, product promotions, trade-fair invitations), with opens and clicks tracked for each send; automated follow-ups; and saved lists to group contacts by market, customer type or any other tag or field you need
Tharinda added that Phase 2’s scope would be discussed in detail in a meeting around the Phase 1 hand-over, or earlier, to decide which features to prioritise and which Empire might not need. Kavindu replied “Noted. Thanks”.
What this commits
| Promised | Feature | Phase |
|---|---|---|
| Sending emails from the CRM | F20-c | 1 |
| Email templates | F20-d | 1 |
| Follow-up reminders | F3-a | 1 |
| Tagging accounts and contacts | F1-e | 1 |
| Each customer’s weekly prices | F26-d | 1 |
| Weekly prices to all customers at once | F37-a (new) | 2 |
| Newsletters, product promotions, trade-fair invitations, with opens and clicks per send | F37-b (new) | 2 |
| Opens and clicks on individual emails | F20-g | 2 |
| Automated follow-ups | F25-a, F25-b | 2 |
| Saved lists by market, customer type, tag or field | F32-a, F34-b | 2 |
Not promised: a segmentation builder or campaign reports across sends (F28, still deferred), and contact sync with Pipedrive.
What is still owed
- The OQ-62 questions were not sent. The draft reply asked about consent, unsubscribing and the sending address; the sent reply left them out. F37-b cannot be specified until Empire answers them (
client/open-questions.mdQ10). - The compensating descope. Adding F37 to Phase 2 is added scope against R-ARCH-001; the reply defers which Phase 2 features move to the scope meeting with Empire (
.forge/owed.md).