source: .forge/client/client-facing-prd.md · generated — edit the markdown, not this file

Empire Teas CRM — Product Requirements (Client Edition)

Prepared by Altrium for Empire Teas (Pvt) Ltd Revised 20 November 2026: contact sync now works one way, from each person’s Outlook contacts into the CRM (Section 3.4). New contacts wait on a list for that person to add or dismiss, so personal contacts stay out of the CRM. You can ask for the other direction during acceptance testing. No price or date changes. Revised 19 November 2026: Section 3.4 now says how newsletters work: they come from the sender’s own mailbox, go to everyone on the list who has not unsubscribed, and carry an unsubscribe link. We chose this ourselves so building can start; please confirm it (Q10). No price or date changes. Revised 18 November 2026: three features planned for Phase 2 are built, so they now arrive in Phase 1: tracking opens and clicks, and sending an email later (Section 3.1); sending the week’s prices to every customer at once (Sections 3.2 and 3.4); and list views with saved filters on accounts, contacts and leads (Section 3.4). 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 to the end of Phase 2’s, so your testers keep their test data (Sections 5 and 8). No change to the build price or the dates.

This document describes what the system will do, in plain language. Its purpose is that everyone signing the Statement of Work agrees to the same picture.

  • The proposal remains the commercial contract.
  • Where Empire Teas agreed a decision after the proposal was issued, this document records the later decision.
  • The schedule is in the companion Project Timeline. What the project needs from Empire Teas is in its own companion document.

1. What is being built, and why

Today Empire Teas runs its front-office sales work on Pipedrive, spreadsheets, email and WhatsApp. That work covers buyer inquiries, private-label product development, sample rounds, quoting, follow-up and export coordination.

These tools were not built for the tea export business, and the gaps cost real revenue:

  • more than 200 inbound leads have not been reviewed;
  • follow-ups are missed;
  • nobody can see the full status of a sample or a quote;
  • accounts that are ready to reorder go quiet.

Altrium is building a sales CRM made for Empire Teas’ business. It will:

  1. Replace Pipedrive without losing anything the team relies on today, including sending and receiving email inside the CRM.
  2. Handle the tea export business directly: sample rounds, certification checks, export documents for each destination, weekly bulk prices, and a checklist a quote must pass before it is sent.
  3. Add an AI assistant that people control. It reads, pulls out details, summarises, drafts and checks. A person approves every action, and a person sets every price.

It is one system for all five offices (Sri Lanka, Kenya, Netherlands, Shanghai and Spain). It is built for Empire Teas and owned by Empire Teas, source code included.

What it is not: it is not an ERP. Stock, production, purchasing, finance and confirmed orders stay in the ERP. The CRM covers everything up to the confirmed order, then hands a won deal over to the ERP.

2. The people who will use it

Six roles were confirmed on 3 August 2026:

Role What they do in the system
Sales Representative Owns their leads, accounts, deals, quotes, activities and email. Uses the system every day.
Sales Manager / Lead Everything a representative can do. Also sees the whole team’s work, moves work between people, and oversees it.
R&D / Sample Owner (Taster) Runs each sample from start to finish: prepares it, sends it, records the feedback and the result.
Tea Room (Pricing) Sets and publishes the weekly bulk prices for each buying standard, and looks after the pricing settings.
Administrator Manages users and roles, pipelines and stages, reference data, templates, custom fields and imports.
Executive / Management Can view, but not change, dashboards, pipelines, forecasts, quotes and reports.

Price control. Representatives can quote freely at or above a required gross-profit margin. A quote below that margin waits for the Managing Director’s approval. The system holds the cost and works out the margin. It never sets a price itself.

Roles are yours to shape

Access depends on a person’s role and on who owns each record. Empire Teas decides what each role can do (agreed 7 September 2026).

  • No roles are built in (decided 24 September 2026, replacing the single built-in Administrator role described on 11 September). The system starts with one ordinary role, IT Admin, held by one named account. Your administrator signs in with it and creates every other role.
  • The six roles above are our recommended first set. We create them with you at go-live.
  • Each person has one role (decided 11 September 2026), to keep the system simple.
  • An administrator builds each role by ticking permissions from a list of everything the system can do.

Each area of the system has two permissions: view and manage. Manage includes view and every action in that area: create, edit, archive, share, change the owner, and ask the AI for a draft. A few permissions stand on their own (decided 24 September 2026):

  • publishing the weekly prices;
  • approving a quote below the margin;
  • the pages under Settings, one permission for each (users, roles, the tag pages and email templates — changed 30 October 2026; before that, one permission covered them all);
  • using your own mailbox.

Anyone who can see the buying-standards book also sees the costs and margins in it. An account page shows that customer’s standards with the final price only.

AI help is not a separate permission.

  • Results the AI produces on its own can be seen by anyone who may view the record.
  • AI help that a person asks for comes with the permission it helps with.
  • Acting on any AI result always needs a person whose role allows that action.

The reporting line

Each person may have a manager. Leads, accounts, deals, quotes and samples have owners. For these areas, every permission covers:

  • the person’s own records (the ones they own, or that are shared with them); and
  • their team’s records (the same, for everyone below them).

