Bid and Procurement Opportunity Discovery Assistant

What Problem Does It Solve?

Bidding and public procurement information is scattered across various platforms, making manual lead screening akin to finding a needle in a haystack. Sales personnel need to quickly locate procurement demands matching their products while avoiding ineffective follow-ups. The core purpose of the CRM客户商机发现助手 is to transform vast amounts of public bidding information into structured, analyzable sales leads, addressing the gap from information acquisition to initial lead qualification.

How Does the Skill Work?

The skill implements opportunity discovery through a clear automated workflow:

1. Input Parsing & Keyword Generation: After a user inputs a product name or service description, the skill generates synonyms and procurement-related expressions (e.g., "procurement," "tender," "consultation"), explicitly noting these as search expansion terms, not core requirements.
2. Data Acquisition & Fact Extraction:
   • Calls the /bid/searchProjectApi interface to retrieve project lists based on conditions like time, region, and industry. It queries the last 30 days by default.
   • For highly matching projects, it further calls the /bid/getZTBStructreDetail interface to fetch structured details like project number, budget amount, deadline, and party A information.
   • For specific target companies, it uses the company profile (/bid/companyProfileSummary) and contact number (/bid/companyProfileContacts) interfaces to supplement corporate background information.
3. Transparent Lead Scoring: Based on the factual data obtained, it scores leads using a 100-point system with weighted criteria: demand match (35 pts), procurement stage (20 pts), timeliness (15 pts), amount match (10 pts), regional match (10 pts), and contact information completeness (10 pts). The score is an analytical result, not a raw API field.
4. Structured Output: Generates a lead list categorized into "Priority Follow-up," "Watch," and "Low Match" tiers. Each lead includes the purchasing unit, project name, budget/amount, contact person and phone (with source noted), and a specific suggested next action. It concludes with a list of "Items Requiring Manual Verification."

Scope and Considerations

• Data Dependency: The skill relies entirely on public bidding interface data and cannot cover non-public procurement or internal tender information.
• API Key & Security: The key must be obtained from the environment variable BBIAO_API_KEY or the user. The key must never be exposed in logs, error messages, or the full request URL. User-provided keys should be securely stored to avoid repeated prompts.
• Interface Limits: The search list is capped at 50 items per page. The skill is designed to limit calls to the detail and company profile interfaces to prevent unbounded API requests.
• Information Verification: All output contact information, budget amounts, and procurement stages are results of data collection or analysis and may become outdated. Contact phone numbers, sourced from two different contexts (project details vs. company profile), require careful verification of their current validity.
• Applicable Scenarios: Suitable for proactive sales lead mining based on public bidding data, not for handling private procurement channels or highly confidential tender projects.