The Three Emails an Investing Bot Should Send
Every automated tool eventually faces the same temptation: notify more. Daily digests, price movers, milestone confetti. Resist all of it. A bot that spends your money owes you exactly three emails — a receipt, a scoreboard, and an alarm — and each one has to answer a question you'd otherwise have to go look up.
The test for any automated notification is brutal and simple: if this email stopped arriving, would you notice within a week? For most bot emails the honest answer is no — they're engagement mail wearing a monocle. The three below pass the test, because each one replaces a manual check you'd otherwise be forced to do. This is written from how cs2stack does it, but the pattern applies to any tool that buys with your money.
Email one: the buy report (the receipt)
Sent after every run that spends money. It answers: what did you buy, where, and for how much? Concretely, that means line items — item name, quantity, venue, native price, converted price — plus the day's total against the budget cap. If the bot compared venues, the report should say which one won and by how much; a buyer that routes each purchase to the cheapest listing should prove it did, every day, in writing.
Two properties separate a real receipt from a vanity summary. It must be money-exact — the same figures that land in the append-only ledger, to the cent, not rounded "approximately $20" prose. And it must report failures with the same prominence as fills: an item skipped because every listing sat above your max-price line is information you paid for. A bot that only reports successes is marketing itself to you. There's a full walkthrough of one of these in how to read an automated buy report.
Email two: the performance report (the scoreboard)
Sent on a slower cadence — weekly or monthly is plenty. It answers: what is the stack worth versus what it cost? The only two numbers that fundamentally matter are total cost basis (every dollar in, from the ledger) and current market value (holdings marked against live prices). Everything else — per-item breakdowns, best and worst performers — is garnish, useful but secondary.
The discipline here is on the reader, not the sender. A daily performance email trains you to feel every wiggle in a market where drawdowns are routine and the strategy's whole premise is a multi-year horizon. Weekly is frequent enough to catch problems and infrequent enough to keep you sane. And the scoreboard must be honest about what it is: a mark-to-market estimate, before fees, on venues with thin books. It measures the position, it doesn't promise the exit.
Email three: the balance alert (the alarm)
Sent only when something needs a human. The canonical trigger for a buy-side bot: marketplace balance is about to run dry. A DCA bot can't top up its own wallet — funding is deliberately manual, which is a feature, because it means no automated system can spend money you haven't explicitly staged. The cost of that safety is that the bot can starve silently, skipping buys for days while you assume it's working. The alert closes that gap: "at the current spend rate, DMarket runs out in N days."
The alarm category extends naturally — a run that errored, a scheduled run that never fired (a real failure mode; see scheduling reliability in the cloud) — but the bar stays the same: an alert means act, not look. The moment alarms fire for non-actionable events, you'll filter them, and then you'll miss the one that mattered. More on the funding case specifically in never let the bot starve.
What deliberately isn't on the list
- Price-movement notifications. "Kilowatt Case up 4% today" invites you to override a plan you set calmly with a reaction you'd make anxiously. DCA works precisely because it ignores this — it's FOMO insurance, and a bot that drip-feeds FOMO back to you is undoing its own job.
- Engagement mail. Streaks, milestones, "your week in review." If it exists so you'll open the app, it's spam from a tool you're paying.
- Anything requiring a login to understand. The email is the report. Numbers in the body, not behind a button.
Why email at all
It sounds old-fashioned next to dashboards and push notifications, but email is the right transport for money automation for unglamorous reasons: it's durable (a searchable archive of every receipt — genuinely useful when tax season arrives), it's independent (readable even when the tool's dashboard is down, which is exactly when you're most anxious), and it's calm (no badge counts, read on your schedule). A dashboard shows state; email preserves history. For a system whose credibility rests on its paper trail — the open-ledger principle — history is the product.
Three emails. A receipt after every spend, a scoreboard weekly, an alarm only when you're needed. If your bot sends more than that, ask what the extra mail is for — and if it sends less, ask what it's hiding.