source: .forge/client/phase-1-acceptance-criteria.md · generated — edit the markdown, not this file

Empire Teas CRM — Phase 1 Acceptance Criteria

Prepared by Altrium for Empire Teas (Pvt) Ltd DRAFT — not yet issued, for Empire Teas to agree. Until Empire Teas agrees it, nothing here binds either party. Revised 19 November 2026: “How the criteria are tested” now says Empire Teas chooses which data and which sign-ins the UAT environment uses, and which criteria arrive in the second UAT delivery. C5, H1, H3 and I3 now match the built CRM. F3 says how email reaches an account, and where a lead’s or contact’s email is shown; F4 says the same for an email a user sends. E1 says the search for the person can be turned off. C8 (several email addresses for one contact) and F10 (files attached to an email) are added for features that are built. Revised 18 November 2026: three features planned for Phase 2 are built, so they are added to Phase 1 and accepted with it: tracking opens and clicks, and sending an email later (F8, F9); sending the week’s prices to every customer at once (G9); and saved views on the account, contact and lead lists (Section N). Revised 17 November 2026: blocking email addresses moves to Phase 2 (F6, Not part of Phase 1), a decision of 11 November 2026; F5 says writing templates needs the Email templates permission; the longer criteria are split into shorter sentences, with no other change of meaning.

This is the written list Phase 1 is accepted against. At the end of Phase 1, Altrium demonstrates each criterion below to Empire Teas’ named signatory. Empire Teas then has five business days to accept the phase or to raise defects against these criteria (Project Timeline, “How to read this schedule”). If Empire Teas does not respond within that window, the phase is deemed accepted (proposal Section 6, Milestone acceptance).

What Phase 1 contains is set by the Product Requirements (Client Edition), Sections 2 and 3, and the Project Timeline, Section 2. This list does not add to that scope or take anything away from it. It turns each Phase 1 item into a check that can be shown and passed.

How the criteria are tested

  • Where: in the temporary UAT environment created in Empire Teas’ AWS account for the Phase 1 round (Project Timeline, Section 2). The development environment is not used for acceptance.
  • Who signs in: Empire Teas chooses this before the round. Testers use either their own Microsoft 365 accounts or the test accounts CRM01 to CRM05. With their own accounts, their real mailboxes connect to the UAT environment, so an email they send from it reaches a real person.
  • With what data: Empire Teas also chooses this before the round. The UAT environment can start empty, hold made-up records, or hold Empire Teas’ Pipedrive data, migrated as described in Section I. Records created during the demonstration are added to it.
    • Some criteria need Pipedrive’s data: Section I, the Dormant badge in C1, cold leads in D5, research on real companies in E1, and E8.
    • If the UAT environment does not hold Pipedrive’s data, these are shown on the production system when the Pipedrive data is first loaded there.
  • Two deliveries: the UAT environment receives Phase 1 in two deliveries. The first is handed over at the start of the round. The second follows during the round, with what is finished after the first. The criteria in the second delivery are F3, F6 and F7, and any other criterion named at the hand-over. Testers check those criteria once the second delivery arrives. Until then, a missing result there is not a defect.
  • Screens: every Phase 1 screen is checked on a desktop and on a tablet (768 pixels wide and up), in current Chrome, Edge and Safari. The capture app (Section L) is checked on a phone first, and on a tablet and a desktop too, in current Safari and Chrome.
  • When a criterion is met: the demonstration shows the result the criterion describes. A defect is something a criterion says should happen and does not. A request for something not in this list is a change request, not a defect.

A. Signing in and access

  • A1. A person whose Microsoft 365 account an administrator has added, and who is active, signs in with that Microsoft account. There is no separate CRM password.
  • A2. A person who has not been added, or who has been deactivated, cannot sign in and sees that sign-in was refused.
  • A3. A signed-in person can sign out, and their session ends.
  • A4. On first use, the system holds one account with the IT Admin role. Signed in with it, an administrator creates roles from the list of permissions Phase 1 provides, choosing each role’s permissions. Examples are a Sales Representative, a Sales Manager and a Tea Room role. A role can be renamed and its permissions changed. The full recommended set of roles is created at go-live. By then the Phase 2 permissions exist (deals, quotes, samples, below-floor approval).
  • A5. An administrator adds a user, gives them one role, and sets their manager. A user can be deactivated and reactivated, never deleted.
  • A6. Deactivating a user ends their open sessions at once. Deactivation is refused while the user still owns records or has people reporting to them, and the administrator is shown how to hand those over first (A8).
  • A7. The system refuses any change that would leave no active user able to administer users and roles, and nobody can deactivate themselves.
  • A8. When someone leaves, an administrator moves all the accounts and leads they own to another user, in one step. In one more step, they move the people who report to the leaver to another manager. The leaver can then be deactivated.
  • A9. For any user, an administrator sees the user’s role, each permission it holds, and which records each permission reaches. Records shared with the user are shown on each record.
  • A10. A permission change takes effect on the user’s next action, without them signing out.

