| What it does without asking you |
| Work it does before you ask | What the scope you agreed covers, on the schedule you agreed | Plans and decisions in the hours you buy. The daily work usually falls to your team or freelancers. | Nothing. It answers when you ask. | What you ask for in a chat. Some plans add a hosted agent that runs workflows on a schedule. | Reads your Stripe invoices, and drafts a service email when a payment fails. It writes nothing else in the Alpha. |
| Watching your numbers between meetings | Depends on the reporting in your agreement | Depends on their hours with you | Only what you paste into a conversation | Scheduled audits and briefs, on the plans that include them | Checks Stripe for failed payments every day, and reports which payments came back, with email-driven, automatic-retry and unknown kept apart |
| Approval and undo |
| Who presses send | Often the agency, under the agreement you sign | Them or your team | You, after copying each draft into the right tool | It asks you first by default. An admin can open its permissions as far as “allow all”, after a strong confirmation. | You. A person approves every message before it is sent, and it sends exactly what was approved. There is no setting that lets an email go out without a click. |
| Limits on what goes out | What you agree with them | What you agree with them | None of its own. It can’t send, so the limits are yours. | Budgets and the guardrails in its settings. Check for a daily send limit and one switch that pauses everything. | Each company starts in Practice mode and gets daily send limits before it goes live. It sends failed-payment emails and nothing else. |
| Undo and a record | Their reports, and the history inside each tool | Their notes, and the history inside each tool | Your chat history | A history of what it asked and what it did, inside the product | A history of every decision. Each entry is chained to the one before, so an edit shows up when you check. Signed daily checkpoints outside the database were enabled on 28 October 2026; see the security page for their limits. A sent email can’t be unsent. |
| Where you use it |
| Where the work happens | Email, calls and their reports | Meetings, email and Slack | The ChatGPT app | Inside your assistant, such as Claude, ChatGPT, Codex or Cursor, through many tools | The web app, where you review and approve each draft. |
| What it reads |
| What it can see | The accounts and documents you give them access to | What you share with them | What you paste or upload into a conversation | The accounts you connect, from a long list, plus its own data tools. With a browser extension, also sites you’re signed in to. | Stripe through a restricted key you create, and your own Resend account’s delivery results. What it reads is treated as data, never as instructions. |
| How it reports results |
| Scores and forecasts | Their reports, in the measures you agree with them | Their judgement, from your numbers | Whatever you work out yourself | Often a score out of 100 for each area, sometimes with a projected score for after its work | Counts, each with its source, such as how many failed payments came back after an email. |
| Cost for a founder-sized setup |
| What you pay | A monthly retainer or a fee per project, scoped by hours or deliverables | A monthly retainer for part of someone’s week | An assistant subscription you may already pay for | A monthly plan with credits. Each run uses some, so a job’s cost varies. | Nothing. There is no charge in the Alpha. |
| Your time | Briefing, waiting and reviewing on their schedule | Meetings, then carrying out the plan | All of it: prompting, checking numbers, copying, sending and following up | Asking in your assistant and answering what it asks; less once you let it act without asking | Reading and approving each drafted email |