source: .forge/client/weekly-updates/2026-10-06.md · generated — edit the markdown, not this file

Empire Teas CRM - Progress Update, 6 October 2026

As sent by email to Kavindu on 6 October 2026, with the title above as its subject.

Hi Kavindu,

Please find below our progress update on the Empire Teas CRM.

Summary: The foundations of the system have been completed. Sign-in, user and role administration, and the first lead and email screens have also been built. The team is now focused on setting up the cloud environment in Empire Teas’ AWS account.

Progress to date:

  1. Foundations: completed in mid-September. Every screen is built on these foundations and is checked at tablet and desktop sizes before it is accepted.
  2. Sign-in: staff sign in with their Microsoft 365 work accounts. This has been tested against Empire Teas’ Microsoft setup using the CRM01–05 test accounts.
  3. Users and roles: an administrator can add users, assign roles, set each user’s manager, and deactivate users who leave the company. Roles are set up from a list of permissions, so access can be arranged to suit Empire Teas rather than being fixed in advance.
  4. Record access: each lead and account has a single owner. Managers can see their team’s records, and a record can be shared with a colleague when needed. Every change is recorded with who made it and when, as is every sign-in.
  5. Leads, email, and pricing: the lead inbox is complete, where users can view, filter, add, and edit leads. Salespeople can connect their own mailbox and see their email in the CRM. Each account shows the buying standards it buys, and the weekly price for each standard is held in the CRM.
  6. Pipedrive migration: the first step is complete. The system reads a Pipedrive export and reports what would be brought across, without moving any data yet.
  7. AWS and Azure setup: the AWS account has been opened in the US East region, and the crm.empire.lk addresses now point to it. The Microsoft approvals and sign-in certificates are also in place. Thank you, Kavindu, for your prompt support.

All of this currently runs in the development team’s own environment. You will be able to review it yourself once the cloud environment is live.

Next steps:

  1. Set up the cloud environment and automatic deployment in the AWS account.
  2. Build the account list, with account creation and editing, and the lead detail page, which includes archiving a lead or setting it to nurture.
  3. Then build the rest of Phase 1: the remaining account screens, AI research and ranking of leads, sending email from a record, uploading and publishing weekly prices, and migrating the Pipedrive data.

Please let me know if you have any questions. Thank you.

Best regards, Tharinda

Generated from .forge/client/weekly-updates/2026-10-06.md by .claude/lib/render-docs-html.js. Markdown is canonical.