B. Who sees which records, and sharing

  • B1. A sales representative sees the accounts and leads they own and those shared with them, and no others.
  • B2. A sales manager also sees the accounts and leads of everyone who reports to them, at every level below them, with nothing extra to set.
  • B3. A role holding the “all records” permission for accounts or leads sees every account or lead.
  • B4. Someone allowed to manage a record can share it with a named colleague, see who it is shared with, and remove a share. What the colleague can then do is decided by their own role. The list of colleagues offered contains only active people who can view that kind of record and cannot already see it. A person sees which records are shared with them, and can filter their lists on it.
  • B5. Someone allowed to manage a record can change its owner.
  • B6. Lists and single records follow the same rule. A person never finds a record in a list that they cannot open. They never open a record that a list hides from them.
  • B7. No permission gives anyone access to another person’s mailbox.

C. Accounts and contacts

  • C1. The account list shows each account’s key details, and can be filtered and searched. It marks an account as Dormant after 90 days without any contact: no email, note, follow-up or other entry on its timeline. If Empire Teas gives another number in answer to Questions for Empire Teas, Q12, that number is used instead. It is a setting, not new work.
  • C2. A user creates and edits an account: its profile, required certifications, preferred packaging and Incoterms, and its owner.
  • C3. The account page shows the profile and the account’s contacts. A user adds, edits and archives contacts, restores an archived contact, and marks one contact as the primary contact.
  • C4. A user adds notes and tags to accounts and contacts, and filters the account list by tag.
  • C5. The account page shows the account’s communication timeline: emails, notes, completed follow-ups and leads, newest first, each marked by type. (Updated 19 November 2026: before, this said “follow-up tasks”. Only a completed follow-up appears on the timeline. An open follow-up shows in Activities, as in Section H.)
  • C6. The account page shows the buying standards that customer buys, with only this week’s final price (Section G).
  • C7. A contacts page lists the contacts the user can see, with a search, and a user opens and edits a contact. People whose role holds the “all records” permission for accounts also see the contacts with no account, such as Pipedrive people with no organisation. They can attach each one to an account. From then on, the contact is seen with that account.
  • C8. Several email addresses for one contact. (Added 19 November 2026: built in Phase 1, and missing from the earlier draft.) A contact has one main email address and can have up to 20 others. A user allowed to manage the contact adds, edits and removes them, and can make any of them the main address. Email to or from any of the contact’s addresses is linked to that contact, as in F3.

D. Leads

  • D1. The lead inbox lists every lead the user can see, with filters for status, country, buyer type, source, tag and owner, and a search. Holders of the “all records” permission for leads also have an Unassigned filter.
  • D2. A user adds a lead by hand and edits it. Every lead records its source (Website, Trade Fair, Referral, Email or Other).
  • D3. The lead page shows the lead’s details, its notes and tags, and the account and contact it matches, if any. A user archives a lead (Archive) and restores it.
  • D4. A user links a lead to an existing account and contact. The lead then appears on that account’s timeline.
  • D5. Hot and cold. Each lead shows whether it is hot or cold, separately from its priority. A lead is hot while the buyer’s last message is no more than 30 days old, and cold after that. The buyer’s last message is the inquiry, or a later email from the buyer. Only the buyer’s own messages count, not ours. The lead inbox can be filtered to show the cold leads, so they can be followed up. The 30 days is a setting that can be changed without new work.

E. The AI assistant on leads and accounts

