# Requested-feature update loop to beta users

> Send early users frequent progress updates and ship the features they asked for, so beta participation starts to feel like ownership.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/requested-feature-update-loop-to-beta-users/
- Source: [quo.com](https://www.quo.com/blog/first-1000-customers/)
- GrowthDex source hub: [Quo (formerly OpenPhone): How we got our first 1,000 customers](/sources/quo-formerly-openphone-how-we-got-our-first-1-000-customers-quo-com/)
- Last checked: 2026-06-07T02:03:15Z
- Rarity: uncommon
- Budget: free
- Channels: Lifecycle, Product, Word of Mouth
- Stages: beta, first customers, feature feedback, word of mouth


## Why this can grow

Quo credits part of its early word of mouth to giving beta users a memorable experience: frequent updates and launches of requested features. This is growth work, not just product housekeeping. Early users share when they feel the team is listening and the product is moving because of them. The loop also gives founders a reason to re-contact users without inventing a newsletter. “You asked, we shipped this” is one of the cleanest lifecycle messages a small team can send.

## 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 requested-feature update loop to beta users can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Lifecycle and Product channel.
3. Use the evidence from quo.com 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

Quo says it sent beta users frequent progress updates and launched features they asked for during the first-customer period.

## Adjacent tactics in the same lane

- [Beta paywall as need filter](/growth-ideas/beta-paywall-as-need-filter/) - same source, 2 shared channels, 2 shared stages
- [Pricing drop-off one-question survey](/growth-ideas/pricing-dropoff-one-question-survey/) - same source, 1 shared channel
- [Group-admin Q&A session before promotion](/growth-ideas/group-admin-qa-session-before-promotion/) - same source, 1 shared stage
- [Adjacent-topic posts before product mention](/growth-ideas/adjacent-topic-posts-before-product-mention/) - same source, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The community thread should already contain the problem](/blog/the-community-thread-should-already-contain-the-problem/) - community-led growth, first customers, customer research

## Advisory

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