Last reviewed by Robert Prime — May 2026
Introduction
A launch team is a group of super-fans, repeat reviewers, and small influencers who agree to support your book launch with reviews and social media posts. Done right, it can produce 30-80 reviews in launch week and a meaningful Amazon BSR boost.
Done wrong, it produces flake-outs, missed reviews, and reader-relationship damage. This guide covers how to build, brief, and run one — without crossing Amazon's terms of service.
What a launch team is — and isn't
It is:
- A group of fans who commit to honest engagement during launch week
- Free ARC distribution + review + social amplification
- A community of super-fans who get insider access
It isn't:
- Paid reviewers (illegal under Amazon TOS)
- Guaranteed positive reviews (reviews must be honest)
- A substitute for marketing
- The same as an ARC team (more focused, smaller, higher-engagement)
The line between ARC team and launch team is fuzzy. Many authors merge them; some keep launch team as a smaller, more committed subset.
Team size — how many you actually need
For most indie authors:
- 5-20 members: good for first launches, manageable, intimate community
- 30-60 members: sweet spot for established authors with 2,000+ subscribers
- 80+ members: large team, requires more management, typical for top-tier indies
A team of 30 committed members produces more results than a team of 100 disengaged ones. Quality over quantity.
Where to recruit
Tier 1: Your engaged newsletter subscribers
The strongest recruits. Email subscribers who:
- Opened 5+ of your last 10 emails
- Have replied to you previously
- Have purchased multiple books
- Have left positive Amazon reviews on previous books
Invite directly: "I'm building a launch team for [Book X]. As one of my most engaged readers, would you be interested?"
Expected conversion: 5-15% of engaged subscribers say yes.
Tier 2: Repeat ARC reviewers
People who reviewed your previous books via ARC platforms. They already know your work and the ARC process.
Tier 3: Social media followers
Especially Bookstagram or BookTok followers who engage with your content. Limit to those with track record of book content.
Tier 4: Cold ARC platform recruits
If you need to fill out the team, use ARC platforms (StoryOrigin, BookSirens) for the rest. Lower commitment level but adds reviewer breadth.
How to invite
The recruitment email/post should be specific:
Subject: Want to join my launch team for [Book Title]?
Body:
Hi [Name],
I'm building a launch team for my new book, [Book Title], releasing on [Date].
Launch teams are a group of about [25] readers who commit to:
- Reading an advance copy 4-6 weeks before launch
- Posting an honest Amazon review within 7 days of launch day
- Sharing the cover/book on social media (optional)
In exchange, you get:
- Free advance copy + finished book on launch day
- Behind-the-scenes content I don't share publicly
- Access to a private community of fellow team members
- My eternal gratitude
If you're interested, reply to this email and I'll add you to the team. Spots are limited and first-come first-served.
[Your name]
Note: no positive-review promise. Honest reviews only. This is legally + ethically essential.
The launch team brief (what to send team members)
Once recruited, send a clear brief document. Should include:
1. Dates:
- ARC delivery: [Date — 4-6 weeks before launch]
- Review goal: [Date — within 7 days of launch]
- Social posts: [Date — launch day if possible]
2. What's expected:
- Read the ARC
- Post an honest review on Amazon (UK and/or US — both ideal)
- Optional: cross-post review to Goodreads
- Optional: share cover image + 1-line endorsement on social
3. What's NOT expected:
- 5-star reviews regardless of opinion (be honest)
- Lengthy reviews
- Multiple social posts
- Active group participation
4. How to do it:
- Where to download the ARC (BookFunnel link)
- Where to post the review (Amazon, Goodreads links)
- Sample social copy + cover graphics (optional templates)
- The team community link (Facebook group or Discord)
5. Thank-you:
- What they get: free finished book, behind-the-scenes content, dedication mention (optional)
Managing the team
Where to host the team
Private Facebook group — most common. Free. Easy for members. Limited engagement features.
Discord server — better for active engagement. Free. More setup work.
BookFunnel Team feature — purpose-built for launch teams. £100/year + delivery. Integrates with ARC distribution.
Telegram group — simple. Free. Works for international teams.
Email-only — works for smaller teams. Members reply, you forward updates.
For first-time launch teams: a private Facebook group is fine. Upgrade to Discord or BookFunnel Team for second/third launch.
Communication cadence
4 weeks before launch: ARC delivered. Welcome message. Set expectations.
3 weeks before: Check-in. "How's the read going? Any questions?"
2 weeks before: Friendly nudge. "ARC reading should be complete soon. Looking forward to your reviews on launch day."
1 week before: Final reminder. Reviewer protocol clarified. Social post templates shared.
Launch day: Excited announcement. Thank-you message. Specific asks (review now if not already).
Launch week: Daily check-ins. Celebrate milestones (first review posted, BSR milestone hit).
Post-launch: Thank-you. Share final stats. Recognise top contributors.
Don't over-communicate. 2-3 emails/posts per week max during launch week; less between launches.
Recognition + rewards
Team members give significant time. Acknowledge it:
- Public mentions in the book's acknowledgements (with permission)
- Free finished hardcover for committed members
- Private "thank-you" video from you
- Early access to book 2 cover reveal
- Insider community that continues between launches
Don't pay individuals or offer rewards conditional on positive reviews — both violate Amazon TOS.
What can go wrong
Flake-outs. 20-40% of recruited team members don't deliver. Plan for it. Recruit 1.5x your target — 40 members if you want 25-30 active.
Negative reviews from team. Possible. Don't take it personally. Honest reviews are the deal.
Slow review posting. Some members read but don't review for weeks. Polite nudge once, no further pressure.
Team becoming demanding. "When's the next book?" "Can I get free copies of all your back catalog?" Manage expectations.
Cliques. Active members form sub-groups; less-active feel excluded. Keep group focused on the book, not social dynamics.
Member sharing ARC with non-members. Rare but happens. Clear rules ("don't share — DM members can request invite") helps.
Legal + ethical limits
Amazon TOS: reviews must be honest, unincentivised. You CAN give ARC reviewers free books. You CANNOT pay them, offer prizes for positive reviews, or condition rewards on review content.
FTC / UK consumer law: reviewers must disclose ARCs received. The standard line: "I received an ARC of this book in exchange for an honest review." Include in your brief.
Privacy: team members' real names + emails are PII under GDPR. Treat them like newsletter subscribers.
Realistic launch-team results
For a 25-member team on a 4-week ARC window:
| Metric | Expected |
|---|---|
| Active readers (vs total recruited) | 15-22 |
| Amazon reviews in launch week | 15-25 |
| Goodreads reviews | 10-18 |
| Social posts (Instagram/TikTok) | 8-15 |
| BSR boost from coordinated launch | meaningful — top of category for 3-5 days |
For a 50-member team:
- 30-45 active readers
- 30-50 reviews in launch week
- Hot New Release placement very likely
UK considerations
- UK Amazon launches require UK reviewers for amazon.co.uk reviews. Recruit at least 5-10 UK-based members.
- Royal Mail — if shipping physical ARCs (rare for fiction), cost £2-£5/UK shipment.
- GDPR — team member data is PII. Keep secure; allow opt-out anytime.
- UK consumer protection — disclosure requirement same as Amazon TOS.
Common mistakes
- Recruiting strangers. Cold ARC platforms work but launch teams are best as engaged super-fans you know.
- Too large team. 100-member teams produce lower per-member engagement than 30-member teams.
- Vague brief. "Just review when you can" produces vague results.
- No social media kit. Asking team to "share on social" without graphics/copy underperforms.
- One-time team. Same team for multiple launches builds compounding engagement. Don't disband.
- Over-management. Daily mandatory check-ins burn out members.
- Under-management. No briefing or follow-up means flake rate climbs.
- Pressuring positive reviews. TOS violation + damages reputation.
When NOT to build a launch team
- First book, no audience. No one to recruit from. Use ARC platforms instead.
- Standalone book with no series follow-up. Launch team works best for series authors.
- Lazy launch ("just put it on Amazon"). Launch team requires active management — pointless without coordinated launch.
The bottom line
Build a 25-50-member launch team from engaged newsletter subscribers and repeat ARC reviewers. Brief clearly. Recruit 1.5x your target to absorb flake-outs. Run a coordinated 7-day launch with daily check-ins. Recognise contributors meaningfully (free books, acknowledgements). Don't pay, don't incentivise positive reviews.
A well-run launch team is the difference between a quiet release and a coordinated launch that hits Hot New Releases. The investment is a few hours of management per launch.
Frequently asked questions
Can I have the same launch team for multiple books?
Yes — and you should. Returning team members build a compounding asset. Add new members as the team grows.
Do team members get paid?
No (TOS). They get free books, recognition, and insider access. That's it.
What if a team member writes a 1-star review?
Honest review — leave it. Don't argue, don't remove them from the team (counterproductive). Use it as learning.
Should I share sales numbers with the team?
Share milestones (BSR top 100, 50 reviews hit, etc.) but not granular daily numbers — keeps the relationship aspirational.
Can I run a launch team without a newsletter?
Possible but harder. Recruit from social or ARC platforms. Newsletter recruits convert at much higher quality.