So a Sales Manager follows their team’s deals with nothing extra to set up. Each of these areas also has an “all records” permission, which covers everyone’s records (decided 27 September 2026).

No permission ever opens another person’s mailbox.

A record can also be shared with a named colleague. What that colleague can then do with it depends on their own role.

Who can sign in, and who can change access

Decided 24 September 2026:

  • Nobody can sign in unless an administrator has added them. There is no invitation email.
  • People are deactivated, never deleted. Deactivating someone ends their sessions at once.
  • The CRM refuses to deactivate someone who still owns records or has people reporting to them.
  • Who holds each permission is a setting. By default, only the Managing Director’s role approves quotes below the margin, and only the Tea Room publishes the weekly prices. But whoever manages users and roles could change that, including for their own role. Every such change is recorded.
  • We recommend that Empire Teas keeps at least two people in an administrator role.

3. What the system will do

This section covers the CRM and the companion capture app, grouped by subject.

  • They are delivered in two phases. Each phase is followed by an acceptance round with your team.
  • Each item says which phase it arrives in. The phases were regrouped on 17 September 2026 (see the Project Timeline, Section 2).
  • Each phase is accepted against written acceptance criteria agreed at its start.

Phase 1 runs to 27 November, with its acceptance round to 10 December. It brings:

  • users and roles;
  • accounts and contacts;
  • leads, with AI research, ranking, summaries and drafted follow-ups;
  • account briefings and follow-up tasks;
  • email and templates, and reminders for customer and lead emails that have no reply;
  • tracking of opens and clicks, and sending an email later;
  • record sharing;
  • the 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 move of leads, accounts and contacts from Pipedrive;
  • the trade-show capture app.

Phase 2 runs to 8 January 2027. It brings deals and pipelines, the tea-export workflow, the dashboard, the rest of the AI features, outreach sequences, the everyday conveniences in Section 3.4, and a final data move after the data freeze (leads, organisations and contacts again).

Deals start fresh in the new system. Past deals stay in Pipedrive.

3.1 The core CRM — nothing lost from Pipedrive

Before these features, Foundation sets up the base that everything else builds on:

  • Sign-in with each person’s company Microsoft account (decided 4 September 2026). It is one work login for everything, protected by Microsoft’s own security and multi-factor sign-in. There is no separate CRM password to manage or forget.
  • The permission system in Section 2, with its first IT Admin account. The six recommended roles are created at go-live.
  • The running environments (development and production).

The features:

  • Accounts and contacts (Phase 1). A full customer record: profile, required certifications, preferred packaging, Incoterms, contacts and the full history of communication. It can be shared with colleagues. Linked deals, samples and quotes join it in Phase 2.
    • A contacts page lists every contact a person may see, including people with no organisation. Each one can be found, edited and attached to an account.
    • Past orders appear once the ERP is connected, which is a separately priced follow-on. The other choice is the simple stop-gap in Questions for Empire Teas, Q17.
  • Leads (Phase 1). Every inquiry becomes a lead. The AI researches, ranks and summarises it (Section 3.3). It can be shared with colleagues.
  • Two sales pipelines (Phase 2): Private Label and Bulk. Each is a drag-and-drop board with its own stages, because the two businesses really do work differently. Deal cards show the value, volume and owner, and warn when a deal has sat in a stage too long.
  • Activities and reminders. Tasks, calls, meetings and deadlines, each linked to the record it belongs to, and grouped as overdue, today and upcoming. On leads and accounts in Phase 1; on deals in Phase 2.
  • The working dashboard (Phase 2): response times, follow-ups due, overdue samples, ageing quotes, quiet high-value accounts, the pipeline, and a weighted forecast.
  • Email inside the CRM (Phase 1, unless marked):
    • Each user’s Microsoft 365 mailbox connects when they sign in, and the CRM shows it live.
    • Email with a known buyer is filed against the right lead, contact and account. Only that email is kept in the CRM, in full, with its attachments. Whole mailboxes are not copied (changed 17 October 2026).
    • Earlier email with a buyer is found automatically, going back 12 months.
    • Blocking personal addresses, so their email is never linked, comes in Phase 2 (moved 11 November 2026).
    • Write, reply and use templates with merge fields.
    • A reminder when a customer’s or a lead’s email has had no reply for one working day (an administrator can change this time). It goes to the person who received the email. They can reply, with a template or an AI draft they check, or mark that no reply is needed (added 12 November 2026).
    • Tracking of opens and link clicks, and sending an email later at a chosen time. Planned for Phase 2, built early, and now in Phase 1 (18 November 2026).
    • Your team already works this way in Pipedrive, so the habit carries straight over.
    • Mail is sent from the user’s own mailbox. For the outreach sequences in Section 3.3, this is our default; we confirm it with you when sequences are designed.
  • A search box on every list. Each list has its own search over the records that person can see: accounts, contacts and leads in Phase 1; deals, quotes and the rest in Phase 2. There is no single search box across every kind of record (11 October 2026, Section 4).
  • The move from Pipedrive (Phase 1). A checked import of leads, organisations and contacts, with duplicates removed and data cleaned. It runs again after the data freeze, to bring across anything added in Pipedrive in the meantime.
    • Pipedrive notes, activities and custom fields are not moved. They stay readable in Pipedrive until you switch it off (decided 28 September 2026).
    • Every imported lead and account first belongs to one Empire Teas user: the person who runs the import, most likely your IT administrator. That person then hands them to each representative in bulk (Phase 1).
    • The Pipedrive owner’s name is kept on each imported record only to make that hand-out quick. It is not shown on the record or in the everyday lists.
    • Deals are not moved. They start fresh in the new system, and Pipedrive stays their record (decided 13 September 2026).
    • The backlog of more than 200 leads comes across and is sorted by priority (Section 3.3).

