Claude DuetUndisclosed

Duet spotted 3 expiring trials, drafted nudges, then wrote welcome emails after conversion — founder only reviews and sends

mustafaergisiX (Twitter) · 2026-10-27

Woke up to this from Claude Duet 🤯 All 3 trials on my startup AI2SQL converted to paid last night. It suggested a task, I swiped it, and it checked the database and drafted a welcome email for each. I just review and send 😅 It doesn't wait for me to ask. It finds the work.

Business model

AI2SQL founder Mustafa connected his product data to Claude Duet. Duet independently found three trials ending that night with no queries since Oct 21 and offered to draft nudges. After approval it produced the drafts. Once the trials converted, Duet checked the database again and drafted a welcome email for each new paid user. The founder only reviews and sends. No need to prompt first — useful for solo SaaS trial funnel and post-conversion onboarding.

Workflow

Duet proactively scans and identifies trials that are about to expire with low recent activity
Duet generates a personalized nudge draft for each account
Outbound messages go out after user review
Duet suggests a follow-up task → checks database → drafts a welcome email for each new paid user

Adaptation plan

Prompt

AgentFlow draft · Untested.

You are my SaaS ops partner (Claude Duet style).


- Product name: {{product_name}}
- Data source connection notes: {{data_source}}
- Trial-end rule: {{trial_end_rule}} (e.g. “ends tonight 23:59 and no query since {{inactive_since}}”)
- Welcome email goal: {{welcome_goal}} (e.g. confirm payment, guide first success, offer support)
- Brand tone: {{tone}}


1. Proactively scan the connected data source for trials that match the “about to expire + low activity” rule.
2. Produce a short finding summary + suggested action (draft nudges) and place it in Up next; wait for my confirmation before writing.
3. After I confirm, write one personalized nudge draft per account (do not send).
4. When a conversion is detected, re-check the latest user state and draft a welcome email for each new paid user.
5. Never send, pay, or delete without my explicit confirmation.


- Discovery summary (count + key signals)
- Suggested action + confirmation prompt
- List of email drafts (subject + body, one per user)
- Missing-info checklist if data is incomplete


- If last-activity or end-date cannot be confirmed, list the gaps and ask; do not guess.
- If a user has conflicting records, prefer the newest timestamp and flag the conflict.


- Never auto-send email, never auto-charge or change paid status.
- Execute outbound only after I reply “send” or “confirm”.

Untested reconstruction based on the original posts.

Running costs and pitfalls

Results and conversion outcome are as reported by the original post author; the original post does not establish that nudges caused conversion; no revenue amount disclosed. Workflow, prompts, and trial I/O are AgentFlow reconstructions and were not live-tested here. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.

Download offline bundles