Finding your first buyer: warm network, communities, and doing things that don't scale

#1. Why this lesson exists before any channel lesson

Every later lesson in this course assumes something this one has to supply first: a working relationship with at least one real buyer. Pricing mechanics, objection handling, the flywheel that turns customer one into customer two — none of it has anything to operate on until a specific person has said yes. The honest, unglamorous truth about where that first yes comes from is that it is almost never a paid channel. Paid acquisition needs a functioning funnel to optimize — a landing page converting at a known rate, an offer tested against real objections, a price that's survived contact with a real budget. A founder's first customer, by definition, arrives before any of that exists to optimize. So the founder needs leverage that doesn't depend on the offer already being proven. That leverage comes from three places, covered here in the order a real founder should actually try them: the people you already know, the communities your buyer already occupies, and the option of becoming, personally and manually, the product's first delivery mechanism.

This isn't a lesson about "hustle" as a vague virtue. Each source below has a specific mechanism behind it — social-science research, a named community with documented rules of engagement, or a well-attested founder history — and the mechanism is what tells you when and why it works, not just that it worked for someone once.

There's a wider map behind the three sources this lesson and the next one cover, and it deserves to be named explicitly rather than left implicit. Lenny Rachitsky's reporting on how B2B founders won their first ten customers — sourced from direct, attributed founder interviews, not survey data — reframes this same research as a seven-stage sequence, each stage asking a stranger for more trust than the last: personal network, then targeted cold outbound, then investor and accelerator networks, then general communities, then content and online presence, then press, then organic launch. [Directional] — a well-sourced practitioner synthesis of named, attributed founders and checkable companies, not a peer-reviewed study, but its ordering logic is stated as a mechanism rather than a ranking by convenience: "It's all a matter of trust" — a founder with no proof yet that the product works can't buy trust with a bigger list or a louder announcement, only borrow it from somewhere it already exists, moving outward from the tightest ring (someone who already trusts you personally) to the loosest (a stranger who has to decide from one public artifact alone). This lesson and the next cover all seven rings between them, though not in that exact order: personal network and general communities are grouped here because they work the same way — finding a buyer where they already are — while cold outbound gets its own lesson next, because it's a distinct skill rather than a place to look. Investor and accelerator networks, a ring with its own borrowed-trust mechanism distinct from both a personal weak tie and a public community, get their own treatment inside the communities section below. Content, press, and organic launch — the three outermost rings — are covered near the end of the next lesson, for a reason that will make more sense once this lesson's own mechanism is on the table: they ask the most of a stranger's trust, and they're the least useful rings to reach for before a closer one has already won you a first customer.

---

#2. The strength of weak ties: why the person you should message isn't your best friend

Start with a finding that runs directly against the instinct most first-time founders act on, which is to tell the people closest to them first. Sociologist Mark Granovetter's 1973 paper "The Strength of Weak Ties" surveyed 282 professional, technical, and managerial workers in Newton, Massachusetts about how they'd found their current job. [Established] — a peer-reviewed, foundational sociology paper, one of the most cited in the social sciences, its methodology and headline numbers corroborated across independent academic summaries. Of the workers who'd gotten their job through a personal contact, Granovetter asked how often they actually saw that contact. The answer inverted what most people would guess: only 16.7% saw the contact often — a genuinely strong tie. 55.6% saw the contact only occasionally, and 27.8% saw them rarely, roughly once a year or less. Put plainly: 83.4% of job leads that came through a personal contact came from someone the person did not see often.

The mechanism, not just the number, is what makes this useful for finding a customer rather than a job. Your close ties — the people you talk to weekly, your family, your daily coworkers — overlap heavily with your own network. They already know most of what you know and most of the people you know. A weak tie sits in a different part of the social graph entirely: an old classmate, a former colleague from a job two roles ago, someone you met once at a conference and never followed up with. Because their network doesn't overlap with yours, they function as what Granovetter called a "local bridge" — a connection to information, people, and opportunities your close circle structurally cannot supply, no matter how much they want to help you.