3.2 The tea-export workflow (Phase 2, except weekly prices)

Everything in this section arrives in Phase 2, except buying standards with weekly bulk prices, which arrive in Phase 1.

  • Sample tracking. Every round of a sample, from start to finish: prepare, send, deliver, feedback, result. It holds the courier and tracking details, reminds people when feedback is overdue, and shows clearly where a sample is stuck. Matching an existing standard usually takes one or two rounds. Developing a new one takes six or seven, and rarely more than ten. The system is built for this.
  • Quotes with a readiness checklist. A quote cannot be submitted until its eight checks pass: product, quantity, packaging, Incoterm, currency, destination, certifications and margin. Its price must also meet the margin rule in Section 2. Each quote keeps its history of changes and shows how old it is.
  • Product briefs. The internal brief for private-label development: tea type, blend, origin, packaging, pack size, certifications and target market. Open questions are flagged before the brief goes to R&D.
  • Certification checks. The system compares what a buyer requires with what the buying standard actually holds. It flags any gap before it becomes a shipment problem.
  • Export-document checklists. The right set of documents for each destination and certification, tracked as they are gathered: invoice, packing list, bill of lading, certificate of origin, phytosanitary certificate, SLTB authorisation, the Lion Logo where it applies, and any extras a destination needs. The CRM shows what is required. Filing with SLTB and Customs stays with the export team.
  • Buying standards with weekly bulk prices (Phase 1):
    • There is no separate product catalogue (agreed 15 September 2026). Every item Empire sells, bulk or private label, is a buying standard for one client, with its own running number, just as the Tea Room works today. Each standard holds its grade, origin, brand and certifications.
    • The Tea Room creates, edits and archives standards. Archiving keeps the price history and takes the standard out of quoting.
    • Prices are set week by week, in US dollars. Each standard has one price, the same for every destination (agreed 9 September 2026). Every past price is kept.
    • The system keeps the working behind each price, not just the final figure (17 September 2026): the rupee price, the rupee price with overhead, the converted dollar figure, and the final dollar price you give the customer. Only the final dollar price is required. The rest is recorded when you have it, so a price can still be entered directly. Because the working is kept, any past week’s price can be explained, not just quoted.
    • The Tea Room publishes the prices; everyone else reads them. A rep can email a customer their standards and current prices from that customer’s account page, one account at a time.
    • From the Pricing page, a person who sends email from the CRM can also send the week’s prices to every customer at once. Each customer still receives only their own prices. Planned for Phase 2 as part of bulk email, built early, and now in Phase 1 (18 November 2026).
    • The Tea Room can withdraw a price published for this week or a later week, with a reason, so that a corrected price can be published instead. The withdrawn price stays on record, and no earlier week ever changes (11 October 2026).
    • The Tea Room can correct a price that is already in force, from today on, with a reason. Earlier days keep the old price, so what was quoted before stays true. The Tea Room can also fix or delete an auction sale that was entered wrongly, while none of its prices is published. The user guide’s Weekly Prices chapter explains both.
    • To find a price, the Pricing page lists every standard, searchable by number or customer, with its current price. Each account page shows that customer’s standards. There is no separate price-lookup page (11 October 2026).
  • Pipeline settings. Administrators can change the stages, each stage’s chance of winning (which drives the weighted forecast), and how long a deal may sit in each stage before it is flagged.
  • Alerts for stalled and quiet work. Deals that sit too long in a stage, quotes older than a set limit, and high-value accounts that have gone quiet are shown automatically.

3.3 The AI assistant — always under human control (Phase 1 for leads and accounts, Phase 2 for the rest)

Every AI result is a draft that a person reviews and approves.

  • The AI never sends anything on its own.
  • It never sets or approves a price.
  • It never makes compliance decisions.
  • Each result is labelled as written by the AI, with how confident it is. The audit trail records who approved what.

