An ARC team is not a Facebook group of forty people you begged for stars. It’s not a spreadsheet of strangers who owe you a favour. And it’s definitely not a shortcut to a wall of five-star reviews by Tuesday.
An ARC team, done properly, is a small group of real readers who get your book before the world does, read it because they actually want to, and leave honest reviews because nobody asked them to be nice. That’s it. That’s the whole job. Everything else — the size, the timing, the platform you use to find them — exists to protect that one simple thing from the two forces that ruin it: authors who get impatient, and an Amazon system that punishes anything that smells like a deal.
This guide is the long version. If you’ve read a dozen “how to build your ARC team” posts and still feel like you’re guessing, this is the one that should settle it.
What ARC Means, and What the Team Is Actually For
ARC stands for Advance Reader Copy — a version of your book sent out before publication, usually to a small group, usually for free. The tradition goes back decades in traditional publishing: send galleys to critics and booksellers, build word of mouth, arrive at launch day with some noise already in the air.
Indie authors adopted the same idea for the same reason. But the *purpose* of an ARC team isn’t “free marketing.” It’s proof. Before a stranger buys your book on Amazon, they’re going to look for evidence that other real people read it and thought it was worth their time. An ARC team’s entire job is to generate that evidence honestly, before launch day, so the book doesn’t have to launch into silence.
That’s the real function: not hype, not volume, not gaming an algorithm. Proof, from real readers, that arrives close enough to launch to matter.
ARC Readers vs Beta Readers — The Real Difference
People use these terms interchangeably and it causes real problems, so let’s be precise.
Beta readers read a manuscript *before* it’s finished — often before it’s even edited. Their job is to tell you what’s confusing, what drags, whether the ending lands. You want their opinions to change the book. A good beta reader will tell you your protagonist is unlikeable in chapter six and you need to hear it.
ARC readers read a finished, polished, final (or near-final) book. Their job is not to fix anything — it’s to react to it as a reader would, and then say so publicly, in a review. If an ARC reader tells you the ending doesn’t work, that’s useful information for book two, but it’s too late to change book one.
Mixing these up is how authors end up with a “review” that’s actually a developmental edit, or worse, an ARC reader who quietly stops responding because they were handed a manuscript full of typos and assumed it wasn’t ready. Use beta readers early, in private, to make the book better. Use ARC readers late, close to publication, to tell the world it’s good. Different people, different timing, different job.
Why the First Handful of Honest Reviews Make or Break a Launch
Here’s the part most advice skips: Amazon’s own systems and human shoppers both use early reviews the same way — as a filter. A book with zero reviews looks unfinished, even if it’s excellent. A book with three reviews and a 4.8 average still looks fragile. A book with fifteen to twenty-five honest reviews in its first couple of weeks looks like something people are actually reading and talking about — and that’s the point where browsing shoppers start to trust it, and where Amazon’s own recommendation and “customers also bought” logic starts to notice it.
This is why the first handful matters more than the next hundred. Reviews fifty through two hundred arrive on their own if the book is good and enough people find it. Reviews one through twenty have to be *earned deliberately*, because without them nobody gives the book a chance to reach reader fifty.
The trap is that this pressure — needing early reviews, fast — is exactly what tempts authors into shortcuts: bulk-buying reviews, trading books for stars instead of honesty, joining sketchy “guaranteed 5-star” services. Those shortcuts work for about three weeks and then either the reviews get stripped or the account gets flagged. We cover the mechanics of doing this the safe way in more detail in how to get honest, Amazon-safe reviews — worth reading alongside this if you’re planning a launch.
How to Build an ARC Team From Scratch
Most authors ask “where do I find ARC readers” like it’s a single answer. It isn’t. Here’s where real ones actually come from, roughly in order of quality:
- Your existing readers. Anyone who’s already bought or finished a previous book, or signed up to your mailing list, is your best source. They already like your voice. Ask directly: “I have ten ARC copies of book two, want one?”
- Your newsletter, even a small one. Twenty engaged subscribers beat two thousand cold names. A short, honest ask — “here’s the book, here’s the release date, no obligation to review” — outperforms anything salesy.
- Genre-specific reader communities, not generic “ARC readers wanted” Facebook groups full of authors swapping with each other rather than actually reading. If you write cozy mystery, find where cozy mystery readers hang out, not where authors hang out pretending to be readers.
- A reader-matching platform built for this specific job — matching your book to people who already read your genre and want an honest review, not a transaction. This is the gap most “ARC team” advice never addresses: matching by taste, not just genre label, is what determines whether the review sounds like a real reader or like someone going through the motions.
- BookTok and Bookstagram creators, if your genre has an active content community — a different skill set from review-writing, but genuinely valuable for pre-launch buzz. We go deeper on that specific channel in free books for BookTok & Bookstagram creators.
A realistic first ARC team is 15–30 readers. You don’t need two hundred. You need twenty people who actually finish the book and actually post something honest.
When to Send ARCs — Timing Relative to Launch
Get this wrong and the whole effort is wasted. The goal is reviews landing in the first one to two weeks after publication, not scattered over the following six months.
A workable timeline: – 4–6 weeks before launch: send ARCs, with a clear, soft deadline — “if you can post a review by launch week, that’s ideal, no pressure if life gets busy.” – 2 weeks before launch: a friendly reminder, not a guilt trip. – Launch day: the book goes live, and if even a third of your ARC readers post in the first week, you’ve got real reviews stacking up exactly when new shoppers are deciding whether to trust the book.
Send too early (three months out) and readers forget, or life gets in the way, and the review lands four months after launch when it does the least good. Send too late (a week before publication) and you’re relying on people to read a whole book overnight — unrealistic, and it shows in rushed reviews.
The Amazon-Compliance Trap
This is the part that actually sinks authors, so it deserves plain language.
Amazon’s guidelines are clear: a free book is fine. A review is fine. A free book *in exchange for* a review, where the reader is expected or obligated to leave one — or worse, expected to leave a *positive* one — is not fine. Amazon calls this an incentivised review, and it can get the review removed, the reviewer’s account restricted, or in worse cases the author’s whole catalogue flagged. This isn’t rare paranoia; it happens to real indie authors every month, often because a well-meaning newsletter said “please leave a 5-star review” instead of “please leave an honest review.”
“Compliant by design” means the mechanics never put a reader in that position in the first place:
- The book is free, full stop. Not free-if-you-review.
- A review is *never* a condition of getting the book. Readers can take the ARC and post nothing, and that has to be genuinely fine, not just fine on paper.
- Every review carries a Verified Reader Badge — proof it’s a real person who actually read the book, not a bot, not a paid rating, not a swap-for-swap arrangement.
- Nobody pays anything, ever, on the reader side. The moment money changes hands for a review, you’re in incentivised-review territory regardless of what anyone calls it.
This is the difference between an ARC team that helps your launch and one that quietly puts your account at risk six months later. If you’re building a launch strategy around reviews at all, read this alongside the broader picture in indie book marketing that actually works — reviews are one piece of a launch, not the whole thing, and treating them as a growth hack rather than honest reader response is exactly how authors end up flagged.
How ReadLoop Matches Readers by Actual Taste
Genre tags lie. “Thriller” covers a reader who wants Gillian Flynn-style domestic dread and a reader who wants a Jack Reacher body count — technically the same shelf, completely different expectations. Match your book to the wrong version of “thriller” and you get a review that’s polite but hollow, because the reader wasn’t really your reader.
ReadLoop matches on actual reading taste — pacing, tone, tropes, comp titles the reader has actually rated highly before — not just the genre dropdown. That’s the difference between a review that reads like a form letter and one that reads like someone telling a friend why they liked your book. It’s also, practically, why the reviews hold up: a genuinely matched reader writes a genuinely specific review, and specific reviews are the ones that both convert browsers and survive scrutiny.
Readers never pay for this. Free books for honest reviews is the whole model — no subscription, no fee, no catch, because the moment a reader pays anything, the relationship stops being about the book and starts being about the transaction. If you want the fuller case for matching over paid ads and algorithm-gaming, reader–book matching vs paid ads lays it out. And if you’re a reader wondering how any of this works from your side, best book discovery platform for readers is the place to start.
Your Next Step
Don’t build a two-hundred-person ARC list. Build a twenty-person one, made of people who’d actually pick up your genre on a normal Tuesday, send it out five to six weeks before launch, and let the reviews be whatever they honestly are.
If you’re looking for a NetGalley alternative that doesn’t require an expensive listing fee or a review quota nobody can promise, or you just want to know how to get book reviews on Amazon without wondering if you’ve broken a rule you didn’t know existed — that’s the actual gap ReadLoop was built to fill. Not a shortcut. A better-matched, compliant, honest version of the ARC team you were already trying to build.
Start at readloop.net/authors if you’re the one who wrote the book. Start at readloop.net/readers if you’re the one who wants to read it first, for free, and tell the truth about it after.
Real books. Real readers. Real reviews. That’s the whole strategy — everything else is just logistics.