This isn't a forty-year-old finding left untested. Granovetter's study was correlational and small — 282 people, self-reported. A far larger and genuinely causal version exists: Rajkumar, Saint-Jacques, and colleagues ran a five-year randomized controlled experiment on LinkedIn (2015–2019) across roughly 20 million users, algorithmically varying whether "People You May Know" surfaced more strong-tie or weak-tie suggestions, tracking about 2 billion new connections and roughly 600,000 jobs obtained through the platform. [Established] — published in Science (2022), a peer-reviewed, large-scale, causal study, not a correlational survey; it confirms Granovetter's claim experimentally and adds a refinement the original couldn't see. The relationship isn't linear — it's an inverted U. The most valuable ties are moderately weak, not the weakest possible. The sweet spot sits around a connection with roughly ten mutual connections: someone with enough shared context to vouch for you, but not so embedded in your circle that they're redundant with what you already know. A total stranger adds little; your best friend adds little. The person in between is where the leverage is.

The application to a first customer is a specific, falsifiable claim, not a vibe: the person most likely to become — or introduce you to — your first paying customer is not your closest friend and is not a cold stranger. It's the person you interned with three years ago. The old coworker you haven't spoken to since you both changed jobs. The person from a course or a conference you met once and never texted again. Two moves follow directly from this, and they're both concrete enough to do this week rather than reflect on:

• Run a weak-tie inventory. List everyone you've worked with, studied with, or been introduced to whom you don't talk to regularly — old LinkedIn connections, alumni lists, a former job's client list, a Slack workspace you left two jobs ago. This is the literal 1973 finding turned into a worksheet, and it's the first item on this lesson's own worksheet below.
• Reactivate, don't cold-contact. A message to a weak tie — "Hey, it's been a while — I'm building X, does this sound like something you or someone you know would want?" — starts from a real relationship, thin as it is. That's a fundamentally different psychological situation for the recipient than a cold email from a stranger, which is the subject of the next section.

#Marlowe, warm network, worked example

Marlowe is an invented example — stated here explicitly, once — used throughout this course to keep every framework grounded in one continuous, specific decision rather than a new hypothetical every lesson. Marlowe is a solo bookkeeper who has just left a corporate accounting job to freelance for small, owner-operated local businesses — the kind currently doing their own books badly, or overpaying a full-service firm $2,000-plus a month for work a fraction of that could cover. Marlowe's offer: $600/month per client for bookkeeping plus a monthly close, positioned as better than doing it yourself and cheaper than a full firm.

Marlowe's actual first customer came through exactly the mechanism section 2 describes, and it's worth being precise about which tie it was. It wasn't Marlowe's best friend, who works in an unrelated field with no local-business connections worth activating. It was a former colleague from the corporate accounting job — someone Marlowe hadn't spoken to in over a year, seen only "rarely" in Granovetter's own terms — whose cousin runs a boutique gym. The former colleague wasn't the buyer; they were the bridge, exactly the role weak ties structurally supply and strong ties structurally can't, because their network didn't overlap with anything already in Marlowe's own circle. A single reactivation message — "I've gone independent doing bookkeeping for small businesses, if you know anyone who's drowning in their books, I'd love an intro" — produced the introduction that became Marlowe's first real prospect conversation.

---

#3. Communities: where a founder's buyer already spends time, and the etiquette that keeps you welcome there

The weak-tie mechanism explains why a person you barely know can outperform a person you know well. It doesn't tell you what to do when your weak-tie inventory runs out, or when nobody in your existing network — close or distant — has a path to the specific kind of buyer you need. That's what real, named online communities are for, and the research here is more mixed in quality than section 2's — mostly self-reported founder accounts rather than peer-reviewed studies — but the patterns converge enough, and the etiquette rules are specific enough, to teach directly.

