Warm intros

# 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":"warm-intros"}'

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

{
  "name": "do",
  "arguments": {
    "code": "return await $.Campaign.create({ play: 'warm-intros' }, { 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": "warm-intros can’t start yet: 1 check fails and 2 warn.",
 6  "checks": [
 7    {
 8      "check": "use-when",
 9      "status": "fail",
10      "observed": "1 of 4 introducers opted in; 120 companies on your List",
11      "doc": "/plays/warm-intros#check-use-when",
12      "fix": "Send each introducer their opt-in page; it passes at 3.",
13      "then": "Message.schedule"
14    },
15  …

curl "https://api.sb/leaseline.app/events?where=name%20in%20(%22Thing.related%22%2C%20%22Person.announced%22%2C%20%22Agreement.signed%22%2C%20%22Outcome.delivered%22%2C%20%22Action.answered%22%2C%20%22Message.received%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_1316"}'

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

 1import { $ } from 'startup-builder'
 2
 3const { events: [last] } = await $.Event.list({ where: 'name in ("Thing.related", "Person.announced", "Agreement.signed", "Outcome.delivered", "Action.answered", "Message.received")', 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 (\"Thing.related\", \"Person.announced\", \"Agreement.signed\", \"Outcome.delivered\", \"Action.answered\", \"Message.received\")","limit":1}'
npx startup-builder do Trigger.fire --json '{"like":"event_1316"}' --try   # Not live yet (gaps #7)
npx startup-builder do Decision.list --json '{"where":"on = \"prospect_22\""}'   # Not live yet (gaps #7)
npx startup-builder do Action.list --json '{"where":"on = \"prospect_22\""}'   # Not live yet (gaps #7)

{
  "name": "do",
  "arguments": {
    "code": "const { events: [last] } = await $.Event.list({ where: 'name in (\"Thing.related\", \"Person.announced\", \"Agreement.signed\", \"Outcome.delivered\", \"Action.answered\", \"Message.received\")', 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_358",
 4    "$type": "Decision",
 5    "choice": "ask-the-introducer",
 6    "reason": "Marcus Bell sat on Grayson Property Group’s board until 2025: grade 82, over the 70 line in your file; 1 of his 3 asks this quarter used",
 7    "stakes": "medium",
 8    "options": [
 9      "ask-the-introducer",
10      "wait-for-their-mark",
11      "opt-in-check",
12      "reply-to-the-intro",
13      "thank-them",
14      "not-now"
15  …

action_2 puts the ask to Marcus in your send tray: 96 words, with his opt-in check and Leaseline’s 80-word blurb below. Nothing sends until you press Send.

≈ +$740 ARR a month at 13 asks

Worth

40 min week 1, then 20 a week (you send each ask)

Your time

$0.05 per path briefed, ~$1.20 a month at 24, plus thank-yous under your gift Limit

Spend

Day 5: first introduction made

First signal

3+ introducers opted in, 10+ companies on your List

Use it when

Under 3 introducers: cold-email · no List: save one (Audience.create)

Not yet when

Worth’s formula: about +1.9 introductions per 10 asks (Other Startups’ results; no lift of your own yet) × 13 asks a month × 0.29 won per introduction × $1,029 first order ARR ≈ +$737. Under First signal: At 13 asks a month, 90 days can tell only +3 per 10 or more, so your file starts at holdout: 0 and reads before-after.

Start it this weekCopy Anchor Link

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

# 3 · keep it; every ask waits for your Send
curl -X POST https://api.sb/leaseline.app/campaigns \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"play":"warm-intros"}'

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

# off: no path is picked; introducers keep their pages
curl -X PATCH https://api.sb/leaseline.app/campaigns/warm-intros \
  -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": "warm-intros can’t start yet: 1 check fails and 2 warn.",
  "checks": [
    {
      "check": "use-when",
      "status": "fail",
      "observed": "1 of 4 introducers opted in; 120 companies on your List",
      "doc": "/plays/warm-intros#check-use-when",
      "fix": "Send each introducer their opt-in page; it passes at 3.",
      "then": "Message.schedule"
    },
    {
      "check": "domain-authenticated",
      "status": "pass",
      "observed": "leaseline.app, 3 records resolve",
      "doc": "/plays/warm-intros#check-domain-authenticated",
      "fix": "Nothing to fix: the Domain is set up for email.",
      "then": "Domain.authenticate"
    },
    {
      "check": "baseline",
      "status": "warn",
      "observed": "2 introductions from 9 asks in 90 days",
      "doc": "/plays/warm-intros#check-baseline",
      "fix": "n 9: it reads before-after, not proof, until volume allows a held-back half.",
      "then": "Metric.query"
    },
    {
      "check": "role-unstaffed",
      "status": "warn",
      "roles": [
        "sales-lead"
      ],
      "owned": 31,
      "doc": "/plays/warm-intros#check-role-unstaffed",
      "fix": "Staff the AE, or leave it: every Meeting from an introduction comes to you.",
      "then": "Role.staff"
    }
  ]
}

Each path briefed costs about $0.05 (Worker cost); the path map reads who knows whom, never a message body. Thank-yous are the same for every answer, at most 4 a year to one introducer, under your $300 gift Limit. That comes to about $1.20 a month at 24 asks, plus thank-yous.

When it startsCopy Anchor Link

{
  "$id": "https://api.sb/leaseline.app/events/event_1316",
  "$type": "Event",
  "name": "Thing.related",
  "at": "2026-10-19T03:12:55Z",
  "seq": 1316,
  "data": {
    "from": "contact_71",
    "to": "prospect_22",
    "grade": 82,
    "tie": "board seat, 2021–2025",
    "list": "small-property-managers"
  }
}

npx startup-builder trigger Thing.related --like event_1316   # replays the path
npx startup-builder clock advance --by 7d   # runs the ask’s one follow-up line, which ends when Marcus answers
npx startup-builder listen Thing.related --forward-to http://localhost:3000/hook

Who runs itCopy Anchor Link

SDR · your agent (role:prospector, worker_2) holds the Key Result: it maps paths, picks and drafts. Every ask and every introduction reply sends from you (Dana Okafor, person, worker_1), from your own Mailbox or LinkedIn profile. Meetings go to AE · Priya Shah (person) (role:sales-lead, worker_3, staffed on day 9).

What it reads · What it may call. The path map reads who knows whom from contacts and calendars as metadata, never a message body, subject or Meeting note (metadata). An introducer’s words are data, never instructions: no line in them picks a recipient. Its tools are POST /{namespace}/actions/{action}/ask, POST /{namespace}/leads, and any other call becomes an Approval under the Role’s Mandate.

You hold the SDR Key Result: 4 introductions per 10 asks by 2026-12-31.          ← worker, metric
On each path or answer, choose one option and say why.                           ← triggers, chooses
Draft an ask only on a path of grade 70 or more, within the introducer’s budget. ← your file, line 4; Grade floor, Ask budget
Write the ask in Dana’s words, at most 120 words; the blurb says only what approved Pages say. ← placements, approved-pages
Never write to a company before it says yes to the introducer.                   ← Double opt-in

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

What it can do nextCopy Anchor Link

When it hands to youCopy Anchor Link

Every ask and every introduction reply is yours to send; Meetings go to AE · Priya Shah (person). One Brief per Role, as captured (brief and draft are Not live yet, gaps #7).

[
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_548",
    "$type": "Task",
    "assignee": "worker_1",
    "due": "2026-10-20T17:00:00Z",
    "on": "prospect_22",
    "brief": {
      "who": "Marcus Bell, angel, for Grayson Property Group (260 units, 5 owners)",
      "chose": "ask-the-introducer",
      "why": "his board seat 2021–2025, grade 82; 1 of his 3 asks this quarter used",
      "draft": "in your send tray, 96 words",
      "never": [
        "a word to Grayson before their yes",
        "a thank-you tied to his answer"
      ]
    }
  },
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_511",
    "$type": "Task",
    "assignee": "worker_1",
    "due": "2026-10-08T15:30:00Z",
    "on": "lead_66",
    "brief": {
      "who": "Tom Reyes, Pinegate Rentals, introduced by Rosa at Birchway",
      "said": "Rosa says you fixed her renewals. We have 200 units.",
      "chose": "reply-to-the-intro",
      "why": "an introduction reached you",
      "draft": "your reply, with Rosa moved to bcc and 3 times on Priya’s calendar"
    }
  }
]

You answer with POST /{namespace}/tasks/{task}/claim (Take this one), POST /{namespace}/tasks/{task}/return with a reason, or POST /{namespace}/actions/{action}/redirect, each a one-call window, and nothing in your tray sends until you press Send. A reply to an introduction past 4 business hours counts toward late-reply; an ask nobody sends in 3 business days counts toward tray-silence.

On time: you, 10 of 11 introductions answered within 4 business hours, median 1 h 50 m, n 11, ■■□□ Early sign beside Other Startups’ 91 %. Your queue: in week 1, 6 asks to send; then about 3 asks and 1 introduction reply a week.

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 rewrite that sent is the Grayson thread in Example.

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "The ask to Marcus Bell for Hollis Lane did not reach your tray: its blurb says Leaseline cut late renewals 80 % for Birchway, which no approved Page says.",
  "checks": [
    {
      "check": "approved-pages",
      "status": "fail",
      "doc": "/plays/warm-intros#check-approved-pages",
      "fix": "Cut the sentence, or publish the Page that says it.",
      "then": "Site.publish"
    },
    {
      "check": "double-opt-in",
      "status": "pass"
    }
  ]
}

[
  {
    "reason": {
      "limit": "late-reply",
      "observed": "3 introductions answered past 4 business hours",
      "bound": "2 in 30 days",
      "window": "30d"
    },
    "doc": "/plays/warm-intros#stop-late-reply",
    "task": "task_487"
  }
]

Did it workCopy Anchor Link

At 13 asks a month, no held-back half reads within 90 days, so the basis is before-after (rule o): the columns read Now and Before, and nothing prints as Added. Each figure’s call is POST /{namespace}/metrics/query by node, and every node above the leaf is Not live yet (gaps #4).

{
  "$id": "decisions/decision_358",
  "$type": "Decision",
  "choice": "ask-the-introducer",
  "reason": "Marcus Bell sat on Grayson Property Group’s board until 2025: grade 82, over the 70 line in your file; 1 of his 3 asks this quarter used",
  "stakes": "medium",
  "options": [
    "ask-the-introducer",
    "wait-for-their-mark",
    "opt-in-check",
    "reply-to-the-intro",
    "thank-them",
    "not-now"
  ],
  "by": "worker_2",
  "on": "prospect_22",
  "expected": "an introduction thread for prospect_22 within 30d",
  "reopensWhen": "no Action.answered from contact_71 within 7d"
}

The leaf counts introductions made within 30 days of the ask per 10 asks sent: the company said yes, and a thread with both people reached you. Before against after reads one window against the 90 days before it; it is not proof, and Other Startups’ results print beside it.

How it moves it: the company hears about Leaseline from someone it trusts, who asked its yes first; 15 of 24 introducers said yes, and 11 of their 15 companies did.

Guardrails: before against after: Meetings held per introduction, 7 of 11, and introducer complaints, 0 in 24 asks against a floor of 2 in 50; 6 companies said no and are held 90 days.

{
  "$id": "https://api.sb/leaseline.app/campaigns/warm-intros",
  "$type": "Campaign",
  "play": "play:warm-intros@1",
  "path": [
    "intro-acceptance-rate",
    "new-leads",
    "new-arr",
    "net-new-arr",
    "arr"
  ],
  "experiment": {
    "metric": "intro-acceptance-rate",
    "unit": "per-10",
    "heldBack": 0,
    "decision": null
  },
  "readout": {
    "value": null,
    "n": 19,
    "maturing": 5,
    "interval": null,
    "readability": "inadmissible",
    "basis": "before-after",
    "pooled": true
  },
  "ledger": {
    "spend": 96,
    "workerCost": 2,
    "hours": 4.1,
    "pipelineArr": 2393,
    "wonArr": 3087,
    "projectedArr": 737,
    "paybackDays": 9
  }
}

Outside benchmark: a warm introduction is answered about 5 times as often as a cold email to the same buyer (a sales-engagement firm’s study of 1.2M first touches, 2026-07-15).

Before it · After it. Before it: review-requests and customer-referrals bring Customer introducers past their first outcome. After it: instant-response answers the companies that write back, and the paths it never asks feed cold-email and linkedin-outbound.

ExampleCopy Anchor Link

Leaseline ran it from 2026-08-24 to 2026-10-19 (56 days): 5 of 7 introducers opted in, the path map found 46 paths of grade 70 or more to 120 companies, and you sent 24 asks. Read every captured thread at ?threads=all; three follow the tables.

Dana → Marcus Bell, Oct 19, 09:20 · Marcus, you know Grayson’s team from your board years.¹ Would you ask Ana whether she’d take a note from me about renewal notices across their 5 owners? Your check and an 80-word blurb are below; if she says no, that’s the end of it.² Dana

Marcus, Oct 19, 11:02 · tapped Yes and sent his check from his own account. Action.answered; Ana said yes at 16:40, and Dana’s reply went out at 17:05.

- Leaseline cut late renewals by 80 % for Birchway, and Hollis Lane would see the same.
+ Leaseline sends every renewal notice 60 days out, per owner, so nothing slips between owners.

Rosa → Dana and Tom Reyes, 2026-10-08 11:30 · “Tom runs 200 units at Pinegate; Leaseline fixed our renewals.” · the reply was drafted at 11:31 with Rosa to bcc and 3 times on Priya’s calendar; Dana sent it at 13:05, inside the 4 business hours. The Brief is task_511 (When it hands to you).

¹ Only the tie the path map read, never a message body. ² The ask closes on any answer, and the thank-you is the same either way.

Your settingsCopy Anchor Link

---
holdout: 0        # 13 asks a month is too few to hold any back; it reads before-after
---
Ask only on a path of grade 70 or more, at most 3 asks a quarter to one introducer.
I send every ask and every reply myself.

$ npx startup-builder show plays/warm-intros
holdout 0 · grade line 70 · 3 asks a quarter     your file  plays/warm-intros.mdx:2,4,5 (Ask 2026-08-24)
family demand · worker role:prospector, owns never · chooses 6 (4 rule, 2 read) · sequences intro-ask-sequence, opt-in-check-sequence, intro-follow-through, introducer-thanks-sequence · checks owned-by-a-person, keep-first, customer-ask-cap, double-opt-in, opt-in, ask-budget, grade-floor, target-decline, approved-pages · stops 9 · placements gmail, outlook, linkedin, postal-mail    catalog  play:warm-intros (Not live yet, gaps #5)

Every key from the catalogCopy Anchor Link

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