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.
Company example
Tope Awotona used feature-request calls to identify super users and then targeted the domains where Calendly was creating the most value.
Source and metric
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.
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.
Founder checklist
- Read First 1000: Calendly and identify what is directly supported.
- Choose one channel context: Founder Sales, Customer Research, Expansion.
- Define the test around First 1000 describes feature-request calls as the simple system Tope used after Calendly moved from 1,000 toward 10,000 users..
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose the first market, local proof, partners, and distribution sequence with operator context.