Wenhui Daily reporting in October 2026 described Yuan Yuan's ONEPILOT as a three-person team working on startup-resource matching. The headcount is limited to that reporting date and does not establish financial results or eligibility.
Make a recommendation open to correction
A hypothetical event recommendation should display location, venture stage, document requirements and information date. Users can then identify incorrect fields for correction. A high match score alone does not explain suitability.
An unsuitable result is useful too
Do not keep recommending plainly inapplicable resources just to generate clicks. Distinguish unsuitable, awaiting confirmation and meeting preliminary conditions, and identify questions the user should ask. Policies, competitions and funders have different decisions; matching does not promise approval or investment.
Improve categories through follow-up
Record whether users did not make contact, could not reach anyone or failed document requirements. These distinctions reveal actual obstacles. Retain contact information only with appropriate consent and authority, avoiding an unauthorized directory of people. These are our suggestions, not verified current ONEPILOT features.
Further reading: OPC Founders.