Calendly feature-request call to domain sales map
Call feature requesters to learn the high-value workflow, then sell into the domain where that workflow repeats.
Why this can grow a startup
After Calendly’s first user base grew, Tope needed to know where to put sales energy. First 1000 says he used feature requests as a signal: when someone asked for a feature, he tried to get on a call to understand how they used the product. That turns the roadmap queue into a segmentation tool. A feature request from a heavy user often reveals the department, industry, or domain where the product is already important. The next step is not blindly building the feature. It is mapping who else has the same workflow and selling into that cluster.
Source-backed example
Tope Awotona used feature-request calls to identify super users and then targeted the domains where Calendly was creating the most value.
Source-reported evidence
Source: First 1000: Calendly · Browse First 1000: Calendly tactics
First 1000 describes feature-request calls as the simple system Tope used after Calendly moved from 1,000 toward 10,000 users.
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 Founder Sales, Customer Research, Expansion is relevant to sales, customer research, expansion and you can run a bounded test with a low 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 Founder Sales and Customer Research, using evidence from First 1000: Calendly as context—not as a promised result.
- Record a baseline for: Qualified conversations that advance to the next sales stage. 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
Choose the first market, local proof, partners, and distribution sequence with operator context.
SOURCE HUB
More tactics from First 1000: Calendly
Explore related GrowthDex examples and evidence connected to First 1000: Calendly.
Open First 1000: Calendly source hub