A COMPLETE USE CASE · ABOUT 11 MINUTES
Prepare my product launch
“My product is ready for people to discover. What do I prepare first?”
Keep Sprout’s interview evidence, positioning and launch assets connected. A launch is a chance to help the right people reach a first useful result—not a promise of a leaderboard rank.
SaaS founders launching a product or a meaningful update.
Current product facts, audience evidence, release changes and actual media.
A reviewed launch brief, draft kit and a practical launch-day plan.
What needs to be set up in the real app?
A SaaS workspace with Growth access and an owner/admin reviewer. Real measurement needs customer-side event setup.
Tools along the way: Project hub → Growth → Launches → Studio (optional)
Where does your story start?
Choose the useful part. Earlier sample outputs are supplied, not credited as your work.
Follow the whole fictional story, from the first decision to the final result.
0 of 5 decisions kept on this path. All practice is fictional and local.
THE GROWER HELPS HERE
Start with what you actually know
The research notebook has three sample interviews and a list of real product capabilities. Choose the evidence that can support a launch message.
Sprout’s interview notes
Sprout is a fictional product for organizing customer interviews. Three sample interviewees said they lose track of repeated requests.
- Observed: scattered notes make themes difficult to compare
- Product fact: themes link back to source quotes
- Unknown: whether this improves retention
THE WHOLE RECIPE, WHENEVER YOU NEED IT
Take the path into Seerist.
Use the same order with your actual facts and permissions. The example outputs here are fictional teaching material.
Start with what you actually know
Project hub → Knowledge; Launches → Validate
Keep interview observations distinct from product facts and hoped-for outcomes. Preserve the source of each claim.
Open the reference lesson →Write one clear positioning promise
Growth → Launches → Brief
Review audience, problem, differentiator, release changes and activation event in the saved brief before generating assets.
Open the reference lesson →Assemble the kit around that brief
Growth → Launches → Generate kit in background
Keep assets version-bound to the approved brief. Media capture/hosting and platform submission use the maker’s own tools and accounts.
Open the reference lesson →Catch a change before it spreads
Growth → Launches → Brief / Assets
Changing product facts invalidates the brief’s approval and makes affected assets stale. The sample kit is revised to describe organizing source-linked themes only.
Open the reference lesson →Put people and checks on the runbook
Launches → Runbook / Launch day
Use the runbook to organize real work. Imported calendar reminders need a calendar import, and launch measurements need actual product instrumentation.
Open the reference lesson →
Source-based guidance checked against Seerist app a365066 · September 13, 2026. Each linked reference lesson identifies its product sources. Guide decisions are learning exercises, not proof of live provider behavior or business outcomes.