Part 6 of 7 · Review responder series ~3 min read

What the review responder costs

A coffee a month at SMB review volume. The fixed cost is essentially zero — if your listings are quiet for a week, the bill matches. The variable cost is dominated by Bedrock tokens for the extractors and the composer; everything else rounds to pennies.

Key takeaways

  • Three cost tiers: always-free or near it (Lambda, DynamoDB, S3, CloudWatch, EventBridge, SNS), per-review pennies (Bedrock tokens for the three extractors and the composer), and optional add-ons.
  • Fixed cost is essentially zero. A quiet week bills nothing because every component is on-demand.
  • Variable cost is dominated by Bedrock Haiku tokens; Titan embeddings for the policies and voice files are a tiny one-off when the docs change.
  • Platform API calls (Google Business Profile, Meta Graph, Yelp polling) are free within rate limits; the Yelp poller fits inside the 500-call free daily tier.
  • ~50 reviews/month lands under $3 total; ~500 reviews/month lands under $15.
Cost structure: three tiers A horizontal three-tier cost diagram. Tier one, "Always-free or near it": Lambda invocations for the intake, extractors, composer, and dispatch; DynamoDB pay-per-request for review IDs, themes, and audit; S3 for archived review packages at small volume; CloudWatch log retention at seven days; EventBridge schedules for the Yelp-style polling and the weekly themes roll-up; SNS topic for handoff and escalation notifications. Tier two, "Per-review pennies": Bedrock Haiku tokens for the three extractors plus the composer at fractions of a cent per review; Bedrock Titan Text Embeddings for the policies and voice file at a tiny one-off cost when files change; SES outbound for draft and escalation emails at $0.10 per 1000; platform API calls to Google Business Profile, Meta Graph API, and Yelp polling are free within their respective rate limits. Tier three, "Optional": SMS notifications via SNS for safety escalations at cents per message, off by default; Bedrock Guardrails on top of the existing custom guardrails for PII redaction and policy validation, billed per text-unit; AWS Secrets Manager for platform credentials at forty cents per secret per month; AWS Budgets alarms at no extra cost. A bottom note reads: a typical small business at 50 reviews a month lands well under three dollars total; a busy one at 500 reviews a month lands under fifteen. tier 1 Always-free or near it Lambda invocations ~ $0.00 DynamoDB (IDs, themes) ~ $0.05 S3 (archive) ~ $0.05 CloudWatch (7-day) ~ $0.10 EventBridge schedules ~ $0.00 SNS topic tier 2 Per-review pennies Bedrock Haiku (extractors) fractions of a cent / review Bedrock Haiku (composer) fractions of a cent / draft Titan Embeddings (files) tiny, on file change SES outbound (drafts) $0.10 / 1000 emails Platform API calls tier 3 Optional SMS for escalations cents/msg, off by default Bedrock Guardrails per text-unit, optional Secrets Manager $0.40 / secret / month AWS Budgets alarm free ~ 50 reviews/month → under three dollars total. ~ 500 reviews/month → under fifteen.
Fig 6. Three tiers of cost. The bill scales with how often new reviews land; the floor is nearly zero.

The fixed cost is essentially zero

There is no per-listing licence, no minimum monthly fee, no “starter plan.” If your listings have a quiet week, the AWS bill matches. Lambda, DynamoDB pay-per-request, S3, CloudWatch, EventBridge, and SNS all sit in or near the always-free tier at the volumes a small business sees. Even running the polling job for Yelp every hour, twenty-four hours a day, all month, costs a vanishingly small amount — EventBridge scheduled invocations are essentially free at this volume, and each poll is a single Lambda call that reads from one platform endpoint.

The biggest single line item in tier one is usually CloudWatch log storage, and you control that by retaining seven days instead of forever. After day eight, the logs are gone and the bill stops compounding.

The variable cost is per-review pennies

Three things scale with review volume:

  • Bedrock Haiku tokens for the extractors. Each review pays for three small model calls (rating-with-sentiment, themes, specifics) running against the review text. At small-model rates and the short input lengths reviews tend to be, the all-in cost per review for extraction lands at fractions of a cent.
  • Bedrock Haiku tokens for the composer. Auto-replies and drafts each pay for one composer call. The input is the structured review plus the relevant policies excerpt; the output is a short reply. Even on the most expensive moves, this is well under a cent per review. The composer doesn’t fire on Ignore, so junk reviews cost only the screening tier.
  • Titan Embeddings for the policies and voice files. One-off per file change; if you edit your policies file twice a month, that’s two embeddings calls totalling tiny fractions of a cent. The embeddings power the citation gate — finding the right policy passage to ground a claim.

Add it up at typical small-business review volumes (twenty to a hundred new reviews a month across all platforms): tier two is in the under-three-dollars range, tier one floors are under fifty cents, and the all-in monthly bill lands at a coffee a month. At higher volumes — a chain with several hundred reviews a month — tier two is the headline number, and even there it stays in the “phone bill, not Netflix subscription” range.

Three traps you’re avoiding

  • Per-listing reputation tools. Most off-the-shelf reputation managers charge $40–$200 per listing per month, regardless of volume. You’re trading a flat per-listing bill for pay-per-use that mostly comes in pennies, with the model running on the same shape regardless of how many listings you connect.
  • Always-on infrastructure for polling. A naive setup might run a small server that polls Yelp once a minute. That’s a $30+/month idle bill before it processes a single review. EventBridge schedules trigger Lambda — pay only when the schedule fires, scale to zero between fires.
  • Compose-on-every-review at long context. A larger model would spend ten to twenty times more per review for what is, at this scale, a short-input short-output task. Haiku-class models are correctly sized for review composition; reaching for a bigger one because it sounds smarter is the most common way to triple the bill.

When this stops being cheap

The math changes if you connect dozens of listings (a multi-location franchise) and the review traffic goes into the thousands per month. At that point the tier-two number becomes the headline, and there are levers: caching policy embeddings (already cached after the first lookup), batching the extractors into a single multi-output call, or moving to a smaller dedicated extraction model for the rating-with-sentiment step. Most small businesses, including small chains, never need any of those levers.

For everyone below that — and that’s most small businesses — a $10 monthly AWS Budgets alarm catches anything strange before it becomes a surprise.

In plain words

The fixed bill is nearly zero. The variable bill is pennies per review, dominated by tokens. A typical setup runs at coffee-money for the whole month. Set a budget alarm that fits your expected volume and the bill can’t surprise you.

All posts