How to build an ARC team from zero
An ARC team — your group of advance readers who get the book early in exchange for an honest review — is one of the highest-leverage assets an indie author can own. Reviews in the first days after launch drive visibility, and visibility drives sales. But almost nobody tells you how to build that team from nothing. Here's the playbook.
What an ARC team actually is (and isn't)
An ARC is an Advance Reader Copy — a pre-release version of your book sent to readers before launch. An ARC team (sometimes overlapping with a "street team") is the group of people who reliably read and review those copies. It is not a mailing list, and it's not the same as paying a service for exposure to strangers. The goal is a relationship you can go back to for every book you publish.
Step 1 — Find your first readers
You don't need a big platform to start. In rough order of quality:
- Your newsletter and existing readers. People who already finished a book of yours are your best ARC readers — they've proven they like your work.
- Your social following. A simple "who wants an early copy in exchange for an honest review?" post surfaces willing readers.
- Genre communities. Facebook groups, Discords, and subreddits for your genre — where allowed by the rules — are full of voracious readers.
- Reader-discovery services. Platforms like BookSirens, StoryOrigin, or Booksprout can put your book in front of readers you don't yet have. Treat these as a source, not your system of record.
Aim wide at first. You're going to filter hard later, so it's fine if this initial list is a mix of dependable readers and unknowns.
Step 2 — Set the expectations up front
Ghosting drops when the deal is explicit. When someone joins, make three things clear: the copy is free, an honest review is the expectation (not a positive one), and there's a deadline tied to launch. Spell out where you'd like the review posted. Clarity here does more for your review rate than any reminder later.
Step 3 — Deliver copies you can stand behind
How you send matters more than authors realize:
- Send each reader their own download link, not one shared link forwarded to a group.
- Use expiring links so a copy doesn't circulate forever.
- Fingerprint each copy to its recipient. It's invisible, it isn't DRM, and it means a leaked file can be traced back to one person — which quietly discourages sharing in the first place.
Step 4 — Track who actually follows through
This is the step that turns a one-off list into a team. For every reader, you want to know: did they download, did they review, did they hit the deadline, or did they take the copy and vanish? A campaign dashboard shows this at a glance instead of forcing you to reconstruct it from email.
Step 5 — Keep score, and let the roster refine itself
After your first launch you'll have data: some readers delivered, some didn't. Don't throw that away. A reliability score that rises for on-time reviewers and falls for downloaders who ghost — while not punishing people who never started — means your list gets more trustworthy every book. By your third or fourth launch, you can invite your proven readers first and quietly stop sending to the collectors.
A spreadsheet forgets. A roster remembers. That memory is the entire point.
Step 6 — Treat your team like a team
The best ARC readers stick around for years if you make it worth their while. Thank them by name. Give them the very first look at the cover. Occasionally send a copy with no review strings attached. People who feel like insiders show up; people who feel like a distribution list drift away.
Turning a list into an asset
Building an ARC team from zero is really a two-part move: cast a wide net to find candidates, then hold them accountable so the reliable ones rise and the freeloaders fall away. Do that consistently and, a few books in, you'll have something most indie authors never build — a permanent roster of readers who reliably turn your launch day into launch-day reviews. That's exactly the system ArcRoster is built to run.