Disappointment survey segment before scaling outreach
Ask early users how disappointed they would be if the product went away, then build outreach and roadmap decisions around the people who would genuinely miss it.
Why this can grow a startup
A large early list can lie to a founder. Polite interest, curiosity, and free-tool usage all look like traction until the team asks what would actually hurt to lose. OpenPhone’s first-1,000-customer writeup points to the “how disappointed would you be” question as a way to understand fit. The growth move is to use that answer operationally: interview the “very disappointed” segment, mine their words for landing-page copy, and aim outreach at lookalike buyers before spending more time on the lukewarm middle.
Source-backed example
OpenPhone says it asked customers how disappointed they would be if they could no longer use OpenPhone as part of its early product-market-fit learning.
Source-reported evidence
Source: OpenPhone: How we got our first 1,000 customers · Browse OpenPhone: How we got our first 1,000 customers tactics
The survey question separates users who would be very disappointed from users who are only mildly interested.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Research, Lifecycle, Positioning is relevant to product-market fit, customer research, first customers and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Research and Lifecycle, using evidence from OpenPhone: How we got our first 1,000 customers as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Connect activation, customer value, retention, and referral into one measurable loop.
SOURCE HUB
More tactics from OpenPhone: How we got our first 1,000 customers
Explore related GrowthDex examples and evidence connected to OpenPhone: How we got our first 1,000 customers.
Open OpenPhone: How we got our first 1,000 customers source hub