Verdict Distribution Aggregate Stats
Every PRISM idea validation and Sentinel claim-verification generates a row in our outcome dataset. Aggregate verdicts, confidence scores, and sector breakdowns are published here — updated continuously.
—
Total engagements
—
Avg confidence score
—
Sectors covered
—
Verifier-signed reports
Verdict Distribution
Across all completed PRISM engagements, how often each verdict is reached. Verdicts are determined by the PRISM scoring model; paid-tier reports are additionally reviewed by a named verifier before delivery.
Verdict definitions: GO — proceed as planned · CONDITIONAL GO — proceed with named conditions · PIVOT — core assumption fails, alternative framing viable · DEFER — insufficient data or premature market timing · KILL — fundamental market or viability failure
Verification Rates
Across all Sentinel engagements, what percentage of founder claims survive independent verification. Broken down by claim type.
Stats will appear once sufficient Sentinel engagements have completed.
Where Founders Come From
What's in This Dataset and What Isn't
What's included
All completed Offer Validation (PRISM) and Release Assurance (Sentinel Method) engagements, from both free tiers (Offer Signal, First Signal) and paid tiers (Build Verdict, Assured Release Pack). Each row captures: verdict, confidence score, sector, geography, stage, and report type. No personal or company-identifying data is stored or published.
What's excluded
Positioning-to-Pipeline Build (QUAD applied directly) engagements are tracked internally but excluded from the public dataset as they often contain client-confidential market mapping. Engagements abandoned before a verdict is reached are excluded. Test/internal engagements are filtered by domain.
How to cite this data
ThriveFinity Outcome Dataset, 2026. Available at: https://www.thrivefinity.uk/dataset. Licensed under CC BY-NC 4.0. For bulk CSV export or academic research access, contact research@thrivefinity.uk.
Update frequency
Stats are updated within minutes of each completed engagement. The "last updated" timestamp reflects the most recent database write. Aggregates are computed by a PostgreSQL view and served via the ThriveFinity API. No manual curation.