What Is an ARC team and Why Do You Need One?
By Alexa Bigwarfe, founder of Write Publish Sell and the Women in Publishing Summit. Updated May 2026.
Quick answer: An ARC team is a group of readers who receive an Advance Reader Copy of your book — usually a digital version — 3 to 6 months before publication, with a request to post an honest review on or near launch day. ARC teams help authors collect early reviews, build social proof, and generate pre-launch buzz on retailers like Amazon, Goodreads, and BookBub.
I’ve helped hundreds of indie authors run book launches through Book Launch in a Box, and if I had to name the single biggest predictor of a strong launch, it wouldn’t be the cover, the ad spend, or the email list size. It would be the ARC team.
A book hits Amazon with zero reviews and the algorithm has nothing to work with. A book hits Amazon with twenty honest reviews on day one and suddenly it’s recommended, it’s converting, it’s gathering momentum. That’s what an ARC team does.
This guide covers everything: what an ARC team actually is, how it’s different from a launch team and from beta readers, how many readers you need, where to find them, the FTC and Amazon rules nobody talks about, and the exact six-month timeline I use. There’s a full FAQ at the bottom for the questions readers ask me most.
Understanding the ARC Team vs. Launch Team
An ARC team — short for Advance Reader Copy team — is a group of readers who receive a pre-release copy of your book and are asked to post an honest review around launch day.
The copy is usually digital (EPUB or PDF), fully edited, and clearly marked as an “uncorrected proof” or “advance reader copy.” Members typically receive it 3 to 6 months before launch. Their job is to read the book and post a review on launch day — or as close to it as possible — on platforms like Amazon, Goodreads, BookBub, NetGalley, and BookSirens.
The goal isn’t feedback. The book is already done. The goal is early reviews, credibility, and visibility at the exact moment new readers are deciding whether to buy.
ARC team vs. launch team: the comparison
These two terms get used interchangeably, and they shouldn’t. They do different jobs. Here’s how they compare:
| ARC Team | Launch Team | |
|---|---|---|
| Primary goal | Generate early reviews and credibility | Amplify visibility and word-of-mouth |
| Who's on it | Genre readers, reviewers, bloggers, influencers | Friends, family, fans, fellow authors |
| Receive book? | Yes — free pre-release copy | Often no |
| Timing | 3–6 months before launch | Launch week and the weeks around it |
| Main action | Post reviews on Amazon, Goodreads, BookBub | Share posts, graphics, links |
| Typical size | 20–100 readers | 10–50 supporters |
| Where to find them | NetGalley, BookSirens, BookFunnel, Bookstagram | Email list, social followers, author groups |
The short version: ARC team members read and review. Launch team members share and promote. Most experienced authors run both, and keep them as separate groups so reviewers stay focused on reviewing.
Beta readers vs. ARC team vs. launch team
A third term gets mixed in here, so let me clear it up. Beta readers are part of the writing process. ARC and launch teams are part of the marketing process.
Beta readers receive an unedited or partially edited manuscript and give you feedback on plot holes, pacing, character development, confusion points, and gaps. Their job is to make the book better before professional editing. Beta readers should be a small, hand-picked group — maybe five to ten avid readers in your genre. If you’re writing a children’s book, a child from your target age group is invaluable.
ARC readers receive a near-final, fully edited version. Their job is to post a public review.
Launch team members may or may not even read the book. Their job is to share, promote, and celebrate when it goes live.
Three different roles, three different stages. Don’t ask one group to do another’s job.
How many people should be on an ARC team?
For most indie authors, an ARC team of 20 to 100 readers is the realistic target. Debut authors should aim for 20 to 50. Authors with established audiences often build teams of 100 or more.
Why the wide range? Because the math is brutal. Even with an engaged team, expect a 20–40% review rate. If you send out 50 ARCs, plan on 10 to 20 reviews showing up around launch. If you need 30 reviews on launch day, your team needs to be at least 75 people.
That drop-off is not a sign you did anything wrong. Readers get busy. Life happens. Build your team big enough to absorb it.
Where to find ARC readers
The best ARC readers come from communities that already exist around your genre. Five sources actually work:
NetGalley is the largest ARC distribution platform, used heavily by trade reviewers, librarians, and serious book bloggers. It costs money but reaches reviewers who post on Goodreads, Amazon, and their own platforms. Best for nonfiction, literary fiction, and authors with marketing budget.
BookSirens is a smaller, more affordable platform with a community of engaged genre readers. You pay per download, and you can target by genre. Strong fit for fiction authors and series writers.
BookFunnel is a delivery tool, not a reader community — but it’s the easiest way to send ARCs to readers you’ve already recruited from your own audience. It handles file delivery to every e-reader without anyone having to email files around.
Bookstagram, BookTok, and book bloggers are influencer channels. Reach out directly to creators in your genre with a personalized pitch. Yes, it takes time. Yes, it works.
Your email list is the highest-converting source you have. People who already read your work, already opened your emails, and already raised their hand — they leave reviews at 3-4x the rate of strangers.
A balanced ARC team usually pulls from at least three of these sources.
How to run an ARC team — the seven-step workflow
This is the workflow I use and teach. It’s not complicated, but every step matters.
1. Build a signup form. Use a Google Form, a Typeform, or your email service provider’s form builder. Ask for name, email, what they read in your genre, where they post reviews, and a yes/no commitment to leave a review by launch day.
2. Screen applicants. Reject anyone who isn’t an active reader in your genre. Reject anyone who can’t or won’t leave a review. You’re not collecting fans — you’re building a review engine.
3. Deliver via BookFunnel or NetGalley. Don’t email out files. They get pirated, they get lost, and you have no way to revoke access. A delivery platform protects you and makes the experience professional for the reader.
4. Send a welcome email with expectations and a hard deadline. Tell them when the book launches, when you need the review by, what platforms you want reviews on, and what disclosure language to include. Make it crystal clear.
5. Mid-point check-in. Three to four weeks before launch, send a friendly “how’s the reading going?” email. This pulls 10-20% of stalled readers back in.
6. Launch-day review link. On launch day, email the team with direct links to leave the review on Amazon, Goodreads, and BookBub. One click. Make it impossible to forget or get lost.
7. Thank-you and re-post ask. A week after launch, thank the team and ask anyone who reviewed on Goodreads to also post on Amazon. You’ll pick up another wave of reviews this way.
The ideal ARC team timeline
Here’s the six-month countdown I use with my Book Launch in a Box authors:
6 months out: Begin recruiting ARC readers. Open your signup form. Start reaching out to influencers (they book up fast). Submit to NetGalley if that’s part of your plan.
4–5 months out: Book is fully edited and formatted. Send ARCs to your team via BookFunnel or NetGalley.
3 months out: Send the welcome email with expectations, deadlines, and disclosure language. Start engaging with team members on social.
6 weeks out: Mid-point check-in. Re-send the ARC file to anyone who lost it.
2 weeks out: Final review push. Confirm everyone has what they need.
Launch day: Send the review-link email. Activate the launch team for sharing.
Launch week + 7 days: Thank-yous and re-post asks. Follow up with anyone who hasn’t reviewed yet.
Amazon and FTC rules every ARC author needs to know
This is the section most ARC guides skip — and the one with the most outdated advice floating around. Here’s the current state in 2026.
Amazon still allows ARC reviews. Authors can give away free copies of their books, and the reviewers can post honest reviews on Amazon. That hasn’t changed.
The FTC still requires disclosure of the free copy. Under FTC endorsement guidelines, anyone who received something of value in connection with a review must disclose that material connection.
But the disclosure language has changed — and this is what trips up most authors. For years, the standard line was “I received a free copy in exchange for an honest review.” Don’t use that anymore. Amazon’s review policy prohibits anything offered “in exchange for” a review — that phrasing reads as a quid pro quo trade, even when it’s meant to be transparent, and reviews using it have been flagged and removed.
The safer approach in 2026 is to disclose the free copy without using “in exchange” language. Some compliant examples:
- “I received a complimentary advance reader copy of this book.”
- “I voluntarily reviewed an advance reader copy.”
- “This review is based on an ARC from the author.”
- “I received an ARC and am reviewing it voluntarily.”
Each one discloses the material connection (free copy received) without framing the review as a trade. That keeps the reviewer FTC-compliant and keeps the review from triggering Amazon’s quid-pro-quo flag.
Paying for reviews is still flat-out prohibited. Not on Amazon, not under FTC rules. ARC readers get a free book and that’s the entire exchange. You can offer non-cash perks like exclusive content, a private community, or swag — but never pay per review.
Friends and family reviews on Amazon get removed. Amazon’s algorithm flags reviews from people who appear to have a personal or social connection to the author — phone contacts, Facebook friends, anyone who’s interacted with you publicly online. Amazon’s own guideline says it doesn’t allow reviews from people who share a household with the author or close friends. Put friends and family on your launch team, not your ARC team.
ARC team mistakes to avoid
The patterns I see most often that kill review rates:
- Team is too small. A 30-person team with a 30% review rate produces 9 reviews. That’s not enough. Build for at least 20–30 reviews on launch day, which means a team of 75+.
- No deadline. “Whenever you get to it” produces zero reviews. Set a hard deadline two weeks before launch.
- No disclosure language. Reviewers forget to include it, the review looks suspicious, Amazon removes it.
- Recruiting from the wrong place. Asking your launch team to also be your ARC team mixes social proof with personal proof and dilutes both.
- Treating it as a one-time list. Your ARC team should be a recurring asset. Same people, every book. Build the relationship.
- Skipping the mid-point check-in. It feels like nagging. It isn’t. It’s how you double the response rate.
How ARC teams feed AI book discovery in 2026
This is the angle that most ARC guides haven’t caught up to yet. ARC reviews don’t just live on Amazon anymore. They’re indexed and surfaced by AI tools — Google AI Overviews, ChatGPT, Perplexity, Claude — when readers ask questions like “is [book title] worth reading?” or “best new books in [genre] 2026.”
A book with twenty thoughtful, detailed ARC reviews on Goodreads and Amazon is the book the AI tools cite. A book with zero reviews is invisible to them.
If you want to dig deeper on this, I’ve written full guides on Answer Engine Optimization for authors and Generative Engine Optimization for authors — both explain how to make your book and your website findable in the new AI-driven search landscape. There’s also a piece on why AI search can’t find your author website that pairs well with this one.
A strong ARC team is one of the most underrated levers in AI book discovery, because it produces exactly the kind of content — detailed, recent, third-party — that AI engines treat as authoritative.
Ready to build your ARC team?
Inside Book Launch in a Box, I walk you through the full ARC team setup — signup form templates, welcome emails, the six-month timeline as a fillable workbook, the screening checklist, and the launch-day review-link email. It’s the same workflow I run with my private clients.
If you’re launching a book in the next 12 months, this is the program that gets you to launch day with reviews ready, not scrambling.
Frequently asked questions
How many people should be on an ARC team?
For most indie authors, an ARC team of 20 to 100 readers is realistic. Debut authors should aim for 20 to 50; established authors often build teams of 100 or more. Plan on a 20–40% review rate — if you send out 50 ARCs, expect roughly 10 to 20 reviews around launch.
How far in advance should you send ARCs?
Send ARCs 3 to 6 months before your launch date. Three months is the minimum for serious reviewers — book bloggers, Bookstagrammers, and NetGalley reviewers all need lead time. Six months gives you room to follow up, gather reviews, and re-send to readers who fall off.
Are ARC reviews allowed on Amazon?
Yes. ARC reviews are still allowed on Amazon, and the FTC still requires the reviewer to disclose the free copy. What’s changed in 2026 is the recommended language. The old phrasing “I received a free copy in exchange for an honest review” can trigger Amazon’s quid-pro-quo flag and get the review removed. The safer phrasing is non-trade language like “I received a complimentary advance reader copy” or “I voluntarily reviewed an ARC of this book.” Both disclose the free copy without sounding like a trade.
Do you pay ARC readers?
No. ARC readers receive a free pre-release copy with a request for an honest review — that’s the entire arrangement. Paying for reviews violates Amazon’s terms and FTC guidelines and can get your reviews removed and your account flagged. You can offer non-cash perks like exclusive content, swag, or early-access communities, but never pay per review.
What’s the difference between an ARC team and beta readers?
Beta readers give feedback on an unfinished or unedited manuscript and help you improve the book before professional editing. ARC readers receive a near-final, fully edited version and post public reviews. Beta reading is part of writing; ARC distribution is part of marketing.
What format should ARCs be in?
Most authors send digital ARCs in EPUB, MOBI, or PDF format because they’re free to distribute and let you control access. Tools like BookFunnel and NetGalley deliver ARCs without sharing your actual book file. Physical ARCs are typically reserved for trade reviewers, bookstores, and major influencers.
Where do you find ARC readers?
The best sources are NetGalley, BookSirens, and BookFunnel for reader communities; Bookstagram, BookTok, and book blogs for influencers; your existing newsletter for super-fans; and genre-specific Facebook groups for engaged readers. Building your team primarily from your own audience produces the highest review rate.
How do you make sure ARC readers actually leave reviews?
Expect a 20–40% review rate even with the most engaged team. To improve it: pick readers who genuinely read your genre, send a clear timeline and review-link reminder email, make leaving a review one-click easy, and follow up twice — once a few weeks before launch and once on launch day itself.
Is it okay for an ARC reader to be a friend or family member?
On Amazon, no. Amazon will remove reviews from people who appear to have a personal relationship with the author — phone contacts, Facebook friends, public online interactions. Friends and family belong on your launch team, where their role is to share and promote, not to leave Amazon reviews.
Can ARC reviews go live before the book is published?
On Goodreads and BookBub, yes — you can post reviews as soon as the book is listed. On Amazon, reviews can only be posted once the book is available for sale. Most authors instruct ARC readers to post on Goodreads early and on Amazon on launch day.
What’s the difference between an ARC team and a street team?
The terms are sometimes used interchangeably, but most authors use “ARC team” specifically for readers who review the book and “street team” or “launch team” for fans who promote it. Some authors combine them; most experienced authors keep them separate so reviewers stay focused on reviewing and promoters stay focused on sharing.
Related guides
- Finding Book Reviewers
- Goodreads for Authors: How to Be Findable in 2026
- The Book Publishing Timeline
- What Is AEO? Answer Engine Optimization for Authors
- What Is GEO for Authors?
- Book Launch in a Box (2026 enrollment)
Alexa Bigwarfe is the founder of Write Publish Sell and the Women in Publishing Summit, and has helped hundreds of indie authors launch books that hit bestseller lists. Learn more about her work on the About page.
