Operations is the role that absorbs everyone else's tax. Duet is AI for operations teams that wants to stop being the help desk — it runs the scheduling tetris, the document plumbing, the weekly report, and the support triage, so your ops team can finally fix the system instead of being the system.
"Half my week is calendar Tetris."
Duet reads the request, checks the calendars, proposes the slot, and prepares the invite under your calendar rules. The whole back-and-forth becomes one message — and the same flow runs for renewals, QBRs, customer onboardings, and the all-hands you keep rescheduling.
"We literally re-type the contract into the renewal sheet."
Duet pulls fields out of contracts, MSAs, and onboarding forms; writes them into the right systems; and flags anything that doesn't match. The data lives in one place instead of three, and renewals stop sneaking up on you because the dates were buried in a PDF.
"I lose too much Friday focus to one PDF."
Duet compiles the report — metrics, summaries, charts — straight from the source systems and emails it to the distribution list on schedule. The reporting window becomes a review pass instead of a manual assembly job, and the report can still ship when you're out.
Book a 30-min onboarding call between Sara (sara@example.com) and our CSM team next week. Prefer Tue/Thu afternoons in Sara's timezone. Send a calendar invite with the onboarding doc attached.When a signed MSA lands in /contracts, extract counterparty, start date, term, and total value. Write a row to the renewals sheet and create a ticket in Linear ahead of renewal.On a weekly cadence, pull recent numbers from Mixpanel, Stripe, and HubSpot. Generate the weekly ops report PDF and email it to the leadership distro.For every new Zendesk ticket: tag urgency, suggest the right macro reply, attach the linked customer record, and ping the on-call engineer if priority is high-priority.Walk Duet through the workflows that eat your week: scheduling rules, document templates, report formats, ticket SLAs. It learns each one as a named skill so the next person on the ops team doesn't have to re-explain the system from scratch.
Connect calendars, Drive, Notion, Slack, Linear, Zendesk, your data warehouse. Duet reads, writes, and triggers across the stack through scoped permissions, and workflows can reuse a connection once it is wired in.
Workflows fire on cron (the weekly report), on event (a contract lands), or on demand (someone asks in Slack). You see what ran and what needs a human in a single feed — no hunting through five different tool logs.
Or skip the role question entirely and browse use cases by job.
Zapier and Make are deterministic plumbing — if X then Y. Duet handles the steps in between that need judgment: parsing an unfamiliar contract, writing a customer email, deciding which playbook applies. It uses Zapier-style triggers where they fit and reasons through the parts that don't.
Duet can connect to ops stacks through native skills, Composio, APIs, CSV exports, or custom wiring depending on the system. Google Workspace, Notion, Linear, Asana, Jira, Zendesk, HubSpot, Salesforce, Snowflake, and BigQuery-style workflows should be scoped by permissions, fields, and approval rules before write access is enabled.
You define them per workflow. Anything Duet writes externally (emails, customer-facing messages, contract changes) can route through a human approval step before it goes out. Low-risk internal updates — moving a ticket, updating a CRM field — can run without manual review when you choose; sensitive writes can stay reviewed.
Duet logs every run and surfaces failures. You can replay a failed run, edit the workflow in plain English, and re-run — no need to dig into integration logs. The error tells you which step failed and what it was trying to do in human terms.
Duet is designed to reduce the recurring coordination work that eats ops calendars. The wins are concentrated on recurring workflows you run — scheduling and recurring reports are common starting points, with document workflows landing after Duet has seen enough variants of the inbound formats.
No. Ops managers design the system; Duet runs it. The job shape changes — less keyboard time, more time on the workflows you used to skip because they took too long to wire up. Ops teams use Duet to take on a function they couldn't staff for, and reframe the role from coordinator to system designer.
Start with one connected workflow, then let Duet run the recurring pieces from your workspace.