Every AI result below is a draft for a person to review. It is marked as produced by the AI, shown with its confidence, and nothing it produces is sent, saved as a decision or acted on until a person approves it. Requests may be processed in any of Amazon’s commercial regions (decided 4 November 2026; Questions for Empire Teas, Q18, answered and closed). A US-only setting is available if Empire Teas asks, and it would change where requests are processed, not these criteria.

  • E1. Research. Each new lead is researched in the background, without anyone asking. The company and the person named on the lead are looked up in public sources. Every finding is shown with the source it came from. An administrator can turn off the search for the person on the Settings page, under Lead research. The company is then still looked up. (Updated 19 November 2026: the setting is built.)
  • E2. Ranking. After research, each lead receives a priority of P1, P2 or P3, with the reason for the priority and a suggested next action. If research cannot run, or has not finished within a day of the lead arriving in the CRM, the lead receives a priority from its inquiry, with lower confidence. It receives a new priority once research is done. The lead inbox can be sorted and filtered by priority.
  • E3. Summary, spam and duplicates. Each lead receives a short summary. A lead that looks like spam, or repeats a lead already open in the inbox, is tagged with the reason, and the inbox can filter on the tag. A lead from someone already recorded as a customer contact is shown with that customer, ready to link. The tag is a suggestion: a person then archives the lead or keeps working it.
  • E4. Extraction. A user pastes the text of an inquiry email and receives a draft lead with the buyer, country, grade, volume, certifications, Incoterm, destination and timeline filled in. Any detail the email does not state is left blank, not guessed. The user corrects the draft and saves it.
  • E5. Drafted reply or follow-up. On every lead a user may work on, a button drafts a reply, follow-up or re-engagement email in Empire Teas’ voice. When a user presses it, the draft is generated and shown for review; the user edits it and sends it from their own mailbox only after approving it. The draft never states a price. Drafts are made when a user asks, not in advance.
  • E6. Account briefing. On an account, a user asks for a briefing. They receive a short summary of the account’s latest state, its open items and a suggested next step, with the sources it used.
  • E7. When AI is unavailable. With the AI turned off in the system’s configuration, or unreachable, every screen above still works by hand: leads can be added, edited and answered without any AI result.
  • E8. The migrated backlog. Every open lead migrated from Pipedrive (Section I) has been researched and ranked, so the team starts from a ranked list. Each one with email from the buyer linked to it has also been summarised from that email. The cold filter (D5) lists the backlog leads that have gone quiet. On any of them, a user drafts a re-engagement email with one press of the button in E5. (Product Requirements, Section 7: the backlog is fully sorted at Phase 1 acceptance.)

