Launch Teams That Show Up: An Indie Publisher's Playbook for ARC, Beta, and Street Readers

There is a specific moment in every book launch that tells you whether the work you did before the launch was enough.

For Vector Strike — Book 1 of The CRITICOM Files, distributed across seven retail platforms plus direct delivery through calianapress.com — that moment arrived when the ebook went live on Amazon, Apple Books, Kobo Writing Life, Google Play Books, and Barnes & Noble Press, and the paperback and hardcover editions populated on Amazon, B&N Press, and Lulu Direct. Each of those platforms has a different review mechanic. Each one shapes shopper behavior differently. Each one has a different role for a launch team to play. And all of them are watching for the same thing in the first seventy-two hours: whether a real audience is converging on a real product at a specific moment.

That is what a launch team is for. Not a mailing list. Not a group of friends. Not a pool of volunteers contacted three days before release. A cohort of readers who have been with you through the pre-launch phase, who have the book in hand, who are primed to act in the window when action matters most, and whom you have earned the right to mobilize because you have treated them as collaborators rather than as a marketing resource.

I spent twelve years in air traffic control before I published anything. The muscle you build in that work is not bravery. It is sequencing. You can see every aircraft in your airspace, you can see every conflict five miles out, and your job is to make sure that when each aircraft reaches its waypoint, the airspace has already been shaped to receive it. A book launch is the same problem. The launch day is the waypoint. The airspace is the conversation each retailer’s recommendation engine is having about your book. Everything you do in the weeks and months before launch is the work of shaping that conversation so it already favors you when the waypoint arrives.

A launch team is how you do that shaping. This playbook is how we run that work at Caliana Press — across three team types, across seven retail surfaces, and with enough operational discipline that the method is repeatable across multiple titles and multiple pen names in the catalog.

This guide is educational. Retailer policies and vendor pricing cited here were current as of April 2026; they change. Verify anything you’re about to act on against the primary source before launch day.

Three Names, One Team

The indie publishing community uses three overlapping terms for what is, in practice, one group of readers playing three roles at three different points in a book’s life.

Beta readers read the manuscript before it is finished. Their job is critical feedback — pacing, confusion in the plot, factual slips, character problems, tonal misalignment. A beta reader delivers notes, not promotion. Their work happens early enough that the writer can still act on it.

ARC readers read the finished manuscript in the weeks before publication. They receive an advance copy — the term advance review copy predates indie publishing by decades, originally used for trade galleys mailed to bookstore buyers and traditional reviewers. For an indie publisher in 2026, an ARC reader is someone who receives the book early and has agreed, voluntarily and without compensation beyond the book itself, to post a review during the release window. ARC reading produces the first wave of social proof, not manuscript feedback.

Street team members agree to actively amplify the book around release — posting on social channels, recommending it to readers in their network, sharing the launch-day announcement. Their work is promotional muscle rather than reading work.

In a large traditional house these are three separate functions run by three separate teams. In a small-press operation they are typically the same people doing different things at different times. The same twenty-five readers might beta-read in January, receive an ARC in March, and promote in April. The consolidation is efficient and honest as long as the role is made explicit when the commitment is made. What breaks trust is recruiting someone as a beta reader and then silently enlisting them as a street team member three weeks before release. That is role substitution without consent, and readers notice it.

Where Real Team Members Come From

The standard advice — recruit from your email list and your social followers — is advice for a publisher who already has both. A first-time indie publisher usually has neither. What follows is ordered by what actually works from a standing start, with an honest note on what each channel does and does not produce.

Your existing readers, if you have them. The back matter of a previous book is the highest-yielding recruitment channel in indie publishing, and nothing else is close. A paragraph at the close of the book that invites readers to join a launch team for the next release, with a clear email capture link, reliably produces committed team members because the person signing up has just finished reading something you wrote and chosen to keep going. This is not available to first-book publishers, which is one reason later books are so much easier to launch than first ones — the team compounds.

