How a Crowdproof study works, and where to doubt it.
Crowdproof produces simulated evidence. This page is the contract for what that evidence is, how it is made, and what it can and cannot tell you. The short version: numbers come with ranges, artifacts come with provenance, and a wide range changes how a decision is executed rather than preventing a decision.
methodology v2.3 · changelog publicEvery artifact is labeled with what it is.
Nothing in Crowdproof pretends to be a human. Provenance labels are printed on each artifact rather than hidden in a footnote.
A million agents, seeded from the census.
The panel is synthetic, but its shape is not invented. Agents are seeded from US census data (ACS-2024) with occupation, income, and media diet, so the mix of people your launch meets resembles the population it would meet in the world.
Facts and simulations stay separate.
Crowdproof combines cited public market evidence with modeled audience research, structured simulated interviews, and scenario analysis. Reports label each evidence class so a simulation cannot masquerade as observed customer behavior.
Stratified, analyzed, decision-ready.
Synthetic interviews are distributed across the available audience segments so loud cohorts do not drown out quiet ones. The report presents cross-interview themes, tensions, and decision implications instead of burying the user in raw transcripts.
The range is the result.
Propagation scenarios execute as multiple stochastic cascades. We report the P10–P90 outcome spread rather than hiding uncertainty behind one point estimate.
reported: 18.0% (P10 14.2 – P90 22.4)
Backtested against launches with known outcomes.
The model earns trust by being checked, not by being confident. We backtest against real launches and campaigns whose outcomes are known, and publish the calibration report quarterly.
The honest edges of the instrument.
Your unreleased work stays yours.
PRDs and research questions run in an isolated environment and are never used to train models. You can delete them and every derived artifact at any time.
questions about the method · methodology v2.3 · changelog public