How do you turn users into advocates?
Advocates are made, not marketed to. They emerge when users experience something so specifically useful—so clearly built for them—that sharing it feels natural rather than prompted. For early-stage founders, this means the path to word-of-mouth starts with depth of relationship, not breadth of reach.
Start with a narrow group you can truly delight
The biggest mistake founders make is trying to make everyone like their product a little, rather than making a small group love it completely. When you concentrate on a tight, well-defined segment, users feel that the product was made for them specifically—not for 'people like them' in some abstract marketing sense, but for their actual job, their actual workflow, their actual frustration. That feeling of being seen is the precondition for advocacy.
Paul Graham's observation about Facebook's early strategy illustrates this precisely: by building exclusively for Harvard students first, Facebook created users who experienced the product as their natural home—not a general social network they happened to use, but something that belonged to them. That sense of ownership is what makes people recommend a product unprompted. When you expand too early, you dilute that feeling before it has time to root.
For your startup, this means resisting the urge to open the doors wide. Pick the smallest defensible user segment where you can create an overwhelming, undeniable experience. Get that group to the point where they'd be genuinely upset if the product disappeared. Advocacy follows from that emotional stake—it doesn't precede it.
Do the unscalable work that creates real loyalty
Early users don't become advocates because of your onboarding flow or your NPS survey. They become advocates because someone from your company actually helped them succeed. That means phone calls, on-site visits, same-day responses to support tickets, and personally walking users through problems. None of this is scalable in the long run, and that's exactly why it works: it communicates that you care in a way no automated sequence can replicate.
Paul Graham has written about how Airbnb's founders went door-to-door in New York meeting hosts, taking photos of their listings, and improving the product in response to direct feedback. The company was fragile at the time—those weeks of in-person engagement were the difference between the product catching and dying. The relationships built in that period created advocates who talked about Airbnb not just because the product was good, but because the founders had treated them as partners.
Every high-touch interaction in your early days is a deposit into the advocacy bank. Users who've experienced that level of attention become your most credible salespeople because they have a real story to tell. They're not repeating a tagline—they're describing a specific moment when your product or your team made their work better. That specificity is what makes word-of-mouth spread.
Build around the user's real outcome, not your feature set
Advocacy requires users to understand what changed for them because of your product. If your product is defined by its features, users will describe it in terms of features—'it has X integration' or 'it does Y automatically.' But advocates describe outcomes: 'we closed 30% more deals,' 'I stopped spending Sundays on invoicing,' 'our team finally stopped missing deadlines.' The shift from feature language to outcome language is a signal that someone has moved from user to advocate.
This means your job in the early relationship is to help users connect the product to the result they care about. Don't just show someone how to use a feature—follow up to ask whether it solved the problem they brought to you. If it didn't fully solve it, fix the gap or help them find a workaround. The goal is for every user to have at least one moment where they think, 'this product actually did the thing I needed.' Without that moment, even satisfied users are passive—they'll recommend you if asked, but they won't bring you up unprompted.
When you find users who are already getting strong outcomes, talk to them in depth. Understand the specific sequence of events: what they were struggling with before, what they tried, how they found you, and what changed. Those stories become your sharpest marketing, but more importantly, they reveal the pattern you need to reproduce for every new user you onboard.
Make advocacy easy and natural, not a campaign
Even users who love your product need a low-friction path to share it. Referral programs can help, but the most durable advocacy happens when sharing the product is a natural extension of how someone uses it. This could mean the product itself is visible to others—a report someone sends, a link that requires a recipient to interact with something, a notification that arrives from your platform in someone's inbox. When non-users encounter your product through a user's workflow, advocacy becomes ambient rather than effortful.
Beyond product design, you can make advocacy easier by giving your best users language and context. When a user tells you they've been recommending you, send them something useful—a one-pager, a short case study, a template, or just a crisp sentence that captures what problem you solve. Users who are already advocating often don't know how to explain you clearly to someone who hasn't seen the product. Help them. A user who was vaguely positive becomes a precise, confident referrer when they have a clean narrative to work with.
Finally, recognize advocacy when it happens. If someone referred a new user, thank them personally—not with an automated email, but with a message that acknowledges the specific thing they did. If someone wrote about you publicly, amplify it. These signals tell advocates that their efforts matter to you, which reinforces the relationship and makes them more likely to advocate again. Advocacy is a behavior, and behaviors that are recognized tend to repeat.
“The feedback you get from engaging directly with your earliest users will be the best you ever get.”
— Paul Graham, source
The one thing to do
This week, identify the three users who've gotten the most value from your product, call them personally, understand the exact outcome they got, and ask directly who else they know with the same problem.
Frequently asked questions
How many advocates do you actually need early on?
Even five or ten deeply committed advocates can generate meaningful referral volume in a focused market. The quality of the advocacy—how specifically and confidently users describe you—matters more than the number. One user who gives a detailed, outcome-focused recommendation to three well-matched prospects outperforms fifty passive users who mention you in passing.
What's the difference between a satisfied user and an advocate?
A satisfied user stays. An advocate recruits. The gap is usually emotional investment—advocates have a personal story about how your product changed something real for them, and they feel some ownership over your success. Satisfaction is passive; advocacy is active and requires that moment of genuine impact.
Should you build a formal referral program to generate advocates?
Referral programs can accelerate sharing among users who are already advocates, but they rarely create advocates from scratch. If users aren't recommending you without an incentive, adding a cash reward usually produces low-quality referrals from people motivated by the reward rather than the product. Fix the advocacy gap first, then layer in a program to amplify it.
How do you know when a user has become an advocate?
Watch for unprompted behavior: they tag you on social media, they mention you in a community without being asked, they connect you to someone specific by name, or they push back when a colleague dismisses your product. Any of these signals mean they've moved beyond satisfied customer into genuine advocate territory.
Sources
- gstack: skillify/SKILL.md — Garry Tan
- Billionaires Build — Paul Graham
- Do Things that Don't Scale — Paul Graham
- How to Raise Money — Paul Graham