Your personal and professional network. Friends, colleagues, professional acquaintances, community members who genuinely read in the category of the book you are publishing. Amazon’s Community Guidelines prohibit reviews from individuals with a direct personal or financial relationship to the seller, and Amazon’s detection is inconsistent but real. Close family is a gray area worth being careful about. Other network recruits are fair game if they read in the category. Individual asks in person or by direct message convert far better than group emails or public posts.

Genre communities. Reddit subreddits, Discord servers, dedicated Facebook groups, Goodreads reader groups. These work, but only after contribution. A publisher who shows up on day one asking for ARC readers will be ignored. A publisher who has been an active, generous member for months and then asks — preferably framed as a beta-read rather than a pure review exchange — will find thoughtful candidates. The beta framing selects for a more engaged reader than a straight free book for a review request.

Reciprocal relationships with other authors. Writing communities are full of publishers running the same problem. Offer to beta-read or ARC-read for another author in your genre with no obligation on their side to return the favor. A meaningful fraction will, on their own, over time. The relationships that develop this way are the most durable ones in an indie catalog.

Professional ARC-distribution services. A category of services exists to connect indie authors with readers willing to accept advance copies in exchange for an honest review. The legitimate ones do not pay reviewers or incentivize specific ratings, which keeps them aligned with retailer rules and with FTC guidance. BookFunnel is the most-used in the category — pricing verified April 2026 at $30 per year for the First-Time Author tier, $200 per year for Mid-List, and $300 per year for Bestseller, with Secure ARC Delivery included on the Mid-List tier and above. StoryOrigin is the closest feature-complete competitor — free Basic tier, or $10 per month / $100 per year for Standard, which includes review-copy management with automated reviewer follow-up, audio review code distribution, newsletter swaps, and beta reader management. BookSirens, BookSprout, and Hidden Gems Books operate in the same category at a range of price points and community sizes; check their current pages directly before committing, because pricing in this space moves.

NetGalley deserves a separate note. NetGalley is the industry-standard platform for trade galley distribution, primarily serves traditional publishers, and has historically been priced out of reach for most indies. Co-op services offer indie access at reduced rates, but the reviewer audience skews toward trade reviewers and librarians whose conversion profile does not map cleanly to indie audience-building. NetGalley is a real option. It is not usually the right first option.

A realistic first-book target is roughly twenty-five committed team members. Roughly half will follow through in the release window. That is not a failure rate; it is the baseline every honest indie publisher plans around. Expand from there.

The Delivery Layer

The least-glamorous part of a launch team program is also where most of them break. Team members who agreed enthusiastically two months earlier, then receive a confusing email with a .docx attachment that will not open in their reading app, quietly stop responding. Enthusiasm does not survive friction. You have three legitimate choices at the delivery layer, each with meaningful tradeoffs.

Option 1: Email the file directly. An author writes, attaches a PDF or EPUB, sends. This is free and immediate, and it is what you should not do. Attached manuscripts have no DRM, no tracking, no expiration, no per-recipient binding. Within weeks of a launch of any meaningful size, a direct-attachment ARC ends up on a piracy site. Email attachments also fail to open reliably in reading apps and force the publisher to become technical support for thirty readers on seven different devices. This is a false economy.

Option 2: A third-party distribution service. BookFunnel and StoryOrigin are the dominant entries here. Both convert files to EPUB, MOBI, and PDF automatically, handle device-specific installation, and issue per-recipient download links with expiration and single-use enforcement. For most indie publishers this is the right answer. It is inexpensive, reliable, and the publisher never has to think about delivery infrastructure again.

Option 3: Own the delivery stack. At Caliana Press we built caliana-delivery, our in-house digital delivery system, because the direct-sales side of the operation needed an owned pipeline anyway and extending it to ARC distribution was a marginal-cost decision. The stack runs on Node.js 22.x. A Stripe webhook from the storefront or an ARC dispatch from operations hits API Gateway, which invokes a Lambda function that writes a uniquely-watermarked copy of the book into S3, generates a one-time download link, and dispatches the delivery email through SES. Every operation is idempotent so a network retry does not produce a duplicate send. CloudWatch monitors the pipeline and alerts on failures. The watermarking is social DRM — the book is not encrypted, but every recipient’s copy carries a per-user signature that makes post-hoc leak tracing trivial.