The AI features:

  • Lead research, ranking and summaries (Phase 1):
    • Every new inquiry is first researched. The AI looks the company and the person up in public sources, and shows the source of each finding.
    • It then gives the lead a priority with a stated reason, summarises it, and checks it for spam and duplicates.
    • If the lookup cannot run, the lead gets a priority from its inquiry, with lower confidence, and a new one once the lookup is done (5 November 2026).
    • A drafted reply is one click away. A button on every lead drafts it in Empire Teas’ voice and shows it for review before anything is sent (8 October 2026).
    • The backlog of more than 200 leads is handled the same way on day one. The team gets a ranked list, can easily find the leads that have gone quiet, and has a drafted re-engagement email one click away on each.
  • Reading inquiries (Phase 1). The AI pulls the buyer, country, grade, volume, certifications, Incoterm, destination and timing from an inquiry email into a draft record. Anything it cannot find is left blank, never guessed.
  • Account briefings (Phase 1). A summary of an account before a meeting: where things stand, open items and a suggested next step, with the history it was drawn from.
    • It is prepared when someone who may edit the account presses a button.
    • On an account with no contact for a while, it suggests how to re-engage the customer.
    • It does not cover past orders, because the CRM does not hold them (21 October 2026).
  • Quote help (Phase 2). Flags missing inputs and risks on a quote. It informs the person pricing; it does not set the price. It no longer shows similar past quotes (11 October 2026, Section 4).
  • The morning briefing (Phase 2). A personal daily summary, on the dashboard, of what needs attention and what is stuck.
  • Drafting. Inquiry replies and follow-ups (Phase 1), and the steps of outreach sequences (Phase 2), drafted in Empire Teas’ voice. A person always edits and approves them before sending.
  • Outreach sequences (Phase 2). A planned series of emails and tasks, with AI-drafted steps that a person approves. They work through the sorted backlog and re-engage quiet accounts.
  • AI quality comparison (Phase 2). A one-time, side-by-side comparison of the AI’s quality against another family of AI models, promised in the proposal. Altrium runs it on Empire Teas inquiries with names and details removed, and reports the result for information. It uses Altrium’s own test accounts; no Empire Teas account or key is involved. The CRM itself uses Claude on Amazon Bedrock.

Where the AI runs. The AI uses Anthropic’s Claude models through Amazon Bedrock, called from inside the project’s AWS account (Empire Teas’ own account, set up by Altrium).

  • There is one provider, with no separate AI company and no separate AI bill. AI use appears on Empire Teas’ AWS bill.
  • Buyer data is never used for any other purpose.
  • Where a request is processed depends on the Bedrock route:
    • When a person is waiting for the answer, the smaller model runs in one of three US regions.
    • The smaller model’s background work on each new lead (its summary, the spam check and the research), and for now the larger model, run through Amazon’s worldwide routing. This may use any commercial AWS region.
  • On every route, each request starts in Empire Teas’ own AWS account and stays on Amazon’s network, encrypted. Anthropic does not see it, and neither Amazon nor Anthropic trains its models on it.
  • So we decided that processing in any commercial region is acceptable. Moving to US-only processing is a setting, if Empire Teas ever needs it (Questions for Empire Teas, Q18, answered and closed 4 November 2026).
  • If the AI is ever unavailable for a while, every AI screen falls back to the manual way of working. An outage never stops the team.
  • Only the minimum data a task needs is sent, and never in bulk.
  • Some AI work runs on its own, such as researching and ranking each new lead and preparing the morning briefing. Its results wait for a person to act on them. The rest, such as a drafted reply or an account briefing, runs only when a person asks for it.
  • Nothing the AI produces is sent, saved as a decision or acted on until a person approves it.

3.4 Everyday conveniences (Phase 2, except the parts marked as coming earlier, in Phase 1)

  • Calendar sync with Microsoft 365, both ways, so outside meetings appear next to the CRM’s activities.
  • Contact sync from Microsoft 365. The CRM reads each person’s Outlook contacts every hour. Contacts the CRM does not have yet appear on that person’s own list. They add the ones they want, choosing the account, and dismiss the rest. Personal contacts never enter the CRM unless someone adds them. Nothing is written back to Outlook. You can ask for that during acceptance testing.
  • List views, saved filters and bulk actions. Every kind of record gets a sortable table, with saved filters (personal or shared) and bulk actions: edit, change the owner, add to a sequence, export. Changing the owner of many leads or accounts at once comes earlier, in Phase 1, for handing out the imported records (30 September 2026). List views with saved filters on accounts, contacts and leads also come earlier, in Phase 1 (18 November 2026). Deals, quotes, samples and buying standards follow in Phase 2, with the other bulk actions.
  • Bulk email (added 9 October 2026):
    • Send the week’s prices to every customer at once. Each customer still receives only their own prices. This part comes earlier, in Phase 1 (18 November 2026; Section 3.2).
    • Send one message to a saved list of contacts, such as a newsletter, a product promotion or a trade-fair invitation, built from an email template.
    • See a summary for each send: how many emails were delivered, opened and clicked.
    • A newsletter comes from the mailbox of the person who sends it, so replies reach them. Everyone on the list receives it unless they have unsubscribed. Each newsletter shows your postal address and an unsubscribe link, which opens a page with one button and needs no sign-in. The CRM leaves out anyone who has unsubscribed or whose email bounced. One person can send to at most 5,000 contacts in any 24 hours, counting their weekly price emails, which keeps within Microsoft’s daily limit. We chose these points ourselves on 19 November 2026 so building can start; please confirm them or tell us what to change (Questions for Empire Teas, Q10).
  • File attachments. Artwork, packaging mock-ups, buyer purchase orders, spec sheets and certification PDFs are kept on the record they belong to. Each upload is checked for file type and size. Virus scanning is built but switched off for now, so each file is marked as not scanned; it can be turned on later if Empire Teas asks. Attachments on accounts, contacts and leads come earlier, in Phase 1 (12 November 2026). Deals, quotes, samples and product briefs follow in Phase 2.
  • Custom fields. Administrators can add fields to any kind of record without any programming, so new needs can be met in-house. Custom fields on accounts, contacts and leads come earlier, in Phase 1 (11 November 2026). Deals, quotes, buying standards and samples follow in Phase 2.
  • Spreadsheet import and export. Regular Excel or CSV imports, with column matching and duplicate checks (for trade-fair lists and data kept in Excel), and export of any list.
  • Handing a deal to the ERP. When a deal is won, the system produces a handoff document, checked by a readiness checklist, for entry into the ERP. A live link to the ERP is a separately priced follow-on, once you have chosen the ERP that replaces IFS and given us its details (12 November 2026). The document always works, whatever happens with the ERP.

