Verified success report
A verified success report is a moderated, publicly visible record that a specific startup's solution passed a specific pilot against a specific company's success criteria. Verification is the trust layer that turns OpenClienting from a directory of problems into a citation-ready knowledge base of proven outcomes.
What verification means
- Every success report is attributed to the company that ran the pilot — no anonymous testimonials.
- A moderator reviews the evidence before the report is marked verified and becomes visible.
- Verified reports follow the solution across the platform — future buyers see who else piloted it successfully.
How verification works in practice
Every success report on OpenClienting goes through the same moderation lifecycle as other content, but with an extra evidence-review step. The key moments:
- Author submission — the company that ran the pilot files a report with the KPI results, pilot duration, and the success criteria that were met.
- Moderator review — a platform moderator reviews the submitted evidence against the original problem's success criteria before marking the report verified.
- Public visibility — once verified, the report is visible on the problem page, on the organization's profile, and on the startup's solution approach page.
- Persistent badge — the verification badge is attached to the startup's solution approach and follows it to future buyers who view the same problem.
Frequently asked questions
Is the company's identity visible on a verified report?
By default, yes — verification implies attribution. The value of the report comes from a real company standing behind the outcome. If the company wants to stay anonymous, the author can mark the report as such, but unattributed reports carry less weight and are labeled accordingly.