Proof-of-work outreach

# 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":"proof-of-work-outreach"}'

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

{
  "name": "do",
  "arguments": {
    "code": "return await $.Campaign.create({ play: 'proof-of-work-outreach' }, { 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": "proof-of-work-outreach can’t start yet: 1 check fails and 2 warn.",
 6  "checks": [
 7    {
 8      "check": "use-when",
 9      "status": "pass",
10      "observed": "a List of 214 fit Prospects; the calendar runs on public listings",
11      "doc": "/plays/proof-of-work-outreach#check-use-when",
12      "fix": "Keep 100 or more fit Prospects, or run warm-intros first.",
13      "then": "Metric.query"
14    },
15  …

curl "https://api.sb/leaseline.app/events?where=name%20in%20(%22Opening.published%22%2C%20%22Company.filed%22%2C%20%22Review.published%22%2C%20%22Company.funded%22%2C%20%22Monitor.checked%22%2C%20%22Visit.recorded%22%2C%20%22Question.asked%22%2C%20%22Page.viewed%22%2C%20%22Conversation.answered%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_5204"}'

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

 1import { $ } from 'startup-builder'
 2
 3const { events: [last] } = await $.Event.list({ where: 'name in ("Opening.published", "Company.filed", "Review.published", "Company.funded", "Monitor.checked", "Visit.recorded", "Question.asked", "Page.viewed", "Conversation.answered")', 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 (\"Opening.published\", \"Company.filed\", \"Review.published\", \"Company.funded\", \"Monitor.checked\", \"Visit.recorded\", \"Question.asked\", \"Page.viewed\", \"Conversation.answered\")","limit":1}'
npx startup-builder do Trigger.fire --json '{"like":"event_5204"}' --try   # Not live yet (gaps #7)
npx startup-builder do Decision.list --json '{"where":"on = \"prospect_88\""}'   # Not live yet (gaps #7)
npx startup-builder do Action.list --json '{"where":"on = \"prospect_88\""}'   # Not live yet (gaps #7)

{
  "name": "do",
  "arguments": {
    "code": "const { events: [last] } = await $.Event.list({ where: 'name in (\"Opening.published\", \"Company.filed\", \"Review.published\", \"Company.funded\", \"Monitor.checked\", \"Visit.recorded\", \"Question.asked\", \"Page.viewed\", \"Conversation.answered\")', 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_548",
 4    "$type": "Decision",
 5    "choice": "send-the-finding",
 6    "reason": "a tier 1 finding that reproduced twice: 12 of the 46 units Fernhill lists turn over before Jan 31, from its listings page on Oct 18",
 7    "stakes": "low",
 8    "options": [
 9      "send-the-finding",
10      "from-the-founder",
11      "benchmark-row",
12      "printed-letter",
13      "open-a-fix",
14      "send-the-work",
15  …

action_3 is the noindex Sample Page with the calendar, its source, date and correction line. action_4 is the plain email to Fernhill’s Ana Ruiz (contact_31), waiting for your approval: every proof email is approved before it sends.

≈ +$1,000 ARR a month at 170

Worth

1 h week 1, then 20 min a week

Your time

$0.18 per Prospect, ~$31 a month at 170

Spend

Day 2: the first Meeting booked

First signal

100+ fit Prospects, a Verb that runs on public data

Use it when

Under 100: warm-intros · needs their private data: cold-email

Not yet when

Worth’s formula: about +9.0 qualified replies per 100 × 170 Prospects a month × 0.12 replies to paid (your last 90 days) × $547 first order ARR ≈ +$1,004. Under First signal: About 7 weeks to tell a +6 lift at 170 a month (5 to read, 2 to mature); at 100 a month, about 11 weeks.

Also runs as: Benchmark rows.

Start it this weekCopy Anchor Link

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

# 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":"proof-of-work-outreach"}'

# on
curl -X POST https://api.sb/leaseline.app/processes/outbound/enable \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

# off: nothing sends; live Sample Pages keep their stated expiry
curl -X POST https://api.sb/leaseline.app/processes/outbound/pause \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "proof-of-work-outreach can’t start yet: 1 check fails and 2 warn.",
  "checks": [
    {
      "check": "use-when",
      "status": "pass",
      "observed": "a List of 214 fit Prospects; the calendar runs on public listings",
      "doc": "/plays/proof-of-work-outreach#check-use-when",
      "fix": "Keep 100 or more fit Prospects, or run warm-intros first.",
      "then": "Metric.query"
    },
    {
      "check": "baseline",
      "status": "pass",
      "observed": "4.2 qualified replies per 100 plain first emails, n 140 in 90 days",
      "doc": "/plays/proof-of-work-outreach#check-baseline",
      "fix": "Read it once; it fills Before in Your number.",
      "then": "Metric.query"
    },
    {
      "check": "domain-authenticated",
      "status": "fail",
      "observed": "leaseline-mail.com, the outbound Domain, has no DNS records",
      "doc": "/plays/proof-of-work-outreach#check-domain-authenticated",
      "fix": "Add the 3 DNS records for leaseline-mail.com; it passes once they resolve.",
      "then": "Domain.authenticate"
    },
    {
      "check": "mailbox-warm",
      "status": "warn",
      "observed": "dana@leaseline-mail.com, day 0 of warm-up",
      "doc": "/plays/proof-of-work-outreach#check-mailbox-warm",
      "fix": "Warm the Mailbox; sends ramp over 14 days.",
      "then": "Mailbox.warm"
    },
    {
      "check": "role-unstaffed",
      "status": "warn",
      "roles": [
        "sales-lead"
      ],
      "owned": 9,
      "doc": "/plays/proof-of-work-outreach#check-role-unstaffed",
      "fix": "Staff the AE, or leave it: requests for the work come to you.",
      "then": "Role.staff"
    }
  ]
}

Each proof check costs $0.02, each Sample Page $0.12 to build and re-run, and each email $0.04 from your outbound Domain (Worker cost); a printed letter costs $1.40. That comes to about $31 a month at 170 Prospects and $18 at 100.

When it startsCopy Anchor Link

{
  "$id": "https://api.sb/leaseline.app/events/event_5204",
  "$type": "Event",
  "name": "Monitor.checked",
  "at": "2026-10-18T06:00:12Z",
  "seq": 5204,
  "data": {
    "prospect": "prospect_88",
    "organization": "organization_41",
    "monitor": "monitor_88",
    "url": "https://fernhillpc.example/listings",
    "changed": true,
    "units": 46
  }
}

npx startup-builder trigger Monitor.checked --like event_5204   # replays the change
npx startup-builder clock advance --by 14d   # runs the monthly sequence’s day-14 step, which ends on any reply
npx startup-builder listen Monitor.checked --forward-to http://localhost:3000/hook

Who runs itCopy Anchor Link

SDR · your agent (role:prospector, worker_2) holds the Key Result. It hands requests for the work to AE · Priya Shah (person) (role:sales-lead, worker_3, staffed on day 9), and founder notes and repository fixes to you (Dana Okafor, person, worker_1), who send them under your own name. Your number links to Did it work.

What it reads · What it may call. It reads only the Prospect’s public pages, never past an auth wall, a rate limit or a robots refusal (fetch). A Sample Page view raises the next touch’s score and never appears in a Message. Its tools are POST /{namespace}/tasks/{task}/assign, POST /{namespace}/changes/{change}/review, POST /{namespace}/conversations/{conversation}/answer, POST /{namespace}/meetings/book, and any other call becomes an Approval under the Role’s Mandate.

You hold the SDR Key Result: 12 qualified replies per 100 by 2026-12-31.         ← worker, metric
On each Trigger, choose one option and say why; no finding sends nothing.        ← triggers, chooses, finding
The first email asks for nothing: no meeting, no call, no question mark.         ← copyRules 2
One finding with its number; the rest wait on the Sample Page.                   ← copyRules 4
Over 300 units, draft a note for Dana to send herself.                           ← your file, line 5
Never write to a Lead or Deal a person owns: draft it into their queue.          ← worker.owns, owned-by-a-person

The slow loop, as a Change. decision_517 (2026-09-28, weekly) read that emails naming the turnover count in the first line drew 15.0 qualified replies per 100 against 9.8 with it in the second, so change_31 moved the finding line first (the template) and Dana merged it with POST /{namespace}/changes/{change}/merge. Replayed on past sends, POST /{namespace}/changes/{change}/review put the agent half at 14.1 per 100; read back at +21d it is 13.6, n 66, ■□□□ Too early to tell beside Other Startups’ +8.0 (Example, day 56).

Bring your own agent (folded) starts at You approve each one whatever it scores, because every proof email here is approved before it sends; POST /{namespace}/roles/{role}/staff seats it.

npx startup-builder eval --scenario proof-of-work-outreach-288 --agent "claude -p" --seat prospector   # seated: 13.2 per 100, every claim traced, 0 Checks failed sent · yours: 11.4, 2 claims untraced

What it can do nextCopy Anchor Link

When it hands to youCopy Anchor Link

Requests for the work and every Interested reply go to AE · Priya Shah (person); founder notes, repository fixes and every approval come to you, and before day 9 every hand-off did. One Brief per Role, as captured (brief is Not live yet, gaps #7).

[
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_611",
    "$type": "Task",
    "assignee": "worker_3",
    "due": "2026-10-14T16:05:00Z",
    "on": "lead_91",
    "brief": {
      "who": "Ana Ruiz, Fernhill Property Co",
      "said": "This is useful. Can we talk Thursday?",
      "chose": "send-the-work",
      "why": "she asked for the full calendar, then a call",
      "shown": "12 of 46 listed units turn over before Jan 31",
      "never": [
        "a price beyond the list",
        "a discount",
        "terms"
      ]
    }
  },
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_590",
    "$type": "Task",
    "assignee": "worker_1",
    "due": "2026-10-02T17:00:00Z",
    "on": "prospect_74",
    "brief": {
      "who": "Oakmont Residential, 800 units",
      "chose": "from-the-founder",
      "why": "a strong fit with a tier 3 build",
      "draft": "a 4-line note from you, with the full calendar on its Sample Page"
    }
  }
]

Each receiver answers with POST /{namespace}/tasks/{task}/claim (Take this one), POST /{namespace}/tasks/{task}/return with a reason, POST /{namespace}/actions/{action}/redirect, POST /{namespace}/approvals/{approval}/approve or POST /{namespace}/approvals/{approval}/refuse, each a one-call window. Once a person claims, the agent’s pending steps to that Prospect cancel with claimedByPerson (Not live yet, gaps #7), and every reply goes to the claimer. A Task nobody claims by its due time goes up a Role through POST /{namespace}/tasks/{task}/escalate (AE to you), and person-promise fires.

On time: AE · Priya Shah, 17 of 18 claimed within 60 min, median 24 min, ■■□□ Early sign, n 18; you, 9 of 9 founder notes within 1 business day, n 9. Your queue: about 30 approvals a week, read in 2 sittings, plus 1 weekly review, 2 founder notes and 3 hand-offs to Priya.

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 Birch Lane thread in Example.

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "The email to Birch Lane Rentals did not send: it states a revenue figure no snapshot holds.",
  "checks": [
    {
      "check": "claims-resolve",
      "status": "fail",
      "doc": "/plays/proof-of-work-outreach#check-claims-resolve",
      "fix": "Cut the sentence, or cite the snapshot that holds it.",
      "then": "Content.draft"
    },
    {
      "check": "finding",
      "status": "pass"
    }
  ]
}

[
  {
    "reason": {
      "limit": "unanswered-delivery",
      "observed": "7m 40s",
      "bound": "5m",
      "window": "1 request"
    },
    "doc": "/plays/proof-of-work-outreach#stop-unanswered-delivery",
    "task": "task_602"
  }
]

Did it workCopy Anchor Link

Both halves are read from the same random assignment, made once the finding gate ran (rules m–o): the agent half got the proof email, your half your plain first email. Each figure’s call is POST /{namespace}/metrics/query by node and by arm; every node above the leaf is Not live yet (gaps #4).

{
  "$id": "decisions/decision_548",
  "$type": "Decision",
  "choice": "send-the-finding",
  "reason": "a tier 1 finding that reproduced twice: 12 of the 46 units Fernhill lists turn over before Jan 31, from its listings page on Oct 18",
  "stakes": "low",
  "options": [
    "send-the-finding",
    "from-the-founder",
    "benchmark-row",
    "printed-letter",
    "open-a-fix",
    "send-the-work",
    "no-finding"
  ],
  "by": "worker_2",
  "on": "prospect_88",
  "expected": "a qualified reply by day 14",
  "reopensWhen": "no Conversation.answered from prospect_88 within 14d"
}

The leaf counts qualified replies (Interested, a referral, an objection with a reason, Not now with a date) within 14 days per 100 Prospects assigned (rule m), to 200 matured in each half; at 144 and 144 so far the Experiment runs on.

How it moves it: each first email carried one finished count about the Prospect’s own units, where your half’s email carried none.

Guardrails: treated against held back: Meetings per qualified reply, 0.63 against 0.67 (opened-deals-and-trials per reply), and stop requests, 1.4 % against 1.1 %.

{
  "$id": "https://api.sb/leaseline.app/campaigns/proof-of-work-outreach",
  "$type": "Campaign",
  "play": "play:proof-of-work-outreach@1",
  "path": [
    "proof-reply-rate",
    "new-leads",
    "new-arr",
    "net-new-arr",
    "arr"
  ],
  "experiment": {
    "metric": "proof-reply-rate",
    "unit": "per-100",
    "heldBack": 160,
    "decision": null
  },
  "readout": {
    "value": 9,
    "n": 288,
    "maturing": 32,
    "interval": [
      2.6,
      15.4
    ],
    "readability": "C",
    "basis": "held-back",
    "pooled": false
  },
  "ledger": {
    "spend": 8,
    "workerCost": 21,
    "hours": 4.1,
    "pipelineArr": 6564,
    "wonArr": 1642,
    "projectedArr": 1004,
    "paybackDays": 6
  }
}

Outside benchmark: this Play’s catalog record carries no sourced range yet, so Other Startups’ results stand in: +8.0 qualified replies per 100, ■■■□ Likely, n 4,120.

Before it · After it. Before it: account-visits and the List feed it fit Prospects; benchmark-rows runs inside it. After it: closer-handoff hears each Meeting it books, buying-committee hears a Sample read in 3 or more places, and lead-nurture holds Not now with a date.

ExampleCopy Anchor Link

Leaseline ran it from 2026-08-24 to 2026-10-19 (56 days). 354 Prospects were checked, 34 had no finding and stayed on the List, and 320 were assigned at random, 160 to each half; 288 have matured and 32 are still maturing. Read every captured thread at ?threads=all; three follow the tables.

Leaseline → Ana Ruiz at Fernhill, Oct 13 08:10 · From the 46 units on fernhillpc.example/listings, checked Oct 12: 12 turn over before Jan 31.¹ The calendar of notices Leaseline would send for them is here: leaseline-mail.com/s/fernhill.² *Signed with the Role’s disclosure line.*³

Ana, Oct 13 15:58 · “This is useful. Can you send the full calendar?” The full calendar went into the thread at 16:01.

Ana, 16:04 · “Can we talk Thursday?” POST /{namespace}/meetings/book booked it on Priya’s calendar, and the Brief reached her at 16:05 (When it hands to you).

- With about $2M in rent a year, missing even one renewal costs you.
+ From the 31 units on birchlanerentals.example, checked Sep 15: 7 turn over before Dec 15.

Oakmont Residential, 2026-10-01 · a tier 3 build: the full 800-unit calendar · The agent, 09:30 · drafted a 4-line note for Dana and assigned it (task_590) · Dana, from her own Mailbox, 14:12 · sent it as drafted, with one line of her own.⁴

¹ One finding with its number, from a public source and a date; no question. ² Exactly one link, on the outbound Domain, to a noindex Sample Page with its source and correction line. ³ The fixed signature line, compiled from the Role’s disclosure Setting. ⁴ A person’s edit, labeled on the Sample Page.

Your settingsCopy Anchor Link

---
holdout: 0.5      # half the Prospects get Dana’s plain first email, as today
---
Send each Prospect the 90-day turnover calendar from their public listings, finding first.
Over 300 units, draft a note for Dana to send herself.

$ npx startup-builder show plays/proof-of-work-outreach
holdout 0.5 · the calendar, finding first · founder note over 300 units     your file  plays/proof-of-work-outreach.mdx:2,4,5 (Ask 2026-08-24; line 4 by change_31, 2026-09-28)
worker role:prospector, owns never · chooses 7 (3 rule, 4 read) · sequences proof-of-work-monthly, proof-of-work-monthly-founder, proof-of-work-printed, proof-delivery-thread, pull-request-touch · approval every-send · checks owned-by-a-person, customer-collision, finding, claims-resolve, sample-rule, organization-lock, fingerprint, mailbox-warm · stops 10 (9 shown) · placements gmail, outlook, yahoo-mail, linkedin, github, postal-mail    catalog  play:proof-of-work-outreach@1 (Not live yet, gaps #5)

Every key from the catalogCopy Anchor Link

Compiled, not written: edit the Play record proof-of-work-outreach 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.