Bid Win-Rate Analyzer

Problem

Bid/no-bid decisions often hinge on concrete questions: whether the buyer prefers incumbent suppliers, which competitors are likely to appear, how well your qualifications and performance match, and where the price should fall. Tender notices alone rarely support an explainable win-probability judgment, so teams can mistake subjective impressions for conclusions.

How it works

The skill runs a project-specific analysis against ZLBX tender data. It resolves the project budget, scope, qualification requirements, and deadline; profiles the buyer's procurement cadence and supplier landscape; predicts likely bidders and checks their award history; aggregates comparable project values and historical unit prices to form a pricing band; and, when a company name is provided, assesses fit for that company. Reports place the conclusion first, attach data support to each judgment, and label missing evidence as data gaps rather than asserting inference as fact. Full reports typically use 12-25 API calls, while quick screening uses 5-8 calls.

Boundaries

It is intended for a specific tender requiring a go/no-go recommendation, not as a general bid-search tool. Language about real organizations must remain factual and evidence-based, avoiding allegations. The workflow depends on an external API and account credits, so expected consumption should be confirmed before analysis; if the user only needs announcements or company records, a lighter data-query skill is more appropriate.