TThe Diary of a CEO
← All frameworks
MarketingJustin McLeod

City-By-City Liquidity Launch

Break stigma by making the cool crowd download it in front of each other, one city at a time

Difficulty
Advanced
Time to result
~weeks to results
Steps
5
Confidence
89%

How Hinge went from a trickle of users to a self-sustaining network: concentrate your entire remaining budget on a single physical event in one city, gate entry on downloading the app, and let the socially-visible crowd adopt it simultaneously in front of each other. The mechanism solves two problems at once — cold-start liquidity, because a few thousand people join the same local pool on the same night, and stigma, because public simultaneous adoption by high-status locals makes the product socially safe. Word of mouth then seeds waitlists in the next city, and you only open a new city once you judge there's enough liquidity to serve it. McLeod is candid that the tactic was of its era and probably doesn't transfer as-is to today's app market.

Origin

At the end of 2012 Hinge had rebuilt for mobile with two and a half months of cash, and spent its last $25,000 on a giant open-bar launch party in Washington D.C. The app was still stuck in App Store review the night before; McLeod sat on the floor of the co-working space with his jacket over his head, crying, expecting 2,000 people at a launch with no app. It was approved the next morning.

Core principles

  • 01Cold-start networks need geographic and temporal concentration, not broad reach.
  • 02Public, simultaneous adoption by high-status peers is the fastest stigma solvent.
  • 03Gate the value on the download — entry is the conversion event.
  • 04Open the next city only once the last one has liquidity.
  • 05The tactic was era-specific; the mechanism (concentrated visible adoption) is what transfers.

How to run it

  1. 1

    Pick one city and concentrate everything

    Choose a single market and commit the remaining budget to one high-visibility event there rather than spreading spend.

    Watch out Hinge literally spent its last $25,000 with no fallback plan.

  2. 2

    Make the download the price of entry

    Require the app to get in, so attendance and installation are the same act.

    Pro tip Invite the visible social scene specifically — their adoption is what carries the signal.

  3. 3

    Let them see each other using it

    Design the event so people are visibly using and discussing the app in front of one another on the night.

    Pro tip This is the actual mechanism — simultaneous visible adoption is what dissolved the 'lonely weirdos' stigma around online dating in 2013.

    Watch out A quiet download drive achieves the install without the social proof, and the stigma survives.

  4. 4

    Watch the organic next-day cohort

    Treat the unprompted signups in the days after as the real signal that the loop is live.

    Pro tip Hinge saw around 400 people log in the next day, then a few hundred more the day after, then build.

  5. 5

    Repeat into the waitlist cities

    Let word of mouth build waitlists in the next markets, then run the same launch party there once liquidity justifies it.

    Pro tip D.C. told New York, New York told San Francisco — follow the referral trail rather than a market-size ranking.

    Watch out Open a city too early and there aren't enough people in the pool to make the product work.

In the wild

The D.C. launch party

2,500 people came to an open-bar party they could only enter by downloading Hinge, after the app was approved in the App Store the very morning of the event.

More matches were made the next day than in the entire prior history of the app, and it snowballed from there.

Watching the logs one user at a time

Before the party, McLeod would sit and watch server logs as a single user came in, clicked a button, passed, and left — then wait for the next one.

The contrast with hundreds of organic signups per day after the launch made the inflection unmistakable.

Common mistakes

Assuming the launch party is the lesson

McLeod agrees the tactic belonged to the 2012 app boom; someone today with $25,000 and an app should not expect a party to solve their problems.

Leaving no buffer on external dependencies

Hinge submitted to the App Store with what seemed like ample time — two weeks against typical review times of a couple of days — and still nearly launched a party with no app.

Is it for you?

Best for

Early-stage network or marketplace products facing a cold start plus a social-acceptability problem.

Not ideal for

Products with no network effect, or any team that cannot survive the concentrated spend failing.

From the transcript

Literally took our last $25,000 and threw a giant open bar party in D.C.

Justin McLeod · 20:30

the fact that everyone saw each other using it, I think like started to like jump-start and get over that stigma problem

Justin McLeod · 22:30

we would start opening cities one at a time once we felt like we had enough liquidity

Justin McLeod · 23:00

We'd throw another launch party.

Justin McLeod · 23:30

From the episode

Hinge Dating App CEO: Everyone Said Hinge Was A TERRIBLE idea! The 7 Love & Dating Secrets From Hinge’s Founder! AI Will Change Love & Dating!

Justin McLeod