source: .forge/discovery/research/initial-findings.md · generated — edit the markdown, not this file

Initial Findings — Empire Teas CRM + AI Discovery

Date: 2026-06-17
Client/prospect: Empire Teas Pvt Ltd
Prepared for: Internal discovery / future proposal work
Status: Early discovery notes; validate with client before treating as fact.


1. Executive summary

Empire Teas is a major Sri Lankan tea manufacturer/exporter with private-label, bulk tea, branded product, and Kenya-linked operations. They are migrating to a new ERP, so our opportunity should not be positioned as ERP implementation or ERP replacement.

The strongest entry point is CRM + workflow automation + AI-assisted productivity around sales, private-label order development, customer communication, sample/quote follow-up, export coordination, and management visibility.

They currently use Pipedrive CRM and are open to replacing it. This is important: Pipedrive gives us a useful reference point for what they have tried, but the proposal should not be limited to optimizing Pipedrive. We should propose a better-fit CRM/workflow platform tailored to their export/private-label process, with AI embedded into specific productivity workflows.

Recommended positioning:

“Since you are already migrating ERP, we can help build the productivity layer around it: CRM discipline, workflow automation, document intelligence, and AI assistants that reduce manual coordination while ERP remains the transaction backbone.”


2. What we know about Empire Teas

Updated 2026-06-30 from empireteas.com (direct website visit).

2.1 Business profile

  • Full name: Empire Teas (Pvt) Ltd
  • Founded: ~2000 (approximately 25 years in operation as of 2026)
  • Registered address: 190/1 Siri Sumana Mawatha, Kelanimulla, Angoda, Sri Lanka
  • Leadership: Third-generation family business. Founding lineage: Thurson de Silva (founder/planter) → Hemasiri de Silva → Lushantha de Silva (current Tea Master and leader). Lushantha’s own description: ”I was born into tea, but Empire was born from a dream — to blend heritage with passion & hope, and deliver the soul of Sri Lanka to the world.”
  • Scale: Among Sri Lanka’s top five tea exporters. Exports 14 million kg/year to 70+ countries. Estimated global impact: ~7 billion cups of tea.
  • Key markets (confirmed): Turkey, Russia, Ukraine, Guinea — plus 65+ others.
  • Awards: 2024/25 Presidential Export Award — Merit category (Sri Lanka’s top national export recognition).
  • Phone: (+94) 011-2549001 | Email: info@empire.lk

2.2 International offices

Empire Teas operates beyond Sri Lanka. Confirmed offices/operations from website:

  • Sri Lanka — HQ in Angoda (Colombo suburb)
  • Kenya — launched 2017; sources African CTC tea for Akina brand
  • Empire Netherlands — European hub
  • Empire Shanghai — China/Asia hub
  • Empire Spain

2.3 Product and service areas

Two core commercial lines:

  1. Bulk tea — raw made tea sold by weight (kg/MT) to importers, blenders, and brands who process or rebrand it. Highest volume.
  2. Private label — Empire Teas manufactures tea under the buyer’s own brand. Handles sourcing, blending, packaging, compliance, and delivery of shelf-ready product. Higher complexity and margin.

Supporting capabilities: Tea sourcing and tasting, blend development and flavour innovation, custom packaging design, export logistics, international customer servicing.

Own brands (4):

Brand Origin Positioning
Thurson Teas Ceylon Heritage, legacy, classic elegance — named after founder Thurson de Silva
Hyson Teas Ceylon Modern connoisseur — tradition meets contemporary
Akina Teas African (Kenya) Full-bodied, women’s empowerment values, social purpose
Ceylon Wild Harvest Ceylon Organic spices (not tea) — wild-harvested, natural

Lifestyle brand: Tea Avenue — a modern café/lifestyle brand connected to the group.

Important distinction on Ceylon vs Kenya: Tea from the Kenya operation cannot be labelled as Ceylon Tea (Sri Lanka Tea Board rules require 100% Sri Lankan origin). Akina is deliberately positioned as a separate African-origin brand to handle this correctly.

2.4 Certifications

Empire Teas holds an unusually comprehensive certification stack covering all major global markets:

Certification Market relevance
Lion Logo (SLTB) Ceylon Tea authenticity — required for Ceylon Tea branding globally
ISO 9001:2025 General quality management
FSSC 22000 Food safety — EU, global retailers
BRCGS UK, EU supermarket supply chains
IFS Food Germany, France retail
GMP (SLTB-issued) Iran exports specifically
SMETA / Sedex EU, UK ethical sourcing requirements
EU Organic European Union organic claims
USDA NOP Organic United States organic claims
JAS Japan organic/quality standard
Halal Middle East, Malaysia, Indonesia
Kosher USA (Jewish market), Israel
Rainforest Alliance EU, North America premium buyers
Fairtrade UK, Europe, North America
FDA (facility registration) United States — all food exports