Indie Hackers is a real, long-running community (acquired by Stripe in 2017) where solo and small-team founders post revenue numbers and tactics publicly, under their own names or persistent handles. [Established] that the community and its acquisition are real and checkable; the individual success stories inside it are [Directional] at best — self-reported, single-account, and subject to survivorship bias, since founders who tried the same tactic and failed silently don't write "how I got my first customer" posts. With that caveat applied to every account below: Indie Hackers' own community thread, "How/Where did you find your first 1, 10 and 100 customers?", documents founders getting early customers through direct phone calls and in-person visits, cold calling, a single Reddit post that reached about 14,000 views and converted roughly 100 users, and one founder personally emailing 24 journalists. These aren't a formula — they're a category list: direct outreach, community posting, content-first, and press outreach, each real and checkable as an event, none independently audited as a repeatable number.

Reddit is not a monolith, and the single most generalizable rule from the research here is the one first-time founders get wrong most often: post where your buyer already is, not where other founders are. [Directional] — this rule converges consistently across multiple independent 2026 community guides on subreddit marketing, though none is peer-reviewed research. A founder-community subreddit like r/Entrepreneur is mostly founders selling to each other; it's a poor place to find an actual buyer unless your buyer is other founders. The better move is the vertical subreddit — one organized around your buyer's specific industry or profession, not around other founders — matching your buyer's actual profession: r/sysadmin or r/webdev for a developer tool, r/accounting or r/legaltech for vertical B2B software (B2B: business-to-business, meaning it's sold to companies rather than individual consumers). r/SideProject and r/AlphaAndBetaUsers are built for founders to show a product and ask for beta users, a narrower use case than finding a paying customer in a buyer's own community.

The etiquette matters as much as the targeting, and it's specific enough to state as a rule: the community norm, cited consistently as the "9:1" or "90/10" rule, is roughly nine genuine, non-promotional contributions — real comments, real help — for every one post that mentions your product. [Directional] — a de facto standard rather than written policy, enforced informally by moderators, and some subreddits enforce a stricter ratio or zero tolerance. A founder account that posts its product on day one, with no participation history, reliably gets removed or shadow-banned on most subreddits worth being in. The practical implication: the clock on finding a customer in a community starts weeks before you're allowed to mention what you're building, not the day you decide to try it.

A stronger, more rigorously reported source on this same question comes from outside the forum-anecdote tier entirely. Lenny Rachitsky — a former Airbnb product manager whose newsletter is one of the most-read in product and growth, and who sources his reporting from direct, named interviews rather than aggregating forum posts — documented how a set of real B2B companies found their first ten customers. [Directional] — named companies and attributed quotes, but journalism rather than peer-reviewed research. Figma's Dylan Field reached early customers through designers he already knew, plus a custom Twitter script to identify and message influential designers directly. Vanta mined Y Combinator's own alumni list for people already voicing compliance pain. Gong's first dozen customers came through a founder or employee's personal connection — every single one, section 2's mechanism showing up again in a different company's origin story. Figma's Sho Kuwamoto, in that same reporting, put the underlying logic in one line worth teaching directly: "It's all a matter of trust. Somebody I trust is going to say, you should use this tool." That's the bridge between this section and the next — trust, not tactics, is the resource all of this accumulates.

The Vanta example above is worth pulling out on its own, because it runs on a structurally different mechanism than either a personal weak tie or a public community, and the same research treats it as its own separate ring in the trust sequence for exactly that reason. Vanta's founders didn't reach that alumni list through anyone they knew personally — they combed a decade of Y Combinator's internal alumni platform, Bookface, for founders at adjacent companies who'd publicly voiced compliance pain, and reached out on the strength of shared program membership rather than any prior history with the specific person. [Directional] — same sourcing tier as the rest of this section's citations to Lenny Rachitsky's reporting: named, attributed, checkable at the level of the event, not independently audited. That's a third form of trust, alongside a weak tie's personal history and a community's shared turf: an institution — an accelerator, a specific investor's portfolio, a professional certification body — vouches for both sides at once, which is why a message that opens with "we're both YC alumni" or "I saw you're a [investor]'s portfolio company" can land even between two people who've never spoken, in a way a fully cold message can't. Two further attributed examples from the same reporting show the mechanism isn't specific to YC: Retool's founders filtered Crunchbase by companies that had recently closed a funding round in their target vertical, using the fundraise itself — public, dated, and checkable — as a signal of both budget and relevance; Sprig treated First Round Capital's own customer-discovery program, which arranges qualified founder meetings for its portfolio companies, as an acquisition channel in its own right rather than a fundraising perk. [Directional], same tier as above.

