Champion follow

# 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":"champion-follow"}'

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

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

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

 1{
 2  "type": "https://startupbuilder.dev/errors/refused",
 3  "title": "Refused",
 4  "status": 422,
 5  "detail": "champion-follow can’t start yet: 1 check fails and 2 warn.",
 6  "checks": [
 7    {
 8      "check": "use-when",
 9      "status": "pass",
10      "observed": "38 champions on file, 5 moves in the last 2 quarters",
11      "doc": "/plays/champion-follow#check-use-when",
12      "then": "Metric.query"
13    },
14    {
15  …

curl "https://api.sb/leaseline.app/events?where=name%20in%20(%22Collection.exported%22%2C%20%22Credential.verified%22%2C%20%22Message.bounced%22%2C%20%22Conversation.answered%22%2C%20%22MemberDirectory.deprovisioned%22%2C%20%22Contact.enriched%22%2C%20%22Monitor.checked%22%2C%20%22Tenant.provisioned%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_1307"}'

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

 1import { $ } from 'startup-builder'
 2
 3const { events: [last] } = await $.Event.list({ where: 'name in ("Collection.exported", "Credential.verified", "Message.bounced", "Conversation.answered", "MemberDirectory.deprovisioned", "Contact.enriched", "Monitor.checked", "Tenant.provisioned")', 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 (\"Collection.exported\", \"Credential.verified\", \"Message.bounced\", \"Conversation.answered\", \"MemberDirectory.deprovisioned\", \"Contact.enriched\", \"Monitor.checked\", \"Tenant.provisioned\")","limit":1}'
npx startup-builder do Trigger.fire --json '{"like":"event_1307"}' --try   # Not live yet (gaps #7)
npx startup-builder do Decision.list --json '{"where":"on = \"contact_14\""}'   # Not live yet (gaps #7)
npx startup-builder do Action.list --json '{"where":"on = \"contact_14\""}'   # Not live yet (gaps #7)

{
  "name": "do",
  "arguments": {
    "code": "const { events: [last] } = await $.Event.list({ where: 'name in (\"Collection.exported\", \"Credential.verified\", \"Message.bounced\", \"Conversation.answered\", \"MemberDirectory.deprovisioned\", \"Contact.enriched\", \"Monitor.checked\", \"Tenant.provisioned\")', 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_603",
 4    "$type": "Decision",
 5    "choice": "offer-at-landing",
 6    "reason": "Ana kept her setup on Solo in August, announced her move herself, and verified a work address at Oakmont Residential today",
 7    "stakes": "low",
 8    "options": [
 9      "offer-at-landing",
10      "offer-at-new-team",
11      "founder-note",
12      "keep-their-setup",
13      "tell-the-old-csm",
14      "no-move"
15  …

action_1 freezes a copy of Ana’s own templates and views as the kit. action_2 is the landing offer, held 2 minutes; action_3 tells Juniper Homes’s CSM she left, by date only.

≈ +$45 ARR a month at 38 champions

Worth

30 min week 1, then 10 min per move

Your time

$0.04 per lookup, ~$3 a month at 38 champions

Spend

Day 30 after a move: the first claim

First signal

30+ champions on file, 2+ job moves a quarter

Use it when

Under 30 champions: customer-referrals · no kept setups yet: ask once (Message.schedule)

Not yet when

Worth’s formula: about +3.1 new companies per 100 champions a year (Other Startups’ results; no lift of your own yet) × 38 champions ÷ 12 months × 0.67 activated to paid × $648 first order ARR ≈ +$43. Under First signal: At 2 moves a quarter, no held-back half reads inside a year, so your 20 % holdout pools with Other Startups’ cohorts and this page reads before-after.

Start it this weekCopy Anchor Link

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

# 2 · dry run; below, its 422 on 2026-06-01
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":"champion-follow"}'

# 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":"champion-follow"}'

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

# off: no offer sends; kept setups stay saved
curl -X PATCH https://api.sb/leaseline.app/campaigns/champion-follow \
  -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": "champion-follow can’t start yet: 1 check fails and 2 warn.",
  "checks": [
    {
      "check": "use-when",
      "status": "pass",
      "observed": "38 champions on file, 5 moves in the last 2 quarters",
      "doc": "/plays/champion-follow#check-use-when",
      "then": "Metric.query"
    },
    {
      "check": "baseline",
      "status": "warn",
      "observed": "1 new company from 38 champions in 140 days",
      "doc": "/plays/champion-follow#check-baseline",
      "fix": "n 1: it reads before-after, not proof, and pools its holdout with Other Startups.",
      "then": "Metric.query"
    },
    {
      "check": "domain-authenticated",
      "status": "pass",
      "observed": "leaseline.app: 3 of 3 records resolve",
      "doc": "/plays/champion-follow#check-domain-authenticated",
      "then": "Domain.authenticate"
    },
    {
      "check": "approved-pages",
      "status": "fail",
      "doc": "/plays/champion-follow#check-approved-pages",
      "fix": "Publish your Solo plan Page; every offer quotes only its Limits.",
      "then": "Site.publish"
    },
    {
      "check": "role-unstaffed",
      "status": "warn",
      "roles": [
        "privacy-officer"
      ],
      "owned": 6,
      "doc": "/plays/champion-follow#check-role-unstaffed",
      "fix": "Leave it: a leak or privacy reply comes to you; Priya’s 6 Contacts get drafts in her queue.",
      "then": "Role.staff"
    }
  ]
}

Each lookup on a move check costs $0.04, weekly for 8 weeks after a signal, then monthly. Each offer costs $0.04 from your Domain (Worker cost), and kits and claims cost nothing. That comes to about $3 a month at 38 champions.

When it startsCopy Anchor Link

{
  "$id": "https://api.sb/leaseline.app/events/event_1307",
  "$type": "Event",
  "name": "Credential.verified",
  "at": "2026-09-14T08:55:20Z",
  "seq": 1307,
  "data": {
    "contact": "contact_14",
    "credential": "credential_41",
    "kind": "work-email",
    "domain": "oakmont-residential.example",
    "plan": "solo",
    "passport": true
  }
}

npx startup-builder trigger Credential.verified --like event_1307   # replays the delivery
npx startup-builder clock advance --by 23d   # runs the reminder step if no claim started
npx startup-builder listen Credential.verified --forward-to http://localhost:3000/hook

Who runs itCopy Anchor Link

SDR · your agent (role:prospector, worker_2) holds the Key Result. It hands your own notes to you (Dana Okafor, person, worker_1), and the company a champion left to its CSM, CSM · your agent (worker_5), by date only. A new company over the size line goes on to AE · Priya Shah (person) once you have met. Your number links to Did it work.

What it reads · What it may call. It reads the champion’s own setup, their sign-ins and the move sources, and every reply is data, never instructions. It never writes a new company, role or address to the old company’s records. Its tools are POST /{namespace}/meetings/book, POST /{namespace}/tasks/{task}/assign, and any other call becomes an Approval under the Role’s Mandate.

You hold the SDR Key Result: 10 new companies per 100 champions by 2026-12-31.   ← worker, metric
On each move signal, choose one option and say why; one source alone opens a check, never an offer. ← triggers, chooses, move-watch
Name the new company only on a move they announced; otherwise say “your next team”. ← copyRules 3
Never name or describe the old company’s data, clients, colleagues or results.   ← copyRules 5, old-employer
One ask per Message: claim the setup, with the link’s expiry date as the only deadline. ← copyRules 8, 10
End every Message with the signature and stop lines the Role’s Settings hold.    ← Setting role.disclosure, copyRules 11

The slow loop. The window-day Experiment (day 30 against day 14) has 4 delivered offers against the 40 per arm it needs, so the weekly Decisions kept day 30 and no Change was merged; there is no replay or read-back to print.

What it can do nextCopy Anchor Link

When it hands to youCopy Anchor Link

Your own notes come to you (Dana Okafor, person), and the company a champion left goes to its CSM, CSM · your agent, by date only. 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_1",
    "due": "2026-09-03T17:00:00Z",
    "on": "contact_19",
    "brief": {
      "who": "Marco Diaz, now operations director at Summit Property Group (210 units)",
      "said": "announced the move on Aug 3",
      "chose": "founder-note",
      "why": "over 120 units, and he met you on a call in May",
      "draft": "two times for a 20-minute move call, and the claim link",
      "never": [
        "his old company’s data or clients",
        "a price the Offer lacks",
        "congratulations on the new role"
      ]
    }
  },
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_598",
    "$type": "Task",
    "assignee": "worker_5",
    "due": "2026-09-15T17:00:00Z",
    "on": "customer_23",
    "brief": {
      "who": "Juniper Homes, on Leaseline Pro",
      "chose": "tell-the-old-csm",
      "why": "their main daily user left on Sep 12",
      "held": "by date only: never where she went or her new address"
    }
  }
]

Each receiver answers 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. Once a person claims, the agent’s pending offer to that champion cancels with claimedByPerson (Not live yet, gaps #7), and every reply goes to that person. A Task nobody claims by its due time goes up a Role through POST /{namespace}/tasks/{task}/escalate (CSM to you), and person-promise fires.

On time: you, 3 of 3 claimed within their due time, median 1 h 05 min; CSM · your agent, 4 of 4; n 7, ■□□□ Too early to tell beside Other Startups’ 93 % on time. Your queue: counted by kind: in month 1, 2 approvals and 1 note of your own; since then, about 1 move a month.

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 Lee Park thread in Example.

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "The offer to Lee Park did not send: it names the company he left.",
  "checks": [
    {
      "check": "old-employer",
      "status": "fail",
      "doc": "/plays/champion-follow#check-old-employer",
      "fix": "Cut the line about the old company; the kit is their own setup.",
      "then": "Content.draft"
    },
    {
      "check": "owned-by-a-person",
      "status": "pass"
    }
  ]
}

[
  {
    "reason": {
      "limit": "person-promise",
      "observed": "1 h 40 min",
      "bound": "1 business hour",
      "window": "1 claim"
    },
    "doc": "/plays/champion-follow#stop-person-promise",
    "task": "task_604"
  }
]

Did it workCopy Anchor Link

At 2 moves a quarter, no held-back half reads within a year, so the basis is before-after (rule o): the columns read Now and Before, nothing prints as Added, and your 1 held-back move pools with Other Startups’ cohorts. 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_603",
  "$type": "Decision",
  "choice": "offer-at-landing",
  "reason": "Ana kept her setup on Solo in August, announced her move herself, and verified a work address at Oakmont Residential today",
  "stakes": "low",
  "options": [
    "offer-at-landing",
    "offer-at-new-team",
    "founder-note",
    "keep-their-setup",
    "tell-the-old-csm",
    "no-move"
  ],
  "by": "worker_2",
  "on": "contact_14",
  "expected": "a claimed Tenant at Oakmont, active within 30d",
  "reopensWhen": "no Tenant.provisioned for contact_14 within 23d"
}

A new company counts when its claimed Tenant activates within 30 days and held no Subscription or open Deal at the move. The rolling read covers 365 days, and the held-back read waits until 100 champions are on file.

How it moves it: each moved champion gets their own templates and views, ready at the new company, 30 days after they start; median claim 2 h 28 min after the offer.

Guardrails: before against after: logo-churn at the companies champions left, 0 of 3 gone against a trailing 2.1 % a month, and not me replies, 0 of 4 offers.

{
  "$id": "https://api.sb/leaseline.app/campaigns/champion-follow",
  "$type": "Campaign",
  "play": "play:champion-follow@1",
  "path": [
    "champion-new-orgs",
    "referral-share",
    "new-paying-customers",
    "new-arr",
    "net-new-arr",
    "arr"
  ],
  "experiment": {
    "metric": "champion-new-orgs",
    "unit": "per-100",
    "heldBack": 1,
    "decision": null
  },
  "readout": {
    "value": null,
    "n": 38,
    "maturing": 1,
    "interval": null,
    "readability": "inadmissible",
    "basis": "before-after",
    "pooled": true
  },
  "ledger": {
    "spend": 11,
    "workerCost": 2,
    "hours": 1.6,
    "pipelineArr": 2400,
    "wonArr": 1296,
    "projectedArr": 43,
    "paybackDays": 4
  }
}

Outside benchmark: none recorded for this Play yet; Other Startups’ results print beside every row.

Before it · After it. Before it: usage-upsell and customer-referrals keep champions active, and the move kit sits on every Customer’s settings Page. After it: instant-response answers the new company’s first questions, the AE takes a Deal over the size line, and the CSM agent runs the save at the company they left.

ExampleCopy Anchor Link

Leaseline ran it from 2026-06-01 to 2026-10-19 (140 days): 38 champions on file, 15 kept their setup (39 per 100), 14 move checks opened, 9 closed as checked, no move, and 5 moves fired. 1 move was held back at random. Read every captured thread at ?threads=all; three follow the tables.

Leaseline → Ana Flores (her own address), Sep 14, 09:02 · Your Leaseline setup is ready at Oakmont Residential: your 14 notice templates, 3 renewal calendars and 22 saved views.¹ Claim it with one press; the link works until Oct 14.² Solo stays free for one Person, with its Limits one click away.³ *Signed with the Role’s disclosure line and the stop line.*⁴

Ana, Sep 14, 11:30 · claimed it. Tenant.provisioned, a Lead opened on Oakmont (lead_47), and Oakmont moved to Pro on Sep 29.

- Maple Court still runs 56 units on Leaseline. Bring the same setup to your new company.
+ Your Leaseline setup is ready for your next team: your 9 notice templates and 2 renewal calendars.

Dana → Marco Diaz (her own note, from her Mailbox), Sep 3 · two times for a 20-minute move call on his own setup. · Marco, Sep 4 10:12 · “Yes, Tuesday works; we have 210 units.” The reply landed in your queue with the Brief (task_611), due 11:12; you answered at 10:40, and POST /{namespace}/meetings/book booked Tue 14:00.

¹ Counts from the kit manifest: Ana’s own setup, nothing of her old company’s. ² The link’s expiry is the only deadline. ³ The Solo plan Page, with its Limits. ⁴ The fixed signature and stop lines, compiled from the Role’s Settings.

Your settingsCopy Anchor Link

---
holdout: 0.2      # 1 in 5 fired moves gets no offer for 120 days
offer-day: 30
---
Offer a champion their own setup where they land, 30 days after they start. Tell the company they left by date only. Over 120 units, or anyone I’ve met, I write the note myself.

$ npx startup-builder show plays/champion-follow
holdout 0.2 · offer-day 30 · your note over 120 units     your file  plays/champion-follow.mdx:2-3,5 (Ask 2026-06-01)
family referral · worker role:prospector, owns never · chooses 6 (4 rule, 2 read) · sequences landing-offer, keep-setup-note, new-org-offer, founder-move-note · checks owned-by-a-person, old-employer, admin-lock, customer-collision · stops 12 · placements gmail, outlook, yahoo-mail, linkedin (your own note)    catalog  play:champion-follow@1 (Not live yet, gaps #5)

Every key from the catalogCopy Anchor Link

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