Amanda Bradford Opened The League to 500 Users After 8,000 Registered

Amanda Bradford built The League around a gap she felt after business school. In a class of about 300, she said, roughly 30 couples formed. The cohort made it easy to meet people with similar backgrounds and ambitions. Graduation dismantled that social infrastructure: people dispersed, and the dating options Bradford saw in the wider world felt less suited to people looking for a serious relationship with a peer.

Her answer was a dating community for career-minded singles, built around a vetted membership rather than an open-ended pool of profiles. Bradford had studied at Carnegie Mellon and Stanford and worked at Salesforce and Google, but she was a solo founder without the technical skills to build the product herself. She knew enough HTML, JavaScript and CSS to prototype, she said, but not enough to build APIs.

The product’s selectivity was part of its design. The League was the first dating startup to use the LinkedIn API, Bradford said, and the first to use an admissions process in which not everyone was accepted. Members received a small batch of prospects at 5 p.m. local time—initially three or five matches, captured in the tagline “five at five”—rather than an endless feed to swipe through. Bradford wanted users to get a few good matches without having to spend half an hour on the app. She described the unlimited-swiping model on other dating apps as feeling like “infinite homework.”

LinkedIn data also helped address a concern that mattered especially to women: being shown to coworkers. Bradford had interned at Sequoia and did not want people she reported to seeing her on a dating app. The League let users block colleagues and contacts based on LinkedIn information. She described that feature as less important to some men, but a meaningful reason women joined. Her broader advice was to identify the users who care most about a particular product feature, rather than assume the same benefits matter to everyone.

The community concept extended beyond profiles and matching. After users had gone through their daily batch, they could find local events and groups. Bradford saw this as a response to a problem that became sharper after school: outside college, the routines and shared spaces that help people meet—classes, clubs, dorm events and campus activities—largely disappear. A bar or gym was a poor substitute for the close-knit cohort she had just left.

That made the League’s positioning more specific than “a dating app.” Bradford aimed at people who were busy, ambitious and looking for a serious relationship. Its brand leaned into high standards and selectivity, with lines such as “better to be single than settle.” She said people sometimes assumed the app was for Ivy League graduates, though that was not its actual admission rule; she considered the association useful because it communicated the brand quickly.

The initial wedge was narrow. Bradford’s business-school network gave her access to MBAs, and one investor joked that the product could have been called “MBA Date” in its first weeks. From there, the user base broadened into finance, technology, law, marketing and other groups with advanced degrees. The lesson she drew was to go deep and narrow before trying to serve everyone.

Bradford began recruiting before the app launched because a two-sided marketplace can fail if either side arrives to an empty room. The League’s San Francisco launch was “pre-gamed” for five months: Bradford built a waitlist, found prospective members and gave them reasons to talk about the product before they could use it. A presentation slide put the results at 8,000 registrations before the alpha launch and 76,000 within three months of going live.

Bradford said the app took four months to build. The timeline slide dates the pre-game period from August through November and the San Francisco launch to November 2014. She first tried outsourcing development, which she said did not work in her experience. She then hired an iOS engineer to work alongside her, giving him equity that vested when he got the app into the App Store. She called the arrangement “a rented co-founder”: someone to build a proof of concept and get the product launched, rather than a conventional long-term co-founder relationship.

Even before acceptance, the onboarding reinforced the feeling of a limited community. Applicants saw how many places remained in the alpha, with separate counts for women and men, and were encouraged to invite friends. Bradford said the countdown created urgency: people who saw that only a limited number of spots remained had a reason to spread the word and help fill the cohort. The screen told one applicant she had secured place 52 of 250 available spots for women, while showing a separate count for men. The alpha, it said, would launch when those groups were filled.

Her most effective recruiting approach was personal. Bradford went to events and asked people to review the onboarding, what they liked or disliked about existing dating apps, and whether they would use the product she was building. That let prospective members act as design partners. She called them founding members and promised them first access when the app launched. Her presentation described this as the “VIP approach”: make target lists, meet people in person, and pitch the parties rather than starting with a product pitch.

