Claude Duet vs a Managed AI Worker for Email Follow-Up

The short verdict for an owner or operations head

If your follow-up work sits in one person's inbox and that person is in the US, Claude Duet is worth a trial once you have a waitlist place. It adds no separate fee during the preview, and it works from the plan you already have. If the follow-up work belongs to a team, touches billing or support, or needs a record of who was contacted and when, a managed AI worker is the better match. You pay for build and monitoring, but the process runs in the business's own accounts under rules the business sets.

The two products are not really rivals for the same job. Duet is a personal agent that watches your connected apps and nudges you. A managed worker is a process that runs for everyone who depends on it. Choosing between them comes down to who owns the work and who needs to see the record.

Side-by-side comparison

What Duet does with email today

Duet's main value is attention. Each morning it sends a short list of items waiting across linked accounts, then keeps watch and reaches out when something needs input. Anthropic built it on Claude Opus 5.5 and says it can draft emails and schedule meetings. It runs on its own virtual machine, so the user's laptop or phone can be switched off.

The limit that matters most for follow-up is timing. Duet does not watch your inbox all the time. It checks linked services every few hours, because constant scanning would use up usage limits much sooner. Anthropic's support material warns that something urgent can arrive between checks. Anthropic also says the agent can misjudge what is urgent, so a reminder that should have gone out today may be queued for tomorrow.

Approvals are clear. Duet shows the exact action before sending a message, making a payment, signing a document or deleting something, and it waits. If you cannot approve straight away, it finishes the rest of the task and brings the approval back later. That protects you from a bad send, but every reminder still needs a person to open the approval screen. For ten invoices a week that is manageable. For two hundred it becomes the job.

Duet also reads content written by other people. Anthropic states that email and web pages can contain instructions meant to mislead the agent. The company says no defence is perfect, which is one reason it asks for approval on consequential actions.

What a managed worker does with the same work

A managed worker runs a fixed process. For payment chasing, that might mean reading open invoices from the billing system, checking the payment record, sending the reminder that matches the stage of the debt, and writing each step to a log. Replies that mention a dispute, a payment plan or a complaint go to a named person. The owner decides the wording, the timing and the escalation rules before the worker goes live.

The advantage is shared ownership. The worker's log can be read by finance, the operations head and the account manager. Access is granted to the business's own accounts, not to one employee's personal login. When someone leaves, the process stays in place.

The disadvantage is that it does not exist until someone builds it. It needs a discovery stage, a test period on real data and a rule for what happens when the source system is down. It also needs monitoring after launch, because email platforms change, invoices arrive in new formats and staff change roles. Those costs are the price of a process that is run rather than prompted.

Where Duet is the right choice

Duet suits a single owner or manager in the US who already pays for Claude Pro or Max and runs most of the business from one inbox and one calendar. The cost of trying it is low, and the morning brief will show quickly whether it notices things you would miss. It is also a sensible way to test how much follow-up work you actually have before you pay for a build.

Duet is a poor choice for regulated sensitive records, for work owned by a team, or for any process where you need a central audit trail. Team and Enterprise customers cannot use it yet, and the preview places work on personal accounts that the company's IT team cannot administer. Anthropic has not announced a broader release date for those plans.

Where a managed worker is the right choice

A managed worker suits a process that runs every working day and involves more than one person. Examples include chasing overdue invoices across several customers, handling a shared support mailbox, or sending renewal and document reminders from a register that changes often. It also suits businesses in several countries, because the build can follow each country's rules for language, currency and data location.

It is not worth building for a few reminders a month. If the work fits in a calendar reminder and one spreadsheet, the audit may recommend a simpler fix. Honest scoping is part of the service.

Total cost of ownership beyond the sticker price

The price of Duet is simple to read. The full cost of either option depends on drivers that rarely appear on a pricing page.

1. Setup. Duet needs a waitlist place, a connected account and an afternoon of rule-setting. A managed worker needs discovery, a build, testing on real records and sign-off.
2. Maintenance. Duet's maintenance falls on the user, who must read approvals. A managed worker needs monitoring, updates when tools change, and someone who owns exceptions.
3. Breakage. A background checker that runs every few hours can miss time-sensitive items. A built process fails in known ways, and its alerts go to a named person.
4. Usage and seats. Duet's background checks draw on the same limits as the rest of Claude. Team seats are priced separately, with Team at $20 per seat a year, or $25 a month, for two to 150 people as listed in 2026.
5. Vendor lock-in. Duet's connections sit inside a personal Claude account, which makes handover harder. A managed worker's rules and logs should be exportable to the business.

For a single owner, the largest hidden cost is attention. For a team, it is the cost of exceptions that nobody owns. Both options can be cheap in the wrong setup and expensive in the right one.

The custom-built alternative and when it wins

A custom build means an in-house or contracted developer writes the worker from scratch, often using a model API directly. It wins when the business has engineers who will own the code after launch, the process is unusual enough that no packaged tool fits, or data must stay inside the company's own cloud account with its own retention rules. It loses when nobody on staff will maintain it. Many custom projects stall after the first version because no one reads the logs.

Migration notes if you start with Duet and move later

Start by listing every account Duet connects, and every person who depends on those connections. Then decide which reminders should move to a shared process and which can stay personal. Check the admin settings on your side before any move. In Google Workspace, admins can block unconfigured third-party apps or mark Gmail and Drive as restricted services, which revokes tokens from untrusted apps. In Slack, owners can restrict installs to pre-approved apps. Both defaults are open, so check them before you connect a team account.

Keep the approval history and the reminder wording you used. Those become the starting rules for the managed worker. Test the new process beside the old one for a few weeks, then switch off the personal connections. Confirm in writing where the records are stored and who can read them.

How to decide this week

Count how many follow-up messages go out each week and how many people touch each one. If the answer is one person and a few dozen messages, try Duet when your waitlist invitation arrives. If the answer is several people, a shared register and a requirement for a record, plan a managed build and ask for a scoped quote. Either way, the first step is measuring your own volume, which is what the free automation audit does. Results depend on your own figures, so measure before you buy.