Applied AI
Plan the workflow without assuming access to Claude Duet
A proactive assistant is interesting because it can continue work between messages. For a Swiss business, the first practical check is whether the product is available to the account and use case you actually have.
Anthropic's 21 October release notes introduce the Claude Duet research preview. (Anthropic)
The access guide limits the preview to invited US Pro/Max accounts, excluding Team/Enterprise. It describes cloud-based work and a design that asks before sensitive actions. This establishes neither Swiss/Spanish availability nor guaranteed behaviour. (Anthropic)
Keep three decisions separate
| Decision | Evidence required |
|---|---|
| Can this account use it? | Current plan, region and invitation conditions from the provider |
| Should this workflow use it? | Defined task, permitted data and an accountable process owner |
| May it perform this action? | Specific authorisation, review boundary and a recoverable outcome |
Do not treat an account in another region as an implementation plan. A Swiss team can still document the work it wants to improve, but should not sell or schedule a Duet rollout based on access that has not been granted. Recheck the official conditions if they change before a future project.
Write a task brief that can survive a product change
Take a hypothetical daily brief assembled from email and calendar. Specify the permitted folders and calendars, the time window, the questions to answer and the sources each finding must reference. 'Tell me what matters' is difficult to verify; 'list unpaid invoices from the approved source, with owner and due-date evidence' gives a reviewer something concrete to check.
- Define what may be read, what may be drafted and what requires explicit approval.
- Identify the person who receives unresolved or contradictory findings.
- Set a boundary for messages, payments and irreversible changes.
- Require a source reference for a factual claim and a visible label for an inference.
A draft is a useful intermediate result
An assistant can propose an action without being authorised to execute it. Preserve that distinction in the workflow: a draft reminder is not a sent email; an assembled financial summary is not a verified account balance. Agree how a person checks source records and signs off the next step before granting broader access.
Start with a task whose mistakes are visible and reversible. Keep a record of missed items, unsupported conclusions and requests that need human input. A pleasant daily summary is not evidence that every source was covered or that the assistant has permission to act for the company.
Prepare what remains useful without the preview
Inventory the existing tools, account owners and manual handovers. Clarify which data may be used and where the final result should live. Those decisions are valuable even if a particular preview is unavailable or changes direction. Budget for review and correction alongside any plan or usage charge; no productivity or return figure is established here.
An automation audit can define that process and its first implementable step. It does not require promising access to a preview that a Swiss account cannot currently use.
Sources
- Get started with Claude Duet — Anthropic
- Claude release notes — Anthropic