The obvious gap in all three examples is that they assume a founder is already inside some institution worth mining — a YC batch, a venture-backed startup with functioning investor relationships — and Marlowe, like most solo and small-business founders, is in neither. The mechanism does generalize further down, though the institutions get smaller and the evidence thins to the same self-reported tier as the community sources earlier in this section: a local small-business incubator's own alumni directory, an SBA or SCORE mentorship cohort, a paid trade or professional association's member directory, a vertical-specific accelerator built for one industry rather than startups broadly. The test for whether a given network belongs to this ring rather than the general-communities ring above is simple: does membership alone hand you a shared, checkable affiliation neither of you had to build personally? If yes, it's this ring. If it's a public forum anyone can join by showing up, it's the communities ring instead.

#Marlowe, communities, worked example

If Marlowe's warm-network path — the former colleague, the cousin, the boutique gym — hadn't worked, the research above points to two alternatives Marlowe could have run in parallel, both matching a realistic prospect for a local bookkeeping service better than a general startup community would. The first is a local small-business Facebook group — organized around local commerce rather than founders, where the actual buyer (a gym owner, a café owner, a solo attorney) already participates. Applying the 9:1 rule directly: Marlowe's first move there is weeks of genuinely answering other members' questions — explaining cash versus accrual basis, unprompted and un-billed — before ever mentioning that bookkeeping services are for sale. The second is a local Chamber of Commerce meeting: the offline version of the same targeting principle, a room selected for owner-operated local businesses, not for other freelance bookkeepers.

---

#4. Doing things that don't scale: manual delivery as a distribution strategy, not just a validation exercise

The third source, and the one most course content gets subtly wrong, is treated everywhere as a product-validation tactic — build a fake or manual version of the thing to test demand — when the more useful frame here is distribution. Manually doing the thing for one specific, named person you've identified is not only a way to learn whether the idea works. It is itself how you find that person, and how they find you when they tell someone else. The essay that names this pattern is Paul Graham's "Do Things That Don't Scale" (2013), worth citing directly rather than the folklore that's grown up around it, because the original argument is more precise than most retellings. [Established] — a primary, freely available essay on Graham's own site, drawn from years of Y Combinator's own portfolio observation. Graham's core claim: startups do not take off by themselves. Founders make them take off, almost always by doing something laborious and unscalable early — usually recruiting users manually, one at a time, by hand.

Three named cases carry the weight of this argument, and each is worth being precise about what's verified versus what's folklore, because the exact numbers attached to all three have drifted in retelling well beyond what any primary source actually confirms.

Stripe's "Collison installation" is the cleanest and best-documented case. Graham's own essay describes the Collison brothers' method for signing up early users: instead of sending a signup link, when a prospect agreed to try Stripe, the brothers would say "Right then, give me your laptop" and install the product on the spot, in person. [Established] that the term and behavior are real — Graham has confirmed coining "Collison installation" himself, and as recently as 2026 noted a YC founder who independently rediscovered the tactic and used it to sign up roughly 10% of his batch, meaning it's still live YC teaching, not a closed 2013 anecdote. What's not verified: some retellings claim it was specifically "nine lines of code" that got installed — untraceable to a Collison quote or Stripe's own account, and it reads as embellishment. [Speculative], worth dropping rather than repeating.

Airbnb's founders personally visiting and photographing early New York hosts is real at the level of the event, weaker at the level of the numbers that circulate around it. Brian Chesky has described it directly, in his own words, on the Masters of Scale podcast: "I remember we met with a couple hosts. It's winter. It's snowing outside and we're in snow boots. We walk up to the apartment and we went there to photograph the home." [Established] as a founder's own first-person account. But the figures that show up in nearly every retelling — a "$500 camera," "24 hosts," "bookings doubled in a week" — appear consistently across secondary blog posts, and a direct check of one of the most-cited sources for those numbers found it cites no primary source for any of them. [Speculative] — treat the visit and the photography intervention as verified, and any dollar figure or host count attached to it as unsourced folklore until a primary citation turns up.

