The best way to know whether a productivity clone will pay off for you is to see the actual work other people delegate. Here are ten real use cases beta users have given us permission to describe, with honest notes on what saves time and what needs supervision.
Use case 1 — Routine scheduling replies. A consultant delegates every "are you free Tuesday 3pm" question to her clone, which reads her calendar and replies. 40-60 emails/week off her plate. Risk: none notable; schedule errors get corrected by the correspondent.
Use case 2 — Document forwarding. A product manager delegates "could you send me the X deck" to his clone, which fetches the latest version from Drive and forwards it with a one-line context. 15-25 emails/week. Risk: outdated deck if Drive version is stale; the clone checks last-modified and flags if uncertain.
Use case 3 — Customer-support triage. A founder delegates the initial read of support inbox. The clone categorises (bug, question, feature-request, churn-risk) and drafts a first reply for human approval. Not send-without-review; the clone is the triage layer. 2-3 hours/week saved.
Use case 4 — Meeting-request politeness. A senior engineer delegates "no, I cannot Tuesday, yes I can Thursday" replies. The clone reads calendar, replies politely in her voice, offers alternatives. 20-30 emails/week.
Use case 5 — Thank-you notes. A speaker delegates post-event thank-you emails to organisers. The clone knows the event name, the attendance figure (she provided it), and the right voice. 5-10 thoughtful-feeling emails/week delivered promptly.
Use case 6 — Expense-context questions. A sole trader delegates "what was that £220 charge on the 14th" questions to his clone, which reads the expense database and replies. 2-3 hours/month of accounting Q&A disappears.
Use case 7 — Re-asking for missing information. A coach delegates "I need your availability for next week" follow-ups to her clone. The clone tracks who has / has not replied and sends gentle reminders. Churn-prevention without human nag fatigue.
Use case 8 — Weekly-update drafting. A team lead delegates the first draft of his weekly update email (read the sprint board, summarise progress, flag risks) to his clone. He edits and sends. First-draft time down from 45 min to 10 min.
Use case 9 — Reference-check responses. A hiring manager delegates initial reference-check replies ("yes, Alice worked at X from Y to Z, here are two questions I am happy to answer on a call"). Short, verified-fact emails. 5-10/week during active hiring.
Use case 10 — Mentor-hour admin. A senior engineer who offers free mentoring via his network delegates scheduling + reminder emails. The clone knows his hours, his preferred video tool, his intro script. Mentoring continues; overhead disappears.
Common thread: every use case is bounded, routine, and low-risk. The clone is not judgement. It is the removal of the boring layer around judgement. If you are delegating a decision, you are using the clone wrong.
What to watch for: context-drift (a stale calendar, an outdated pricing doc), tone-drift (the clone gets too formal over time; correct it with journal entries), and over-delegation (work you would have declined yourself, the clone accepts because it cannot say no). Quarterly reviews of what the clone has been doing keep it healthy.