The stack serves two surfaces simultaneously. When a reader buys direct from calianapress.com, the checkout layer — Stripe Payment Links, at the 2.9 percent fee we moved to after dropping Payhip’s five percent — fires the same webhook pipeline that an ARC dispatch does. The same infrastructure that protects a paid download protects a pre-release copy. Print fulfillment is a separate matter: print orders route through Lulu Direct, currently manual, with AWS automation in development.

I am not recommending that every indie publisher build this. For most publishers the BookFunnel subscription at $200 a year is obviously the right tool. Building caliana-delivery made sense for Caliana because the direct-sales stack had to exist regardless — I was not willing to rent the paid-download experience to a third party whose fee structure or terms I could not control, and I had the engineering capability to build it in-house. Once the direct-sales pipeline existed, extending it to ARC delivery was cheap. For a publisher with multiple titles across multiple pen names and a plan to keep the infrastructure for a decade, the math favors ownership. For a publisher with one or two books and no engineering background, the math does not.

The honest framing: there are more indie publishers building their own delivery infrastructure in 2026 than there were three years ago, because the AWS primitives are now cheap enough and well-documented enough that it is feasible. Most publishers still should not. The ones who should are the ones who already need the infrastructure for direct sales, and for whom ARC distribution is a second use of a system that exists for other reasons.

The Communications Rhythm

Most launch-team programs underperform because they have exactly two touchpoints: a recruitment message and a release-day request. The readers who signed up expecting a relationship get a broadcast email and a silence in between, and by the time the launch ask arrives they have mentally unsubscribed.

The correct frame is cycle, not checklist. Pre-agreement, pre-launch, launch window, post-launch — each phase has its own tone, its own goals, and its own rhythm.

Pre-agreement is the recruitment conversation. One-to-one, not one-to-many. The ask explains what the program is, what the reader is agreeing to, and what they are not agreeing to. Specifically: they are agreeing to receive a free advance copy; they are not agreeing to leave a positive review. Critical reviews are acceptable. The free copy is not conditional on the review. FTC disclosure — receiving a free book is a material connection under the Endorsement Guides, and the reviewer must disclose that fact clearly in the review itself — is the reader’s obligation, but the publisher has a duty to inform them of it in writing the first time they join the program. A well-run program says this plainly in the first message and revisits it when the ARC ships.

Pre-launch is the long middle. The reader has the book. The publisher is running the final production steps. The team is, ideally, reading. Most publishers go quiet here, and the quiet is where launch teams go to die. The counter-move is a warm, low-pressure check-in every two to three weeks with no ask attached. How is the book treating you. What else are you reading right now. How is your own writing going, if they are a fellow author. The goal is to remind the team member that the relationship is real, that the publisher is a person, and that the reader is known. This phase separates an ARC program from a mass-email campaign.

Launch window is release day plus the first seven to ten days. The first communication on release day is short: the book is live, here is the link, thank you. The follow-up three or four days later is a personal note to any team member whose review has not yet appeared — no pressure, a check-in on whether they need anything, an offer of a different format if format is the problem, a reminder that a partial-read review is still useful and editable later. The tracking sheet earns its keep in this window; knowing who posted and who did not is the only way to send personal follow-ups instead of broadcast nudges.

Post-launch is where the asset is built for the next book. Ten days after release, a note goes to the full team with the launch numbers, standout reviews, and what the publisher learned. Private thank-yous go to team members whose reviews added specific value — not in a public reply on the review page (Amazon and most other platforms discourage author replies on reviews, and it reads as defensive even when meant sincerely), but in private correspondence. The question of whether to invite each team member to the next book’s team gets answered here, case by case. Those who opt in become the compounding asset that makes the next launch easier than this one was.

For a team of roughly thirty, the arithmetic runs to seven or eight personal communications per team member across a ten-week cycle. That is a workload. It is not an unbearable one. A publisher who cannot maintain it either needs a smaller team, an assistant, or a different business model.

