Claude Duet: Small-Business Preview Checklist

What changed on October 21, 2026

Anthropic opened a research preview of Claude Duet on October 21, 2026, targeting professionals and small-business owners. Its announcement describes a proactive assistant that checks connected apps, prepares work and asks for approval before consequential actions. MacRumors' dated launch report corroborates the event date.

The important distinction is background work. Anthropic says Duet runs on its own cloud computer, continues when your device is off, and sends a morning brief. It checks connected accounts every few hours rather than continuously. The announcement also warns that this early version can misread conversations or misjudge urgency.

Our recommendation: evaluate a narrowly defined administrative task, not an unattended business process. Before connecting business information, decide who may authorize access, who will review the output and what would make you stop the trial.

Confirm access before planning a rollout

The official product page limits the research-preview waitlist to Claude Pro and Max subscribers in the United States. Team and Enterprise plans are not included yet. Duet has standalone iOS and Android apps and is accessible on the web.

For a business owner, eligibility should be the first decision gate:

• Check your subscription and location against the current official requirements.
• Treat joining the waitlist as a request for access, not a confirmed start date.
• Do not plan a company-wide deployment around an individual preview invitation.
• If your business requires Team or Enterprise access, wait for explicit support rather than moving company information into a personal account just to participate.

The last two points are our deployment recommendations, not additional Anthropic restrictions. Keep the preview separate from any commitment to replace an existing workflow.

Review existing connections and remembered context

Start with the account's existing access, not just the apps you intend to add. According to the official getting-started guide, Duet inherits the memory, skills and connectors already configured in Claude. Supported connector examples include Gmail, Google Calendar, Google Drive, Slack, QuickBooks, HubSpot and Docusign.

Before starting, make an inventory of connected apps and decide which information is appropriate for the trial. Ask the person responsible for each business system to review the proposed access. Prefer a task that can be evaluated without payroll, personal financial information or confidential agreements.

There is an important distinction between stopping access and removing past context. Anthropic says disconnecting an app prevents further access, but memory of information from earlier conversations remains. Do not describe disconnection as a complete data-erasure procedure.

The same guide says Duet can search its own chats and Claude chats outside projects. To stop that search, it directs users to turn off Search and reference chats in Settings > Memory. Review this setting alongside app connections; neither should be treated as a substitute for a broader review of what business information belongs in the account.

Pick a task with a source you can check

Use a documented capability rather than assuming Duet supports your entire workflow. Anthropic's launch announcement names these business uses:

• Finding unpaid invoices in QuickBooks or Stripe and drafting reminders.
• Drafting follow-up emails from HubSpot contact and deal history.
• Finding missed Gmail and Slack messages and helping prepare replies.

Choose one of these supported task types and keep the first trial at the preparation stage. These are vendor-described capabilities, not results from a WebSprint client deployment.

For the unpaid-invoice use case, our recommended review sequence is straightforward: inspect the proposed invoice list in the original accounting system, check each reminder against the current record, and review the recipient and wording before approving any message. Keep collection decisions with the person responsible for billing.

For HubSpot follow-ups, compare each draft with the underlying contact and deal history. Reject unsupported promises, incorrect next steps or a recipient mismatch. Do not infer that a drafted follow-up proves the entire sales process is ready for automation.

These checks extend the documentation's advice to review drafts and approval requests. The getting-started guide says Duet identifies the email, file or spreadsheet behind a number or summary. Use that source information to verify the output rather than judging only whether it reads well.

Name the approver before allowing actions

Anthropic describes Duet as designed to show the proposed action and wait before sending messages, making payments, signing documents or deleting anything. Its announcement also says some actions, including securities trading and moving money between accounts, remain off-limits even with approval.

For a trial, assign a named reviewer and define their authority in advance. We recommend keeping payments, signatures and deletion outside the initial scope. Start with reviewed drafts, and leave any approval request pending until the responsible person can inspect it.

Do not treat a written instruction as proof of a technical permission boundary. Observe the actual approval behavior, and stop the trial if it differs from your agreed scope. Anthropic's support guide explicitly warns that external emails and web pages can contain misleading instructions, known as prompt injection, and that no defense is perfect.

That warning is a reason for careful review, not evidence of a specific vulnerability. This article does not establish a security guarantee or claim that Duet has suffered an incident.

Measure background usage as well as output quality

Duet is included with Pro and Max at no extra cost during the preview, but it does not have a separate unlimited allowance. The official guide says background briefs and check-ins count toward the same five-hour session and weekly limits used by Claude chats. Anthropic warns that users may reach those limits sooner than with chat alone.

Keep a simple trial record: task requested, result received, corrections needed, review time and any usage-limit interruption. Record what you actually observe; do not convert a vendor capability into an assumed saving.

Keep ordinary checks for urgent work in place. The product page warns that Duet can miss something arriving between checks. Treat an absent notification as inconclusive, not as proof that nothing needs attention.

Use the Tasks tab to review ongoing work and requests for input. The support guide says only the user can mark a task completed. Our recommendation is to do so after checking the result, not merely after receiving a completion message.

Decide what would justify continuing

Continue only if the trial produces useful, verifiable work within your chosen data and approval boundaries. Pause if errors, review effort or shared usage make the arrangement unsuitable. Disconnect unneeded apps when the trial ends, remembering that this does not erase past conversational memory.

We have not independently tested Duet's safety effectiveness, measured business time savings or established its reliability for a particular company's records. The fetched sources support the preview's documented capabilities and limits, not a productivity guarantee.

For a broader rollout, first define the workflow and human checkpoints through business automation planning. Consider AI development separately if you need to evaluate requirements beyond this preview. The immediate decision is smaller: whether one documented task can produce trustworthy work under review without expanding access beyond what your business has approved.