F. Email inside the CRM

  • F1. A user whose role includes email has their own Microsoft 365 mailbox connected automatically when they sign in, with nothing to press. They can disconnect and reconnect it from their own settings.
  • F2. The CRM’s inbox shows that user’s mailbox live from Microsoft — Inbox, Sent Items, Archive and their own folders, newest first — without copying it. Only email linked to a lead, contact or account is kept in the CRM, in full with its attachments.
  • F3. An email to or from a known lead or contact is linked to that lead or contact automatically. It then appears in the lead’s or the contact’s list of emails. An account gets its email through its contacts: an email linked to one of its contacts appears on the account’s timeline. A user can also link an email by hand, remove a wrong link, or create a lead from an email in one step. (Updated 19 November 2026: before, this said an email was linked to an account directly and appeared on the record’s timeline. An account has no email address of its own, so its email comes through its contacts. A lead and a contact show a list of emails, not a timeline.)
  • F4. A user writes a new email, or replies to one, from an account or a lead, with CC and BCC. It is sent once, from the user’s own mailbox. It appears on the account’s timeline, or in the lead’s list of emails. (Updated 19 November 2026: before, this said it appears on “the record’s timeline”. A lead has no timeline; its emails are shown as a list, as in F3.)
  • F5. A starter set of email templates is ready, including the weekly-prices template. A person with the Email templates permission creates and edits the templates, which every user can use. (Updated 17 November 2026: since 26 October 2026, writing any template, a person’s own included, needs that permission; before, any user could write their own.) Templates carry merge fields, such as the contact’s name or the account’s name. A user starts an email from a template, and the merge fields are filled in from the record.
  • F6. Email from the past 12 months is linked when a lead or contact is added, when a user’s mailbox is connected, and after an import. So migrated records show their past email. (Updated 17 November 2026: blocking addresses and domains moved to Phase 2 on 11 November 2026; see Not part of Phase 1.)
  • F7. (Added 12 November 2026.) An email from a customer or a lead is linked to its record, as in F3. If it has had no reply for one working day, the person who received it gets a follow-up about it in Activities (Section H). From the follow-up, they reply as in F4, starting from a template or from an AI draft they check and send themselves. Or they mark that no reply is needed, which closes it. A reply sent from the CRM or from Outlook closes it too. An administrator can change the wait on the Settings page. The system never sends a reply on its own.
  • F8. Tracking opens and clicks. (Added 18 November 2026: planned for Phase 2, built early, and accepted with Phase 1.) When a user writes an email in the CRM, Track Opens and Clicks is ticked. The user can untick it for that email. A tracked email shows Sent, then Opened once someone opens it, then Clicked once someone clicks a link in it. The mark shows on the email, in Sent Items, and on the account’s timeline for a price email. Opens and clicks are estimates. If an email went to several people, Opened means one of them opened it. The CRM keeps only that an open or a click happened, when, and which link. It keeps no internet address, device or location.
  • F9. Sending later. (Added 18 November 2026: planned for Phase 2, built early, and accepted with Phase 1.) When writing, replying or forwarding, a user chooses Send Later, picks a date and time from 2 minutes to 30 days ahead, and chooses Schedule Send. The email goes from their own mailbox within 2 minutes of that time. The inbox’s Scheduled folder lists the user’s waiting emails, and the user can cancel one there before it goes. If an email cannot go at its time, for example because the mailbox was disconnected, it shows as failed with the reason. Once the problem is put right, the user opens it with Edit and Send and sends or schedules it again. Send Later is not offered when approving an AI-drafted reply to a lead, or for the price email in G8, because those are sent at once.
  • F10. Files attached to an email. (Added 19 November 2026: built in Phase 1, and missing from the earlier draft.) When writing, replying or forwarding, a user attaches files from their computer. The types allowed are PDF, JPEG, PNG, and Excel, Word or PowerPoint in their current formats (.xlsx, .docx, .pptx). One email carries up to 25 MB of files in all, counting the attachments a forwarded email keeps. A file of any other type, an older .xls or .doc file, or a password-protected Office file is refused with the reason.

G. Weekly prices

  • G1. The Tea Room creates, edits and archives buying standards, each with its own running number, grade, origin, brand and certifications. An archived standard keeps its price history and cannot be chosen for new work. The Tea Room records the cost of a standard from a given date.

  • G2. The Tea Room uploads the week’s pricing workbook as it is today. The system reads it into draft prices for the week. It asks once which column holds which figure on each sheet, and remembers the answer for that sheet’s name. It flags any standard priced twice.

  • G3. Each price can record the rupee price, the rupee price with overhead, the dollar figure and the exchange rate used, and the final dollar price. Only the final dollar price is required.

  • G4. The Tea Room reviews the draft prices, edits any of them, and publishes the week’s prices. Only a role holding the publish permission can publish, and every publication is recorded.

  • G5. Each standard has one price for a given week, the same for every destination. Earlier weeks’ prices are kept and can be looked up; a published price is never overwritten.

  • G5a. The Tea Room can withdraw a published price that starts today or later, giving a reason, so that a corrected price can be published in its place. The withdrawn price stays on record with who withdrew it, when and why, and no earlier week’s price changes. (Added 11 October 2026.)

  • G5b. A price that started before today cannot be withdrawn. Instead, the Tea Room corrects it from today or a later date, giving a reason. Earlier days keep the old price, so what was quoted before stays true. (Added 16 November 2026, to match the built CRM.)

  • G5c. The Tea Room adds each weekly auction sale with its number, first day and last day. While none of a sale’s prices is published, the Tea Room can correct its number and dates, or delete it, giving a reason. Once a price is published, only its last day can change. (Added 16 November 2026, to match the built CRM.)

  • G6. A published price holds until the next weekly auction sale starts. A standard that has no price in the new sale’s round then shows No current price until a price is published for it. Before publishing, the Tea Room can carry a standard’s current price forward into the new round, one standard at a time or all at once, and this is recorded. (Updated 16 November 2026, to match the built CRM: before, this said the price showed as “lapsed” and could be extended by hand.)

  • G7. People who can see the standards book see costs and margins. On an account page, a user sees only that customer’s standards and their final prices.

  • G8. From an account’s page, a sales representative emails that customer its standards and this week’s prices, using the weekly-prices template, from their own mailbox, one account at a time.

  • G9. Sending the week’s prices to every customer. (Added 18 November 2026: planned for Phase 2, built early, and accepted with Phase 1.) After the week’s prices are published, a user who sends email from the CRM chooses Send Prices to Customers on the Pricing page. Then:

    1. The window lists the customers the user can see that have a published price this week. Those not yet sent this week’s prices are ticked. Customers that cannot be sent to are listed with the reason.
    2. The user ticks or unticks customers, and can preview any customer’s email.
    3. One confirmation sends them all.

    Each email goes to the customer’s primary contact. It copies the account’s other contacts, unless the user unticks Copy Each Customer’s Other Contacts. Each email uses the weekly-prices template and carries only that customer’s own standards and prices. The emails go from the user’s own mailbox, at most 20 a minute. The results show each customer as waiting, sent, not sent with the reason, skipped with the reason, not known, or stopped. Stop Sending stops the customers not yet sent. Each email sent is recorded on the customer’s account, as in G8.