Bradford’s account of the method was practical rather than automated. Founders might have to become socialites, she said, or find a co-founder who already enjoys that role. At events she could ask for feedback and exchange contact information; she described that work as a form of door-to-door sales. The value of the interaction was not just adding names to a list. The prospective member had been asked to contribute to the product and could feel like a founding participant.

The invitation often came through an event rather than a product pitch. Bradford organized mixers, shopping events and parties, including a boat party during San Francisco’s Fleet Week. The events were free or inexpensive to put on: a local business might stay open later in exchange for a minimum in sales; a fitness studio could provide an otherwise unused class slot; and guests could pay for a larger event such as the boat party. Bradford said she rented the boat several months ahead and charged $300 for that event, which brought in a few thousand dollars. For an open-bar event, she might cover the first drink and put later drinks on guests’ own cards.

At the door, the condition for admission was having The League app on their phone. Bradford said she did not always mention that requirement until guests arrived, so the person checking tickets had to hold the line. That combination made an event both a gathering and a recruiting channel. It gave people a reason to attend, put potential members in a room with one another, and turned app installation into a condition of entry.

The events also gave Bradford a way to reach people who had not yet encountered the product. She described a Wharton contact forwarding her introduction to a Facebook group of about 350 people; Bradford had not attended Wharton herself, so the friend provided a route into that network. She also emailed journalists who covered dating and startups. She wrote roughly 30 pitches before launch, later judging her first email too long, and said she had received advice from friends with PR experience about whom to contact and how to pitch.

The press liked the exclusive-admissions angle, Bradford said. Headlines framed The League as an elitist or invite-only dating app. That attention helped communicate selectivity, but it also risked making people think they were not eligible if they had not attended a prestigious school. Bradford judged the effect more positive than negative, while noting that a journalist can take a founder’s pitch and reshape it.

She did not frame the pre-launch work as a substitute for product use. It was a way to assemble a founding group, create word of mouth and avoid an empty-room launch. The product still had to work once those users arrived. In her account, the events and press created the conditions for an initial community; the first cohort’s activity gave her something more useful than a waitlist when it came time to judge the launch.

When The League opened in San Francisco on November 12, 2014, Bradford accepted 500 people. Of those pre-launch members, 419 showed up on launch day. She reported that 72% of users sent a message, 91% remained through day seven, and half invited friends.

Bradford argued that the limited opening was a better way to learn than admitting thousands at once. Five hundred people who were enthusiastic about the app could reveal what was working; a much larger launch could make it harder to understand what had gone wrong. “It’s really better to have 500 people that like are obsessed with your app than trying to open it to like 5,000 people and figure out what what you’re doing wrong,” she said. The small cohort was not merely a scarcity tactic. It gave the team a defined group to observe and improve the product for.

After the first city, The League repeated the pattern at a measured pace. The company stayed in San Francisco for six months before launching New York. It operated in San Francisco and New York for a full year before launching Los Angeles, and added monetization in the interval between New York and Los Angeles. Partnerships with venues and brands helped keep events inexpensive, Bradford said. Equinox locations in each city let the company hold events at no cost if it brought in people who were not members. After The League worked with brands such as Equinox and Soho House, companies including HBO and Netflix approached it about events connected to their own launches.

Expansion was not costless. Bradford said The League eventually launched in 155 cities, but in retrospect she would have capped expansion at 20. Revenue from cities 21 through 155 was negligible, she said, while each additional market brought operational complexity. Her advice to founders was to get deeper penetration in the first city before opening new ones. She also said she would have held off on monetization until that first market was established.

The growth was not exponential, Bradford said. A slide in her presentation showed 1.4 million total signups and 75% organic growth, alongside about $1.2 million in marketing spend. She described the user base as rising consistently before The League eventually reached 155 cities. Those figures sat alongside her warning about expansion: a larger count of markets did not mean that each market contributed meaningfully to revenue.