DoorDash's founders manually dispatching orders by phone is the strongest of the three at the level of a direct, on-record founder quote. Tony Xu, in a 2015 Stanford Graduate School of Business interview, described it plainly: "When we first started, we were the drivers ourselves... After six months of doing deliveries, you learn it's really complicated... Humans are not good at parallel processing, which is what you need to do to solve peak demand. Software can solve these problems." [Established] — a direct, on-record founder quote, corroborated by a sourced Wikipedia timeline of the company's January 2013 launch as PaloAltoDelivery.com. Co-founder Stanley Tang, in a separate Y Combinator lecture, described the launch as fully manual: PDF menus with the founders' personal cell number in place of a checkout flow, Square to take payment, Google Docs to track orders. What's not independently confirmed: the widely repeated claim that Xu personally signed up the first 50 restaurants door-to-door — the recruiting method is well corroborated, the number "50" is not traced to a primary quote. [Directional] on the method, [Speculative] on the count.

The distribution logic tying all three together, and the reason this belongs in a lesson about finding a customer rather than validating a product: in every case, the founders identified a specific person or small set of people, then did something for them personally that would never work at scale — and that specificity generated both the learning and the customer relationship at once. There was no gap between "test whether this works" and "acquire the person it worked for." That's the pattern worth carrying into your own first sale.

There's a structural gap in this evidence worth naming rather than stepping past. Stripe, Airbnb, and DoorDash aren't a representative sample of founders who tried manual, founder-led recruitment — they're three companies whose manual-recruitment years got told and retold specifically because each one later became a large, venture-scale business, which is also the only reason a podcast, a Stanford GSB interview, or Graham's own essay bothered preserving the story. [Directional] — the founder-led tactics themselves are independently corroborated (the quotes and events cited above are on-record and checkable); what isn't checkable, and isn't available anywhere in this evidence base, is the much larger set of founders who ran the identical playbook — installing the product on a stranger's laptop, cold-visiting hosts, manually dispatching deliveries by phone — and got nothing for it. Nobody publishes a retrospective, and no founder gets a Stanford GSB interview, for a manual-recruitment push that quietly failed. This section can show the tactic worked often enough among the companies that survived to be written about; it cannot show the base rate, and treating three success stories as proof the tactic reliably works would be the same mistake section 3 already flagged about Indie Hackers' self-reported posts, applied here to much bigger names.

#Marlowe, concierge distribution, worked example

Marlowe's actual first customer was won using exactly this mechanism, and the specific shape of it matters. Once the former colleague's introduction produced a conversation with the boutique gym's owner, Marlowe didn't open with a pitch for the $600/month retainer. The opening offer was a free "books audit" — a concierge-MVP move in the same spirit as Zappos's Nick Swinmurn manually buying and shipping shoes he didn't yet have inventory for, or Manuel Rosso personally building one Austin mother's grocery lists by hand before Food on the Table had any software behind it. Marlowe spent a few unpaid hours going through the gym's actual books and came back with a real, specific finding: three months of miscategorized expenses quietly overstating the gym's tax liability. That's the Airbnb-photograph move and the DoorDash-phone-dispatch move applied to bookkeeping: doing the real work, by hand, for one named person, before any retainer existed, as the way of finding and winning that person rather than a separate step before finding them.

It's also where the gym owner's real objection surfaced, because a free audit that reveals a genuine problem doesn't automatically produce a signed retainer. The owner was already using — badly, by their own admission — a $40/month software subscription for the books, and balked at paying 15 times that for a person instead of a tool. That objection, and how a first-time founder without sales training actually answers it, is the subject of the next lesson; this lesson's job was only to get Marlowe into that room.

