Marketing & strategy
How to Build a Book Street Team
A practical guide to building and running a book street team — what a street team does, how to recruit members, what to ask of them, and how to keep them engaged across book launches.
A street team is a small, committed group of readers who help amplify your book launch in exchange for early access, exclusive content, and community. The term borrows from music industry promotion — street teams once literally walked neighborhoods putting up posters for concerts — but the modern author street team operates almost entirely online. Its members post reviews on launch day, share your cover reveal on social media, talk about your book in reader groups, and create the early momentum that changes a book's trajectory from "quiet release" to "worth noticing."
The key word in that description is committed. A street team is not a mass mailing list or an open ARC pool. It is a smaller, more invested group of readers who have opted into active participation, not just passive receipt. Managing that distinction well — being clear about what you are asking and why — is what separates a street team that burns through goodwill from one that sustains itself across multiple launches.
What a Street Team Does
A functional street team performs a concentrated set of tasks around your book launch. The core activities are:
Posting reviews on launch day. This is the most high-value thing a street team member can do. Amazon's algorithm rewards books that accumulate reviews quickly in their first days of availability. A cluster of genuine, honest reviews on launch day creates social proof for new readers browsing your title and signals to the algorithm that the book is generating engagement.
Sharing cover reveal content. Cover reveals are a natural early entry point for street team activity. Providing team members with the cover image, a short blurb, and suggested caption language lowers the friction to participation and ensures the reveal is coordinated.
Word-of-mouth in reader groups. Street team members who participate in Facebook reader groups, Goodreads groups, or genre-specific communities can naturally mention the book in relevant conversations — recommending it in "what should I read next?" threads, responding to posts asking for comparable books, or sharing their honest reactions. This is the most powerful and the least controllable street team activity. You cannot script organic conversation, but you can ask team members to share genuinely if they enjoyed the book.
Amplifying social content. Sharing, retweeting, and commenting on your launch posts increases their visibility in social algorithms. Even members who do not have large followings contribute to this through simple shares and authentic comments that increase engagement signals.
Participating in launch events. Many authors run virtual launch events — live readings, Q&A sessions on Instagram or Facebook Live, or launch-day giveaways. Street team members who show up, comment, and share these events extend their reach organically.
Street Team vs. ARC Team
These two roles are related but distinct, and conflating them creates confusion and resentment.
An ARC (Advance Review Copy) team receives pre-release copies of the book for the specific purpose of posting reviews before, on, or shortly after launch. The relationship is transactional in the most literal sense: they get a free book; you get an honest review. ARC team members may have no ongoing relationship with you and may never interact with your content outside of this one exchange.
A street team is an ongoing relationship. Street team members are readers who care enough about your work to participate in your launch activities beyond just posting a review. They might have been reading you for years, or they might be newer fans who connected with your brand and wanted to be involved. The defining characteristic is engagement and commitment over time, not just for one book.
In practice, the overlap is significant. Many street team members will also receive ARCs and post reviews. The distinction matters most when you are setting expectations: if you recruit readers for a "street team" but only ever ask them to post reviews, you are actually running an ARC program with misleading branding, and participants who expected community will feel let down.
How Many People You Need
Ten to fifty members is the practical range for most indie authors. Larger is not inherently better. A street team of fifteen highly engaged members who post reviews, share content, and show up to launch events consistently outperforms a list of two hundred people who agreed to join but rarely participate.
Team size should be calibrated to your capacity to manage it. Every street team member you add is a relationship to maintain. If your team grows to eighty people but you can only realistically communicate meaningfully with twenty, you have seventy people who will drift into disengagement. A smaller, well-managed team with consistent communication will outperform a larger, neglected one every time.
For debut authors, ten to twenty members is a realistic and manageable starting point. As you build more launches and a stronger reader community, the team can grow with it.
Where to Find Street Team Members
Your email list is your most reliable source. Readers who have already opted into your list, opened your emails, and engaged with your content are the most likely candidates for meaningful street team participation. They have already demonstrated sustained interest.
Facebook reader groups. Most genres have active Facebook groups for readers. Participate genuinely in these groups before recruiting — posting a cold "join my street team" message in a group you have never engaged with produces poor results and can come across as spam. Readers who have seen you in conversation are far more likely to respond to an invitation.
Bookstagram and BookTok. Readers who actively create content about books on Instagram or TikTok are often enthusiastic street team candidates. They already have the habit of sharing what they read. A few well-connected Bookstagram or BookTok members can significantly extend the reach of your launch content.
Previous reviewers. Anyone who has posted a genuine review of your previous work is a warm lead. They read you, liked you enough to post publicly about it, and may welcome an invitation to be more involved.
Your newsletter. Send a dedicated email inviting your list to apply. Be specific about what the team does, what they will receive, and what you are asking of them. Vague invitations ("want to be part of my team?") produce lower-quality responses than specific ones ("I'm looking for fifteen readers who can post a review on Amazon launch day and share the cover reveal on social media. In exchange, you will receive a free copy two weeks before publication").
What to Offer in Exchange
Street team members volunteer their time, attention, and social credibility. The exchange should feel fair to them.
Advance copies (ARC or galley format) are the baseline offer. Most street team members expect a free pre-release copy. This can be digital (EPUB or MOBI, typically via BookFunnel) or physical for members whose participation you want to especially recognize. Physical advance copies cost real money, so they are usually reserved for your most active members or those with large audiences.
Exclusive content. Deleted scenes, alternate POV chapters, extended epilogues, or early excerpts of the next book give street team members something that general readers cannot get. This is a high-value offer with low monetary cost to you.
Signed copies. A signed finished copy for your most active members is a meaningful gift that costs you postage and a few minutes. For readers who care about books as objects, this matters.
Acknowledgment in the book. Including a street team acknowledgment page — or individual names in the acknowledgments — is a deeply appreciated gesture for dedicated members. It makes the book a tangible record of their participation.
Community access. The community itself is part of the value exchange. Access to a private group, early announcements, and the experience of being "in the room" where your creative decisions happen is genuinely compelling to many readers.
Recruiting Your Team
The recruitment message should accomplish four things: explain what the team does, describe what members will receive, make clear that participation is voluntary without pressure, and tell them how to join.
A sample framing: "I'm putting together a small street team for [Book Title], releasing [Date]. Team members will receive a free digital advance copy two weeks before launch. In exchange, I'm hoping you'll post an honest review on Amazon on launch day and share the cover reveal on your social media if you feel comfortable doing so. There is no pressure to post if you don't enjoy the book — honest reviews only. [Link to form or reply to this email to join]."
For more than a handful of members, an application form (Google Form or Typeform) is worth the minor setup effort. It filters for readers who are genuinely interested — anyone unwilling to fill out a short form is unlikely to show up on launch day — and gives you contact information and social handles in a structured format.
Open recruitment (anyone can join without an application) produces larger teams with lower average engagement. Application-based recruitment produces smaller teams with higher engagement. For most authors, the application approach is worth it.
Onboarding
Once someone joins your team, they need to understand what is expected of them immediately. Do not assume they remember everything from the recruitment message. A welcome packet — sent as an email or a document in your team's communication channel — should cover:
- What you'll be asked to do: A clear, specific list. Not vague categories, but actual tasks: post a review on Amazon, share the cover reveal graphic on Instagram, show up to the virtual launch event.
- What the timeline looks like: When they will receive their ARC, when the cover reveal happens, when launch day is, when reviews should go live.
- What you are NOT asking for: Explicitly state that you want honest reviews, not positive ones. This matters ethically and practically — readers who feel free to be honest produce more credible reviews.
- How you will communicate: Where team announcements will be posted, how often, and what the expected time commitment is per week.
- How to ask questions: A clear contact method for when things are unclear.
Onboarding is where you set the tone. A professional, organized welcome makes team members feel like they have joined something real. A disorganized or absent welcome makes them question whether they will actually receive their ARC.
Managing Communication
Three platforms dominate author street team communication, and each has meaningful trade-offs:
Facebook Group is the most common choice because most readers already have Facebook accounts. A private Facebook group is easy to set up, supports file sharing and events, and most members will already receive notifications. The downsides: Facebook's algorithm suppresses group posts from some members' feeds, and younger readers are less likely to be active Facebook users.
Discord is increasingly popular, particularly with romance, fantasy, and sci-fi authors whose readers skew younger. Discord supports structured channels (separate channels for announcements, reviews, social sharing, general chat), voice chat, and real-time engagement. It requires members to set up or already have a Discord account, which is a mild barrier.
Email newsletter (a dedicated segment or list) is the lowest-friction option for members who are already on your list. It does not require any additional platform. The downside is that it is one-directional — you can send announcements but members cannot easily talk to each other, which limits the community element.
Many authors use a combination: a Discord or Facebook group for community interaction and a dedicated email for formal announcements and time-sensitive information. Whatever you choose, pick one primary channel and use it consistently. Teams that are spread across multiple platforms with inconsistent posting drift into inactivity.
What to Ask of Your Team
Specificity is essential. Vague asks ("tell your friends about my book") are easily ignored. Specific asks with clear actions are acted on.
| Period | Task | Notes |
|---|---|---|
| 3–4 weeks before launch | Cover reveal: share the graphic with caption | Provide the graphic and suggested caption; let them personalize |
| 1–2 weeks before launch | Read the ARC; note any reactions to share | No required format; just ask them to read |
| Launch week | Post review on Amazon and/or Goodreads | Specify that reviews should go live on or after release date |
| Launch day | Share launch day post; comment on your announcement | Provide shareable graphics and caption ideas |
| 1 week after launch | Share any reader reactions or personal posts | Optional but high-value for algorithmic momentum |
| Inter-launch period | Engage with newsletter; mention book organically | Low-ask; no pressure |
Keep the total ask reasonable. A reader who enjoys your work and wants to support you will happily spend two to three hours around a launch: reading the ARC, writing a review, and sharing a few posts. A reader who is asked to post on every platform every day for two weeks will burn out and disengage.
Keeping the Team Engaged Between Launches
Street teams that only hear from authors at launch time become less responsive with each book. Members feel used rather than valued. The solution is low-frequency, high-quality communication between launches.
Exclusive updates. Tell your team about your next project before you announce it publicly. Share a working title, a first sentence, a cover concept in progress. These small previews make members feel genuinely inside your creative process.
Early news. Let your team know about rights deals, awards, or positive reviews before public announcements. Being first is a meaningful gesture.
Non-ask community posts. Ask your team what they are reading. Share a reading recommendation. Post a question about your work-in-progress and genuinely respond to their answers. Community does not have to be launch-related to build the loyalty that makes launch participation more reliable.
Common Street Team Mistakes
Asking too much. Twenty tasks across three platforms in two weeks is too many. Pare your ask to the three or four highest-impact activities and let everything else be optional.
Giving too little. A digital copy of the book is the minimum. If you want sustained engagement, you need to provide consistent value to your team between launches — exclusives, community, acknowledgment.
Not communicating regularly. A team that hears from you only when you need something will respond accordingly. Regular, non-transactional communication is the investment that makes transactional asks land well.
Recruiting too broadly. Signing up two hundred readers who are only mildly interested creates a management burden and produces lower engagement than twenty highly motivated members.
No follow-up after launch. After launch day, send your team a genuine thank-you that acknowledges what they did specifically. "Seven of you posted reviews on launch day and it mattered — the book hit [milestone] in the first week" is more meaningful than a generic thank-you note.
For distributing advance copies to your street team, see the Advance Review Copies Guide for detailed guidance on ARC distribution platforms, timing, and reviewer follow-up. For building the email list from which your best street team members will come, see Building Your Email List as a New Author.
FAQ
How far in advance should I start recruiting a street team? For a debut book: six to eight weeks before launch, which gives you time to recruit, onboard, distribute ARCs, and allow time for reading before reviews go live. For subsequent books with an established team: four to six weeks is sufficient if you are working with existing members.
Do street team members have to post positive reviews? No, and being explicit about this is important. You want honest reviews. Readers who post dishonestly positive reviews out of obligation produce reviews that other readers can identify as inauthentic, and they erode the trust that makes reader recommendations valuable. Ask for honest reviews. If a member did not enjoy the book, they are under no obligation to post.
Can I have a street team if I have a small following? Yes. You do not need a large existing audience to start a street team. Your first team might be eight people from your email list and two from a reader group you participate in. A ten-person street team that posts genuine reviews on launch day is a meaningful advantage for a debut author.
What happens if team members don't post reviews? Some will not. Expect roughly 40–60% follow-through even from well-managed teams. Do not chase, pressure, or publicly call out members who did not participate. Send one gentle reminder close to launch day ("If you've had a chance to read and would like to post a review, launch day is [date]") and leave it at that. Pressure produces inauthentic reviews and destroys team morale.
Should I pay street team members? No. Payment for reviews violates Amazon's and Goodreads's terms of service and constitutes paid endorsement under FTC guidelines unless disclosed. The exchange is early access and community, not payment. If a team member has a large platform and you want to work with them in a more formal promotional capacity, that is a separate relationship governed by different rules.
LiberScript produces professionally formatted ARCs in EPUB and PDF formats that you can distribute directly to your street team via BookFunnel or email.
Get started with a Day pass to format your manuscript today.
Related guides
Ready to put this into practice?
LiberScript brings writing, critique, design, and export into one workspace, with no subscription.