3.5 The trade-show capture app (Phase 1)

Updated 12 November 2026: moved from Phase 2 to Phase 1, as agreed at the progress meeting of 10 November.

The capture app is a web app that can be installed on a phone, for use at exhibitions. It closes a gap: today, exhibition contacts get one conversation and are then lost in a stack of business cards.

At the stand:

  1. During the conversation, photograph a business card or scan a badge, one at a time.
  2. Add a short note if you want, and carry on.
  3. The app reads and researches the captured lead. The lead then waits in the app until someone reviews it.
  4. Converting the lead puts it in the CRM’s leads, owned by the person who converted it. From there it is handled like any other inquiry. Rejecting it keeps it in the app only. (Updated 12 November 2026; before that, every capture went straight into the CRM.)

Using the app needs its own permission. An administrator gives it to the roles of the people who work at trade fairs.

The full app is delivered within this version. That includes capture, card reading, company research, ranking, and notifications to the sales team inside the app: a list of new and reviewed leads, and an on-screen notice when a lead is ready. The app sends no email (updated 12 November 2026). It runs as its own small application at its own web address, separate from the CRM.

Planning a show (added 12 November 2026, in Phase 1, after the planning screens were shown at the progress meeting of 10 November):

  1. Before a show, a representative sets it up in the app, with its first and last day if known.
  2. They load the show’s list of exhibitors from a spreadsheet, or add exhibitors one by one. The app matches the spreadsheet’s columns by their headings, and the representative checks them.
  3. The AI researches every exhibitor and ranks it, with the reason it is worth a visit, for a person to review.
  4. On the day, the representative writes visit notes and marks each stand as visited.

A smaller version is still available if Empire Teas prefers it: capture and send to the CRM, with research afterwards. Captured leads are still reviewed in the app before they reach the CRM. The agreed scope is recorded in the Statement of Work.

4. What is not included

To protect the timeline and the price, the following are not part of this version (V1). Several can be added later as separately agreed work.

  • Any ERP work: stock, production, purchasing, finance, invoicing or confirmed orders.
  • A live, automatic link between the CRM and the ERP. This is a priced follow-on, once you have chosen the ERP that replaces IFS and given us its details. V1 provides the handoff document instead.
  • Estate, plantation and factory operations; auction bidding; AI tea grading.
  • Apps in the App Store or Play Store. The CRM is a web app that works on any screen size, and the capture app is a web app that can be installed. Store versions can be added later from the same code.
  • A general tool for building automations without code, or a store of add-ons from other companies.
  • A full marketing suite.
    • The Pipedrive paid add-ons are not part of V1: newsletter campaigns (beyond the bulk email in Section 3.4), a website chatbot and live chat, data enrichment, LinkedIn tools and sales goals. They sit outside the V1 price and timeline, as the proposal says.
    • Updated 11 October 2026: they are no longer planned for a later version either, because none is expected to add enough for your team to be worth building. We will ask whether the team uses any of them in Pipedrive today. If it does, it is raised then and agreed separately through change control, not added to V1.
    • Other marketing tools (drip campaigns, ad campaigns, landing pages, buying lead lists) are out of scope completely.
    • A note, because these two are easy to confuse: the system does research your leads. Before a lead gets a priority, the system looks up the company and the person in public sources: what they do, how big they are, where they are, and what certifications they hold. The priority and its reason are based on what it finds, and the sources are shown. If the lookup cannot run, the priority is given from the inquiry and given again once the lookup is done. What is not in V1 is a paid data-enrichment subscription, where contact details are bought one record at a time from a data company. The research is included; bought data is not.
  • WhatsApp integration (decided 11 September 2026, after the discussion on 9 September). The system does not copy or send WhatsApp conversations. People note them in the CRM by hand.
  • An email campaign product beyond bulk sending (9 October 2026). Bulk email is in Section 3.4: the week’s prices to every customer in Phase 1, and messages to a saved list in Phase 2. What stays outside V1 is the rest of a campaign tool: audience groups beyond saved lists, reports that compare campaigns over time, a drag-and-drop email designer, and subscriber management. In Phase 1, every email leaves from a person’s own mailbox, including the week’s prices sent to every customer at once.
  • An automatic feed of tea-auction prices into the system. A public auction data service does exist. Pulling in weekly reference prices to help the pricing team is a planned follow-on, not V1 work, and the system is built ready for it. In V1, the Tea Room enters and publishes the weekly prices, and no automation ever sets a price. Taking part in the auction itself (bidding) is something the CRM will never do.
  • Four items left out on 11 October 2026, to keep Phase 2 to its dates. Any of them can be added later as separately agreed work.
    • A single search box across every kind of record. Each list has its own search instead.
    • AI matching of similar past quotes.
    • The AI product-brief assistant. A rep fills in the brief, and its open-questions check stays.
    • A separate price-lookup page with a price-history screen. The Pricing page and account pages show current prices, and every past price is kept.
  • Two more items left out the same day:
    • The capture app’s same-day email to people met at the stand. One bulk email to a saved list of a show’s contacts does the same job (Section 3.4).
    • Creating new custom fields during a spreadsheet import. An administrator creates the field first.
  • Sending forms directly to SLTB, ASYCUDA or Customs.
  • Any decision made by the AI on its own.
  • Email providers other than Microsoft 365. The team uses Microsoft 365; anything else needs a change request.

