Empire Teas CRM - Progress Update, 9 October 2026
As sent by email to Kavindu, Sajeev and Praveen on 9 October 2026, copied to Altrium, with the title above as its subject.
Dear all,
Please find below our progress update on the Empire Teas CRM.
Summary: This week the account list, the lead detail page and the weekly price upload were completed, and the screen for handling staff who leave the company was built. In Empire Teas’ AWS account, the development environment now has its database, its servers and its web address, ready for the first deployment of the CRM.
Progress this week:
- Accounts: The account list is complete. Users can search, sort and filter their accounts, see which ones have gone dormant, and create and edit accounts, adding a main contact when they create one.
- Lead detail: From a lead, users can now archive it, set it to nurture or restore it, add notes, add and remove tags, and link it to the matching account and contact. A lead linked to an account also appears in that account’s history.
- Weekly price upload: The Tea Room can upload the weekly price workbook in its current form. The CRM checks the file first, flags any buying standard that appears on more than one tab, and then creates draft prices for review. For each tab, the Tea Room confirms which column holds which figure, and the CRM remembers the choice for the following week.
- User administration: An administrator can open any user and see exactly what that person can see and do, and why. When someone leaves the company, an administrator can hand all of their leads and accounts to a colleague in one step, move the people who report to them to a new manager, and then deactivate them from the same screen. Final testing of this screen is under way.
- Cloud environment: The development environment in AWS now has its database, the servers that will run the CRM, and its address, api.dev.crm.empire.lk.
- Reliability: Sign-in and mailbox connection were made more robust, and a user who cancels or declines the mailbox connection now sees a clear message.
Next steps:
- Deploy the CRM to the development environment in AWS, so that it can be reviewed there.
- Complete the account page, with the account’s details and its contacts.
- Build the first AI feature: turning a buyer’s inquiry, pasted into the CRM, into a draft lead.
- Continue with the rest of Phase 1: AI research and ranking of leads, sending email from a record, reviewing and publishing the weekly prices, and migrating the Pipedrive data.
Please let me know if you have any questions.
Best regards, Tharinda