Empire Teas CRM β Project Timeline
Prepared by Altrium for Empire Teas (Pvt) Ltd Revised 18 November 2026: three features planned for Phase 2 are built and move into the Phase 1 lists of Sections 1 and 2: tracking opens and clicks, and sending an email later; sending the weekβs prices to every customer at once; and list views with saved filters on accounts, contacts and leads. The rest of bulk email, and list views on deals, quotes, samples and buying standards, stay in Phase 2. Also, one test environment now serves both acceptance rounds: it is kept, with its data, from Phase 1βs round until Phase 2βs round ends (Section 2). No date changes. Revised 16 November 2026: rewritten in simpler English, with the earlier change notes moved to Change history at the end. No date or scope changes. Revised again 12 November 2026: the paragraph under The capture app adds the review of each captured lead and planning a show before it starts, both in Phase 1. It also says the review stays if capture-and-send is released first. No date changes.
How to read this schedule
- The dates assume two things:
- the project started on Tuesday 1 September 2026; and
- the AWS environment Empire Teas provides was ready, with the access the team needs, by Friday 2 October 2026.
- If the AWS environment, or another input from Empire Teas, arrives late, the milestone that needs it moves later by the same number of days. So does every milestone after it. Altrium will say so at the time.
- Week numbers start the week after the AWS environment is ready. Week 1 is Mon 5 β Fri 9 October 2026.
- Each phase is built, then accepted in an acceptance (UAT) round. Empire Teas has five business days to review Phase 1 and any delivery in between, and ten business days for Phase 2 and the final acceptance (Statement of Work Β§8.2).
- Some stages overlap on purpose: Empire Teas tests Phase 1 while Phase 2 is being built.
- These dates already allow for Sri Lankan public holidays and the Christmas and New Year break.
1. The schedule
| Stage | Weeks | Dates | Target |
|---|---|---|---|
| Foundation (see below) | 1β2 | 5 Oct β 16 Oct | Fri 16 Oct 2026 |
| Phase 1 (see below) | 2β8 | 12 Oct β 27 Nov | Fri 27 Nov 2026 |
| Phase 1 acceptance round | 9β10 | 30 Nov β 10 Dec | Thu 10 Dec 2026. Empire Teas tests Phase 1 while Phase 2 is built. Fixes are made in the Phase 2 window. |
| Phase 2 (see below) | 11β14 | 14 Dec β 8 Jan | Fri 8 Jan 2027 |
| Phase 2 acceptance and settling in (see below) | 15β17 | 11 Jan β 29 Jan | Fri 29 Jan 2027 |
| Signed-off V1: formal final acceptance | β | β | Fri 29 Jan 2027 |
What each stage contains:
- Foundation: the code repositories, the build and deployment pipeline, sign-in and the permission system, the core data layer, and the cloud environments.
- Phase 1:
- users and roles;
- accounts and leads, moved from Pipedrive, with AI research, ranking, summaries and drafted follow-ups;
- email and templates, with reminders for customer emails that have no reply;
- tracking of opens and clicks, and sending an email later;
- weekly prices, including sending them to every customer at once;
- custom fields, file attachments, and list views with saved filters, on accounts, contacts and leads;
- the trade-show capture app.
- Phase 2:
- deals and pipelines;
- the tea-export workflow;
- dashboards;
- the rest of the AI features, and outreach sequences;
- calendar and contact sync, and list views on deals, quotes, samples and buying standards;
- attachments on deals, quotes, samples and product briefs;
- custom fields on deals, quotes, buying standards and samples;
- import and export, and bulk email to a saved list of contacts;
- the ERP handoff document.
- Phase 2 acceptance and settling in: testing that nothing has broken, training, the final acceptance round and its fixes, the security review, a rehearsal of restoring from backup, the data freeze, the final data move, and its report.
The application foundation (repositories, sign-in, the permission system and the data layer) was finished on 16 September 2026. The cloud side (the environments and the automated deployment) started once the AWS environment was ready. The weekly updates report its progress.
2. Phases at a glance
| Phase | What is built | Ends with |
|---|---|---|
| Foundation | The development environment in Empire Teasβ AWS account, the automated deployment, monitoring and email sending. Everything built so far is tested again there, from start to finish. | A working system in the cloud that can be deployed β Fri 16 Oct |
| Phase 1 | See the list below. | Users, accounts, leads, email, weekly prices and the capture app, working from start to finish β Fri 27 Nov. Then handed to Empire Teas for the Phase 1 acceptance round. |
| Phase 1 acceptance round | Empire Teas tests Phase 1 in a temporary test environment, created for the round and kept until Phase 2βs round ends. The development environment is kept for building. | Findings sorted; fixes are made in the Phase 2 window β Thu 10 Dec |
| Phase 2 | See the list below. | All features built β Fri 8 Jan 2027 |
| Phase 2 acceptance and settling in | Testing that nothing has broken (this already runs during Phase 2); training for administrators and for each role; the final acceptance rounds and their fixes, in the same test environment as Phase 1, removed after sign-off; the security review; a rehearsal of restoring from backup; the data freeze; the final data move and its report. | Sign-off β Fri 29 Jan 2027 |
Phase 1 builds:
- signing in with Microsoft;
- users, roles and the reporting line;
- accounts and contacts, and leads, moved from Pipedrive, with AI research, ranking, summaries and drafted follow-ups;
- follow-up tasks on leads and accounts;
- email and templates inside the CRM, with a reminder for a customer email nobody has answered (added 12 November 2026);
- sharing records between colleagues;
- tracking of opens and clicks, and sending an email later (added 18 November 2026);
- buying standards, publishing the weekly prices, and sending prices to one customer at a time;
- sending the weekβs prices to every customer at once (added 18 November 2026);
- custom fields on accounts, contacts and leads (added 11 November 2026);
- file attachments on accounts, contacts and leads (added 12 November 2026);
- list views with saved filters on accounts, contacts and leads (added 18 November 2026);
- the trade-show capture app (moved from Phase 2, as agreed on 10 November 2026).
Running the CRM side by side with Pipedrive starts during Phase 1, on a date agreed once the data move is proved.
Phase 2 builds:
- both pipelines, with boards and deal details, and activities on deals;
- the dashboard;
- the tea-export workflow: sample tracking, quotes with the readiness checklist and approval step, product briefs, the certification check, export-document checklists, pipeline settings, and alerts for stalled deals, ageing quotes and quiet accounts;
- the rest of the AI: quote help, the daily briefing and βwhatβs stuckβ;
- outreach sequences, and the AI quality comparison;
- calendar and contact sync, and list and table views on deals, quotes, samples and buying standards;
- attachments on deals, quotes, samples and product briefs;
- custom fields on deals, quotes, buying standards and samples;
- import and export, and bulk email to a saved list of contacts;
- the ERP handoff document.
The ERP handoff document comes late in Phase 2. So any deal won before then is handed to the ERP by hand. This is expected and manageable, but worth planning for.
The capture app
The capture app is built in Phase 1, so that it can be used at the January 2027 trade fairs. It was moved from Phase 2, as agreed at the progress meeting of 10 November 2026. It has its own code repository and its own web address.
It covers:
- capturing business cards and badges, and reading the cards;
- reviewing each captured lead, and sending it to the CRM;
- research and ranking;
- notifications inside the app;
- planning a show before it starts (added 12 November 2026).
Captured leads notify the sales team inside the app. The app sends no email (updated 12 November 2026).
Both parties review its progress on Fri 20 November 2026. This date is proposed and still to be confirmed. The Statement of Work placed this review in Phase 2, when the app was planned there. Holding it now means its decisions are in place before the Phase 1 acceptance round starts on 30 November.
If finishing research and ranking would delay the release:
- V1 can be released with capture-and-send first. Captured leads are still reviewed in the app before they reach the CRM.
- Research and ranking are then finished during the settling-in period.
- If they are still not finished by the end of Phase 2 acceptance and settling in, the completion date is agreed through change control (Statement of Work Β§14.1).
3. Moving off Pipedrive and going live
| Stage | When | What happens |
|---|---|---|
| Running side by side begins | During Phase 1, on a date to be agreed | The new CRM runs alongside Pipedrive. Pipedrive stays live and remains the main record. |
| Running side by side continues | Until sign-off | The team uses the CRM for real before anything is switched off. |
| Data freeze | A short agreed period before go-live, during Phase 2 acceptance and settling in | Nobody creates records in Pipedrive while the final copy runs. |
| Final data move | Straight after the freeze | Everything created while both systems ran is brought across. |
| Going back is possible | Until sign-off | Empire Teas can go back to Pipedrive at any time. |
| Sign-off | Fri 29 Jan 2027 | Formal acceptance of V1 |
| Stable period, then Pipedrive switched off | After sign-off, for an agreed time | Pipedrive is switched off when Empire Teas decides, based on the data-move report. |
4. What is most likely to move these dates
- The AWS environment. It is the first item on What the Project Needs from Empire Teas, and the Foundation date depends on it directly. The cloud environments and pipelines take about two weeks once the team has access. Every day it is late moves every later date by one day.
- Pipedrive access and the other inputs from Empire Teas on the same list, for the same reason.
- Testing that nothing has broken starts before each phase is finished. So each acceptance round is spent on acceptance, not on the teamβs first look at the system.
- Acceptance criteria are issued at the start of each phase. So each phase closes against a known list.
- The Christmas and New Year break falls in Phase 2. Both organisations will have fewer people working from about 21 December to 4 January, so the Phase 2 build is planned around it. Any change to scope goes through change control, not into these dates.
Change history
Older changes to this document, newest first. The body above already includes each of them.
- 12 November 2026 (second): two additions to the Phase 1 rows of Sections 1 and 2, after the progress meeting of 10 November: reminders for unanswered customer email, and file attachments on accounts, contacts and leads (built, and shown in the meeting). Attachments on deals, quotes, samples and product briefs stay in Phase 2. No date changes.
- 12 November 2026 (first): the trade-show capture app moves from the Phase 2 rows of Sections 1 and 2 to the Phase 1 rows, as agreed at the progress meeting of 10 November, so that it can be used at the January 2027 trade fairs. The review of its progress, which the Statement of Work holds during Phase 2, is proposed for Fri 20 November 2026 (The capture app). No other date changes.
- 11 November 2026: custom fields on accounts, contacts and leads are built and move into the Phase 1 rows of Sections 1 and 2. Custom fields on deals, quotes, buying standards and samples stay in Phase 2. No date changes.
- 11 October 2026: the Phase 2 rows in Sections 1 and 2 now list bulk email (added to Phase 2 on 9 October) and no longer list global search (left out on 11 October; each list has its own search β Product Requirements, Section 4). No date changes.
- 29 September 2026: new dates, from the revised Statement of Work (SOW-ET-001 v1.1). Sign-off moves from Tue 15 December 2026 to Fri 29 January 2027. Empire Teas now provides the AWS environment, which must be ready by Fri 2 October 2026. The delivery team is now four developers. The schedule this replaces is kept, unchanged, in the appendix below.
- 27 September 2026: the summary rows in Section 1 were changed to show the phases as regrouped on 17 September. No date changes.
Appendix β the schedule as it stood on 27 September 2026 (replaced 29 September 2026)
Kept unchanged as the record of the earlier plan. It assumed an Altrium-provided AWS environment and a three-developer team.
| Stage | Weeks | Calendar window | Target milestone | Latest (range edge) |
|---|---|---|---|---|
| Foundation | 1β3 | 31 Aug β 18 Sep | Foundation complete Fri 18 Sep | 25 Sep |
| Phase 1 β users and roles, accounts and leads (migrated, with AI research, ranking, summaries and drafted follow-ups), email and templates, weekly prices | 3β9 | 14 Sep β 30 Oct | Core CRM usable Fri 9 Oct (parallel run begins) Β· Phase 1 complete Fri 30 Oct | 6 Nov |
| Phase 1 UAT (client round) | 10β11 | 2 Nov β 13 Nov | Client tests Phase 1 scope while Phase 2 builds on; fixes fold into the Phase 2 window | β |
| Phase 2 β deals and pipelines, the tea-export workflow, dashboards and search, the remaining AI, outreach sequences, sync, views, attachments, custom fields, import/export, ERP handoff Β· capture app lands | 7β13 | 26 Oct β 27 Nov | Feature-complete Fri 27 Nov | 11 Dec |
| Phase 2 UAT and stabilisation | 14β17 | 30 Nov β 15 Dec | Final client acceptance rounds | Christmas week (w/c 21 Dec) β only by the Section 4 decision, never silently |
| Signed-off V1 | 14β17 | β | Target Tuesday 15 December 2026 | Realistic edge Tue 22 Dec; buffered outer bound mid-January 2027 |
In that version the weeks counted from kickoff (Week 1 = Mon 31 Aug β Fri 4 Sep), phase acceptance used a five-business-day window throughout, and the capture-app checkpoint was Fri 13 Nov.
Revision, 17 September 2026 (Gate 3) β kept as written. The two phases above were re-grouped when the build was decomposed. The proposalβs Β§6/Β§7 and the earlier version of this table put pipelines, Kanban boards, activities, the dashboard and global search in Phase 1; they now sit in Phase 2, and the AI work on leads and accounts (research, ranking, summaries, drafted follow-ups, account briefings) moves up into Phase 1 alongside email, templates, follow-up tasks, record sharing and the weekly price publishing. The same scope in a different order β nothing is added or removed, the dates are unchanged, and the Phase 1 acceptance round therefore covers users, accounts, leads, email and weekly prices while Pipedrive remains the record for deals until Phase 2. The Pipedrive migration brings accounts, contacts, leads and their notes (deals are a fresh start, per the 13 September decision). Recorded as a post-issue note on the proposal header and as Gate 3 Run 1 in the delivery records.