5. Our commitments on security, data and ownership

  • Ownership. Empire Teas owns the source code and all data, with access to the code from the first week of the build. There is no lock-in. At the end, Empire Teas holds the full source code, a complete copy of the database and all stored files.
  • Hosting. The system runs in an AWS cloud account, with development and production kept apart. Your team’s acceptance testing runs in a temporary test environment. It is set up for Phase 1’s acceptance round and kept until Phase 2’s round ends, then removed. Testing can also run in production before go-live, with the test data removed afterwards. The development environment is only for building. The expected running costs are in Section 8. The providers bill them directly to the account holder, separately from the build price and the support fee.
  • Security.
    • Data is encrypted when it moves and when it is stored.
    • Passwords and keys are kept in a managed vault.
    • Administrators sign in with their company Microsoft account (single sign-on), with multi-factor sign-in.
    • AWS’s continuous threat detection (GuardDuty) is available but switched off for now. It is turned on if Empire Teas asks.
    • A log of actions on the infrastructure that cannot be changed.
    • Every build checks the software libraries it uses. A test or live release stops if one of them has a known security weakness.
    • A security review before go-live, covering sign-in, sessions, permissions, file uploads and the limits on the AI.
  • Backup and recovery. Automatic backups, with recovery to any five-minute point, kept for 14 days in production; and daily snapshots. We rehearse a restore, and write it up, before go-live, and test a restore every three months after that.
  • Data protection.
    • Buyer contact data, including data about people in the EU, is treated as confidential.
    • Each role sees only what it is allowed to, and every change is recorded.
    • Only email linked to a customer record is stored. A wrong link can be removed, together with the stored copy.
    • All data stays inside Empire Teas’ own AWS account, never in a shared or third-party store. Altrium works in it on Empire’s behalf, as its data processor, and the data is never used for any other purpose.
    • The account is in the US East region, chosen for cost. Users reach the applications through CloudFront, Amazon’s worldwide network, so the location does not slow the pages down.
  • AI data handling. As Section 3.3 explains, the models are called through Amazon Bedrock from inside the project’s AWS account (Empire Teas’ own). Where a request is processed depends on the Bedrock route, in any of Amazon’s commercial regions. Buyer content never reaches a separate AI company. Only the minimum a task needs is sent, and never in bulk.
  • A record of every change. Every change made in the system is recorded: who, what and when (decided 24 September 2026). This includes stage moves, price approvals, weekly price publishing, changes to settings and permissions, sharing, and every AI approval. Every sign-in, refused sign-in, sign-out and export is recorded too. Viewing is not recorded. V1 has no screen for this record: it is kept in the database, and we answer audit questions from it when asked.

6. How the move off Pipedrive is kept safe

  1. Running both systems side by side. Once the core CRM and the data move are ready in Phase 1, the new CRM runs alongside Pipedrive. The start date is agreed with you when the data move is ready; on the current schedule it is late in Phase 1. Pipedrive stays live and remains the main record.
  2. Data freeze and final data move. Before go-live, a short agreed freeze is used to bring across everything created in Pipedrive while both systems ran.
  3. Going back. Until Empire Teas signs off, the team can go back to Pipedrive at any time.
  4. Switching Pipedrive off. Pipedrive is cancelled only after sign-off, a stable period, and Empire Teas’ own review of the data-move report. Empire Teas decides when.

7. How success is measured

At acceptance, the test is practical: the team can work a full day without Pipedrive, including email, and each phase has passed its written acceptance criteria.

After acceptance, these are the results the system is built to improve. We measure the starting point together at kickoff.

Result Today Aim
Leads not yet reviewed 200+ All sorted by Phase 1 acceptance: researched, ranked and summarised, with a drafted re-engagement email one click away
Average time to answer an inquiry not measured Hours, not days. The exact target is set against the kickoff measurement.
Missed follow-ups common Fewer. Every follow-up has an owner and a date.
Samples stuck without feedback not visible None past the limit without being shown
Quotes older than the limit not visible Shown, with the value at risk
Quiet high-value accounts not noticed Found and re-engaged through sequences
Manual typing for each inquiry minutes Seconds: the AI reads it and a person confirms. Measured against the kickoff measurement.

8. What it costs to run

