Skip to content
allanninal.dev/build
Collaborate

Part 6 of 7 · Offer letter generator series ~5 min read

What the offer letter generator costs

Offer volume is low even in a business that is growing quickly, and the model runs only on the note lane. Four offers a month is a healthy small business hiring steadily; fifty is a company several times larger than this design is aimed at. Here is where each cent goes.

Key takeaways

  • About $1 a month at 14 offers. Roughly $1 at 50 offers.
  • One Bedrock read per offer is the only line that scales. Everything else is rounding.
  • Nothing is always-on, so a quiet month genuinely costs almost nothing.
  • The model only runs on the note lane, so a team that uses the form pays nothing for it at all.
  • The duplicate test runs before the read, so resends are free.
  • The three real risks: a retry loop, storage nobody expires, and a bigger model than the job needs.

The bill at three volumes

These are US East prices at the time of writing, at three volumes that bracket most small businesses. Find the bar closest to your own and read across.

Monthly cost of the offer letter generator at three volumesA stacked bar chart with three bars, one per volume tier: 4 offers totalling about $1, 14 offers totalling about $1, and 50 offers totalling about $1. Each bar is stacked from bands. The largest and fastest-growing is Bedrock, one read per offer, in teal. Then SES for the messages, in pink. Then S3 and DynamoDB storage in green. Then a fixed orange band for Secrets Manager and AWS Budgets, which is eighty-six cents at every volume. Then a grey band for Lambda, SQS and CloudWatch. A note says the read is the only bar that grows with the business and the orange band never moves.$0$0.5$1$1.5$2~$1.254 offers~$1.314 offers~$1.4650 offersBedrock — one read per offerSES — asks, results, receiptsS3 + DynamoDBFixed — Secrets Manager, BudgetsLambda, SQS, CloudWatchThe read is the only bar that grows with the business. The orange fixed band never moves.
Fig 1. The monthly bill at three volumes. The teal band — one model read per offer — is the only part that grows; the orange fixed band is the same 86 cents at every volume.

Line by line

LineAt 14 offersHow it scales
Bedrock read$0.04Linear. One call per offer, roughly 1,800 in and 200 out tokens.
SES$0.01Linear. About 2.5 messages per offer.
DynamoDB + S3$0.28Storage grows with what you retain, not with throughput.
Lambda + SQS$0.12Linear, and effectively free at this scale.
CloudWatch$0.16Flat, if you set retention. Unbounded if you do not.
Secrets Manager$0.40Flat. One secret, $0.40 a month.
AWS Budgets$0.46Flat. Two actions, so you find out before the bill does.

The messaging line is the largest variable cost here, because an offer involves several messages: the draft to the approver, the letter to the candidate, and any clause request. All of it is still fractions of a cent.

The three ways this bill surprises you

Every one of these has happened to somebody, and all three are cheap to prevent.

  • Storing renders rather than documents. Not a cost risk but the one worth repeating: re-rendering an old offer with today’s code produces a document nobody signed.
  • Re-reading a resent note. A forwarded email thread that grows with each reply will be re-read on every arrival unless the read is keyed on the confirmed terms rather than the message.
  • Log retention left at never. At four offers a month the logs will be the entire bill within a year without a retention setting.

What it costs when nothing happens

This matters more than the headline number for a seasonal business. In a month with nothing to process the bill is the fixed band: Secrets Manager at forty cents, AWS Budgets at forty-six, and a few cents of storage. Call it a dollar. There is no instance to stop and nothing to remember to turn off.

The monthly bill at four volumes plus one failure modeA horizontal row of five boxes. Quiet month, about one dollar. 4 offers, about $1. 14 offers, about $1. 50 offers, about $1. And one bad retry loop, about two hundred dollars. A note says four of these are the design working and the fifth is a missing dead-letter queue.THE BILL, AT A GLANCEQuiet month~$14 offers~$114 offers~$150 offers~$1One bad loop~$200Four of these are the design working. The fifth is a missing dead-letter queue.
Fig 2. The bill at a glance, including the one that is not a volume at all. A retry loop with no dead-letter queue costs more than every legitimate use of the system put together.
  • Management
  • Analytics
  • Front-end & mobile

Set these on day one

  • A dead-letter queue on every SQS queue, with a maximum receive count of three.
  • Thirty-day retention on every CloudWatch log group. There is no default that is safe.
  • An S3 lifecycle rule on the object prefix, tiering at 90 days and expiring at your actual record-keeping horizon.
  • Two AWS Budgets actions — one that emails at half your expected spend, one at double it. The second is how you find out about a loop in an hour instead of a month.
  • Provisioned concurrency: none. Nothing here is latency-sensitive enough to justify paying for a warm function.

Next: the same system drawn for engineers — service names, resource identifiers, IAM scopes, table schemas and the model id.

All posts