Platform-Specific Review Mechanics

Most launch-team advice treats reviews as a monolithic concept, which in practice means it is Amazon advice pretending to be generic advice. A launch team distributing a book across seven platforms does not have the luxury of that abstraction. What follows is a compact reference on how reviews actually work on each retailer we use at Caliana Press, as of April 2026.

Amazon KDP

• Native ARC mechanism: None. ARC distribution happens out-of-band — through BookFunnel, StoryOrigin, in-house infrastructure, or direct contact. Amazon does not provide a publisher tool for pre-release reviewer access.
• Review policy posture: The strictest of the five. Amazon’s Community Guidelines prohibit incentivized reviews beyond the copy of the book itself, prohibit reviews from individuals with a personal or financial relationship to the seller, and rely on a combination of algorithmic detection and manual moderation. Verified-purchase reviews carry additional display weight and factor into the recommendation signal. Reviewer disclosure of a free ARC is an FTC requirement independent of Amazon’s rules.
• 2026 notes: No material ARC-policy change confirmed at time of writing. Amazon’s policy pages are sometimes difficult to fetch cleanly; verify current state before any launch-window decision.

Apple Books

• Native ARC mechanism: Promotional codes. Apple Books is the only major retailer in this group with a built-in ARC channel. A publisher receives a fixed number of promo codes per title per period, valid for approximately a month. Critically, only Apple Books purchasers and promo-code recipients can post a rating or review. An ARC reader who received the book through a third-party service but does not have an Apple Books account cannot post an Apple Books review. Promo codes are therefore the correct channel for any team member you expect to review on Apple Books specifically.
• Review policy posture: Reviews are scoped per territory — a US-based reviewer’s review appears only to US customers by default. Apple’s policy addresses profanity, hate speech, overtly sexual language, and significant factual inaccuracy as grounds for removal, and does not explicitly prohibit ARC-driven reviews. The Apple Books for Authors guidance openly encourages authors to solicit reviews from their readers.
• 2026 notes: The web-based Publishing Portal is now open for any PC — a useful procedural change for publishers previously bottlenecked by Mac-only workflows.

Kobo Writing Life

• Native ARC mechanism: None. ARC distribution is out-of-band.
• Review policy posture: Light moderation. Kobo requires a minimum review length of 100 characters. Star ratings can be submitted independently of written reviews on some devices. Kobo moderates for rude or profane language, spoilers, and reviewer personal information; it does not publish an explicit anti-incentivization rule. The Kobo review surface is smaller than Amazon’s — most Kobo customers do not leave written reviews — and the marginal impact of any individual Kobo review is correspondingly lower.
• 2026 notes: Nothing material confirmed this cycle.

Google Play Books

• Native ARC mechanism: Content Reviewer access. Google Play Books Partner Center lets a publisher grant Content Reviewer permissions that include free pre-release access to uploaded files. This is Google’s equivalent of a promo code, structured as an account grant rather than a single-use code, and it is the legitimate way to put a pre-release copy in front of a reviewer who will then post on the platform.
• Review policy posture: Light. Google uses automated and human content review of book metadata and covers; the customer review policy does not publish an explicit ARC rule.
• 2026 notes: New-publisher accounts face an ingestion review of up to thirty business days. Any publisher launching a first title on Google Play needs to front-load this gate in the production schedule.

Barnes & Noble Press

• Native ARC mechanism: None. ARCs are out-of-band.
• Review policy posture: Standard. B&N Press guidance directs authors toward NOOK customer reviews and toward book-blogger outreach with free copies. No explicit incentivization rule beyond retailer norms.
• 2026 notes: Material policy change in effect. Starting April 22, 2026, new B&N Press listings must be priced at or above $14.99. Titles already listed below that threshold will be removed from sale beginning May 14, 2026. A 100-title-per-account cap is also being enforced on the same date. These are pricing and catalog-scale rules, not review rules, but any 2026 launch on B&N Press needs to account for them.

Quick reference