Once the system is live, the providers bill the running costs directly to Empire Teas, as the account holder. These costs are separate from the one-time build price and the monthly support fee. Those two are commercial terms in the proposal and Statement of Work.

Line Expected monthly cost (USD)
AWS infrastructure, both permanent environments ≈ 124. The temporary test environment runs from Phase 1’s acceptance round to the end of Phase 2’s, about 11 weeks (≈ 100–155 in total, spread over November to January, less if it is paused between the rounds). It is removed after that, so it is not a standing cost.
AI use: Anthropic’s Claude models through Amazon Bedrock, on the same AWS bill ≈ 26–31 expected at the planned volumes. Budget: 50. A billing alert at 150, a switch to turn off each AI feature, and a hard limit that turns AI features off rather than allow an unlimited bill.
Web search for lead research: Exa, chosen by Empire Teas on 10 November 2026, on its free credit for now ≈ 0–2. Nothing while the free credit covers the month.
Source control and build pipeline 0–50
The trade-show capture app once live: separate hosting, extra AWS cost (its notifications are inside the app, at no extra cost) ≈ 25–45
Expected total ≈ 150–207 a month; ≈ 175–252 once the capture app is live

Optional extra protection, a database spread over more than one AWS data centre and a web application firewall, adds ≈ 45 a month if Empire Teas chooses to turn it on.

These figures are below the proposal’s estimates (≈ 165–215, and ≈ 195–280 with the capture app). Three decisions taken after the proposal explain this:

  • both applications are served as plain files rather than running as a container;
  • the AWS region is settled as US East, so the extra regional cost the proposal warned about does not apply;
  • the capture app notifies people inside the app rather than through a messaging company.

A small arithmetic correction in the proposal’s development subtotal also lowers the figure. None of this changes the scope, the build price or the support fee. The line-by-line working is in the companion Running Cost Annexe, whose figure is the one quoted in the Statement of Work.

9. Assumptions and change control

This document rests on the assumptions in the proposal (Section 13). In particular:

  • In V1, the ERP handoff is a document.
  • The certification data will be provided in a usable form. If it cannot be, the certification check becomes a manual checklist, agreed before it is built.

Every change follows the same steps, whether it is a new request or an assumption that turned out differently:

  1. Altrium assesses the effect on scope, timeline and cost, in writing.
  2. Empire Teas approves.
  3. The plan and price are adjusted.

Work continues on the agreed scope until a change is approved.

Change history