One additional example, briefly, to keep this general-purpose beyond bookkeeping: a SaaS founder (SaaS: software-as-a-service, a company selling ongoing access to software by subscription rather than a one-time purchase) building a narrow tool for freelance video editors would run the same three-part sequence — a weak-tie inventory turns up an old coworker now running a small editing studio; a Discord for freelance editors, matched to the buyer's profession rather than to other SaaS founders, supplies the community; and a manually-run, unscaled version of the tool delivered by hand to one named editor before the product is finished is this founder's version of the Collison installation.

---

#5. Widening the brainstorm: Traction's 19-channel checklist, and why the clock starts on day one

Sections 2 through 4 deliberately narrow the field to three specific paths, in a specific order, because those are the three that work with nothing yet proven. They aren't the only channels that exist, and it's worth being honest about where they sit inside a wider list a founder may already have heard of. Gabriel Weinberg and Justin Mares' Traction (2015) is the source of that wider list, and this platform's own Marketing course already covers the book's centerpiece directly — the Bullseye Framework, the three-ring brainstorm/rank/test process for choosing a channel once there's a real budget and something proven to test it against. Two smaller pieces of the same book are directly relevant to a founder still at zero customers and aren't taught anywhere else on this platform, so they belong here rather than nowhere.

The first is a claim about timing, not tactics. Traction's core structural argument — corroborated consistently across multiple independent secondary summaries (Dan Silvestre's and ReadingGraphics' book summaries, cross-checked against each other) — is that a founder should split time roughly evenly between building the product and finding traction for it, starting on day one rather than sequentially, on the logic that "almost every failed startup has a product — what failed startups don't have is enough customers." [Speculative] — this course could not verify the "50%" figure against Traction's primary text directly; treat it as a paraphrase consistently reported across independent secondary sources, not a page-cited quote, while the underlying direction — acquisition work starts alongside the product, not after it's finished — is the more load-bearing and better-corroborated part of the claim. It's worth naming plainly because it corrects the exact instinct a first-time founder defaults to: finish the product, or at least get it presentable, before doing anything that looks like sales. Marlowe didn't wait for a polished monthly-close process before running the weak-tie outreach in section 2 — the free books audit in section 4 happened while the actual service was still being refined, not after it was done, because there was no evidence yet about which parts of the product needed refining until a real prospect reacted to it.

The second is a checklist, not a rule. Traction's 19 named channels — targeted blogs, publicity, unconventional PR, SEM (search engine marketing), social and display ads, offline ads, SEO (search engine optimization), content marketing, email marketing, engineering as marketing, viral marketing, business development, sales, affiliate programs, existing platforms, trade shows, offline events, speaking engagements, and community building — are brainstorming input for the Bullseye process's first step, not a to-do list to work through in order. [Speculative], same source and same caveat as above. Most of the nineteen don't apply yet at zero-customers scale — trade shows and offline ads assume a budget and an audience neither of which exists this early — and several of the ones that do apply are simply this lesson's own three paths under different names: "existing platforms" and "community building" are section 3's communities discipline; "business development" and "sales" are what section 4's concierge delivery actually is, once a prospect says yes. The remainder — content marketing, SEO, affiliate programs, engineering as marketing — are real channels, just not ones a founder with no proven offer yet should be running: they're the Marketing course's territory, once there's a repeatable result worth investing in scaling.

#Marlowe, the wider list, worked example

Run Marlowe's actual channels against the checklist and the pattern holds. The weak-tie introduction to the boutique gym is "existing platforms" and a personal network at once; the Chamber of Commerce meeting from section 3 is "offline events"; the free books audit is "business development" in Weinberg and Mares' own terms. None of the other fifteen — content marketing, SEM, affiliate programs, trade shows among them — did any work in getting Marlowe's first customer, and that's the point of naming the checklist honestly rather than pretending nineteen equally weighted options exist for a founder at zero customers: most of them don't apply yet, and the ones that do are the three this lesson already teaches.

---

#6. Worksheet: map your own warm network and communities

Fill this in against your own business — not Marlowe's — before doing any outreach. The point of this worksheet is the same as every worksheet in this course: a framework you haven't run against your own numbers and your own names isn't yet useful, it's just an idea you agree with.