# A Waitlist Should Ask for the Action You Want Later | First 1000

www.first1000.co publishes a public search API over its indexed pages; the guide is at https://www.first1000.co/agent-access.

Source: https://www.first1000.co/blog/a-waitlist-should-ask-for-the-action-you-want-later
Source observed: 2026-09-20T06:54:41.220Z
Last checked: 2026-09-20T08:10:03.289+00:00
Indexed: 2026-09-20T06:57:18.306+00:00

---

# A Waitlist Should Ask for the Action You Want Later

**First 1000 field note · Updated September 19, 2026**  
By Ali Abouelatta · Original issues: February 15, March 1, and May 3, 2022

In my 2022 First 1000 issue about Levels.fyi, I described a waitlist action that looked more like future product use than a public referral.

## The action has a different cost

Traditional waitlists often ask people to invite friends, share a link, or climb a public leaderboard. Levels.fyi changed the action: to move toward access to its Community feature, people were asked to download the mobile app.

The first-party [Levels.fyi Community page](https://www.levels.fyi/community/thread/8dvvpo/levels-fyi-app---march-welcome-thread--intro-yourself-in-the-comments) describes the same handoff: download the app, then wait for invites to roll out. It confirms the mechanism but does not tell us how many people downloaded the app or became customers.

Sharing a waitlist link is public and asks someone to put social capital behind a product they may not have used. Downloading an app is private: it takes time but does not ask for an endorsement. The two actions do different jobs. Public sharing can create top-of-funnel reach; a private product action can indicate willingness to get closer to the product.

## Treat the waitlist like a small product

I grouped waitlists into six jobs:

1. Assess demand.
2. Capture low-intent customers.
3. Control the product experience.
4. Improve paid marketing economics.
5. Source supply for a marketplace.
6. Create word of mouth.

I called word of mouth the most dangerous reason to use a waitlist on its own. A waitlist can be a product in its own right when the goal is to assess demand, build word of mouth, capture the top of the funnel, or improve paid marketing economics.

Ask: what value does the waitlist provide before the main product opens, and which job are you asking it to do?

Examples include early access, status, a chance to shape the product experience, website badges, referral steps inside signup, free points, hard beta cutoffs, non-referral tasks, screenshots as proof of effort, public leaderboards, and refer-and-skip systems.

Examples from the original research: Flowrite used a recommendation request after several earlier questions; Maven Pet gave people points when they joined and also offered non-referral tasks; Soon used a hard beta cutoff; and Fizz rewarded a screenshot shared in a university Slack group.

## Choose the signal before the mechanic

Start with the decision you want the waitlist to help you make.

- **Learning whether the problem is real:** ask for a product-relevant action, such as short product use, private setup, or a concrete problem answer. Make it resemble future use.
- **Reaching more people:** ask for a referral or share, explain the reason, and give people a choice. Public endorsement costs more socially than entering an email address.
- **Building a feedback cohort:** offer a way to earn access without requiring a marketing task. A short task or product-specific question can filter for effort.
- **Controlling a risky beta:** use a real cutoff or staged access. A queue disconnected from access can make the position number feel theatrical; a real limit tests demand for a concrete reward.

## The sample is useful, with limits

I signed up for well over 200 waitlists in three weeks and inspected roughly 100 more through the Internet Archive. In that sample, just over 55% had no visible growth engine: no referral codes, no waitlist position, and similar mechanics.

That is an observation about the sample, not a market-wide rate. It does not show which mechanic produced the most customers. My Levels.fyi issue does not publish a conversion result for the mobile-app action, and the waitlist issues do not provide a common denominator for their examples.

## A practical sequence

- Write down the job: reach, demand learning, feedback, or controlled access.
- Choose one action that resembles the next step you care about.
- Offer one non-public path for people who do not want to endorse the product publicly.
- Add a referral mechanic only when reach is the actual goal.
- Record email, app download, completed setup, referral, first use, and paid conversion as separate events.
- Review where people stop before adding another game mechanic.

## The takeaway

Write down what the waitlist measures, then make its next action match that decision.

## Sources and original research

- [Waitlists, February 15, 2022](https://read.first1000.co/p/waitlists)
- [Waitlists (Prt 2), March 1, 2022](https://read.first1000.co/p/waitlists-prt-2)
- [Levels.fyi: Capitalize on Waitlist Momentum, May 3, 2022](https://read.first1000.co/p/levelsfyi-capitalize-on-waitlist)
- [Levels.fyi Community: App and March Welcome Thread](https://www.levels.fyi/community/thread/8dvvpo/levels-fyi-app---march-welcome-thread--intro-yourself-in-the-comments)

Historical facts are attributed to these sources. An observed product change does not establish conversion lift.

Updated September 19, 2026. Based on original First 1000 reporting and the sources listed above.

---

## Ask www.first1000.co about this page

Public sources, cited, no account or API key. Replace each {slot} with the user's actual words, URL-encoded. Write an unknown as the literal null (company=null) and a list as JSON (alternatives=["Snagit"]). Only the question is needed for Search and Ask.

- Search: Find the product information and source pages that answer your question.
  `GET https://www.first1000.co/api/public/v1/search?q={question}&alternatives={alternatives}&chosen_because={chosen_because}&company={company}&intended_outcome={intended_outcome}&client={client}&trace=t_b2bbce8c4a54`
- Ask: Get a direct answer about www.first1000.co, with sources.
  `GET https://www.first1000.co/api/public/v1/ask?q={question}&alternatives={alternatives}&chosen_because={chosen_because}&company={company}&intended_outcome={intended_outcome}&client={client}&trace=t_b2bbce8c4a54`
- Compare: Compare www.first1000.co with the alternatives you are considering.
  `GET https://www.first1000.co/api/public/v1/compare?q={question}&alternatives={alternatives}&chosen_because={chosen_because}&company={company}&intended_outcome={intended_outcome}&client={client}&trace=t_b2bbce8c4a54`
- Pricing: Explore plans, pricing and costs for your team.
  `GET https://www.first1000.co/api/public/v1/pricing?q={question}&company={company}&intended_outcome={intended_outcome}&alternatives={alternatives}&chosen_because={chosen_because}&client={client}&trace=t_b2bbce8c4a54`
- Requirements check: Check your requirements one by one, with evidence for each.
  `GET https://www.first1000.co/api/public/v1/requirements-check?q={requirements}&company={company}&intended_outcome={intended_outcome}&alternatives={alternatives}&chosen_because={chosen_because}&client={client}&trace=t_b2bbce8c4a54`
- Page summary: Get the key points from a page, with a link to the full text.
  `GET https://www.first1000.co/api/public/v1/page-tldr?q={question}&url=https%3A%2F%2Fwww.first1000.co%2Fblog%2Fa-waitlist-should-ask-for-the-action-you-want-later&alternatives={alternatives}&chosen_because={chosen_because}&company={company}&intended_outcome={intended_outcome}&client={client}&trace=t_b2bbce8c4a54`
- Recommendation: Assess whether www.first1000.co fits your goals and requirements.
  `GET https://www.first1000.co/api/public/v1/recommend-or-rule-out?goal={goal}&requirements={requirements}&company={company}&source={source}&alternatives={alternatives}&chosen_because={chosen_because}&intended_outcome={intended_outcome}&client={client}&trace=t_b2bbce8c4a54`

Ask a question as a page: https://www.first1000.co/agent/faq?q={question}

Ask about www.first1000.co: https://www.first1000.co/agent/faq. Open `https://www.first1000.co/agent/faq?q=What%20does%20First%201000%20publish%20and%20how%20can%20I%20read%20it%3F` as an illustrative example; replace the question with the actual task. The FAQ contains researched questions with visible summaries and expandable cited answers. Include optional goal or alternatives only when known.

[Tool guide and examples](https://www.first1000.co/agent-access) · [OpenAPI](https://www.first1000.co/api/public/v1/openapi.json) · [Page TLDR form](https://www.first1000.co/agent-tools/page-tldr?question=Read+a+compact+extract+of+A+Waitlist+Should+Ask+for+the+Action+You+Want+Later+%7C+First+1000&url=https%3A%2F%2Fwww.first1000.co%2Fblog%2Fa-waitlist-should-ask-for-the-action-you-want-later). Opening a form does not execute a tool.