The same bias toward testing early shaped her approach to subscriptions. The League did not charge users during its first year and a half, but Bradford wanted evidence that people might pay. She presented users with an offer to upgrade to a “Heavy Hitter” membership for $15. When they clicked, the app said they had been charged and granted them the features, but the team had not actually built payment processing. Bradford described it as a “smoke and mirrors” test.

About 15% of users clicked, she said, though she thought the real willingness-to-pay figure might be closer to 13%. The result was not a measure of completed purchases; no payment had been taken. It was a test of whether users would express interest in the offer, and Bradford used that signal to explain a possible subscription model to investors before the company had implemented billing. She said it helped investors feel more comfortable that the product could be monetized.

Her broader advice was to test monetization as early as possible, even if the mechanism was provisional. The test did not establish how many users would ultimately pay, but it gave her a basis for discussing price and interest before the billing system existed.

Other advice followed the same practical logic. Do not wait indefinitely for the perfect co-founder; if one does not appear, keep moving. Show investors that the company will proceed whether or not they invest. For press, make targeted pitches to people with distribution, and consider influencers as an earned-media channel. And once traction appears, start planning to rebuild the MVP: Bradford said The League encountered scaling problems as it entered New York, and that rebuilding became part of the work required to grow.

In the exchange after her presentation, Jason Calacanis pushed Bradford to extend the live-event approach beyond dating. The value, he suggested, was not simply that events could attract customers or press, but that they could bring together people who were a good match for one another.

Bradford used The League’s audience to explain the idea. Members were often frustrated by going to a bar and finding people who were already partnered, too old or too young. A curated event improved the chance that attendees would meet people within the group they wanted to reach. For a developer tool, Bradford proposed finding a specific developer community whose members had trouble meeting peers with a shared specialty, then organizing a meetup or hackathon around that need. The format could change; the underlying question was who the audience wanted to connect with and could not easily find.

Calacanis sharpened the example by pointing out that an event full of founders already had a high “hit rate” for founders meeting other founders. He suggested adding investors to make the networking more valuable. Bradford agreed that the relevant audience and its needs had to determine the mix. An event should not simply assemble people who fit a broad label; it should give them a reason to want to be in the same room.

The exchange also turned to how an event might become a press story. Bradford said The League sometimes used unusual stunts and invited journalists, offering them a free ticket and a reason to expect interesting people or a striking scene. For one event in Montauk, she described flying people out by helicopter and setting up three blind dates. The press angle came from the combination of a distinctive event and a detail journalists might consider unusual or controversial.

When Calacanis challenged her to apply the approach to a probiotic soda, Bradford suggested gathering people with competing views about probiotics and how they should be consumed, then building a discussion around those differences. The event could function more like a salon: a place to exchange ideas and debate a live question, rather than a product presentation. The exchange left a useful tension intact. A provocative hook might make an event easier to cover, but the gathering still needs to fit the people the company wants to reach.

In a 2017 interview, Patrick Collison described Stripe as handling billions of dollars in aggregate revenue for customers, serving thousands of companies and operating in about 124 countries. Calacanis said the company was approaching 700 employees. The more consequential shift in the interview was Collison’s account of how the founders came to understand the size of the problem they were working on.

Stripe initially looked like a tool that made it easier for developers to integrate payments. But, as the founders worked on it and spoke with companies, they heard about more than a difficult developer task: businesses described markets they could not serve, fraud problems, integrations they could not make and a broader system that made online transactions hard.

Collison recalled that about 2% of consumer spending took place online at the time. The founders began to see the payment problem not as a small pond of developer inconvenience, but as a much larger problem with the infrastructure of doing business on the internet. That shift led them to take a leave of absence from school and raise initial funding from Sam Altman, Peter Thiel, Sequoia and others.

Alex Wilhelm compared the 2017 figures with later numbers he cited during the discussion: Stripe processed $1.9 trillion in 2023, up 34% from the year before. For the first half of 2024, he said, Stripe processed an amount equivalent to about 2% of global GDP; the company had announced five million businesses on the platform, and revenue in that half-year was up 41%. The figures were presented as a comparison with the scale Collison described in 2017, not as an update beyond the period the hosts were discussing.

