Pregame Your Launch Before Your App Exists (w/ Amanda Bradford) | E2355

Amanda Bradford’s central lesson from building The League was to create a community and a reason to care before the app was ready. The dating startup, sold to Match Group in 2022, targeted ambitious people seeking serious relationships, using LinkedIn verification and an admissions process to distinguish itself from casual-swiping apps. Bradford said it was the first dating startup to use LinkedIn’s API. The app delivered three or five matches at 5 p.m., and its LinkedIn-based workplace privacy feature, which hid users from colleagues, was especially valued by women.

The League began with a narrow MBA audience and expanded to professionals in finance, marketing, technology, and law. Its Ivy League association came from its name and positioning, Bradford said, not from restricting admission to Ivy League graduates. Messaging such as “for the ambitious,” “for the picky,” and “better to be single than settled” made selectivity part of the product. Bradford personally reviewed every application at first, then recruited her best friend to help. She approached prospective members for feedback on onboarding and other dating apps, and offered early access, building a potential audience while the product was still in development.

Bradford and an iOS engineer built the first version in four months, while the team spent five months building and preparing for a San Francisco launch. Bradford used her HTML, JavaScript, and CSS experience to QA-test the app and send bugs to the engineer. Outsourcing development had not worked for her; she preferred a developer working alongside her, who received equity that vested when the app reached the App Store. Before launch, the team held small mixers, shopping nights, and parties, and recruited waitlisted people directly rather than relying on a single large launch event. Local business partnerships helped keep some events inexpensive, while a Blue Angels boat party generated a few thousand dollars. Equinox and Soho House supported events and later attracted inbound partnership requests.

A selective waitlist, visible slot counts, and invitations to friends created urgency and referrals, while events, partnerships, press outreach, and networks such as a 350-person Wharton group helped build word of mouth. Press coverage of the app’s elite positioning brought in users but also made some people think they were not eligible. The team opened access to 500 people and started with 419; Bradford preferred a small group that loved the product to thousands of users before the team knew what needed fixing. The company opened New York six months after San Francisco and Los Angeles after a full year in those first two cities. It raised $2 million after launch, with evidence that San Francisco users liked the app; Bradford said consumer businesses generally need traction to raise before launch. A pre-monetization test of a $15 “heavy hitter” upgrade drew about 15% of users to click, and Bradford estimated roughly 13% might pay. It was evidence of demand, not actual revenue: billing was not implemented, even though the message said users’ cards had been charged.

The League eventually launched in 155 cities, but Bradford said in retrospect she would have capped expansion at 20. Cities 21 through 155 brought negligible revenue while increasing operational complexity. Her advice was to deepen penetration in the first city before expanding to other cities or internationally; scaling problems in New York contributed to delaying Los Angeles. More broadly, the speakers argued that founders should investigate a problem and talk to prospective customers before deciding what to build. Research, iteration, and customer education may be necessary, and businesses with difficult or non-obvious models can take longer to gain traction than startup-growth narratives imply.

The conversation also connected persistence to Stripe’s early experience. Patrick recalled that Stripe began by making payment integration easier for developers, then its founders recognized broader obstacles to online transactions, including market access, fraud, and integration with existing systems. About six months into operations, a misconfigured data-center switch took down Stripe’s API at 4 a.m.; redundant servers and internet connections could not fix the broken uplink, and service returned only after the switch was replaced nearly eight hours later. Patrick found the lack of customer complaints more troubling than anger, because it suggested users did not care. The speakers said capturing attention online is exponentially harder in 2026 than in 2017, while faster product development makes it easier for competitors to copy and compress a startup’s lead. They emphasized persistence and commitment to a vision over being the smartest founder or having the best idea or advisers.

Patrick said Stripe had planned in 2017 to delay going public so it could pursue long-term investments and its unfinished mission. He said public-company status does not preclude long-term thinking, though stock-price scrutiny can make it harder; Stripe still felt early in its trajectory, and an IPO would make more sense after reaching stability or a plateau and accomplishing initial goals. The speakers disagreed about how strongly public-market pressure should weigh against an IPO, citing Amazon’s long-term outlook and the public-company growth of Microsoft, Apple, Alphabet, and Nvidia, while noting that tender offers can provide private-company shareholders liquidity. They also discussed a reported $60.50-per-share, roughly $53 billion Stripe and Advent International offer for PayPal, which appeared stalled; one host said he preferred Stripe to remain unencumbered.