Hire a closer who does not send mail
Sales outbound
Draft follow-ups from the account list. Do not send. Ask before anything leaves the thread.
Use cases
Each Bot is a person in the sidebar. Job title optional. These are the jobs founders actually message first.
Hire a closer who does not send mail
Draft follow-ups from the account list. Do not send. Ask before anything leaves the thread.
A teammate for Postiz, Post Bridge, and Typefully
Indie schedulers already exist. Groxbot is the coworker who fills the calendar and never hits publish.
DataFast, not a BI warehouse
Pull the numbers you name. Cite the source. Never change production dashboards. Five bullets, then open questions.
A sourcer who does not email anyone
Source candidates from the brief. Never email anyone without approval. End with a shortlist and why.
Numbers first. No live campaign edits.
Pull spend and results from the sources you name. Cite the sheet. Never change live campaigns.
Receipts in. Policy out. No payments.
Read receipts and statements. Flag anything over policy. Never submit or pay. Return a table of exceptions.
A computer, a ticket, a fixture
Reproduce the bug from the report. Write steps, expected vs actual, and a minimal fixture. Do not change production.
Churn risk with evidence
Watch the accounts you name. Flag churn risk with evidence. Do not message the customer until you say so.
What changed. What needs you.
A source-linked digest of Slack, inbox, calendar, and notes — only the items that map to this week’s priorities. Does not send. Does not move meetings.
Gmail without the guilt
Sort the pile. Draft the replies. Never send. The inbox is still yours.
GitHub and Linear, in English
What shipped, what is stuck, what needs you. No merge, no deploy.
Marc Lou, Jack Friks, and the rest of Twitter
DataFast for revenue, Postiz or Post Bridge for posts, Polar or Stripe for money. One Bot, no Zapier cartoon.
Hire the first one
Name, optional job, how it should work. Open the thread. The first message is a real task.
Get started