Important distinction: IFS Food certification is different from IFS ERP software. Empire Tea Kenya historically implemented IFS Applications ERP. The IFS here refers to the food safety certification, not the ERP.


3. Current situation from our discussion

  • Empire Teas is migrating to a new ERP.
  • We are not expected to implement or replace the ERP.
  • They liked the idea of a proper CRM.
  • They currently use Pipedrive CRM.
  • They are willing to replace Pipedrive if there is a better-fit solution.
  • They have 200+ leads in Pipedrive that have not been reviewed, which indicates a concrete lead management/productivity gap and a strong AI workflow entry point.
  • Pipedrive replacement must include migration of existing leads, contacts, organizations, deal history, notes, activities, and any useful custom fields into the new CRM.
  • Our opportunity is likely to improve productivity by proposing a tailored CRM/workflow platform with embedded AI assistance, not just by configuring another generic CRM.

Working hypothesis

Their ERP migration will focus on core operational transactions: inventory, production, procurement, finance, sales orders, warehouse, etc. But CRM and front-office workflows may remain under-optimized.

This creates a natural opportunity:

Customer / lead / inquiry / email / trade fair
        ↓
CRM + workflow automation + AI productivity layer
        ↓
ERP for confirmed transactional operations
        ↓
Dashboards, alerts, documents, customer communication

4. Why CRM aligns with our thought process

CRM is the right wedge because it is:

  1. Close to revenue — owners understand missed follow-ups, slower quotes, and poor customer visibility.
  2. Lower risk than ERP — can improve productivity without disrupting finance/inventory/manufacturing.
  3. A natural AI entry point — sales emails, customer briefs, quote notes, document requests, and follow-ups are text-heavy and repetitive.
  4. Measurable — response time, follow-up completion, quote turnaround, sample request SLA, conversion by stage.
  5. Integratable — Pipedrive supports API/webhooks/marketplace integrations.
  6. Expandable — once CRM discipline improves, we can add AI workflows for documents, customer support, export coordination, and management reporting.

5. Pipedrive CRM notes

5.1 High-level fit

Pipedrive is a sales-focused CRM built around activity-based selling and visual pipelines. It is generally good for SMB/mid-market sales teams that need:

  • Deal pipelines.
  • Activities and follow-ups.
  • Contacts and organizations.
  • Email sync and communication history.
  • Sales reporting.
  • Workflow automation.
  • Marketplace integrations.
  • API/webhooks for custom extensions.

This fits an export/private-label sales process if configured well.

5.2 Useful Pipedrive capabilities for Empire Teas

Relevant capabilities from Pipedrive’s public product/API docs:

  • Custom pipelines and stages.
  • Leads, deals, people, organizations, activities, projects.
  • Workflow automations with triggers/actions.
  • Date-based triggers.
  • Email sync and automated email actions.
  • Notes and activity creation.
  • Custom fields.
  • Reports and dashboards.
  • API access on every plan.
  • OAuth 2.0 / API-token based access.
  • Webhooks.
  • Marketplace with 500+ apps/integrations.
  • Integrations via Zapier, Slack, Teams, Trello, Asana, Mailchimp, PandaDoc, etc.
  • AI sales assistant, AI email writer/summarizer, and AI reporting features.

5.3 Pipedrive limitations / watch-outs

Items marked [CONFIRMED] are verified from official Pipedrive documentation (researched June 2026). Items marked [VALIDATE WITH CLIENT] require a client meeting to confirm.


[CONFIRMED] Automation features are strictly plan-gated.

Verified from Pipedrive’s official usage-limits and automation-limits documentation.

Plan Active Automations If/Else Conditions Email Sequences
Lite None None None
Growth 50 3 5
Premium 150 10 25
Ultimate 250 20 50

The Lite plan has zero automation access. Empire Teas’ current plan is unknown — must be confirmed in discovery. If they are on Lite, they have no working automations at all, which changes the migration complexity significantly.

Note: Pipedrive rebranded plans in 2025 — Essential → Lite, Advanced → Growth, Professional → Premium, Power/Enterprise → Ultimate.


[CONFIRMED] Automated emails are sent from the individual user’s synced email account — not a shared company address.

Verified from Pipedrive’s troubleshooting-automations documentation.

