~/blog/invite-only-launch-models-reviewed
Invite-only launch models, reviewed
Waitlists, referral codes and application forms. Reviewed on whether gated launches solve the density problem or simply dress it up.
The gated launch is the default opening move for a new dating app: a waitlist, a referral code, an application, or some combination. It is doing several jobs at once, and only one of them is the job it advertises.
We are reviewing the mechanism rather than any app that uses it.
The variants
What gating genuinely does well
It solves the timing half of the cold-start problem. A waitlist lets an app accumulate registrations and open with enough people in one place to be usable on day one. That is a real engineering answer to a real problem, and it is why the mechanism persists.
Referral gating produces better initial composition. Users arriving through existing users tend to overlap socially and geographically with them, which concentrates density where it is needed rather than scattering it. It also imports a mild accountability effect, since people behave somewhat better among networks adjacent to their own.
Geographic gating is the most honest form, because it states the constraint plainly rather than dressing it as selectivity. An app that says “we are only in this city” has told the user exactly what they are getting.
Scarcity aids retention early on. Users who waited tend to engage more on arrival. That is a psychological effect rather than a product quality, but it is real and it buys an app time.
Where it fails
It is frequently theatre. A waitlist that admits everyone within a day is a sign-up form with a delay screen. This is common, and it is hard to distinguish from the outside until you are through it.
Referral gating narrows the pool along existing social lines. The mechanism that improves composition also reproduces whatever homogeneity the seed users had — socially, economically and demographically. For a product whose value depends on meeting people outside your existing network, this is a genuine tension.
Application gating is rarely explained. Where an app selects, it usually declines to say on what basis. We cannot audit selection criteria from outside and will not pretend to; what we can say is that unstated criteria are unfalsifiable, and an app claiming to curate should be asked to describe how.
It caps growth at the moment growth matters most, which is why many gated launches quietly abandon the gate within months.
Scarcity implies quality it does not deliver. A hard-to-join app is not thereby a good one, and the inference is exactly what the mechanism is designed to encourage.
Telling a real gate from a decorative one
Since the distinction decides whether the mechanism is worth anything, here is how it can be assessed from outside.
Check how long the wait actually is. A waitlist that admits within hours is a sign-up form. Check whether the app states a city or region — a gate that is geographic will say so, because geography is the constraint it is managing. Check whether the app is discoverable in app stores in markets it has not launched in; a genuinely concentrated launch usually is not.
And check what happens on admission. An app that opens to a populated grid was batching admissions properly. An app that opens to a handful of profiles was managing perception rather than density, and the waiting accomplished nothing except making the emptiness feel more disappointing.
Pros and cons
Verdict
Our reading is that gating deserves credit as engineering and scepticism as marketing. The apps using it to concentrate a launch in one city, and saying so, are doing the right thing for the right reason. The ones running a waitlist that admits everyone in a day while implying selectivity are running a growth tactic. Ask which city an app is actually live in and how many people are in it — the answer tells you which kind you are looking at, and most of the rest follows.
Coverage here is for adults; the apps discussed require users to be 18 or over.