Integration partners

# 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":"integration-partners"}'

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

{
  "name": "do",
  "arguments": {
    "code": "return await $.Campaign.create({ play: 'integration-partners' }, { 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": "integration-partners can’t start: 2 checks fail and 1 warns.",
 6  "checks": [
 7    {
 8      "check": "use-when",
 9      "status": "pass",
10      "observed": "41 paying Customers; 23 use Ledgerly, 14 use Porchlight",
11      "doc": "/plays/integration-partners#check-use-when",
12      "then": "Metric.query"
13    },
14    {
15  …

curl "https://api.sb/leaseline.app/events?where=name%20in%20(%22Partner.ranked%22%2C%20%22App.passed%22%2C%20%22Message.replied%22%2C%20%22Integration.connected%22%2C%20%22Agreement.signed%22%2C%20%22Monitor.checked%22%2C%20%22Referral.registered%22%2C%20%22App.failed%22%2C%20%22Organization.announced%22%2C%20%22Customer.activated%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_1203"}'

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

 1import { $ } from 'startup-builder'
 2
 3const { events: [last] } = await $.Event.list({ where: 'name in ("Partner.ranked", "App.passed", "Message.replied", "Integration.connected", "Agreement.signed", "Monitor.checked", "Referral.registered", "App.failed", "Organization.announced", "Customer.activated")', 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 (\"Partner.ranked\", \"App.passed\", \"Message.replied\", \"Integration.connected\", \"Agreement.signed\", \"Monitor.checked\", \"Referral.registered\", \"App.failed\", \"Organization.announced\", \"Customer.activated\")","limit":1}'
npx startup-builder do Trigger.fire --json '{"like":"event_1203"}' --try   # Not live yet (gaps #7)
npx startup-builder do Decision.list --json '{"where":"on = \"partner_9\""}'   # Not live yet (gaps #7)
npx startup-builder do Action.list --json '{"where":"on = \"partner_9\""}'   # Not live yet (gaps #7)

{
  "name": "do",
  "arguments": {
    "code": "const { events: [last] } = await $.Event.list({ where: 'name in (\"Partner.ranked\", \"App.passed\", \"Message.replied\", \"Integration.connected\", \"Agreement.signed\", \"Monitor.checked\", \"Referral.registered\", \"App.failed\", \"Organization.announced\", \"Customer.activated\")', 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_429",
 4    "$type": "Decision",
 5    "choice": "propose-to-the-partner",
 6    "reason": "the Porchlight build passed its sandbox suite on Oct 17; 14 of your Customers use Porchlight, it runs a partner program, and you hold no Agreement",
 7    "stakes": "medium",
 8    "options": [
 9      "build-it-privately",
10      "propose-to-the-partner",
11      "list-it",
12      "adoption-email",
13      "intro-a-lead",
14      "park-it"
15  …

action_1 ran the suite against Porchlight’s sandbox, never a production account. action_3 is the proposal with the sandbox link, waiting on your approval as the first one to this partner.

≈ +$290 ARR a month at 2 builds

Worth

45 min week 1, then 10 a day

Your time

$0 cash; ~$6 a build in sandbox and model minutes

Spend

Day 15: first paying Customer through a build

First signal

10+ paying Customers or 50 Prospects with a known stack

Use it when

Under 10 and 50: marketplace-listings · no tool 5+ use: cold-email

Not yet when

Worth’s formula: about +14 ICP Organizations per build in 90 days (Other Startups’ results; no lift of your own to read) × 2 live builds ÷ 3 months × 0.09 ICP Organizations to paid × $347 first order ARR ≈ +$291. Under First signal: Each build reads at day 90; at 2 builds, 90 days can tell only +30 per build or more, so your file reads before-after.

Start it this weekCopy Anchor Link

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

# 3 · keep it: first listings and every Agreement wait on you
curl -X POST https://api.sb/leaseline.app/campaigns \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"play":"integration-partners"}'

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

# off: proposals stop; live builds stay listed and keep their nightly suite
curl -X PATCH https://api.sb/leaseline.app/campaigns/integration-partners \
  -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": "integration-partners can’t start: 2 checks fail and 1 warns.",
  "checks": [
    {
      "check": "use-when",
      "status": "pass",
      "observed": "41 paying Customers; 23 use Ledgerly, 14 use Porchlight",
      "doc": "/plays/integration-partners#check-use-when",
      "then": "Metric.query"
    },
    {
      "check": "baseline",
      "status": "pass",
      "observed": "9 ICP Organizations in 90 days through 1 listed build (the CSV import)",
      "doc": "/plays/integration-partners#check-baseline",
      "then": "Metric.query"
    },
    {
      "check": "sandbox-connected",
      "status": "fail",
      "doc": "/plays/integration-partners#check-sandbox-connected",
      "fix": "Connect each partner’s sandbox account; no suite touches a production account.",
      "then": "Integration.connect"
    },
    {
      "check": "domain-authenticated",
      "status": "fail",
      "doc": "/plays/integration-partners#check-domain-authenticated",
      "fix": "Add the 3 DNS records shown; it passes once they resolve, often within an hour.",
      "then": "Domain.authenticate"
    },
    {
      "check": "role-unstaffed",
      "status": "warn",
      "roles": [
        "sales-lead"
      ],
      "owned": 0,
      "doc": "/plays/integration-partners#check-role-unstaffed",
      "fix": "Staff the AE, or leave it: partner Leads come to you.",
      "then": "Role.staff"
    }
  ]
}

A private build costs no cash: about $6 of sandbox and model minutes to build and $0.30 a month for its nightly suite (Worker cost). Store listings cost nothing, and a partner reward is 15 % of collected first-year revenue, paid after the refund window. That comes to about $14 a month at 2 live builds.

When it startsCopy Anchor Link

{
  "$id": "https://api.sb/leaseline.app/events/event_1203",
  "$type": "Event",
  "name": "Partner.ranked",
  "at": "2026-10-19T06:00:11Z",
  "seq": 1203,
  "data": {
    "partner": "partners/partner_9",
    "name": "Porchlight",
    "customersUsing": 14,
    "prospectsUsing": 31,
    "build": "green",
    "program": true,
    "agreement": null
  }
}

# each delivery is signed with the Watch’s secret
curl -X POST https://api.sb/leaseline.app/watches \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"selector":"Partner.ranked","url":"https://leaseline.app/hooks/sb"}'
npx startup-builder trigger Partner.ranked --like event_1203   # replays the delivery
npx startup-builder clock advance --by 7d   # runs the one follow-up with one new fact

Who runs itCopy Anchor Link

Partner Manager · your agent (role:partner-manager, worker_9) holds the Key Result: it ranks the stacks, builds privately, runs the suites and drafts proposals. First proposals, first listings per Venue and every Agreement hand to you (Dana Okafor, person, worker_1); partner Leads go to AE · Priya Shah (person) (role:sales-lead, worker_3, staffed on day 9).

What it reads · What it may call. It reads the tools your Customers connect and each partner’s public docs and terms; an overlap list is matched on domains only and never appears in copy. It may call POST /{namespace}/integrations and POST /{namespace}/integrations/{integration}/call against sandboxes only; POST /{namespace}/apps/{app}/publish needs your Approval for a Venue’s first listing. Its tools are POST /{namespace}/integrations, POST /{namespace}/integrations/{integration}/call, POST /{namespace}/approvals/{approval}/approve, POST /{namespace}/apps/{app}/publish, POST /{namespace}/sites/{site}/publish, POST /{namespace}/leads, POST /{namespace}/leads/{lead}/assign, and any other call becomes an Approval under the Role’s Mandate.

You hold the Partner Manager Key Result: 30 ICP Organizations per live build by 2026-12-31. ← worker, metric
On each ranked tool, green build or partner reply, choose one option and say why. ← triggers, chooses
Build privately once 8 Customers or 20 Prospects use a tool.                     ← your file, line 5
Say “works with” and the tool’s name until an Agreement exists; never “official”. ← copyRules 2, 3
List a build only after a paying Customer outside the team connects.             ← chooses.list-it, paying-user
Pass a Lead to a partner only with the Person’s recorded Consent.                ← consent-stop

The slow loop, as a Change. decision_389 (2026-09-21, weekly) read 2 green builds out of 2 tools at 8 or more Customers against 0 of 3 at 5 to 7, so change_28 raised the build line from 5 to 8 Customers (your file, line 5), and Dana merged it with POST /{namespace}/changes/{change}/merge. Replayed on past ranks, POST /{namespace}/changes/{change}/review cut parked builds from 3 to 1 with no live build lost; read back at +28d, 0 builds parked, n 1 rank, ■□□□ Too early to tell (Example, day 56).

Bring your own agent (folded) builds at the same rung when it matches or beats the seated agent on the eval suite; first listings and Agreements wait on you either way, and POST /{namespace}/roles/{role}/staff seats it.

npx startup-builder eval --scenario integration-partners-6 --agent "claude -p" --seat partner-manager   # seated: 0 premature listings, 0 partner claims sent, 41 sandbox min a build · yours: 0, 1 “official” drafted, 63 min → You approve each one

What it can do nextCopy Anchor Link

When it hands to youCopy Anchor Link

First proposals, first listings and every Agreement go to you (Dana Okafor, person); partner Leads go to AE · Priya Shah (person). As captured, one Brief per Role: your Approval, then the AE’s Task (brief, draft, route and checks are Not live yet, gaps #7).

[
  {
    "$id": "https://api.sb/leaseline.app/approvals/approval_94",
    "$type": "Approval",
    "verdict": null,
    "deadline": "2026-10-20T17:00:00Z",
    "draft": "Hi Porchlight partner team: 14 property managers on Leaseline use Porchlight. We built the integration against your sandbox; it passes. Here it is, with your half of the listing drafted.",
    "route": "propose-to-the-partner",
    "checks": [
      {
        "check": "announced-only",
        "status": "pass"
      },
      {
        "check": "terms-hold",
        "status": "pass"
      }
    ]
  },
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_482",
    "$type": "Task",
    "assignee": "worker_3",
    "due": "2026-10-15T16:00:00Z",
    "on": "lead_47",
    "brief": {
      "who": "Hilltop Rentals, 95 units, registered by Ledgerly",
      "consent": "recorded on the partner’s form, 2026-10-14",
      "chose": "intro-a-lead",
      "why": "a partner Lead with the Person’s Consent; they keep their books in Ledgerly",
      "never": [
        "a discount",
        "a promise of a Ledgerly feature"
      ]
    }
  }
]

You answer the Approval with POST /{namespace}/approvals/{approval}/approve, an edit, or POST /{namespace}/approvals/{approval}/refuse with a reason; one unanswered by its deadline expires, and the proposal never sends. The AE answers with POST /{namespace}/tasks/{task}/claim (Take this one), POST /{namespace}/tasks/{task}/return with a reason, or POST /{namespace}/actions/{action}/redirect; once claimed, the agent’s pending sends to that Lead cancel with claimedByPerson (Not live yet, gaps #7). A Task nobody claims by its due time goes up a Role through POST /{namespace}/tasks/{task}/escalate (AE to you).

On time: You: 4 of 4 Approvals answered within 1 business day, median 2h 40m, n 4. AE · Priya Shah: 2 of 2 partner Leads claimed within 1 business day, median 50 min, n 2, ■□□□ Too early to tell beside Other Startups’ 90 % on time. Your queue: counted by kind: in week 1, 2 sandbox connections and 1 proposal Approval; after that, about 1 Approval and 1 partner Lead every 2 weeks.

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 listed is the Ledgerly thread in Example.

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "The Ledgerly listing copy did not publish: it says “official partner” before an Agreement exists.",
  "checks": [
    {
      "check": "announced-only",
      "status": "pass"
    },
    {
      "check": "paying-user",
      "status": "pass"
    },
    {
      "check": "partner-claim",
      "status": "fail",
      "doc": "/plays/integration-partners#check-partner-claim",
      "fix": "Say “works with Ledgerly” until the Agreement is signed.",
      "then": "Content.draft"
    }
  ]
}

[
  {
    "reason": {
      "limit": "red-build",
      "observed": "3 red nights",
      "bound": "3",
      "window": "the nightly suite"
    },
    "doc": "/plays/integration-partners#stop-red-build",
    "task": "task_461"
  }
]

Did it workCopy Anchor Link

Each build reads at day 90, and at 2 builds no held-back half reads, so the basis is before-after (rule o): the columns read Now and Before, nothing prints as Added, and Too early to tell prints with its counts. 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_429",
  "$type": "Decision",
  "choice": "propose-to-the-partner",
  "reason": "the Porchlight build passed its sandbox suite on Oct 17; 14 of your Customers use Porchlight, it runs a partner program, and you hold no Agreement",
  "stakes": "medium",
  "options": [
    "build-it-privately",
    "propose-to-the-partner",
    "list-it",
    "adoption-email",
    "intro-a-lead",
    "park-it"
  ],
  "by": "worker_9",
  "on": "partner_9",
  "expected": "a partner yes within 14d",
  "reopensWhen": "no Message.replied from partner_9 within 14d"
}

Before against after reads ICP Organizations reached through live builds against the 90 days before, when one CSV import was the only listing, scaled to 56 days. It is not proof; Other Startups’ results, read with half of gated builds listed at once and half 30 days later at random, print beside it.

How it moves it: the Ledgerly build listed on day 18 after Maple Court paid through it, and its store listing and 2 pair Pages reached 34 ICP Organizations in its first 38 days.

Guardrails: before against after: partner-sourced-revenue, $1,388 against $0, and refunds within 30 days on build-sourced Customers, 0 of 5 against Leaseline’s 4 %.

{
  "$id": "https://api.sb/leaseline.app/campaigns/integration-partners",
  "$type": "Campaign",
  "play": "play:integration-partners@1",
  "path": [
    "integration-icp-accounts",
    "icp-reached",
    "new-arr",
    "net-new-arr",
    "arr"
  ],
  "experiment": {
    "metric": "integration-icp-accounts",
    "unit": "per-build",
    "heldBack": 0,
    "decision": null
  },
  "readout": {
    "value": null,
    "n": 0,
    "maturing": 2,
    "interval": null,
    "readability": "inadmissible",
    "basis": "before-after",
    "pooled": true
  },
  "ledger": {
    "spend": 0,
    "workerCost": 21,
    "hours": 6.5,
    "pipelineArr": 2400,
    "wonArr": 1735,
    "projectedArr": 291,
    "paybackDays": 4
  }
}

Outside benchmark: none measures ICP Organizations per partner build; Other Startups’ results, +14 per build, ■■□□ Early sign, n 96 builds, stand in for one.

Before it · After it. Before it: the weekly rank reads the tools your Customers connect. After it: listed builds go to marketplace-listings, pair Pages to programmatic-seo, and the integration as a product fact to cold-email.

ExampleCopy Anchor Link

Leaseline ran it from 2026-08-24 to 2026-10-19 (56 days). The weekly rank read 41 Customers’ and 118 Prospects’ stacks; 3 builds went green, 1 listed, 1 is proposed and 1 parked. Read every captured thread at ?threads=all; three follow the tables.

Leaseline → Ledgerly partner team, Aug 28, 10:05 · 23 property managers on Leaseline keep their books in Ledgerly.¹ We built the integration against your sandbox, and it passes end to end: renewals post as receivables the day they sign.² Here it is, with your half of the listing drafted.³

Ledgerly, Sep 1, 14:30 · “Looks good. List it once a customer is live.” Maple Court connected on Sep 8, and the listing went up Sep 11 with “works with Ledgerly”.

- Leaseline is an official Ledgerly partner.
+ Leaseline works with Ledgerly: renewals post as receivables the day they sign.

Ledgerly, 2026-10-14 15:12 · registered Hilltop Rentals (95 units) as a Lead, with Consent on their form. The agent chose Introduce a Lead and sent the Brief to Priya, due 16:00 the next business day. · Priya, 2026-10-15 09:40 · claimed it with POST /{namespace}/tasks/{task}/claim and booked a call for Oct 17. The Brief is in When it hands to you (task_482).

¹ A count from your own Customers’ connected tools, never a private overlap match. ² A result the suite measured in the partner’s sandbox. ³ Their half of the listing and docs, drafted.

Your settingsCopy Anchor Link

---
holdout: 0          # 2 builds are too few to stagger listings; it reads before-after
adoptionHoldout: 0.1
---
Build once 8 Customers or 20 Prospects use a tool. I sign every Agreement.

$ npx startup-builder show plays/integration-partners
holdout 0 · adoption holdout 0.1 · build line 8 Customers or 20 Prospects     your file  plays/integration-partners.mdx:2,3,5 (Ask 2026-08-24; line 5 by change_28, 2026-09-21)
family demand · worker role:partner-manager, owns never · chooses 6 (4 rule, 2 read) · sequences partner-proposal-two-touch, joint-adoption-two-touch, overlap-brief-three-touch, idle-unlist-notice · checks owned-by-a-person, consent-stop + 8 · stops 4 · placements 13 stores and registries, google-search, linkedin, gmail, outlook, yahoo-mail    catalog  play:integration-partners@1 (Not live yet, gaps #5)

Every key from the catalogCopy Anchor Link

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