Empire Teas CRM — the web-search tool for the AI features
Date: 14 October 2026 Meeting: online call, about ten minutes Participants: Kavindu Anthony (Empire Teas); Tharinda Rajapaksha and Dinil Gamage (Altrium), from one meeting room Source: the meeting tool’s transcript and summary, read on 15 October 2026. The transcript does not separate the two Altrium speakers reliably, so who said what on Altrium’s side is approximate.
Why this file exists: it is the dated record of Empire hearing the search-provider comparison (SP-ARCH-004,
.forge/design/ai/lead-research-source-options.md§11) and asking for the recommendation in writing. The provider decision itself waits on Kavindu’s answer to that email.
1. The web-search tool
Tharinda explained that the AI features (lead research, F11-c, and the capture app’s research, F36-c) need a web-search tool besides the AI model on Bedrock: the search finds current public information about a company, and Claude reads it and writes the research. The plan had been AWS’s own tool, AgentCore Web Search, and the team had also tested three outside tools.
- Kavindu’s preference was to stay on AWS, because Empire has just arranged the AWS account and its billing, and another vendor means another bill and some financial arrangements on Empire’s side.
- Dinil showed the stage-2 results: AgentCore found the right company least often, and Exa most often. Tharinda noted that the prototype Thilina demonstrated used Tavily, because AgentCore was not available then.
- Kavindu asked whether Claude can search the web itself. Dinil answered that Claude does the reading and ranking, but has no current details about companies, so a search tool has to fetch them first. (Anthropic’s own search tool is not offered on Bedrock — §2 of the design doc.)
- Price, as stated in the meeting: Exa and AgentCore both cost $7 per 1,000 searches; Tavily and Serper were described as more expensive. (Checked afterwards: Tavily is $8 per 1,000; Serper is $1 per 1,000 but sold only in $50 packs that expire after six months, so it costs the most at Empire’s volume — design doc §11.)
- The drawback of Exa: a separate Exa account, with a payment card on it.
- Volume, as stated in the meeting: normally under 1,000 searches a month, perhaps $10 a month at most; the first month may exceed 1,000 when existing leads are imported in bulk. (Checked afterwards: about 692 open leads are in the Pipedrive export F4-b migrates, and research may take a second search per lead for the person, PRD Rev 56 — design doc Rev 7.)
- Kavindu asked for the findings and the recommendation by email, with Sajeev De Silva (Empire director; “Saji” in the transcript) included. Tharinda said Rukshan had suggested the same.
2. CRM03’s mailbox
Tharinda said CRM05’s mail works again but CRM03’s has stopped working, and asked Kavindu to look into it, not urgently. Kavindu agreed. (.forge/owed.md has the row: on 14 October mail to crm03@empire.lk bounced as an unknown address.)
3. Friday’s progress meeting
A progress-update meeting with Empire is set for Friday 16 October, which Rukshan asked for. Kavindu will attend, and will check with Sajeev De Silva whether others from Empire will join.
Actions
| Action | Owner | Recorded in |
|---|---|---|
| Email Kavindu the comparison and the recommendation, addressed to Kavindu and Sajeev De Silva | Tharinda | .forge/owed.md (the search-provider row) |
| Look into the CRM03 mailbox | Kavindu Anthony | .forge/owed.md (the crm03@empire.lk row) |
| Check with Sajeev De Silva who else attends Friday’s meeting | Kavindu Anthony | this note |
| Attend Friday’s progress meeting | Kavindu Anthony | this note |