Research methodology
Product launch measurement methodology
How Dough will measure time to storefront, sampling, manufacturing, and launch outcomes without publishing unsupported numbers.
Direct answer
Dough does not yet publish a statistically reliable benchmark dataset. This page defines the metrics, methodology, and release threshold for future reports so unavailable data is never presented as fact.
What is available today
Dough can document the workflow its product supports: a founder develops a product concept, selects or refines a draft, creates a storefront, validates demand, and moves through sourcing or manufacturing.
Aggregate outcome metrics are not published here because the current public evidence set has not been reviewed for sample quality, consent, cohort boundaries, or survivorship bias.
Current status: methodology published, benchmark values unavailable.
Metrics planned for a first report
Each metric needs a defined start event, end event, eligible cohort, and explicit missing-data treatment.
- Time from product creation to a ready storefront
- Time from custom-product approval to first sample order
- Sample revision count before production approval
- Share of launches that receive a first order or pre-order
- Time from paid order to supplier submission and shipment
- Observed unit-cost and selling-price ranges by product category
Publication standard
A report should disclose the analysis window, cohort definition, exclusions, sample size, median, distribution, and the date each tracked event became available. Dough should separate catalog products from custom products because their sourcing and manufacturing paths differ.
Customer-level outcomes require permission or aggregation that prevents re-identification. Revenue, conversion, and fulfillment claims should link to a reproducible query or another approved evidence record.
- No averages without a distribution or sample size
- No comparison across events introduced on different dates
- No claim that a missing event means an outcome did not occur
- No customer quote, revenue figure, or timeline without approval
How to cite a future release
Future releases should include a stable publication date, version, downloadable table, data dictionary, and correction log. Every chart should state whether it is descriptive or supports a causal claim.