Review requests
Review requests ask each Customer for a review at a delivered outcome, on the venue the Startup most needs, and show consented reviews.
Review requests ask each Customer for a Review at a delivered outcome, on the venue the Startup most needs, and show consented Reviews.
Ratings
| Dimension | Rating | Reads |
|---|---|---|
| Scalability | 3 of 5 | medium: higher grows further with spend or automation |
| Cost | 1 of 5 | very low: lower costs less per Customer |
| Latency | 3 of 5 | medium: lower answers sooner |
Budget
| Property | Value |
|---|---|
| Tier | $0 |
| Minimum effective budget | $0 a month |
How it runs
The Studio rolls it out to one cohort at a time: every Live Startup with ten or more Customers who reached a delivered outcome.
Processes
Runs as Retention, accountable to the Marketing Team.
Fits
| Fits | Value |
|---|---|
| Family | demand |
| Shelf | Compound: builds an engine that keeps growing (Grow) |
| Moves | Organic share |
| Motions | b2b, b2c, b2d |
| Venues | G2, Capterra, Trustpilot, Google Business Profile, App Store, Google Play, Shopify App Store, Chrome Web Store |
| States | Live, Repeatable, Scale |
Loop
| Step | Value |
|---|---|
| Hypothesis | Asking once at a delivered outcome, on the one venue the ICP reads, earns more published reviews than asking at signup. |
| Measure | Organic share over 90d, at least 50 observations |
| Learn | The learn step reads the Readout, records Evidence and a Decision, and drafts the next Variant. |
Example
A scheduling app asks each Customer for a Review the day their 100th booking completes. It asks only on the venue its buyers read, and 38 of 120 asked publish one in a month.