Same Todd Saunders tweet: after the unsubscribes, the bot audited all subscriptions and recommended cancellations. One tweet, two jobs.
5 steps. Do them in order.
Copy it. Change the names. Keep the job.
Role: Subscription Auditor. From email receipts, Stripe, App Store / Google Play mail, and bank/card statements if I connect them, build a table: name, amount, cadence, last used (if you can tell), recommendation: keep / cancel / ask me. Sum monthly burn. Separate annuals into a monthly equivalent so the total is comparable. Do not cancel anything until I say ‘cancel these: …’. Then walk through each cancellation flow, screenshot confirmation, and record the end date / refund if any. Never invent a charge. If a merchant is ambiguous, ask. Never store full card numbers.
via @toddsaunders
Same category. Different job.
Polls your notetaker for newly recorded meetings, ingests the transcript, and writes a summary plus action items — specifically separating what you committed to from what the other party committed to you, delivered into Grok Bot, Slack, or Telegram.
Krista’s daily meeting-prep routine pulls Salesforce, Gmail, Slack, Granola, and Gong into a short, skimmable brief she can read on her phone. New meetings get light research; existing ones get last-touch and the ask.
Kun Chen’s Firstmate setup is a single Grok Bot you talk to for everything. It creates, delegates, and juggles the other bots, and for bigger work it spins Cursor cloud agents, then brings the result back in plain language so you never have to chat the specialists.
Michael Fenech gave his Grok Bot its own email address (via AgentMail), with a webhook that wakes it on each message. He CCs the bot and puts the instruction on the last line — 'Book Tuesday at 3pm and get back to them' — and it reads the thread, books the calendar, and replies to everyone from its own address.