Pipedrive’s own docs state verbatim: “If the default email account setting is disabled, your email actions in automations will stop working.”

There is no native workaround for sending from a shared address (e.g. sales@empireteas.com). This is a hard structural constraint. If a rep leaves or their email is suspended, all automations tied to them stop dead.


[CONFIRMED] Native Pipedrive AI features are generic with no domain-specific customisation.

Verified from Pipedrive’s pipedrive-ai, sales-assistant, and ai-email-creation documentation (updated June 2026).

The AI email writer offers exactly three customisation options: tone (Professional/Formal/Friendly), length (Short/Standard/Long), and content type. No industry or domain context can be configured. The AI Sales Assistant has no industry-specific configuration options documented anywhere in official sources. Admin must accept AI Beta terms before any user can access the Sales Assistant.

This confirms that Pipedrive’s native AI cannot serve Empire Teas’ domain-specific needs — tea grades, certifications, private label workflows, export documentation. A custom CRM calling Claude directly is the correct approach, not a Pipedrive extension.


[VALIDATE WITH CLIENT] Pipedrive is sales-first — complex sample/quote/artwork/packaging workflows may not fit cleanly.

Cannot be confirmed from documentation alone. Depends on how Empire Teas has configured their instance and what workarounds they have built. Covered by discovery questions Q21–Q24.


[VALIDATE WITH CLIENT] CRM data quality — are custom fields standardised or ad hoc?

Only someone with direct Pipedrive access can confirm this. Covered by discovery question Q12.


[VALIDATE WITH CLIENT] Does management trust the CRM reports?

Internal to Empire Teas. Covered by discovery question Q27.


[VALIDATE WITH CLIENT] ERP integration — system-of-record boundaries need to be defined.

Depends on which ERP Empire Teas is migrating to and whether it has an API. Covered by discovery questions Q38–Q41.

5.4 Likely opportunity with Pipedrive

They are open to replacing Pipedrive, so discovery should treat Pipedrive as the current baseline, not the target platform.

Key questions:

“Which parts of Pipedrive failed for your workflow, and which data/processes must survive migration into the new CRM?”

Replacement implications:

  1. Audit current Pipedrive usage — pipelines, fields, leads, deals, activities, notes, users, automations, reports, integrations.
  2. Recover stale leads — use AI to triage the 200+ unreviewed leads before or during migration.
  3. Migrate useful data — leads, contacts, organizations, deal history, notes, activities, custom fields, source attribution, and ownership.
  4. Clean while migrating — deduplicate, classify, archive spam/irrelevant records, and normalize countries/customer types/product interests.
  5. Design a better-fit replacement CRM — tailored around export/private-label workflows rather than generic sales stages.
  6. Plan ERP handoff — define what moves from CRM to the new ERP when an opportunity becomes a confirmed order.

6. Domain workflow: tea export/private-label CRM

A generic CRM pipeline is not enough. Empire’s CRM should reflect the tea export/private-label journey.

Suggested pipeline stages to validate:

New inquiry / lead
→ qualified buyer
→ product requirement captured
→ sample requested
→ sample prepared / dispatched
→ sample feedback received
→ quote requested
→ quote submitted
→ negotiation
→ order expected / pending confirmation
→ won: handoff to ERP/order processing
→ lost / dormant / nurture

Key CRM entities and fields

Organization / account

  • Company name.
  • Country/region.
  • Customer type: importer, distributor, supermarket, private-label brand, foodservice, wellness brand, etc.
  • Annual potential volume.
  • Certifications required.
  • Preferred packaging formats.
  • Target markets served.
  • Incoterms/payment preferences.
  • Existing/past customer flag.
  • Strategic account flag.

Person/contact

  • Role: owner, buyer, category manager, procurement, QA, logistics, finance.
  • Communication channel.
  • Language/timezone.
  • Decision influence.

Deal/opportunity

  • Product type: black tea, green tea, herbal, flavored, decaf, matcha, private label, bulk, etc.
  • Packaging type: single-chamber, double-chamber, pyramid, loose leaf, tin, gift pack, carton, sachet.
  • Estimated volume.
  • Target price.
  • Currency.
  • Required certifications.
  • Sample status.
  • Quote status.
  • Expected order date.
  • Probability.
  • Competitor/current supplier if known.

Sample request

Could be represented as deal fields, activities, or a linked custom workflow/app:

  • Sample brief.
  • Blend/profile requested.
  • Packaging/sample format.
  • Responsible taster/R&D owner.
  • Dispatch date.
  • Courier/tracking.
  • Feedback received.
  • Next action.

7. AI workflow opportunities

