Twin templates

One scheduled briefing every morning — markets, ops numbers or inbox summary — delivered to email or Telegram.

Buyer:

Founders and OPC owners who start the day by manually checking five dashboards.

Monetised as:

Cost avoided (run it for yourself)

Time back:

3–6 hours / month

Handles refund requests with a duplicate-refund guard, and always pauses on a Decision Card with real order evidence.

Buyer:

Small e-commerce operators losing money to duplicate and unverified refunds.

Monetised as:

One-off build fee

Time back:

5–10 hours / month, plus prevented duplicate payouts

Sorts incoming messages by urgency and drafts replies — you press send, never the twin.

Buyer:

Consultants and OPCs spending an hour a day in their inbox.

Monetised as:

Cost avoided (run it for yourself)

Time back:

8–15 hours / month

Produces the recurring client report and emails it, with a signed receipt as proof of delivery.

Buyer:

Agencies and freelancers who owe clients a weekly or monthly report.

Monetised as:

Subscription / retainer

Time back:

4–8 hours / month per client

Receives inbound leads over a signed webhook, scores them against your rules and drafts the follow-up.

Buyer:

Solo sellers and small sales teams drowning in unqualified inbound.

Monetised as:

Usage-based (per run / per item)

Time back:

6–12 hours / month

A Twin Bundle sold in the marketplace with entitlements and creator earnings. Not live — do not sell it yet.

Buyer:

Buyers who want a ready-made twin, not a build project.

Monetised as:

Marketplace bundle

Time back:

n/a until commerce ships

The same twin running fully on a local GPU box with Qwen via Ollama, for buyers who cannot send data abroad.

Buyer:

Businesses with data-residency constraints.

Monetised as:

One-off build fee

Time back:

Same as the twin you deploy