H. Follow-up tasks

  • H1. A user adds a follow-up (a task, call, meeting or deadline) with a date to a lead or an account. The follow-up is assigned to the user, or to a colleague who can manage that record. (Updated 19 November 2026: assigning to a colleague is built.)
  • H2. The activities page lists the user’s follow-ups grouped as overdue, today and upcoming, with overdue ones highlighted.
  • H3. A user marks a follow-up as done. A completed follow-up on an account then appears on the account’s timeline (C5). A lead has no timeline, so a follow-up on a lead shows on the lead’s page and in Activities. (Updated 19 November 2026: before, this said follow-ups appear on “the record’s timeline”.)

I. Moving off Pipedrive

  • I1. From a Pipedrive export, the system first produces a report of what it would bring across: organisations, people and leads, including the records that may be duplicates. This changes no data. Possible duplicates are resolved by Empire Teas in Pipedrive before the import runs.
  • I2. The import then brings across Pipedrive’s organisations as accounts, its people as contacts, and its leads as leads. Pipedrive deals, notes, activities and custom fields are not brought across; deals start fresh.
  • I3. Every imported account and lead belongs at first to the person who ran the import. There is one exception. A Pipedrive organisation that matches an account already in the CRM keeps that account’s owner. (Updated 19 November 2026, to match the built import.) The person who ran the import filters the account and lead lists by the original Pipedrive owner and gives the records to each representative in bulk. The Pipedrive owner’s name is used only for this and is not shown elsewhere.
  • I4. The import can be run again later to bring across what was added in Pipedrive in the meantime, without creating duplicates of records already brought across or changing their owner.
  • I5. After each run, a migration report states how many records of each kind were found, brought across or left out, and why.

J. Records and safeguards

  • J1. Every change made in the system is recorded with who made it and when, as are sign-ins, refused sign-ins, sign-outs, permission changes, sharing and changes of owner. There is no screen for this record in V1; Altrium answers questions from it on request, and demonstrates this on a change made during the demonstration.
  • J2. Phase 1 is delivered as a numbered release, and the UAT environment runs that release.

K. Custom fields on accounts, contacts and leads

(Added 11 November 2026: planned for Phase 2, built early, and accepted with Phase 1.)

  • K1. A Custom fields page in Settings opens only for a role holding the custom-fields permission, which no role holds until an administrator grants it (A4). On it, an administrator adds fields to accounts, to contacts and to leads separately. Each field is one of five kinds: text, number, date, one choice from a list, or several choices from a list. Each kind of record holds up to 50 fields in use. Two fields in use on the same kind of record cannot share a name, whatever the capitals.

  • K2. An administrator renames a field, adds, renames and retires choices on a list, and changes the order the fields appear in. A field’s kind cannot be changed after it is created. A field can be archived, which hides it from every form and record page while the values already entered are kept, and restored, which shows those values again. A field is never deleted.

  • K3. The forms that create and edit an account, a contact and a lead show a Custom fields section with the fields in use, in the order set. A user allowed to manage the record fills them in. The system refuses a value that does not fit its field, and says which field. It refuses:

    • text longer than 1,000 characters, on more than one line, or holding hidden control characters;
    • a number with more than 15 significant digits;
    • a date outside 1900 to 2100;
    • a choice that is not on the list.

    A retired choice stays on the records that already have it, marked as retired, and cannot be chosen for any other record.

  • K4. The account, contact and lead pages show a Custom fields card to everyone who can see the record, with each field’s value and a dash where none is entered. Where no fields are in use for that kind of record, no card is shown.

  • K5. Creating, changing, reordering, archiving and restoring a field, and changing a record’s custom-field values, are recorded as in J1.