Prioritize AI where there is repetitive text/document work and human review is acceptable.

7.1 AI inquiry capture

Convert unstructured emails/forms/trade fair notes into structured CRM records.

Extract:

  • Buyer/company/country.
  • Product interest.
  • Quantity/volume.
  • Packaging requirements.
  • Certifications.
  • Target price.
  • Timeline.
  • Missing information.

Output:

  • Create/update CRM lead/opportunity in the new CRM.
  • Draft reply.
  • Create follow-up activity.
  • Create sample request task if applicable.

7.1A AI lead triage and Pipedrive backlog recovery

Context:

  • Empire Teas has 200+ leads in Pipedrive that have not been reviewed.

Workflow:

Pipedrive lead export/API
→ AI classifies and summarizes each lead
→ duplicate/spam/irrelevant detection
→ priority score and recommended next action
→ human review queue
→ approved follow-up / conversion to opportunity
→ migration into new CRM

AI output:

  • Priority: P1 high-potential, P2 needs qualification, P3 low intent, P4 irrelevant/spam/duplicate.
  • Buyer/company type.
  • Country/market.
  • Product interest.
  • Missing information.
  • Suggested owner/queue.
  • Draft follow-up.

Migration point:

  • Qualified leads should be migrated into the new CRM with lead source, notes, activities, contact/company links, original Pipedrive IDs, and AI triage metadata.
  • Low-quality records should be archived or placed into nurture rather than blindly migrated.

7.2 AI account briefing

Before a sales call or trade fair meeting, generate:

  • Account summary.
  • Last communication.
  • Open deals.
  • Previous samples/quotes.
  • Complaints/issues.
  • Next recommended action.

7.3 Private-label product brief assistant

Turn customer discussions into an internal product brief:

  • Tea profile.
  • Target market.
  • Packaging.
  • Certifications.
  • Artwork/label requirements.
  • Samples required.
  • Open questions.
  • Internal owners.

7.4 Quote assistant

Human-controlled assistant that:

  • Checks if quote inputs are complete.
  • Finds similar previous quotes/deals.
  • Drafts quote email.
  • Flags missing cost/approval fields.
  • Does not autonomously decide final price.

7.5 Export documentation assistant

Later-stage opportunity:

  • Extract requirements from customer emails, LC/shipping instructions.
  • Generate shipment document checklist.
  • Flag missing/inconsistent fields.
  • Draft emails to customers/freight forwarders.
  • Link documents to CRM/ERP records.

7.6 Customer support / status copilot

Draft answers to repetitive customer questions:

  • Sample status.
  • Quote status.
  • Production/order status.
  • Shipment status.
  • Certificate/document resend requests.

7.7 Knowledge/compliance assistant

Search and answer from controlled internal sources:

  • Certifications.
  • SOPs.
  • Country/customer requirements.
  • Packaging options.
  • Product specs.
  • Export procedures.
  • Audit evidence.

Option A — AI lead triage + Pipedrive-to-new-CRM migration pilot

Best first wedge because they already have 200+ unreviewed leads and are open to replacing Pipedrive.

Scope:

  • Export/API pull of Pipedrive leads, contacts, organizations, notes, activities, and useful custom fields.
  • AI classify and prioritize the 200+ unreviewed leads.
  • Detect duplicates, spam, supplier/job inquiries, and irrelevant records.
  • Create a human review queue with recommended next action and follow-up drafts.
  • Migrate qualified leads into the new CRM data model with original Pipedrive references.
  • Archive or nurture low-quality leads instead of blindly importing everything.

Success metrics:

  • 100% of stale leads classified.
  • High-priority leads surfaced and assigned.
  • Follow-up drafts ready for human approval.
  • Duplicate/spam records removed from migration.
  • Qualified leads migrated cleanly into the new CRM.
  • Responses, meetings, sample requests, or quotes generated from recovered leads.

Option B — New CRM foundation + AI sales assistant

Best if owner interest is broader CRM replacement and revenue productivity.

Scope:

  • Audit current Pipedrive setup.
  • Redesign pipelines/stages/fields for export/private-label workflow.
  • Create required activities and follow-up rules.
  • Add dashboards for pipeline/sample/quote visibility.
  • Add AI inquiry summarization and follow-up draft workflow.

Success metrics:

  • Faster inquiry response time.
  • Fewer missed follow-ups.
  • Better visibility into sample/quote pipeline.
  • Reduced manual CRM data entry.

Option C — Private-label sample/quote workflow

Scope:

  • Structured product brief workflow.
  • Sample request tracking.
  • Quote readiness checklist.
  • AI-generated internal briefs and customer reply drafts.

