Sibling audiences

# 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":"sibling-audiences"}'

 1import { $ } from 'startup-builder'
 2
 3return await $.Campaign.create({ play: 'sibling-audiences' }, { 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":"sibling-audiences"}' --try   # Not live yet (gaps #2)

{
  "name": "do",
  "arguments": {
    "code": "return await $.Campaign.create({ play: 'sibling-audiences' }, { 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": "sibling-audiences can’t start yet: 1 check fails and 1 warns.",
 6  "checks": [
 7    {
 8      "check": "use-when",
 9      "status": "pass",
10      "observed": "your other Startup: 4,200 Contacts it collected; Lists overlap on small landlords",
11      "doc": "/plays/sibling-audiences#check-use-when",
12      "fix": "Pair with a Startup of yours holding 2,000 or more Contacts, or run retargeting.",
13      "then": "Metric.query"
14    },
15  …

curl "https://api.sb/leaseline.app/events?where=name%20in%20(%22Schedule.fired%22%2C%20%22Consent.withdrawn%22%2C%20%22Contact.created%22%2C%20%22Order.paid%22%2C%20%22Subscription.canceled%22%2C%20%22Offer.published%22%2C%20%22Startup.graduated%22%2C%20%22Complaint.filed%22%2C%20%22Audience.resized%22%2C%20%22Experiment.matured%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_9701"}'

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

 1import { $ } from 'startup-builder'
 2
 3const { events: [last] } = await $.Event.list({ where: 'name in ("Schedule.fired", "Consent.withdrawn", "Contact.created", "Order.paid", "Subscription.canceled", "Offer.published", "Startup.graduated", "Complaint.filed", "Audience.resized", "Experiment.matured")', 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 (\"Schedule.fired\", \"Consent.withdrawn\", \"Contact.created\", \"Order.paid\", \"Subscription.canceled\", \"Offer.published\", \"Startup.graduated\", \"Complaint.filed\", \"Audience.resized\", \"Experiment.matured\")","limit":1}'
npx startup-builder do Trigger.fire --json '{"like":"event_9701"}' --try   # Not live yet (gaps #7)
npx startup-builder do Decision.list --json '{"where":"on = \"audience_12\""}'   # Not live yet (gaps #7)
npx startup-builder do Action.list --json '{"where":"on = \"audience_12\""}'   # Not live yet (gaps #7)

{
  "name": "do",
  "arguments": {
    "code": "const { events: [last] } = await $.Event.list({ where: 'name in (\"Schedule.fired\", \"Consent.withdrawn\", \"Contact.created\", \"Order.paid\", \"Subscription.canceled\", \"Offer.published\", \"Startup.graduated\", \"Complaint.filed\", \"Audience.resized\", \"Experiment.matured\")', 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_903",
 4    "$type": "Decision",
 5    "choice": "add-to-audience",
 6    "reason": "38 new host Contacts passed fresh reads; 11 removals were uploaded and acknowledged first; 16 drawn into the held-out 30 % stay out",
 7    "stakes": "low",
 8    "options": [
 9      "add-to-audience",
10      "hold-out",
11      "leave-out",
12      "pair-two-startups",
13      "answer-a-report",
14      "run-a-lookalike"
15  …

action_2 uploads today’s 11 removals. action_3 adds the 38 new members only once the Venue acknowledges every removal; no file leaves your account, and the Audience name carries no Startup or Market.

≈ +$970 ARR a month at $200

Worth

30 min week 1, then 10 a week

Your time

$14 per added first order, ~$200 a month

Spend

Day 4: the first signup from the sister Audience

First signal

another Startup of yours with 2,000+ Contacts

Use it when

No other Startup: retargeting · no cold winner: promote-winners

Not yet when

Worth’s formula: about +1.4 first paid Orders per $100 (Other Startups’ results; your own read is too early) × $200 a month × $347 Pro ARR ≈ +$972. Under First signal: One 90-day block per read: about 13 weeks to tell +1.4 per $100 at 4,200 Contacts with 30 % held out; under 2,000, 90 days can tell only +3.5 or more.

Start it this weekCopy Anchor Link

npx startup-builder add play sibling-audiences   # 1 · writes plays/sibling-audiences.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":"sibling-audiences"}'

# 3 · keep it, at You approve each one
curl -X POST https://api.sb/leaseline.app/campaigns \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"play":"sibling-audiences"}'

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

# off: every sister ad set pauses and uploads stop
curl -X PATCH https://api.sb/leaseline.app/campaigns/sibling-audiences \
  -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": "sibling-audiences can’t start yet: 1 check fails and 1 warns.",
  "checks": [
    {
      "check": "use-when",
      "status": "pass",
      "observed": "your other Startup: 4,200 Contacts it collected; Lists overlap on small landlords",
      "doc": "/plays/sibling-audiences#check-use-when",
      "fix": "Pair with a Startup of yours holding 2,000 or more Contacts, or run retargeting.",
      "then": "Metric.query"
    },
    {
      "check": "baseline",
      "status": "pass",
      "observed": "0.16 first paid Orders per 100 host Contacts with no Ads, n 4,200",
      "doc": "/plays/sibling-audiences#check-baseline",
      "fix": "Read it once; it fills Before in Your number.",
      "then": "Metric.query"
    },
    {
      "check": "removals-first",
      "status": "fail",
      "observed": "the Facebook connection returns no removal acknowledgments",
      "doc": "/plays/sibling-audiences#check-removals-first",
      "fix": "Reconnect with the Audience scope that acknowledges removals.",
      "then": "Integration.reconnect"
    },
    {
      "check": "role-unstaffed",
      "status": "warn",
      "roles": [
        "marketing-lead"
      ],
      "owned": 0,
      "doc": "/plays/sibling-audiences#check-role-unstaffed",
      "fix": "Staff the Marketing Lead, or leave it: pairings and reports come to you.",
      "then": "Role.staff"
    }
  ]
}

The Ads cost what the Venues bill, capped at $200 a month by your Limit; the daily build, the removal audit and the canaries cost about $0.15 a day (Worker cost). That comes to about $14 for each added first order at Other Startups’ rate.

When it startsCopy Anchor Link

{
  "$id": "https://api.sb/leaseline.app/events/event_9701",
  "$type": "Event",
  "name": "Schedule.fired",
  "at": "2026-10-19T05:00:00Z",
  "seq": 9701,
  "data": {
    "audience": "audience_12",
    "trigger": "sibling-build-due",
    "added": 38,
    "removed": 11,
    "heldOut": 16,
    "readsAgeMinutes": 12
  }
}

npx startup-builder trigger Schedule.fired --like event_9701   # replays the daily build
npx startup-builder clock advance --by 1d   # runs the removal audit and the next build
npx startup-builder listen Consent.withdrawn --forward-to http://localhost:3000/hook

Who runs itCopy Anchor Link

Paid media · your agent (role:paid-media-manager, worker_7) holds the Key Result. Pairing two Startups, any lookalike and every knowledge report come to you (Dana Okafor, person, worker_1), because the Marketing Lead Role has no person. It writes to no one; it builds Audiences. Your number links to Did it work.

What it reads · What it may call. It reads the host’s own Contacts with Suppression, Consent and opt-out reads under 1 hour old, and Leaseline’s approved cold concepts. No Ad names, mimics or borrows the other Startup, or implies anything a Person did there. Its tools are PATCH /{namespace}/audiences/{id}, POST /{namespace}/flags/{flag}/evaluate, POST /{namespace}/audiences, POST /{namespace}/conversations/{conversation}/answer, POST /{namespace}/contacts/{contact}/suppress, POST /{namespace}/ads, and any other call becomes an Approval under the Role’s Mandate.

You hold the paid media Key Result: 2.0 added first orders per $100 by 2027-01-21. ← worker, metric
Each day, upload removals, wait for every acknowledgment, then add.              ← removals-first
Only Contacts the host collected, read fresh within the hour.                    ← first-party, fresh-reads
Hold 30 % out for each 90-day block.                                             ← your file, line 2
Run Leaseline’s approved cold concepts unchanged; never write one for them.      ← copyRules 1, 2
Watch the host: its cancellations among the exposed never rise past held out.    ← host-churn

The slow loop. The block runs to Nov 21 and no Change can touch its held-out share inside it, so there is no replay or read-back to print.

Bring your own agent (folded) starts at It does it for builds only when it matches the seated agent’s removals-first order on the eval suite; spend and pairing stay with you. POST /{namespace}/roles/{role}/staff seats it.

npx startup-builder eval --scenario sibling-audiences-4200 --agent "claude -p" --seat paid-media-manager   # seated: every removal acknowledged before additions, 0 Checks failed served · yours: 1 addition before an acknowledgment, refused

What it can do nextCopy Anchor Link

When it hands to youCopy Anchor Link

This Play hands no buyer to a person. What lands in your queue is the pairing, any lookalike and each knowledge report, because the Marketing Lead Role has no person. As captured (draft and checks are Not live yet, gaps #7).

[
  {
    "$id": "https://api.sb/leaseline.app/approvals/approval_151",
    "$type": "Approval",
    "verdict": "approved",
    "deadline": "2026-08-25T17:00:00Z",
    "draft": "Pair: your other Startup hosts, Leaseline receives; Lists overlap on small landlords; 30 % held out; $200 a month",
    "route": "pair-two-startups",
    "checks": [
      {
        "check": "first-party",
        "status": "pass"
      },
      {
        "check": "removals-first",
        "status": "pass"
      }
    ]
  },
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_914",
    "$type": "Task",
    "assignee": "worker_1",
    "due": "2026-10-02T17:00:00Z",
    "on": "contact_388",
    "brief": {
      "who": "a commenter on the cold concept",
      "said": "How did this ad know me?",
      "chose": "answer-a-report",
      "why": "a knowledge report gets the fixed answer, in your name",
      "never": [
        "arguing",
        "naming what they did anywhere"
      ]
    }
  }
]

You answer with POST /{namespace}/approvals/{approval}/approve or POST /{namespace}/approvals/{approval}/refuse, POST /{namespace}/tasks/{task}/claim (Take this one) or POST /{namespace}/tasks/{task}/return with a reason, each a one-call window. A suppression request never waits on you: it leaves every Audience at the next build. A Task nobody claims by its due time goes up a Role through POST /{namespace}/tasks/{task}/escalate, and person-promise fires.

On time: you, 2 of 2 within 1 business day, n 2, ■□□□ Too early to tell beside Other Startups’ 95 % on time. Your queue: in week 1, the pairing and 2 concepts to approve; then about 1 report a month and the weekly review.

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 concept that ran instead is in Example.

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "The concept did not run in the sister ad set: it addresses the other Startup’s users by name.",
  "checks": [
    {
      "check": "knowledge-hold",
      "status": "fail",
      "doc": "/plays/sibling-audiences#check-knowledge-hold",
      "fix": "Run Leaseline’s approved cold concept unchanged.",
      "then": "Ad.update"
    },
    {
      "check": "price",
      "status": "pass"
    }
  ]
}

[
  {
    "reason": {
      "limit": "removal-lag",
      "observed": "3 removals unacknowledged at 26h",
      "bound": "24h",
      "window": "Facebook, Sep 15 build"
    },
    "doc": "/plays/sibling-audiences#stop-removal-lag",
    "task": "task_902"
  }
]

Did it workCopy Anchor Link

The host’s Contacts were held out at random, 30 % for the block that ends Nov 21 (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_903",
  "$type": "Decision",
  "choice": "add-to-audience",
  "reason": "38 new host Contacts passed fresh reads; 11 removals were uploaded and acknowledged first; 16 drawn into the held-out 30 % stay out",
  "stakes": "low",
  "options": [
    "add-to-audience",
    "hold-out",
    "leave-out",
    "pair-two-startups",
    "answer-a-report",
    "run-a-lookalike"
  ],
  "by": "worker_7",
  "on": "audience_12",
  "expected": "removals acknowledged within 24h; first paid Orders per $100 above the held-out rate by the block’s end",
  "reopensWhen": "a removal unacknowledged at 24h, or a canary still in the Audience"
}

The leaf counts Leaseline first paid Orders from the host’s Contacts, exposed against held out, less any rise in the host’s cancellations, per $100 of sister spend over the 90-day block; the block reads on Nov 21.

How it moves it: people who already pay your other Startup saw Leaseline’s best cold concept, unchanged, at a 7-day frequency of 3.2.

Guardrails: exposed against held out, the pair under sibling-sourced-share: host cancellations, 1.9 against 2.3 per 100 host Customers, and sister-product opt-outs, 1.0 against 0.8 per 1,000.

{
  "$id": "https://api.sb/leaseline.app/campaigns/sibling-audiences",
  "$type": "Campaign",
  "play": "play:sibling-audiences@1",
  "path": [
    "sibling-audience-lift",
    "sibling-sourced-share",
    "new-arr",
    "net-new-arr",
    "arr"
  ],
  "experiment": {
    "metric": "sibling-audience-lift",
    "unit": "ratio",
    "heldBack": 1260,
    "decision": null
  },
  "readout": {
    "value": 2.6,
    "n": 4200,
    "maturing": 4200,
    "interval": [
      -0.1,
      4.8
    ],
    "readability": "inadmissible",
    "basis": "held-back",
    "pooled": false
  },
  "ledger": {
    "spend": 360,
    "workerCost": 8,
    "hours": 1.4,
    "pipelineArr": 0,
    "wonArr": 4858,
    "projectedArr": 972,
    "paybackDays": 27
  }
}

Outside benchmark: this Play’s catalog record carries no sourced range yet, so Other Startups’ results stand in: +1.4 added first orders per $100, ■■■□ Likely, n 61,000 Contacts.

Before it · After it. Before it: family-opt-in and your other Startup’s own Plays collect the Contacts it hosts. After it: product-led and instant-response take the trials and forms it brings, and cross-sell holds the sister-product Offers inside each product.

ExampleCopy Anchor Link

Leaseline ran it from 2026-08-24 to 2026-10-19 (56 days) as the receiver, with Unitledger, Dana’s other Startup, as the host: 4,414 host Contacts, 214 left out by the Guard, and 4,200 assigned, 2,940 exposed and 1,260 held out, on Facebook and Instagram at about $6.40 a day. Read every captured Ad and comment at ?threads=all; three follow the tables.

Leaseline’s cold concept, Instagram, Sep 9 · Every renewal notice, 60 days out, for every owner you manage. Try Leaseline free for 14 days.¹

A small landlord who keeps her books in Unitledger, exposed, Sep 10 · started a trial; paid for Pro on Sep 24: +$347 ARR, an Acquisition of kind sibling.²

- Already on Unitledger? Add Leaseline and your renewals sync with your books.
+ Every renewal notice, 60 days out, for every owner you manage. Try Leaseline free for 14 days.

A commenter, 2026-10-01 18:20 · “How did this ad know me?” · The agent, 18:21 · drafted the fixed answer and assigned it to you (task_914), due tomorrow 17:00 · Dana, Oct 2 09:05 · posted it: the privacy notice, the entity it names and a one-step opt-out.³ They opted out; they left every Audience at the next build.

¹ Leaseline’s approved cold concept, unchanged: nothing written for the sister Audience. ² Credit through noun:acquisition with kind sibling; the sister product’s own cancellations read beside it. ³ The answer copy rule 10 fixes: never an argument.

Your settingsCopy Anchor Link

---
holdout: 0.3      # 30 % of the host’s Contacts held out for each 90-day block
budget: $200/month
---
Rebuild daily: removals first, then additions, on reads under 1 hour old.
Run Leaseline’s approved cold concepts only, unchanged.

$ npx startup-builder show plays/sibling-audiences
holdout 0.3 · budget $200/month · daily build, removals first · cold concepts unchanged     your file  plays/sibling-audiences.mdx:2,3,5,6 (Ask 2026-08-24)
worker role:paid-media-manager, owns never · chooses 6 (4 rule, 2 read) · approval first-send, every-send · checks fresh-reads, removals-first, first-party, knowledge-hold, consent-stop, claims-resolve, price · stops 13 · placements facebook, instagram, linkedin, google-display    catalog  play:sibling-audiences@1 (Not live yet, gaps #5)

Every key from the catalogCopy Anchor Link

Compiled, not written: edit the Play record sibling-audiences 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.