source: .forge/discovery/meeting-notes/2026-11-10-kavindu-crm-progress-update-demo.md · generated — edit the markdown, not this file

Empire Teas CRM — progress update and demo with Empire Teas leadership

Date: 10 November 2026 Meeting: online call, about fifty-seven minutes, titled “CRM Progress Update”. Kavindu Anthony brought in Empire’s marketing director and the managing director of Empire Brands so they could see what has been built. Participants: Empire Teas — Kavindu Anthony; Sahampathy Dissanayake (Director of Marketing); Roshan (managing director of Empire Brands; spelled as the transcript has it); Sajeev De Silva; Praveen M. Altrium — Tharinda Rajapaksha, Dinil Gamage, Biseni Perera. The transcript shows Kavindu also calling on Malinda, who did not speak. Source: the meeting tool’s transcript, read on 10 November 2026. The speech-to-text is rough in places (for example “be” for “view”, “Pipe Drive” for Pipedrive), so this note records only what is clear from context. The transcript ends mid-discussion at 56:53, so the end of the Sajeev De Silva exchange (§5) is missing.

Why this file exists: it is the dated record of Empire leadership’s first look at the CRM, of the three requests they made that go beyond what Phase 1 holds (§3, §5), and of their ask to show the CRM to the wider brand and marketing team before implementation. Where a statement made in the meeting differs from the design or the issued proposal, §6 says so.


1. Overview given by Tharinda

  • The CRM replaces Pipedrive: the basic CRM features, plus functions aimed at Empire’s pain points.
  • Phase 1 includes moving the existing leads and customer accounts out of Pipedrive, and the email integration.
  • Pain points the design addresses: the backlog of leads (AI ranks them and drafts follow-ups for cold ones), and a mobile app for trade fairs where a rep scans a business card, the system searches the web, and a lead is created on the spot.

2. Demonstration (Biseni, on dev)

Shown, in this order:

  • Sign-in: a Microsoft sign-in button only. There is no sign-up; an administrator creates every user, who then signs in with their Microsoft account.
  • Settings: users (list, detail, the reporting line, deactivation instead of deletion, with the refusals — no self-deactivation, no removal of the last administrator, no deactivation of someone with direct reports), roles (permissions, the three access levels, the all records option, a role cannot be deleted while users hold it), tags, and email templates.
  • Leads: create by hand; create from a pasted inquiry (AI fills the form and marks it as AI-drafted, with a confidence figure; editing it marks the edit); the list and its filters; the AI web research with a link to every source; the AI priority (P1, P3) with a reason and a recommended next action; the approve-and-send email with a template or an AI draft; follow-ups; sharing; attachments; notes; duplicate and spam flags with the reason.
  • Accounts and contacts: the same list, filter and archive behaviour; Prepare briefing (an AI account summary); contacts and the primary contact; manage access, where a manager sees the accounts of their direct reports; the dormant status after 90 days without contact; buying standards, notes and the timeline.
  • Activities: every follow-up, grouped as upcoming, overdue and completed.
  • Pricing: buying standards, weekly prices (draft, published, cannot-publish), auction sales, and import of weekly prices from a document.
  • Emails: the connected mailbox, an Outlook-like inbox, sent and archived views, and composing.

Tharinda then showed the capture app as a prototype, not built yet (§4).

3. Questions from Roshan