Success metrics:

  • Faster sample turnaround.
  • Fewer handoff misses between sales/R&D/packaging.
  • Clearer accountability.

Option D — Export document/checklist assistant

Scope:

  • Document checklist by customer/country/shipment type.
  • AI extraction from email/shipping instructions.
  • Missing document alerts.
  • Draft forwarding/customer emails.

Success metrics:

  • Reduced document errors.
  • Faster shipment readiness.
  • Less manual chasing.

9. Discovery questions for next meeting

Current Pipedrive usage and migration

  1. How long have they used Pipedrive?
  2. How many active users?
  3. Which teams use it: sales only, export, management, customer service?
  4. Is email sync enabled?
  5. Are activities used consistently?
  6. Are leads and deals both used? If yes, what is the distinction?
  7. How many pipelines exist today?
  8. What are the current stages?
  9. What custom fields exist?
  10. What reports/dashboards do owners use?
  11. What automations are active?
  12. What integrations are connected?
  13. What data is still tracked in Excel/WhatsApp/email outside CRM?
  14. How many total leads, contacts, organizations, deals, notes, and activities need migration?
  15. Which Pipedrive fields/custom fields are business-critical and must map to the new CRM?
  16. Do they want to migrate all records, or only cleaned/qualified records after AI triage?
  17. Should original Pipedrive IDs and source history be preserved for audit/reference?

CRM pain

  1. What does Pipedrive not do well for them today?
  2. Are follow-ups being missed?
  3. Is management pipeline visibility good enough?
  4. Can they track sample requests end-to-end?
  5. Can they track quote status and quote aging?
  6. Can they see customer history before a meeting?
  7. Can they identify dormant accounts or reorder opportunities?

ERP integration

  1. What new ERP are they moving to?
  2. What should happen when a deal is won?
  3. What customer/order data must move from CRM to ERP?
  4. What ERP data should come back to CRM: order status, shipment status, invoice status, documents?
  5. Is there an API/integration plan for the new ERP?

AI readiness

  1. Where are inquiry emails stored?
  2. Are customer communications centralized?
  3. Where are product specs, certifications, and packaging docs stored?
  4. What data can AI safely access?
  5. What outputs require human approval?
  6. What workflow would save the most time in 60–90 days?

10. Proposed discovery deliverables

For a paid discovery / phase 1:

  1. Pipedrive audit and migration inventory.
  2. AI triage/recovery plan for the 200+ unreviewed Pipedrive leads.
  3. CRM pipeline/field redesign proposal.
  4. Sales/private-label workflow map.
  5. Automation opportunities backlog.
  6. AI workflow shortlist with ROI/risk scoring.
  7. ERP integration boundary map.
  8. Pipedrive-to-new-CRM migration approach, including field mapping, deduplication, and qualified-lead import strategy.
  9. 60–90 day pilot proposal.
  10. Prototype of one AI-assisted workflow if access/data allows.

11. Risks and constraints

  • ERP migration may consume internal attention; CRM project must be lightweight and complementary.
  • Pipedrive data quality and migration complexity may be higher than expected; lead triage should clean, dedupe, and classify before import into the new CRM.
  • AI must not make pricing/compliance/export decisions autonomously.
  • Export documentation and compliance outputs must remain human-approved.
  • Need clear system-of-record boundaries between CRM and ERP.
  • Avoid over-customizing Pipedrive before understanding whether current usage is disciplined.
  • Avoid building a parallel mini-ERP inside CRM.

Say this:

“Since you are moving to a new ERP, we should keep ERP as the transaction backbone. Our recommendation is to make Pipedrive or a CRM layer work properly for the front office: leads, private-label inquiries, samples, quotes, customer follow-up, and management visibility. Once that is disciplined, AI becomes practical because it has clean context and clear workflows.”

And this:

“We should not start with broad AI. We should pick one measurable workflow — inquiry capture, sample/quote workflow, or export document checklist — and prove time saved in 60–90 days.”


13. Source notes

Public sources reviewed during initial research:

  • Empire Teas website: About, certifications, private label, bulk tea, brand pages.
  • Sri Lanka EDB exporter profile for Empire Teas.
  • Daily Mirror / Sunday Times coverage of Empire Tea Kenya IFS Applications implementation.
  • Pipedrive public product pages, API page, marketplace page, and automation support docs.

Need client validation for current internal systems, Pipedrive configuration, ERP migration details, team structure, data access, and priority workflow.

Generated from .forge/discovery/research/initial-findings.md by .claude/lib/render-docs-html.js. Markdown is canonical.