Bid Award Query and Competitive Analysis

Problem

In bidding and procurement due diligence, a company's award history is only a starting point. Raw records show where and how much it won, but do not explain its core business lines, customer structure, competitors, or public risk signals. When comparing two companies, manually reviewing announcements and news can miss shared customers, regional overlap, and repeated bidding patterns.

How It Works

The skill takes a company name as input and queries Zhiliao Bid Intelligence data, supplemented by WebSearch for public official-site, news, litigation, and administrative penalty information. It first resolves the exact entity with search_company to avoid name collisions, then builds a profile using get_company_profile and get_company_business_keywords. It maps customer and supplier relationships with get_company_partners, summarizes recent award volume, value, regional distribution, and flagship projects using search_bids, query_bids_advanced, and aggregate_bids_advanced, and identifies competitors through find_competitors based on bidding overlap and shared customers.

Reports lead with conclusions, then evidence, and can export a shareable HTML file. In dual-company mode, it runs core profiles for both companies and focuses on competitive overlap. Contacts are queried only on request and displayed according to account permissions.

Boundaries

This skill is best for company-level diligence, competitor analysis, and initial risk screening. If the input is a specific tender, bid document, or announcement link, a bid-decision tool is more appropriate. If the goal is lead generation by industry, product, or region, an opportunity radar tool is a better fit. All amounts, counts, and company names should be traceable to API results; missing data should be marked as a data gap rather than interpreted as absence.