Question Answer given Note
Can Empire manage its customers fully in the CRM, without Outlook, across about twenty-five customers in different countries and brands? Dinil: yes. Tharinda: not yet — emails will be linked to the customer account later, in the communication timeline. The mail-to-record link is F20-f (.forge/features.md).
Can the CRM identify emails that have not been replied to? Tharinda: should be possible, perhaps by flagging conversations not attended to; “we will see whether we can accommodate it in phase one coming”. Kavindu said this was one of the main reasons Empire wanted the CRM and that he thought it was already done. Not in the design as far as checked — see §6 and .forge/owed.md.
Can marketing material (presentations, links, videos) be attached to new inquiries and kept? Yes, as attachments; each is stored under the customer account. Roshan then asked whether the CRM replaces the archiving mailbox. Tharinda: mail syncs to the CRM in real time and is stored in the database for records it is linked to. Kavindu: the emails also stay in Empire’s Microsoft account, and the CRM retrieves them.
Can the CRM link to the ERP, for the customer’s sales? Kavindu: yes, once Empire has chosen its ERP; it was raised in the initial proposal. F19 is a manual hand-off document until the ERP is known (AD #10).
Can the AI show a company profile for a new lead? Dinil and Tharinda: yes, already built — the lead research, from public sources, with the links shown. Biseni showed it on test data. F11-c.

Roshan said it was looking good and that Empire’s brand teams should now see it, since the aim is for them to stop using Outlook for customers and manage them in the CRM. He and Sahampathy want to see any account and its status. Kavindu has not shown the CRM to the brand team yet.

4. Trade-fair capture app

  • Sahampathy asked whether business cards can be scanned and uploaded, and whether a brief profile of the person can come from AI or the web. Tharinda showed the prototype: create a campaign (for example Gulf Food 2027); add exhibitors by CSV or by hand; AI ranks them and summarises public information; scan a card or QR code, search the web, and create a lead with an AI summary and recommendations. This is not built yet.
  • Empire’s priority: Sahampathy said trade fairs are the primary source of Empire’s customer contact and that few leads arrive by email, so “this needs to be fast-tracked” to be useful from January 2027. Kavindu asked for it in Phase 1: “this is one of the main attractions which we saw in your initial demonstration.”
  • Tharinda’s answer: Phase 1 is likely done by the end of November and the capture app (Phase 2) is planned for January 2027. The Phase 1 priority was the Pipedrive lead backlog (bulk upload, ranking, follow-ups). He would not promise it within November but said the team will try to bring it forward and finish it as soon as possible rather than wait for January.
  • Sahampathy noted that the backlog database exists, but without the capture app it will only keep growing.
  • Praveen: “I think initially we discussed to have all that information as well.”
  • Outcome: the capture app is delivered in Phase 1 (§8).

5. Follow-ups and what sets the CRM apart

  • Sahampathy asked how the CRM differs from Pipedrive. Dinil: it is custom-built for Empire’s operations, while Pipedrive is general purpose; the AI lead ranking and research are not in a general CRM.
  • Sajeev De Silva asked about automatic replies and follow-ups. His points: automatic reminders, follow-ups and replies to stagnant leads have to be there; the team should not have to check and resend; many follow-ups after a fair only remind the person that Empire can supply them, with no sensitive content. He would start with drafts saved for a person (first phase), and move toward automatic sending later.
    • Tharinda: the team’s approach so far is that AI drafts are reviewed and sent by a person, not sent automatically. A strict template with no per-customer content could be automated, with name-level personalisation. Bulk email is planned for Phase 2.
    • The transcript ends here, so no conclusion was reached in the recording.

6. Statements to check against the design and the proposal

The proposal outranks in-meeting answers (.claude/rules/source-trust.md). .forge/owed.md carries a row for each item below.

What was said What the design says
The CRM can flag emails that have not been replied to (“maybe we can accommodate that in phase one”) No feature in .forge/features.md was found for this, and Kavindu believes it is already done. The team has to decide the scope, and tell Empire whether it is in Phase 1. Not checked against the PRD beyond a search of features.md.
Automatic AI-drafted follow-ups and replies (Sajeev) The PRD keeps a person approving every AI action; a strict-template, no-personal-content automatic send is a change to that, so it needs a decision before anyone promises it.
The capture app “will try to be brought forward” from Phase 2 Gate 3 placed it in Phase 2 with its scope unchanged (AD #20). Bringing it forward is a schedule decision against R-ARCH-001, so it needs the lead’s decision, not a promise made in a meeting. Decided: it is delivered in Phase 1 (§8; PRD Rev 91).
The CRM is already linked to the mail, as seen in the communication timeline The timeline shows notes; linking synced mail to a contact, account or lead is F20-f. Tharinda said this correctly (§3).

7. Agreed next steps

Roshan asked that, before implementation starts, the CRM be shown to a wider group (the brand and marketing team who manage customers), that their feedback be taken, and that a date for implementation be set, so Empire can start using it and learn it. Sahampathy agreed, suggesting the presentation come once a few areas are settled so more ideas can be gathered. Kavindu agreed to arrange a demonstration; he had invited some colleagues to this meeting, but a shipping meeting kept them away.

8. Agreed with Kavindu, not in the transcript

Recorded on 11 November 2026 from Dinil Gamage’s account of the meeting; the transcript does not hold these exchanges.

  • Exa is the lead-research search provider. Kavindu Anthony confirmed Exa. This is Empire’s answer on Exa that the provisional choice of 20 October waited for, and it closes SP-ARCH-004 (.forge/design/ai/lead-research-source-options.md Rev 11).
  • The person search: a switch on the CRM’s Settings page, on by default. The team proposed that an administrator chooses on a Settings page whether lead research also searches for the person named on the lead, which sends that person’s name to Exa, and that the switch starts turned on. Kavindu accepted this. It answers the F11-c question put to Empire (spec decision 5, FR-H2 (b)): a person search may go to Exa, and Empire controls it. Today the person search is a server setting, et.research.person-search.enabled, off in every environment (F11-c FR-P2), so the switch is new work and an F11-c spec revision. F11-c FR-P2 also asks for Empire’s agreement in writing and Exa’s data processing agreement for each environment’s account before the person search is on there; Kavindu’s agreement was spoken in the meeting.
  • The capture app is delivered in Phase 1. The delivery team and Empire agreed that the capture app, F36-a to F36-d, is delivered in Phase 1, to Phase 1’s dates, with its scope unchanged, so that it can be used at Empire’s January 2027 trade fairs. Rukshan Salgado, Thilina Abeyrathna and Malinda Wellalage (Altrium) also asked for it to be done in Phase 1. The lead recorded it in the tracker on 11 November (features.md § Delivery Plan; PRD Rev 91; AD #20). Recorded here on 12 November 2026 from Tharinda Rajapaksha’s account.
  • Phase 1’s UAT needs its own environment. Kavindu said UAT is needed, meaning the temporary uat environment for Phase 1’s round. This is Empire’s yes to the question asked on 25 October (answer wanted by 20 November), which F38-h’s waves 5 and 6 wait for.

Actions

Action Owner Recorded in
Arrange a demonstration of the CRM for the wider brand and marketing team, and agree a date for implementation Kavindu Anthony, with Tharinda .forge/owed.md
Decide whether the capture app can be brought forward from Phase 2, and answer Empire Tharinda (the lead) .forge/owed.md
Decide the scope and the phase of flagging emails that have not been replied to Tharinda (the lead) .forge/owed.md
Decide the position on automatic follow-up emails (template-only sending) against human approval of every AI action, and answer Sajeev De Silva Tharinda (the lead) .forge/owed.md
Review the CRM from the brand side and say what the brand teams need added Roshan, with Kavindu this note
Build the person-search switch on the Settings page, on by default (an F11-c spec revision) Dinil (F11-c’s owner) .forge/owed.md
Get Kavindu’s agreement to the person search in writing, and Exa’s data processing agreement for each account, before the switch is on in that environment Tharinda (the lead) .forge/owed.md
Record Empire’s yes to Phase 1’s UAT environment as an F38-h spec revision, and start F38-h wave 5 Tharinda (the lead) .forge/owed.md

Generated from .forge/discovery/meeting-notes/2026-11-10-kavindu-crm-progress-update-demo.md by .claude/lib/render-docs-html.js. Markdown is canonical.