The changes made to this document since it was issued, newest first. The body above already includes each of them.

  • 17 November 2026: blocking personal email addresses moves from Phase 1 to Phase 2 (Section 3.1, Email inside the CRM), a decision of 11 November 2026. No price or date changes.
  • 16 November 2026: rewritten in simpler English, with the earlier change notes moved to Change history at the end. Section 3.2 now also says that the Tea Room can correct a price already in force and fix or delete a wrongly entered auction sale; both are built. Section 8 records that Empire Teas chose Exa for lead research on 10 November. No price or date changes.
  • 12 November 2026 (fifth change that day): the trade-show capture app also plans each show before it starts: a list of the show’s exhibitors, each researched and ranked, with visit notes and a visited mark for each stand. It arrives in Phase 1 with the rest of the app (Section 3.5).
  • 12 November 2026 (fourth): in the capture app, a captured lead waits in the app until someone reviews it. Converting it puts it in the CRM’s leads, owned by whoever converted it; rejecting it keeps it in the app only. Cards and badges are captured one at a time, and using the app needs its own permission (Section 3.5). No price or date changes.
  • 12 November 2026 (third): the capture app tells the sales team about each new lead inside the app, with a notifications list and an on-screen notice, instead of by email. It sends no email (Sections 3.5 and 8). No price or date changes.
  • 12 November 2026 (second): two additions to Phase 1, after the progress meeting of 10 November: a reminder for a customer email that nobody has answered (Section 3.1, Email inside the CRM), and file attachments on accounts, contacts and leads, which are built and were shown in that meeting (Sections 3 and 3.4). No price or date changes.
  • 12 November 2026 (first): the capture app arrives in Phase 1 instead of Phase 2, as agreed at the progress meeting of 10 November, so that it can be used at the January 2027 trade fairs (Sections 3 and 3.5). Its scope is unchanged. No price changes.
  • 11 November 2026: custom fields on accounts, contacts and leads are built and arrive in Phase 1 (Section 3.4). Custom fields on deals, quotes, buying standards and samples, and list columns and filters on custom fields, stay in Phase 2. No price or date changes.
  • 5 November 2026: if the public-source lookup for a lead cannot run (the search service is down or switched off, or the lookup has not run within a day), the lead gets a priority from its inquiry, with lower confidence, and a new one once the lookup is done. No lead is left without a priority (Sections 3.3 and 4). No price or date changes.
  • 4 November 2026: Section 3.3 says where the AI’s background work on each new lead is processed: through Amazon’s worldwide routing, as the larger model already is. This gives it its own capacity, so it no longer slows the answers people wait for. Those answers stay in the US. Processing in any of Amazon’s commercial regions is accepted, which settles Questions for Empire Teas, Q18 (Sections 3.3 and 5). No price or date changes.
  • 26 October 2026: Section 8 names the web-search service used for lead research, Exa, on its free credit for now, until Empire Teas answered on it (settled on 10 November), as the running-cost annexe already did. No price or date changes.
  • 21 October 2026: an account briefing is prepared when someone who may edit the account asks for it, with a button at the top of the account, instead of in the background. People who may only view an account do not start AI work. Because the CRM holds no order history, the briefing does not cover past orders. On an account with no contact for a while, it suggests how to re-engage the customer (Section 3.3). No price or date changes.
  • 17 October 2026: email inside the CRM keeps only the emails linked to a lead, contact or account. The rest of each mailbox is shown live from Microsoft and never copied. The mailbox connects when the user signs in, past email with a buyer is linked automatically back 12 months, and addresses can be blocked (Section 3.1, Email inside the CRM; Section 5, Data protection). This answers the question raised on 16 October about very large mailboxes.
  • 11 October 2026 (later): the equivalents of the Pipedrive paid add-ons (newsletter campaigns, chatbot and live chat, data enrichment, LinkedIn tools, sales goals) are no longer planned for a later version either (Section 4). Bulk email (Section 3.4) and lead research do not change.
  • 11 October 2026 (second): two more items leave V1 (Section 4). The capture app’s same-day email to people met at the stand: the same message can go to a show’s contacts as one bulk email to a saved list (Section 3.4), and Question Q15 is withdrawn. Creating new custom fields while importing a spreadsheet: an administrator creates the field first, then imports.
  • 11 October 2026 (first): four items leave V1 to keep Phase 2 to its dates (Section 4). Search across every kind of record: instead, each list (accounts, contacts, leads, deals, quotes, standards) has its own search box. AI matching of similar past quotes: earlier quotes stay on the account and in the quote list, and the quote assistant still flags missing inputs and risks. The AI product-brief assistant: a rep fills in the brief, which still flags open questions before handoff. A separate price-lookup page with a price-history screen: the Pricing page already finds any standard by number or customer with its current price, and every past price is kept. Also: the Tea Room can withdraw a price it has published for this week or later, with a reason; the withdrawn price is kept, and earlier weeks never change (Section 3.2).
  • 9 October 2026 (first): bulk email is now part of Phase 2: the week’s prices to every customer at once, and newsletters, product promotions and trade-fair invitations to a saved list of contacts, with opens and clicks shown for each send (Sections 3.4 and 4). It is added to what the proposal covers. Which Phase 2 features you need least is agreed with you at or before the Phase 1 hand-over, so the price and dates do not change.
  • 9 October 2026 (second): virus scanning of uploaded files and AWS’s continuous threat detection (GuardDuty) are switched off for now. They can be turned on later without any change to the software, if they are needed or Empire Teas asks. Uploads are still checked for type and size, and are marked as not scanned (Sections 3 and 5). No date changes. The AWS bill is about $5 a month lower for each environment while they are off.
  • 8 October 2026: the AI drafts a reply or follow-up for a lead when a person asks, with a button on every lead, instead of drafting every lead in advance. The moved backlog is still researched, ranked and summarised on day one (Sections 3.3 and 7). A contacts page, including contacts with no account, arrives in Phase 1 (Section 3.1). No price or date changes.
  • 5 October 2026: where Bedrock processes AI requests is stated as it is today (Sections 3.3 and 5; Questions for Empire Teas, Q18). The Phase 2 data move is the final run of leads, organisations and contacts (Section 3). Section 8’s AI and total figures match the running-cost annexe. Section 5’s dependency check stops a test or live release, not every build. No price or date changes.
  • 30 September 2026: the person who runs the Pipedrive import hands the imported leads and accounts to your team in bulk, so changing the owner of many leads or accounts at once arrives in Phase 1 (the other bulk actions stay in Phase 2). The Pipedrive owner’s name is kept only for that hand-out. Running both systems side by side starts on a date agreed with you once the data move is ready, not in early October (Sections 3 and 6). No price changes.
  • 29 September 2026: the phase dates follow the revised Statement of Work: Phase 1 to 27 November, with its acceptance round to 10 December; Phase 2 to 8 January 2027; sign-off 29 January 2027 (Project Timeline). The AWS account is now Empire Teas’ own, billed to Empire Teas directly by AWS (Sections 3.3 and 5). No scope or price changes.
  • 28 September 2026: the data move brings leads, organisations and contacts only. Pipedrive notes, activities and custom fields stay in Pipedrive (Section 3). No price or date changes.
  • 27 September 2026: Section 3 shows which phase each item arrives in, as regrouped on 17 September. The data move no longer lists deals (they start fresh, decided 13 September), and its activities and custom fields come with the final data move in Phase 2. Mail is sent from the user’s own mailbox. Past orders come with the ERP connection unless you choose the stop-gap in Q17. Lead research and ranking run automatically as each lead arrives, and a person still approves every AI result (recorded on the proposal on 27 September). A permission no longer carries its own reach: every permission on leads, accounts and the other owned areas covers a person’s own and their team’s records, and one “all records” permission for each such area covers everyone’s (Section 2). No scope, price or date changes.

Generated from .forge/client/client-facing-prd.md by .claude/lib/render-docs-html.js. Markdown is canonical.