Growth idea action plan
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.
Ian's take
From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.
Action plan
- Define one narrow startup segment where calendly feature-request call to domain sales map can create a measurable lift.
- Turn the tactic into one offer, page, campaign, or workflow for the Founder Sales and Customer Research channel.
- Use the evidence from read.first1000.co to set the first version of the message, format, and audience.
- Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
- Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.
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: First 1000: Calendly (read.first1000.co)
GrowthDex source hub: First 1000: Calendly
Last checked: 2026-06-07T02:32:11.958Z
Adjacent tactics in the same lane
If this page is close to your problem, these tactic pages usually belong in the same working set.
- Calendly competitor teardown before first build same source · 1 shared channel · 1 shared stage
- Calendly parent-teacher beachhead workflow same source
- Calendly free launch because billing is not core loop same source
- Calendly recipient-first product loop same source
Related GrowthDex essays
- The link should sell the recipient before the sender explains product-led growth, first customers, founder sales
Read GrowthDex essays
The Blog turns real growth tactics into plain-English case studies by niche, channel, and buying situation.
Why this is worth your time
GrowthDex starts with tactics that founders, marketers, and product teams have actually tried. Each essay turns the evidence into a practical move you can test without pretending one case study is a guarantee.
Ian Goh has helped grow consumer platforms across Southeast Asia, India, and MENA. His work includes scaling Tiki to 100M+ users, doubling BIGO's MENA revenue in 7 months, and increasing OYO's direct booking share across 6 Southeast Asian markets.
- Helped scale Tiki to 100M+ users.
- Doubled BIGO's MENA revenue in 7 months.
- Raised OYO's direct booking share by 50% across 6 Southeast Asian markets.
Want help turning this into a growth system?
If you want someone to pressure-test this against your real market, Ian works with founders on growth, market entry, and operator-led distribution.
Work with Ian on growth advisory