# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/calendly-feature-request-call-to-domain-sales-map/
- Source: [read.first1000.co](https://read.first1000.co/p/-calendly)
- GrowthDex source hub: [First 1000: Calendly](/sources/first-1000-calendly-read-first1000-co/)
- Last checked: 2026-06-07T02:32:11.958Z
- Rarity: rare
- Budget: low
- Channels: Founder Sales, Customer Research, Expansion
- Stages: sales, customer research, expansion, feature requests


## Why this can grow

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

1. Define one narrow startup segment where calendly feature-request call to domain sales map can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Founder Sales and Customer Research channel.
3. Use the evidence from read.first1000.co to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. 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.

## Adjacent tactics in the same lane

- [Calendly competitor teardown before first build](/growth-ideas/calendly-competitor-teardown-before-first-build/) - same source, 1 shared channel, 1 shared stage
- [Calendly parent-teacher beachhead workflow](/growth-ideas/calendly-parent-teacher-beachhead-workflow/) - same source
- [Calendly free launch because billing is not core loop](/growth-ideas/calendly-free-launch-because-billing-is-not-core-loop/) - same source
- [Calendly recipient-first product loop](/growth-ideas/calendly-recipient-first-product-loop/) - same source

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The link should sell the recipient before the sender explains](/blog/the-link-should-sell-the-recipient-before-the-sender-explains/) - product-led growth, first customers, founder sales

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.