Harris drew a distinction between identifying a problem and knowing the product that will solve it. A founder may recognize a real need, he said, without yet knowing the right solution. That requires talking to customers, building, learning how the problem appears in practice and iterating toward something people will use repeatedly. Wilhelm added that this kind of work can be slow and non-obvious, especially in a startup culture focused on short-term growth benchmarks. He was not dismissing fast-growing companies; he argued that the industry should retain room for founders who need time to understand a large problem before its eventual scale is apparent.

Collison’s account of an early Stripe outage gave the problem of interpreting early signals a sharper edge. About four to six months into the company’s life, he said, his pager went off at 4 a.m. The API was down. Stripe had multiple servers, but an upstream switch at its data center had failed, and the supposed redundancy was misconfigured. The underlying internet connection was broken, and the company could not fix the problem itself.

Collison reached the office within minutes and waited for the data center to repair the switch. The outage lasted almost eight hours. He expected customers who relied on Stripe to process revenue to respond with complaints and anger. By 1 p.m., he had heard no complaints. As he reflected on that silence, he said, it felt “existentially bad news.”

The silence did not establish why customers had not complained, or whether they had noticed the outage. Collison presented it as a troubling signal about how much the service mattered at that early stage. The distinction matters: the API’s unavailability was real, but the absence of complaints alone did not tell the founders what customers thought or what they would need to do to become essential.

Harris and Wilhelm interpreted the story through the difficulty of earning attention. Harris said founders can be highly conscious of how others might judge them, but a company also has to compete for customers’ focus. Wilhelm added that products can now be prototyped and launched more quickly, which can make it easier for others to follow. Those were the hosts’ reflections on the story, not conclusions Collison drew from the outage itself.

The company’s early experience also connects to the gap between a product’s eventual importance and its initial standing. In the interview, Collison described how the founders began with a developer tool and, through work and customer conversations, came to see a larger infrastructure problem. The outage offered no guarantee that persistence would pay off; it did not show that Stripe was already indispensable. It showed the founders confronting a discouraging signal while still trying to understand the problem and build the service.

Harris’s broader observation was that founders who succeed are not necessarily the ones with the best initial idea or advisers; persistence can matter. The Stripe story illustrates the point without making persistence a universal prescription. The hosts wondered whether the lack of complaints could have led the founders to conclude that customers did not care. The source does not establish that they considered abandoning Stripe, only that the outage and the silence afterward made for a difficult moment in Collison’s account.

In the 2017 interview, Collison said Stripe intended to hold off on going public for as long as possible. His stated reason was time horizon. The company wanted to invest in projects that could take a long time to bear fruit, and he believed being public could make that harder. Amazon was his example of a company that had maintained a long-term outlook in public markets, though its early years as a public company had been turbulent. Stripe, he said, still felt early in the trajectory it had set for itself.

Wilhelm later disputed the implication that public markets necessarily prevent long-term investment. He pointed to Amazon, Microsoft, Apple, Alphabet and Nvidia as large companies that had done much of their growth while public. He also questioned Collison’s use of Amazon’s early public-market turbulence as evidence for Stripe’s position, noting that Amazon had gone public before the dot-com crash. Wilhelm’s counterargument was that public status does not, by itself, rule out long-term investment.

The disagreement was not about whether Stripe had chosen to stay private at the time of the 2017 interview. It was about what that choice demonstrated. Collison described the value of keeping a long horizon while Stripe worked on infrastructure. Wilhelm suggested that founders’ ability to refuse a public listing might explain more than any general limitation of public markets.

Harris noted that the company’s continued growth made the question of when it would go public an open topic in the discussion. The hosts also mentioned tender offers as a way to provide liquidity while Stripe remained private. They did not establish a future listing date or resolve the disagreement over the advantages of staying private. The tension they preserved was between Collison’s preference to keep building before reaching what he considered a more stable point and Wilhelm’s view that public-company examples complicate the claim that a listing necessarily shortens a company’s time horizon.