What should an explainable match report look like?
This is a public demonstration skeleton. Real projects replace the placeholders with specific companies, real evidence sources, and reviewable timestamps.
The sample demonstrates output structure, not an actual business conclusion. A formal report must state sources, confidence, and unverifiable parts.
Company A-B Match Report Sample
Company A: regional equipment manufacturer | Target Company B: new-energy industry-chain customers and partners | Version: demo skeleton
Match reasons
- Company A's product capabilities overlap with the project direction of the target companies.
- The target region has recent policy, project, and industry-chain expansion signals.
- Similar historical cooperation paths show that this relationship type is worth validating.
Evidence trail
Confidence and risk
Next actions
- Validate B-01's project stage and procurement roles first.
- Use regional industry-chain nodes to find an entry point into B-02.
- Compare B-03 against similar customer cases to test whether substitution space is real.
Output format
Formal output can be a briefing, spreadsheet, CRM lead, sales task, graph node, or monitoring list. The key is that every recommendation carries a reason, evidence, confidence, and action.
To turn the sample into a real project, provide these inputs.
Real matching does not start from a generic AI promise. It starts from your business goal, current information, and a verifiable output contract.
Company A profile
Industry, products, capabilities, region, customer type, reference cases, excluded scope, and current goal.
Target Company B scope
Industry, region, size, role, relationship type, exclusion rules, and priority.
Success criteria
Whether the deliverable should be a list, opportunity explanation, sales action, monitoring workflow, or internal decision material.