Most authors meet their first hard launch the same way. The book goes live, the page sits there with nothing on it, and the readers who promised to show up are already three books further down their pile. An ARC team is how you avoid that, but only if you build it on purpose. Here is how to build an ARC team that puts your book in front of real readers a few weeks before it goes on sale, so the reviews are there in the opening days, when a brand-new listing needs them most.
What an ARC team actually does
An ARC, an advance reader copy, is your finished book handed to a small group of readers before release. They read early and, if they choose, post an honest review during release week. That first handful of reviews is what a cold buyer checks before they click buy. A launch with a few reviews already up makes a different first impression than a launch with none, and the readers you treat well become a base you keep for the next book.
What it does not do is guarantee sales, rankings, or a set number of reviews. Anyone selling you those is selling you a scam. The reviews stay voluntary and honest. That is the part that keeps readers coming back.
How to build an ARC team, step by step
Start where your readers already gather. Your newsletter is the strongest source by far, because those people already said yes to you once. If you don’t have one yet, that is the first thing to fix, and I walk through it in how to start an author newsletter. After that comes your reader group, genre Facebook groups, your team from the last book, and author swaps.
Then screen. Not everyone who signs up should get a copy. A short form does the work: which format they prefer, where they review, whether they have read the earlier books in the series, and what they actually enjoy about the genre. “I love fantasy romance with political intrigue” tells you far more than “I read everything.” Screen every reader for genre fit before you send a file, because a reader who was never going to like your book is the one who leaves a one-star review about a book they were wrong for.
Send the finished copy two to three weeks before release, as a watermarked EPUB through a delivery tool like BookFunnel, with the review window and a disclosure line ready to paste. Every copy is stamped to the individual reader. Say up front that sharing the file removes them from the team. That one sentence handles most of the piracy worry. Amazon is fine with ARC reviews as long as the reader discloses the free copy and you never demand a review in return. What you never do is gate reviews by star rating. Asking readers to only post if it’s four stars or higher is manipulation, and it can breach a retailer’s terms.
What a healthy team returns
Here is the number that saves authors a lot of panic. Across the campaigns I run, 10 to 20 percent of a team posts a review. That is healthy. A team of fifty giving you eight to ten honest reviews at launch is exactly what a good campaign looks like. Readers are volunteers with their own lives and their own moods, and DNF is a normal outcome you allow without penalty.
Reviews mostly land from release day on, because most retailers only let readers post once the book is live. Goodreads is the exception and takes reviews earlier, which is where early discussion builds. They keep trickling in for weeks after launch too, so don’t judge the whole campaign by release day alone. Where the retail reviews matter most depends on whether you are wide or in Kindle Unlimited, so point readers to the stores that actually matter to you rather than to Amazon by default.
If you have run a team before and watched the reviews never arrive, that has its own set of causes, and I pulled them apart in why ARC readers don’t post reviews.
Keep the team, don’t burn it
The habit that ends teams is treating them like unpaid staff. You cannot demand social posts, chase people for reviews, or hint that the next copy depends on a good one. One gentle reminder is all your follow-up needs to be. Chasing volunteers is how you lose them.
Do it the other way and the list compounds. A reader who felt respected signs up again, so each launch starts warmer than the last. That is the real return: a team that comes back, a little bigger each book. Genre timing shifts the details, and for romance in particular I break it down in ARC strategy for romance authors.
So the short version of how to build an ARC team is this: recruit where your genre gathers, screen for fit, send a clean file early, ask only for honesty, and treat the readers well enough that they come back. Get those right and your next book opens with reviews on the page instead of silence.
Frequently asked questions
What is an ARC team?
An ARC team is a small group of readers who get your finished book two to three weeks before release and post honest reviews during launch week, so a brand-new listing has reviews on it when the first buyers arrive.
How many ARC readers actually leave a review?
Across the campaigns I run, 10 to 20 percent of a team posts a review. A team of fifty giving you eight to ten honest reviews at launch is a healthy result.
Is it against Amazon’s rules to give away ARCs for reviews?
No, as long as the reader discloses they received a free copy and you never require a review or gate it by star rating. Demanding or star-gating reviews is what breaches retailer terms.
Get the free ARC Team Field Guide
I put the process into a free guide you can keep. It covers who reads when, the readiness check to run before you send, the five emails a campaign runs on, what a healthy review return really looks like, how reviews work on each platform, and the troubleshooting for when something goes sideways. It is written for authors who would rather be writing than running a spreadsheet.
And if you would rather hand the whole thing over, I run ARC campaigns for authors start to finish.