How to Build a Book Launch Team (Street Team) for Your Release

A book launch team — sometimes called a street team — is a group of readers who agree to help spread the word about your book in the weeks around its release. They read your book early, post reviews, share on social media, and generally generate the buzz that signals to other readers (and to Amazon's algorithm) that your book is worth paying attention to. Done well, a launch team turns your solo release into something that feels like an event.

Launch teams don't require a massive existing audience. Authors with modest followings — a few hundred email subscribers, a small social presence — can assemble teams of 20 to 50 enthusiastic readers who make a real difference at release. The key is setting clear expectations, making it easy to participate, and treating your team members as the genuine allies they are.

This guide covers everything from recruitment to coordination to what actually makes a launch succeed versus fall flat.

What a Launch Team Does

At its core, a launch team amplifies your launch in ways that are otherwise hard to manufacture. Members typically:

• Read your book before release (via an advance copy you provide)
• Post a review on Amazon on or after your release date
• Share about the book on social media
• Add the book on Goodreads and mark it as read
• Recommend the book to friends or family who read in your genre

The cumulative effect is an early cluster of reviews, social shares, and reader word-of-mouth that gives your book credibility and visibility right when it matters most — the launch window.

Launch Team vs. ARC Team: Understanding the Difference

These two terms get used interchangeably but describe slightly different things. Knowing the distinction helps you structure the right ask for the right group.

	Launch team (street team)	ARC team
Primary purpose	Amplify the launch through reviews and social sharing	Provide advance reviews and feedback
Timing	Active during launch week and the weeks surrounding it	Receive books 4–8 weeks before release
What members receive	Early ebook access, exclusive content, community access	Advance review copy (ARC) of the book
What they do	Reviews, social posts, word of mouth	Reviews (primarily); sometimes feedback
Overlap	High — launch team members often serve as ARC readers	ARC readers may or may not be launch team members
Commitment level	Higher — multiple tasks over several weeks	Lower — read and review

In practice, many indie authors combine these roles: the same group receives the ARC and serves as the launch team. That's a perfectly workable approach, especially for authors earlier in their career. Just be clear about what you're asking when you recruit.

How Large Does a Launch Team Need to Be?

There's no magic number, and bigger is not always better. A team of 50 people who are genuinely engaged will outperform a team of 200 who don't follow through.

Realistic ranges by platform size:

• Small platform (under 500 email subscribers): 15–35 members. Achievable through your list, social followers, and genre communities.
• Mid-size platform (500–2,000 subscribers): 30–80 members.
• Established platform (2,000+ subscribers): 80–200+ members.

These are starting points, not targets. The percentage of people who follow through on tasks will always be lower than the number who sign up — plan for roughly 50–60% active participation from the people who join. If 40 people join and 22 post a review, that's a success.

Where to Recruit Launch Team Members

The quality of your recruits depends heavily on where they come from. Some sources consistently produce more engaged team members than others.

Your email list is by far the most reliable source. People on your list have already opted in to hear from you — they're invested in your success. A dedicated recruitment email explaining what the team is, what you're asking for, and what they'll receive should be your first outreach. See the building your email list guide for how to grow this asset before your next launch.

Social media followers are a secondary source. Post an open call for team members on your primary platforms. TikTok and Instagram can work well for this, especially if you've built any engagement around your book already. Followers who comment regularly or engage with your posts are more likely to follow through than passive followers.

Previous readers and fans — anyone who has emailed you, messaged you, or left a review of a previous book — are gold. These readers already like your work. A personal outreach message asking if they'd like to read your next book early has a high response rate.

Genre communities — Facebook groups for readers in your genre, subreddits, Discord servers — can be useful but require more vetting. Readers from these communities may not know your work yet, which can affect their buy-in. Be clear in any community post what the commitment involves.

What to Offer Launch Team Members

Your launch team is doing you a real favor. In return, they should receive genuine value:

• Early access to your ebook: This is the primary incentive. Getting to read the book before anyone else is exciting for readers who love your work.
• A personal thank-you in the book's acknowledgments: Simple, costs nothing, means a great deal.
• Access to a private community: A Facebook group or Discord server just for team members creates belonging and is where you share updates, exclusive content, and behind-the-scenes looks at your release.
• Exclusive content: A deleted scene, an alternate POV chapter, a bonus short story, author notes on the writing process. Something no one else gets.
• Early notification of future releases: Team members get the next ARC offer first.

You do not need to pay your launch team (more on this in the FAQ). The right readers will participate because they love your work and enjoy being part of the inner circle — not for compensation.

What to Ask Launch Team Members to Do

Clarity is everything here. When people join without a clear list of what's expected, most will do nothing. When you give a specific, time-stamped task list, participation rates are dramatically higher.

Task	When to request	Importance
Read the book and note thoughts	3–4 weeks before release	High — foundation for all other tasks
Add book on Goodreads (mark as read, add rating)	Release week	High — feeds Goodreads discovery
Post review on Amazon	On or after release date (not before)	Very high — critical for launch visibility
Share on social media	Release week	High — creates visible buzz
Tell friends/family who read your genre	Any time	Medium — word of mouth
Vote on Goodreads Listopia lists	Release week or after	Low-medium — supports long-term discoverability
Share in genre Facebook groups (where appropriate)	Release week	Medium

One important note on Amazon reviews: team members should not post their reviews before your release date on Amazon. Amazon's system can flag or remove pre-release reviews on some titles. Release day and onward is the safe window.

Setting Up a Launch Team Hub

Your team needs somewhere to gather, get updates, and receive their materials. Three main options:

Facebook Group: Easy to set up, most readers already have Facebook. Post updates, share files, answer questions. The downside is reduced organic reach — Facebook shows group posts to fewer members than you'd expect. Still the most common choice because of its accessibility.

Email group: Run everything through email. Lower friction for members who aren't on Facebook, but lacks the community feel of a group. Works well for smaller teams or as a supplement to another platform.

Discord server: Better for ongoing community, stronger engagement from members who are comfortable with Discord. Skews younger. Channels let you organize materials, announcements, and casual conversation separately. Worth considering if your genre has a strong Discord presence (fantasy, sci-fi, and romance communities tend to).

Most authors use a Facebook group as their primary hub and email as a backup for members who aren't responsive there. Whatever you choose, set it up at least three weeks before you plan to send ARCs — you want the space ready before members arrive.

The Launch Team Timeline

A well-structured timeline prevents the chaos that derails most first-time launch team efforts.

8–10 weeks before release: Recruit your team. Send the invitation to your email list, post on social media, reach out personally to past readers. Give people a one-to-two-week window to sign up.

6–8 weeks before release: Set up your team hub (Facebook group, Discord, etc.). Send ARCs. Introduce yourself and the book. Explain the task list clearly and set expectations about the timeline.

4 weeks before release: Check in. Remind members what's coming. Share exclusive content (a deleted scene, cover reveal if not already public). Keep energy high.

2 weeks before release: Send a reminder with the specific tasks you'll be asking them to complete. Give them the exact links they'll need (Amazon page, Goodreads page).

Release week: Send the task list with links. Thank them in advance. Make it feel like a celebration, not an obligation.

One week after release: Follow up. Thank everyone who participated. Share any exciting news (sales rank, review count). This closes the loop and sets the stage for your next launch.

How to Manage the Team Without Burning People Out

The single biggest mistake authors make with launch teams is over-asking. When every email is another request, people tune out or quietly disengage. A few principles that keep teams engaged:

Give more than you ask. The ratio of value-to-request should feel generous to your members. If every communication is a task, that's a grind. If you share exclusive content, exciting news, and gratitude regularly, the occasional task request lands well.

Keep asks specific and bounded. "Help spread the word!" is paralyzing. "On Tuesday, share this graphic to Instagram with the caption below" is actionable. The more specific your asks, the higher your completion rate.

No guilt for non-participation. Acknowledge that real life happens and participating is optional. The readers who feel pressured become the ones who quietly disengage and don't join your next team.

Say thank you publicly and specifically. Name members in your newsletter, thank the team on social media, acknowledge them in the book. Public recognition matters to people who care about your work.

What Makes a Launch Team Succeed vs. Fail

Succeed:

• Team members are recruited from your existing audience (people who already like your work)
• Expectations are set clearly before people join
• Communication is consistent but not overwhelming
• Tasks are specific with exact timing and links provided
• The team hub is active and welcoming, not just a notice board

Fail:

• Members recruited cold from communities where no one knows your work
• No onboarding — people join and hear nothing for weeks
• Vague asks with no clear timing
• Too many requests, too close together
• No follow-up or thank-you after the launch

The difference between a launch team that delivers real results and one that fizzles is almost always in how well the author manages communication and expectations — not in the size of the team.

Frequently Asked Questions

Should you pay your launch team? Generally, no. Payment creates a transactional relationship that actually undermines the authenticity reviewers need to post. Amazon's review policies prohibit reviews given in exchange for compensation, and paying launch team members could put those reviews at risk. What team members want is the book early, a sense of belonging, and acknowledgment — not money.

Can launch team reviews be posted on Amazon before the release date? It's safer to wait until release day. Amazon has been known to flag and remove pre-release reviews on some titles, though the policy isn't uniformly enforced. Avoid the risk by asking your team to wait until launch day to post on Amazon. Goodreads has no such restriction.

How do you keep your launch team engaged book to book? Keep the community active between launches with occasional exclusive content — a short story, a character Q&A, updates on your current work in progress. A group that goes silent for a year between books will need to be rebuilt. Low-frequency engagement (once a month or every six weeks) is enough to maintain the relationship.

How far in advance should you build your launch team? Ideally, start recruiting six to eight weeks before your release date. You need time for readers to actually read the book — rushing this produces fewer reviews and worse social content. Factor the launch team timeline into your overall book launch plan.

What if nobody signs up for my launch team? If you have a small platform, your team will be small. That's okay. A launch team of ten engaged readers who follow through beats fifty who don't. Focus on growing your email list and reader relationships between launches so each successive team is larger. The building your author platform guide covers the long-term approach.

Do I need a launch team for every book? It's worth doing for every release, even if the team is small. The early reviews matter most for books that don't have years of accumulated social proof. For a backlist title you're re-promoting, the calculus changes — but for any new release, the launch window is critical and a launch team is one of the best tools you have.

Bottom Line

A launch team is one of the highest-leverage things you can do for a book release. It costs no money, requires no advertising expertise, and creates the kind of authentic word-of-mouth that paid marketing can't replicate. What it requires is genuine relationships with readers, clear communication, and respect for the people who give their time to support your work.

Start building your email list now if you haven't — it's the foundation your future launch teams will be built on. Treat every reader who reaches out as a potential team member. By the time your next book is ready, you'll have a group of people who are genuinely excited to help.

Make sure your book is ready when you recruit your team. Format your manuscript with LiberScript and have your ARC files export-ready before you open recruitment — nothing deflates a launch team faster than delays getting the book into their hands.