L. The trade-show capture app

(Added 12 November 2026: planned for Phase 2, moved to Phase 1 and accepted with it.)

As in Section E, every AI result here is a draft for a person to review, and nothing it produces is acted on until a person approves it.

  • L1. The capture app opens at its own web address, on the phones, tablets and browsers named under “Screens” above, and can be added to a phone’s home screen. Only a signed-in user of the CRM whose role has the permission Use the capture app can use it; anyone else is told so and can only sign out.
  • L2. A user photographs one business card or scans the QR code on one visitor’s badge, may add a short note, sends it, and can start the next capture at once.
  • L3. The AI reads the details on the card, such as the person’s name, job title, company, country, email address and phone number, and the user checks and corrects them. The lead then waits in the app until someone reviews it. Converting it puts it in the CRM’s leads, with the trade show shown as its source, owned by the person who converted it. Rejecting it keeps it in the app only, with an optional reason and note. A rejected lead can be moved back for review.
  • L4. While scanning, the app tells the user whether the organisation or the person is already a customer, and how often Empire deals with them. When the check cannot run, the app says the check is still to come.
  • L5. Each captured lead is researched and given a priority with its reason, as in Section E. The app tells the sales team inside the app, in its notifications list and with an on-screen notice. The app sends no email.
  • L6. If a capture’s upload fails, for example with no connection at the venue, the capture is kept on the phone and shown as not sent. It is sent again when the app is open with a connection.
  • L7. Each capture, and the lead it creates, is recorded as in J1.
  • L8. Before a show, a user sets up the show, with its first and last day if known. They load its exhibitor list from a CSV or Excel file, and check which column holds the company name, the stand number and the other details. Rows with no company name are left out. A user can also add, edit and archive exhibitors by hand.
  • L9. The AI researches every exhibitor on the show’s list and ranks it, with the reason it is worth a visit, as in Section E. On the day, a user writes visit notes for each stand and marks it visited, and the list can be searched, filtered and sorted.

At the capture app’s progress review, both parties may choose to release capture and the feed into the CRM first (Project Timeline, “The capture app”). If they do, the rest of Section L is accepted with Phase 1. L5 and L9 are accepted later, during the settling-in period, once the research, priority and notifications are finished.

M. File attachments on accounts, contacts and leads

(Added 12 November 2026: planned for Phase 2, built early, shown at the progress meeting of 10 November, and accepted with Phase 1.)

  • M1. The account, contact and lead pages each have an Attachments card listing the record’s files, newest first, with each file’s name, who added it, when, and its size. Anyone who can see the record can download a file, which saves under its own name without leaving the page.
  • M2. A user allowed to manage the record adds files by choosing or dropping them, up to 10 at a time, up to 25 MB each. The types allowed are PDF, JPEG, PNG, and Excel, Word or PowerPoint in their current formats (.xlsx, .docx, .pptx). Any other type, older .xls and .doc files and CSV files included, or a larger file, is refused with the reason. A user who can only see the record cannot add or delete files.
  • M3. A user allowed to manage the record deletes a file after confirming it in place, on the file’s own row.
  • M4. Adding and deleting a file are recorded as in J1.

N. Saved views on the account, contact and lead lists

(Added 18 November 2026: planned for Phase 2, built early, and accepted with Phase 1.)

