Switch from Duet to Task Machine

Duet is an always-on AI hire for small businesses: one assistant that drafts replies, runs research, builds decks and small dashboards, and answers wherever you already are — Slack, Telegram, email, the web. Task Machine is an operating layer rather than an assistant: work lives in durable tasks and deterministic, verifiable workflows, and everything that needs you lands in one inbox.

Why do people switch from Duet?

• Chat threads evaporate, but work objects don't. An ask in Slack is gone when the thread scrolls away, and next month's version starts from zero. Task Machine keeps work in tasks, goals, and workflow runs with step-level run history, so what happened and why is always on record.
• The fifth client report should run like the first. Re-asking an assistant produces a slightly different report each time. Task Machine runs the same deterministic, verifiable workflow on a schedule, with verifier steps checking the output before it reaches anyone.
• One assistant vs a team you direct. Duet is a single hire doing broad back-office work. Task Machine is a team of humans and agents, not an org chart — agents you configure or install from playbooks, each with autonomy levels per agent, project, or goal.
• Approvals scattered across channels vs one inbox. Reviewing drafts across Slack, Telegram, and email means things slip. Task Machine's three-surface workflow (chat, inbox, tasks) collects every approval, question, and result in one inbox — and agents act through accounts you own: you keep 100% of your revenue, Task Machine takes no cut and never custodies your accounts.

What maps to what?

What do you give up?

Honesty first: for ad-hoc asks, Duet is simpler — one assistant, no workflows to define, answering in the chat tools you already live in. Its chat-surface reach is also broad: Slack, Telegram, email, and the web, with integrations across Gmail, Notion, HubSpot, Linear, Figma, and more, which covers more surfaces than Task Machine's connector set today. If your work is mostly one-off requests, a single assistant may be all you need.

How does the switch work?

1. Join the Task Machine waitlist and connect a workspace to the accounts you own — email, docs, CRM — through connectors.
2. Write down the asks you kept repeating to Duet — the weekly report, the reply drafting, the research digest — and pick the playbooks that match. Each installs the agents, workflows, and documents for that job.
3. Set autonomy levels low to start: drafts and client-facing sends wait for approval in your inbox instead of a chat thread.
4. Schedule the recurring workflows, set token and money budgets with 80% and 100% alerts, and keep chat for directing new work.

Common questions

Can I still just ask for things in chat?

Yes — chat is one of the three surfaces, and it's where new work starts. The difference is what happens next: the ask becomes a task with a workflow behind it, instead of a reply that scrolls away.

Is Task Machine overkill for a small business?

It depends on the mix. If most of your work is one-off questions, Duet's shape wins. If the same reports, outreach, and support work recur every week, that's exactly what deterministic workflows and one inbox are for.

What happens to the context Duet built up?

There's no importer. You'd move the durable parts — templates, briefs, client details — into workspace knowledge documents by hand, and the workflow definitions replace what previously lived in the assistant's memory.