What to Measure, and What to Ignore

Total review count is the vanity metric. It is what indie authors count because it is the easiest thing to count. It is not what matters.

What matters is review velocity — the rate at which reviews accumulate in the first seventy-two hours and the first seven days. Ten reviews on release day with seven more in the next forty-eight hours is a different signal than seventeen reviews spread across three weeks. The retailers’ recommendation engines read velocity. A launch team’s job is to concentrate reviews into the window where velocity matters, not to produce the largest possible total.

Two other things are worth tracking that most publishers do not:

Completion versus partial reads. A reviewer who finished the book writes a different review than one who stopped at chapter three. Completion correlates with star rating, with review length, and with the probability that the same reader returns for the next book. Partial-read reviews are not bad — they are honest signals about pacing or premise — but they tell the publisher something different than a completed review does, and a publisher who confuses the two makes worse decisions downstream.

Review-page language, not star count. Individual star ratings fluctuate. The consistent thread across reviews — what readers describe when they describe what the book does — is the most useful feedback an indie publisher can get, and it is available on every retailer’s review page. A book that is getting four-star reviews for one reason and three-star reviews for a related reason is telling the publisher something specific, and that specific feedback is worth more than the rating average.

In our experience running launches under the Caliana imprint, the variable that correlates best with a team member actually delivering on release day is not the size of the reader’s audience or their prior review count. It is whether they responded to at least one pre-launch communication that was not a request. A reader who engaged during the long middle shows up. A reader who went silent after accepting the ARC usually does not. That signal is visible in the tracking sheet two weeks before release if the publisher is paying attention.

Common Failure Modes

Four patterns account for the substantial majority of underperforming launch teams. They are not mysterious. They are what happens when a publisher treats the team as a resource to be deployed rather than as a relationship to be cultivated.

Mass-list treatment. The team receives broadcast emails addressed in plural, and the relationship the publisher thought they were building evaporates. The fix is to address team members as individuals, with a specific reference in each message. This is the single most expensive and most effective change available.

Last-minute assembly. A publisher starts recruiting three weeks out and sends ARCs ten days before release. Readers cannot read a novel in ten days on top of their actual lives, and the team collapses into a small set of skimmed reviews. The fix is to treat ARC distribution as the closing phase of production, not the opening phase of marketing — six to ten weeks of reading time for a novel, four to six for shorter work.

No curation. Accepting every volunteer produces a team of strangers whose only connection to the project is a one-click yes. The fix is to describe the commitment honestly at recruitment. Volunteers who cannot meet the terms self-deselect when the terms are visible, and the remaining team is smaller and more reliable.

No loop closure. The launch happens, the team performs, the publisher disappears. Eighteen months later the next book needs a team, and the publisher rebuilds from scratch while the original team silently decides not to respond. The fix is ten days of follow-up work after release: a post-mortem to the full team, private thank-yous to specific reviewers, and a standing invitation onto the next book’s team for those who want to continue. The return compounds.

The pattern underneath all four is identical. The publisher is treating the team as a resource and the readers are treating the publisher as an acquaintance. The corrective is to treat readers the way a publishing house that plans to exist for a decade treats readers: as the people the enterprise is built around, not the audience it mines.

The Long Game

A launch team is a compounding asset. Treated well, it grows across books, across years, and across the format and platform shifts that indie publishing will keep producing. Treated as a mailing list, it produces one adequate launch and then disperses, and the publisher rebuilds from zero each time.

I am not going to pretend the launch methodology we run internally at Caliana Press is a secret. There is no secret. There is only the refusal to shortcut the relationships that make a launch team real — and the willingness to build the infrastructure that makes those relationships sustainable across a catalog. That is all it is. It is also, for reasons the indie-publishing advice ecosystem does not acknowledge often enough, the single most durable competitive advantage available to an independent publisher.

The readers who show up on release day are the ones who believe you will show up for them afterward. Do the second thing and the first takes care of itself.

For a shorter companion on the four habits that kill most indie launch teams, read The ARC Team Myth: Why Most Launch Teams Don’t Work.