Family opt-in

# Not live yet (gaps #2)
curl -X POST "https://api.sb/leaseline.app/campaigns?mode=try" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"play":"family-opt-in"}'

 1import { $ } from 'startup-builder'
 2
 3return await $.Campaign.create({ play: 'family-opt-in' }, { mode: 'try' })   // dry run on the day-0 Startup, 2026-08-24 · Not live yet, gaps #2

npx startup-builder do Campaign.create --json '{"play":"family-opt-in"}' --try   # Not live yet (gaps #2)

{
  "name": "do",
  "arguments": {
    "code": "return await $.Campaign.create({ play: 'family-opt-in' }, { mode: 'try' })   // dry run on the day-0 Startup, 2026-08-24 · Not live yet, gaps #2",
    "mode": "try"
  }
}

 1{
 2  "type": "https://startupbuilder.dev/errors/refused",
 3  "title": "Refused",
 4  "status": 422,
 5  "detail": "family-opt-in can’t start yet: 1 check fails and 2 warn.",
 6  "checks": [
 7    {
 8      "check": "use-when",
 9      "status": "pass",
10      "observed": "2 Startups, buyer overlap 0.72; 141 sign-ups in 30 days at the host",
11      "doc": "/plays/family-opt-in#check-use-when",
12      "fix": "None needed: 100 sign-ups a month is enough.",
13      "then": "Metric.query"
14    },
15  …

curl "https://api.sb/leaseline.app/events?where=name%20in%20(%22Form.opened%22%2C%20%22Contact.subscribed%22%2C%20%22Consent.withdrawn%22%2C%20%22Offer.published%22%2C%20%22Brand.lapsed%22%2C%20%22Portfolio.changed%22)&limit=1" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

# Not live yet (gaps #7)
curl -X POST "https://api.sb/leaseline.app/triggers/fire?mode=try" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"like":"event_1702"}'

# Not live yet (gaps #7)
curl "https://api.sb/leaseline.app/decisions?where=on%20%3D%20%22contact_77%22" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

# Not live yet (gaps #7)
curl "https://api.sb/leaseline.app/actions?where=on%20%3D%20%22contact_77%22" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

 1import { $ } from 'startup-builder'
 2
 3const { events: [last] } = await $.Event.list({ where: 'name in ("Form.opened", "Contact.subscribed", "Consent.withdrawn", "Offer.published", "Brand.lapsed", "Portfolio.changed")', limit: 1 })   // { play } compiled to this Play’s Trigger Events
 4const { subject } = await $.Trigger.fire({ like: last.$id }, { mode: 'try' })   // the same Event again, in try mode · Not live yet, gaps #7
 5const { decisions: [decision] } = await $.Decision.list({ where: `on = "${subject}"` })   // what it chose, and why · Not live yet, gaps #7
 6const { actions } = await $.Action.list({ where: `on = "${subject}"` })   // what it did, with its checks · Not live yet, gaps #7
 7return { decision, actions }

npx startup-builder do Event.list --json '{"where":"name in (\"Form.opened\", \"Contact.subscribed\", \"Consent.withdrawn\", \"Offer.published\", \"Brand.lapsed\", \"Portfolio.changed\")","limit":1}'
npx startup-builder do Trigger.fire --json '{"like":"event_1702"}' --try   # Not live yet (gaps #7)
npx startup-builder do Decision.list --json '{"where":"on = \"contact_77\""}'   # Not live yet (gaps #7)
npx startup-builder do Action.list --json '{"where":"on = \"contact_77\""}'   # Not live yet (gaps #7)

{
  "name": "do",
  "arguments": {
    "code": "const { events: [last] } = await $.Event.list({ where: 'name in (\"Form.opened\", \"Contact.subscribed\", \"Consent.withdrawn\", \"Offer.published\", \"Brand.lapsed\", \"Portfolio.changed\")', limit: 1 })   // { play } compiled to this Play’s Trigger Events\nconst { subject } = await $.Trigger.fire({ like: last.$id }, { mode: 'try' })   // the same Event again, in try mode · Not live yet, gaps #7\nconst { decisions: [decision] } = await $.Decision.list({ where: `on = \"${subject}\"` })   // what it chose, and why · Not live yet, gaps #7\nconst { actions } = await $.Action.list({ where: `on = \"${subject}\"` })   // what it did, with its checks · Not live yet, gaps #7\nreturn { decision, actions }",
    "mode": "try"
  }
}

 1{
 2  "decision": {
 3    "$id": "https://api.sb/leaseline.app/decisions/decision_495",
 4    "$type": "Decision",
 5    "choice": "welcome-them",
 6    "reason": "ticked the Leaseline box on your other Startup’s sign-up at 10:04, address verified, and no Suppression covers Leaseline",
 7    "stakes": "low",
 8    "options": [
 9      "show-the-box",
10      "ask-after-sign-up",
11      "welcome-them",
12      "hold-for-a-confirm",
13      "send-the-launch",
14      "to-the-ae",
15  …

action_2 records one Consent naming Leaseline, stamped with the host, the Page, the words shown and the time; action_3 creates the Contact with the address, a first name and the region, and nothing else. action_4 is the welcome, sent after a 30-second hold.

≈ +$380 ARR a month at 120 sign-ups

Worth

40 min week 1, then 5 a week

Your time

$0.01 per welcome, ~$1 a month at 30 yeses

Spend

Day 1: first yes and its welcome

First signal

2+ Startups with overlapping buyers, 100+ sign-ups a month at the host

Use it when

One Startup: customer-referrals · under 100 sign-ups: owned-newsletter

Not yet when

Worth’s formula: about +23 yeses per 100 sign-ups (your held-back read) × 120 sign-ups a month at your other Startup × 4 paid per 100 yeses × $347 first order ARR ≈ +$383. Under First signal: The yes rate reads within 14 days at 120 sign-ups a month; Customers from the yeses take about 90 days, so new-arr reads Too early to tell until January.

Start it this weekCopy Anchor Link

npx startup-builder add play family-opt-in   # 1 · writes plays/family-opt-in.mdx (Not live yet, gaps #5)

# 2 · dry run; below, its 422 on 2026-08-24
curl -X POST "https://api.sb/leaseline.app/campaigns?mode=try" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"play":"family-opt-in"}'

# 3 · keep it, at You approve the first wave
curl -X POST https://api.sb/leaseline.app/campaigns \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"play":"family-opt-in"}'

# on
curl -X PATCH https://api.sb/leaseline.app/campaigns/family-opt-in \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"endsAt":null}'

# off: the box comes off the host within 1 hour; every recorded yes stands
curl -X PATCH https://api.sb/leaseline.app/campaigns/family-opt-in \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"endsAt":"now"}'

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "family-opt-in can’t start yet: 1 check fails and 2 warn.",
  "checks": [
    {
      "check": "use-when",
      "status": "pass",
      "observed": "2 Startups, buyer overlap 0.72; 141 sign-ups in 30 days at the host",
      "doc": "/plays/family-opt-in#check-use-when",
      "fix": "None needed: 100 sign-ups a month is enough.",
      "then": "Metric.query"
    },
    {
      "check": "baseline",
      "status": "warn",
      "observed": "0 yeses: no box has run",
      "doc": "/plays/family-opt-in#check-baseline",
      "fix": "The 1 in 10 shown no box is the comparison from day 1.",
      "then": "Metric.query"
    },
    {
      "check": "approved-pages",
      "status": "fail",
      "doc": "/plays/family-opt-in#check-approved-pages",
      "fix": "Approve the box line and the welcome; each says only what your Page says.",
      "then": "Approval.approve"
    },
    {
      "check": "role-unstaffed",
      "status": "warn",
      "roles": [
        "marketing-lead",
        "sales-lead"
      ],
      "owned": 31,
      "doc": "/plays/family-opt-in#check-role-unstaffed",
      "fix": "Staff the Marketing Lead, or leave it: buying replies come to you.",
      "then": "Role.staff"
    }
  ]
}

Each welcome and discovery note costs about $0.01 from Leaseline’s broadcast Mailbox (Worker cost); the box and the Consent cost nothing. That comes to about $1 a month at 30 yeses.

When it startsCopy Anchor Link

{
  "$id": "https://api.sb/leaseline.app/events/event_1702",
  "$type": "Event",
  "name": "Contact.subscribed",
  "at": "2026-10-19T10:04:51Z",
  "seq": 1702,
  "data": {
    "contact": "contact_77",
    "host": "startup_2",
    "form": "form_3",
    "receiver": "leaseline.app",
    "words": "Leaseline: lease renewal software, same team as this app. Monthly updates.",
    "region": "us"
  }
}

npx startup-builder trigger Contact.subscribed --like event_1702   # replays the delivery
npx startup-builder clock advance --by 3d   # then sends the discovery note, unless they replied
npx startup-builder listen Contact.subscribed --forward-to http://localhost:3000/hook

Who runs itCopy Anchor Link

Marketing Lead · your agent (role:marketing-lead, worker_6) holds the Key Result for both Startups. Buying replies go to AE · Priya Shah (person) (role:sales-lead, worker_3), and each launch to your family subscribers comes to you (Dana Okafor, person, worker_1). Your number links to Did it work.

What it reads · What it may call. It reads the yes itself, the address, a first name and the region. It never passes the host’s plan, Form answers, Orders, Visits or usage to Leaseline, and no Message mentions anything they did at the host. Its tools are PATCH /{namespace}/forms/{id}, PATCH /{namespace}/pages/{id}, POST /{namespace}/consents, POST /{namespace}/messages/{message}/schedule, POST /{namespace}/approvals, POST /{namespace}/conversations/{conversation}/escalate, POST /{namespace}/tasks/{task}/assign, and any other call becomes an Approval under the Role’s Mandate.

You hold the Marketing Lead Key Result: 20 yeses per 100 sign-ups by 2026-12-31. ← worker, metric
On each ask point, yes or withdrawal, choose one option and say why.             ← triggers, chooses
Render each box unticked, never required, naming Leaseline, same team and its cadence. ← copyRules 1, 2
Record one Consent per yes, naming Leaseline as recipient.                       ← your file, line 4
The welcome’s first line names the host and the date of the yes.                 ← copyRules 5
Show no box to 1 Visitor in 10, held for 90 days.                                ← your file, line 2

The slow loop. The weekly Decisions kept the box rule as written, and no Change was merged in the window, so there is no replay or read-back to print.

Bring your own agent (folded) starts at It does it, you can stop it on welcomes when it matches or beats the seated agent on the eval suite; renders stay rule-bound either way; POST /{namespace}/roles/{role}/staff seats it.

npx startup-builder eval --scenario family-opt-in-260 --agent "claude -p" --seat marketing-lead   # seated: 23 yeses per 100, 2,140 of 2,140 renders passed, welcome in 38 s · yours: 23, 2,139 passed, 1 failed `render-check`

What it can do nextCopy Anchor Link

When it hands to youCopy Anchor Link

Buying replies go to AE · Priya Shah (person); each launch to your family subscribers comes to you. One Brief per Role, as captured (brief is Not live yet, gaps #7).

[
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_622",
    "$type": "Task",
    "assignee": "worker_3",
    "due": "2026-10-02T15:31:00Z",
    "on": "contact_71",
    "brief": {
      "who": "Sam Ortiz, 200 units",
      "said": "We’d like to try it for our 200 units.",
      "chose": "to-the-ae",
      "why": "asks to buy, over 100 units",
      "yes": "ticked the Leaseline box on your other Startup’s sign-up, 2026-09-28",
      "never": [
        "anything they did at the other Startup",
        "a discount"
      ]
    }
  },
  {
    "$id": "https://api.sb/leaseline.app/approvals/approval_74",
    "$type": "Approval",
    "verdict": null,
    "deadline": "2026-10-27T17:00:00Z",
    "draft": "Leaseline’s owner portal opens Nov 2: owners see every renewal in one place. You said yes to Leaseline updates on Sep 3 on our maintenance app.",
    "route": "send-the-launch",
    "checks": [
      {
        "check": "consent-stop",
        "status": "pass"
      },
      {
        "check": "claims-resolve",
        "status": "pass"
      }
    ]
  }
]

Priya and you answer with POST /{namespace}/tasks/{task}/claim (Take this one), POST /{namespace}/tasks/{task}/return with a reason, POST /{namespace}/approvals/{approval}/approve or POST /{namespace}/approvals/{approval}/refuse, each a one-call window; an Approval unanswered by its deadline expires and nothing sends. Once a person claims, the agent’s pending notes to that Person cancel with claimedByPerson (Not live yet, gaps #7). A Task nobody claims by its due time goes up through POST /{namespace}/tasks/{task}/escalate, and person-promise fires.

On time: AE · Priya Shah, 2 of 2 claimed within 60 min, median 26 min, n 2, ■□□□ Too early to tell beside Other Startups’ 95 % on time. Your queue: counted by kind: in week 1, 1 approval for the box line and welcome; since then about 1 hand-off a month and 1 launch approval.

The fixed line: POST /{namespace}/deals/{deal}/assign sets owner to the receiving person, the agent is never a Deal’s owner, and Meetings land on the owner’s calendar under the owner’s name.

When it won’t sendCopy Anchor Link

The captured refusal, then the Stop that fired as a Campaign.paused reason (Not live yet, gaps #2); the box that rendered after the fix is the second thread in Example.

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "The welcome to contact_63 did not send: their yes names your maintenance-request Startup, not Leaseline.",
  "checks": [
    {
      "check": "consent-stop",
      "status": "fail",
      "doc": "/plays/family-opt-in#check-consent-stop",
      "fix": "Ask once for a yes to this Startup.",
      "then": "Message.schedule"
    },
    {
      "check": "owned-by-a-person",
      "status": "pass"
    }
  ]
}

[
  {
    "reason": {
      "limit": "welcome-lag",
      "observed": "7 yeses with no welcome at 24 h",
      "bound": "0",
      "window": "24h"
    },
    "doc": "/plays/family-opt-in#stop-welcome-lag",
    "task": "task_617"
  }
]

Did it workCopy Anchor Link

Each Visitor at the host was assigned at random, 9 in 10 to the box and 1 in 10 to no ask, so both halves read the same assignment (rules m–o); each figure’s call is POST /{namespace}/metrics/query by node and by arm, and every node above the leaf is Not live yet (gaps #4).

{
  "$id": "decisions/decision_495",
  "$type": "Decision",
  "choice": "welcome-them",
  "reason": "ticked the Leaseline box on your other Startup’s sign-up at 10:04, address verified, and no Suppression covers Leaseline",
  "stakes": "low",
  "options": [
    "show-the-box",
    "ask-after-sign-up",
    "welcome-them",
    "hold-for-a-confirm",
    "send-the-launch",
    "to-the-ae",
    "not-now"
  ],
  "by": "worker_6",
  "on": "contact_77",
  "expected": "the welcome delivered within 1 minute, and a Leaseline trial within 90d",
  "reopensWhen": "Consent.withdrawn for contact_77, or no Message.delivered within 24h"
}

The leaf counts yeses per 100 completed sign-ups at the host’s ask point, over 14 days, to 300; at 260 the Experiment runs on. The parent reads Leaseline Customers per 100 host sign-ups in each arm, 90 days out.

How it moves it: one honest, unticked box on the host’s sign-up, and a welcome from Leaseline 38 seconds after the yes, naming the host and the date.

Guardrails: boxed against no ask: host sign-up completion, 71 % against 73 %, inside the 2-point Stop, and welcome unsubscribes, 3.7 % of 54 against the 8 % floor; 6 trials are still deciding.

{
  "$id": "https://api.sb/leaseline.app/campaigns/family-opt-in",
  "$type": "Campaign",
  "play": "play:family-opt-in@1",
  "path": [
    "family-opt-in-rate",
    "sibling-sourced-share",
    "new-arr",
    "net-new-arr",
    "arr"
  ],
  "experiment": {
    "metric": "family-opt-in-rate",
    "unit": "per-100",
    "heldBack": 26,
    "decision": null
  },
  "readout": {
    "value": 23,
    "n": 260,
    "maturing": 31,
    "interval": [
      18,
      28
    ],
    "readability": "B",
    "basis": "held-back",
    "pooled": false
  },
  "ledger": {
    "spend": 0,
    "workerCost": 1,
    "hours": 1.1,
    "openArr": 2082,
    "wonArr": 694,
    "projectedArr": 383,
    "paybackDays": 1
  }
}

Outside benchmark: no measured range for a same-team box survived the research’s check, so Other Startups’ results (n 18,300 host sign-ups) stand in.

Before it · After it. Before it: your other Startup’s own Plays bring the sign-ups that see the box. After it: owned-newsletter hears every yes as a new subscriber, and instant-response answers the ones who write in.

ExampleCopy Anchor Link

Leaseline ran it from 2026-08-24 to 2026-10-19 (56 days) on your other Startup’s sign-up: 2,140 Form opens, 260 completed sign-ups, 234 shown the box and 26 shown no ask. Read every captured thread at ?threads=all; three follow the tables.

Leaseline → Mia Chen, Sep 3, 09:12:40 · You said yes to Leaseline updates on our maintenance-request app at 09:12 today.¹ Leaseline sends every renewal notice 60 days out, per owner; updates come monthly.² Signed with the Role’s disclosure line. Footer: where and when you said yes, and one-click unsubscribe.³

Mia, Sep 6 · replied to the discovery note: “Renewals are our biggest headache.” She started a trial on Sep 9 and moved to Pro on Oct 4.

- ☑ Get Leaseline updates (recommended)
+ ☐ Leaseline: lease renewal software, same team as this app. Monthly updates.

Sam Ortiz, 2026-10-02 14:31 · “We’d like to try it for our 200 units.” · Leaseline, 14:33 · *Thanks, Sam. Priya, our account lead, replies with times by 15:31.*⁴ The Brief went to Priya (task_622); she wrote at 14:57.

¹ The first line names the host and the date of the yes. ² What Leaseline makes, and its cadence. ³ Every footer says where and when they said yes. ⁴ The routed line, compiled from the Role’s Settings.

Your settingsCopy Anchor Link

---
holdout: 0.1    # 1 Visitor in 10 at the host sees no box, sticky 90 days
---
One unticked Leaseline box on the maintenance app’s sign-up, below every field. Welcome each yes from Leaseline; buying replies go to Priya.

$ npx startup-builder show plays/family-opt-in
holdout 0.1 · 1 box · welcome from Leaseline · AE on buying replies     your file  plays/family-opt-in.mdx:2,4 (Ask 2026-08-24)
worker role:marketing-lead, owns never · chooses 7 (4 rule, 3 read) · sequences family-welcome, launch-sequence, launch-note, closing-note · approval first-send · checks owned-by-a-person, consent-stop, render-check · stops 9 · placements portfolio-network, gmail, outlook, yahoo-mail    catalog  play:family-opt-in@1 (Not live yet, gaps #5)

Every key from the catalogCopy Anchor Link

Compiled, not written: edit the Play record family-opt-in and its Leaseline run, then regenerate. Every step runs from a sentence or a line of code. In your words: the CRM words you know, and where each lives here.