A view is a saved set of a list’s filters, sort order and columns, with a name.

  • N1. The account, contact and lead lists each show a row of views above the list, starting with the default view. A user sets the filters, sort order and columns, chooses Save View, and gives the view a name. Choosing a view opens the list as it was saved. A view still opens the same way from a link or after reloading the page. When the views do not fit on one line, the rest are under More Views.
  • N2. A view is personal at first. Its owner can share it with everyone who can see that list. A shared view shows Shared by and its owner’s name. Only the owner can change or delete it. If the owner has been deactivated, an administrator who manages users can delete it.
  • N3. A shared view never shows anyone a record they cannot otherwise see (Section B). Two people opening the same view each see only their own matching records.
  • N4. When a user changes an open view’s filters, its tab shows Changed. The owner can choose Save Changes. Anyone can choose Save as New View, or Reset to go back to the view as saved.
  • N5. The Columns menu hides, shows and reorders a list’s columns. The name column always stays. Reset to Default Columns brings back the usual columns. With the default view open, the user’s choice is kept for next time, on any computer they sign in from. With a saved view open, a column change marks the view Changed (N4).
  • N6. The account list filters on several countries and several tags at once, and the lead list on several sources and several owners. The contact list filters on the account’s country, region and customer type, and on tags. People who see contacts with no account (C7) can also filter on those.
  • N7. Creating, changing and deleting a view, and saving a column choice, are recorded as in J1.

Not part of Phase 1

These arrive in Phase 2, or are outside V1 (Product Requirements, Sections 3 and 4). They are not tested in the Phase 1 round:

  • deals, the two pipelines and their Kanban boards, pipeline settings, and turning a lead into a deal; follow-ups on deals; the dashboard;
  • samples, quotes and the margin approval, product briefs, the certification check, export-document checklists;
  • alerts for deals idle in a stage, ageing quotes and dormant accounts (the Dormant badge in C1 is Phase 1);
  • quote assistance, the morning briefing, outreach sequences, and the AI provider comparison;
  • calendar and contact sync, list views and saved views on deals, quotes, samples and buying standards (Section N covers accounts, contacts and leads), bulk actions other than changing owner, file attachments on deals, quotes, samples and product briefs, custom fields on deals, quotes, buying standards and samples, list columns and filters on custom fields, spreadsheet import and export, the ERP handoff document;
  • bulk email to a saved list of contacts: newsletters, product promotions and trade-fair invitations, with a summary for each send (added to Phase 2 on 9 October 2026). Sending the week’s prices to every customer at once is in Phase 1 (G9);
  • the administrator’s on/off switch for each AI feature, and the monthly AI spending ceiling (proposal Section A.3.2), which come in a later phase. In Phase 1, the AI is turned on or off in the system’s configuration (E7);
  • blocking email addresses and domains so their email is never linked (moved to Phase 2 on 11 November 2026);
  • the final migration run after the data freeze;
  • past orders on the account (unless Empire Teas chooses the stop-gap in Questions for Empire Teas, Q17), and WhatsApp.

Change history

Older changes to this draft, newest first. The list above already includes each of them.

  • 16 November 2026: the weekly-prices checks (Section G) now match the built CRM. G5b (correcting a price in force) and G5c (adding, correcting and deleting an auction sale) are added, and G6 says a standard with no price in the new sale shows No current price and can be carried forward.
  • 12 November 2026 (fifth change that day): the capture app also plans each show before it starts, with the show’s exhibitors researched and ranked, and visit notes for each stand (L8, L9).
  • 12 November 2026 (fourth change that day): in the capture app, cards and badges are captured one at a time, using the app needs its own permission, and a captured lead reaches the CRM’s leads only when someone converts it (L1, L2, L3).
  • 12 November 2026 (third): the capture app tells the sales team about each researched lead inside the app instead of by email. It sends no email (L5).
  • 12 November 2026 (second): two additions, after the progress meeting of 10 November: a reminder for a customer email nobody has replied to (F7); and file attachments on accounts, contacts and leads, which were planned for Phase 2, are built and are accepted with Phase 1 (Section M). Attachments on deals, quotes, samples and product briefs stay in Phase 2.
  • 12 November 2026 (first): the trade-show capture app was planned for Phase 2 and now arrives in Phase 1, as agreed at the progress meeting of 10 November, so it is added to Phase 1 and accepted with it (Section L).
  • 11 November 2026: custom fields on accounts, contacts and leads were planned for Phase 2 and are now built, so they are added to Phase 1 and accepted with it (Section K). Custom fields on deals, quotes, buying standards and samples stay in Phase 2.
  • 8 October 2026: the draft was ready to issue. It was due to Empire Teas by Mon 12 October, when Phase 1 began.

Generated from .forge/client/phase-1-acceptance-criteria.md by .claude/lib/render-docs-html.js. Markdown is canonical.