Tools on request

# 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":"request-desk"}'

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

{
  "name": "do",
  "arguments": {
    "code": "return await $.Campaign.create({ play: 'request-desk' }, { 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": "request-desk can’t start yet: 1 check fails and 2 warn.",
 6  "checks": [
 7    {
 8      "check": "use-when",
 9      "status": "pass",
10      "observed": "2 communities, 41 problems posted a week",
11      "doc": "/plays/request-desk#check-use-when",
12      "fix": "Keep 2 communities with 20 or more problems a week, or run community-answers.",
13      "then": "Metric.query"
14    },
15  …

curl "https://api.sb/leaseline.app/events?where=name%20in%20(%22Schedule.fired%22%2C%20%22Post.replied%22%2C%20%22Post.published%22%2C%20%22Tool.used%22%2C%20%22Tool.called%22%2C%20%22Version.deployed%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_6107"}'

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

 1import { $ } from 'startup-builder'
 2
 3const { events: [last] } = await $.Event.list({ where: 'name in ("Schedule.fired", "Post.replied", "Post.published", "Tool.used", "Tool.called", "Version.deployed")', 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\", \"Post.replied\", \"Post.published\", \"Tool.used\", \"Tool.called\", \"Version.deployed\")","limit":1}'
npx startup-builder do Trigger.fire --json '{"like":"event_6107"}' --try   # Not live yet (gaps #7)
npx startup-builder do Decision.list --json '{"where":"on = \"problem_23\""}'   # Not live yet (gaps #7)
npx startup-builder do Action.list --json '{"where":"on = \"problem_23\""}'   # Not live yet (gaps #7)

{
  "name": "do",
  "arguments": {
    "code": "const { events: [last] } = await $.Event.list({ where: 'name in (\"Schedule.fired\", \"Post.replied\", \"Post.published\", \"Tool.used\", \"Tool.called\", \"Version.deployed\")', 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_602",
 4    "$type": "Decision",
 5    "choice": "build-the-tool",
 6    "reason": "“I rebuild our turnover calendar from a spreadsheet every January” scored 8.4, 3rd of this week’s 10; Leaseline’s calendar Verb builds it from a CSV",
 7    "stakes": "low",
 8    "options": [
 9      "build-the-tool",
10      "send-a-sample",
11      "answer-in-writing",
12      "not-this-week",
13      "not-ours",
14      "to-the-ae"
15  …

action_2 publishes the turnover-calendar tool once its known-answer cases pass. action_3 is the reply in the asker’s own thread, waiting in your send tray: you post every reply by hand.

≈ +$400 ARR a month at 35

Worth

1 h week 1, then 40 min a week

Your time

$0.60 per tool, ~$12 a month at 20

Spend

Day 1: the first tool live

First signal

2+ communities, 20+ problems posted a week

Use it when

No community: community-answers · no one-day build: free-tools

Not yet when

Worth’s formula: about +6 entry starts per 100 askers (Other Startups’ results; no lift of your own yet) × 35 askers a month × 0.55 entry to paid × $347 Pro ARR ≈ +$401. Under First signal: Every asker gets an answer, so nothing is held back: it reads before-after, not proof, beside Other Startups’ results.

Start it this weekCopy Anchor Link

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

# 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":"request-desk"}'

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

# off: no call posts; live tools stay up and open requests still get an answer
curl -X POST https://api.sb/leaseline.app/processes/content-marketing/pause \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "request-desk can’t start yet: 1 check fails and 2 warn.",
  "checks": [
    {
      "check": "use-when",
      "status": "pass",
      "observed": "2 communities, 41 problems posted a week",
      "doc": "/plays/request-desk#check-use-when",
      "fix": "Keep 2 communities with 20 or more problems a week, or run community-answers.",
      "then": "Metric.query"
    },
    {
      "check": "owner",
      "status": "fail",
      "observed": "no booked founder reply slot",
      "doc": "/plays/request-desk#check-owner",
      "fix": "Book a weekly 45-minute reply slot; no call posts without one.",
      "then": "Task.assign"
    },
    {
      "check": "baseline",
      "status": "warn",
      "observed": "1 entry start of 22 askers you answered by hand in 90 days",
      "doc": "/plays/request-desk#check-baseline",
      "fix": "n 22: it reads before-after, not proof; every asker gets an answer.",
      "then": "Metric.query"
    },
    {
      "check": "role-unstaffed",
      "status": "warn",
      "roles": [
        "marketing-lead",
        "sales-lead"
      ],
      "owned": 0,
      "doc": "/plays/request-desk#check-role-unstaffed",
      "fix": "Staff the AE, or leave it: product questions from big askers come to you.",
      "then": "Role.staff"
    }
  ]
}

Each tool costs about $0.60 in build compute and each Sample $0.08 (Worker cost), under the $25 monthly build Limit; posting from your own profile costs nothing. That comes to about $12 a month at 20 tools.

When it startsCopy Anchor Link

{
  "$id": "https://api.sb/leaseline.app/events/event_6107",
  "$type": "Event",
  "name": "Post.replied",
  "at": "2026-10-17T15:22:09Z",
  "seq": 6107,
  "data": {
    "post": "post_88",
    "room": "r/PropertyManagement",
    "reply": "I rebuild our turnover calendar from a spreadsheet every January.",
    "problem": "problem_23",
    "window": "48h"
  }
}

npx startup-builder trigger Post.replied --like event_6107   # replays the request
npx startup-builder clock advance --by 1d   # runs the build clock’s 24-hour check
npx startup-builder listen Post.replied --forward-to http://localhost:3000/hook

Who runs itCopy Anchor Link

Content Lead · your agent (role:content-lead, worker_6) holds the Key Result: it reads, ranks and builds. You (Dana Okafor, person, worker_1) post every call and every reply by hand from your own profile. Askers at companies over 100 units who ask about Leaseline go to AE · Priya Shah (person) (role:sales-lead, worker_3). Your number links to Did it work.

What it reads · What it may call. It reads the replies to your call and the URLs dropped in the thread, and fetches at most 20 public pages a Sample, never past a login or a form (public-fetch). A run count, a visit or an asker’s reach never appears in a reply. Its tools are POST /{namespace}/problems/rank, POST /{namespace}/apps/{app}/publish, POST /{namespace}/pages, POST /{namespace}/conversations/{conversation}/answer, POST /{namespace}/problems/suggest, POST /{namespace}/leads/{lead}/assign, POST /{namespace}/tasks/{task}/assign, and any other call becomes an Approval under the Role’s Mandate.

You hold the Content Lead Key Result: 15 entry starts per 100 askers by 2026-12-31. ← worker, metric
On each request, choose one option and say why; every asker gets an answer.      ← triggers, chooses, copyRules 3
Build the weekly 10 within 24 hours; the last 3 slots are a logged draw.         ← your file, line 4
Name an asker only after they agree.                                             ← copyRules 6; consent-stop
Name the entry Offer only when the asker asked about price.                      ← copyRules 12
Draft every reply for Dana to post by hand.                                      ← tactic request-reply

The slow loop, as a Change. decision_571 (2026-09-21, weekly) read that requests naming a file people already keep (a spreadsheet, a rent roll) led to 5 of the first 7 entry starts, so change_33 added 1 point to the score for them (your file, line 4) and Dana merged it with POST /{namespace}/changes/{change}/merge. Replayed on past requests, POST /{namespace}/changes/{change}/review put entry starts at 13.0 per 100; read back at +28d it is 12.1, n 31, before-after, not proof (Example, day 56).

Bring your own agent (folded) starts at It does it, you can stop it for builds when it matches the seated agent on the eval suite; every reply stays yours to post. POST /{namespace}/roles/{role}/staff seats it.

npx startup-builder eval --scenario request-desk-64 --agent "claude -p" --seat content-lead   # seated: 62 of 64 inside 24 h, 0 Checks failed posted, $0.60 a tool · yours: 57 of 64, 1 known-answer fail

What it can do nextCopy Anchor Link

When it hands to youCopy Anchor Link

Every reply lands in your send tray, because you post them all by hand; askers over 100 units who ask about Leaseline go to AE · Priya Shah (person). One Brief per Role, as captured (brief is Not live yet, gaps #7).

[
  {
    "$id": "https://api.sb/leaseline.app/approvals/approval_95",
    "$type": "Approval",
    "verdict": null,
    "deadline": "2026-10-19T17:00:00Z",
    "draft": "Built it: drop your spreadsheet in and it lays out every turnover for the year…",
    "route": "build-the-tool",
    "checks": [
      {
        "check": "claims-resolve",
        "status": "pass"
      },
      {
        "check": "consent-stop",
        "status": "pass"
      }
    ]
  },
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_644",
    "$type": "Task",
    "assignee": "worker_3",
    "due": "2026-10-07T15:00:00Z",
    "on": "lead_102",
    "brief": {
      "who": "Kai, Westbrook Lofts, 180 units",
      "said": "Does Leaseline do this for a whole portfolio?",
      "chose": "to-the-ae",
      "why": "over 100 units, asking about the product itself",
      "got": "the owner-report tool, built Oct 3",
      "never": [
        "a price beyond the list",
        "what the tool’s runs show"
      ]
    }
  }
]

You answer with POST /{namespace}/approvals/{approval}/approve (you post it), 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 reply unposted 72 hours after the cutoff pages you once (answer-clock). 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, 121 of 124 replies posted inside 72 h, median 26 h, n 124; AE · Priya Shah, 3 of 3 within 1 business day, n 3, ■□□□ Too early to tell beside Other Startups’ 96 % on time. Your queue: about 15 replies to post a week, in your Friday and Monday slots, plus 1 weekly review and the next call.

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 posted is the Glenwood thread in Example.

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "The reply to u/glenwood_pm did not post: it says how many times their tool ran.",
  "checks": [
    {
      "check": "claims-resolve",
      "status": "fail",
      "doc": "/plays/request-desk#check-claims-resolve",
      "fix": "Cut the sentence, or link the page and date it checked.",
      "then": "Content.draft"
    },
    {
      "check": "consent-stop",
      "status": "pass"
    }
  ]
}

[
  {
    "reason": {
      "limit": "build-clock",
      "observed": "26h 10m",
      "bound": "24h",
      "window": "1 picked request"
    },
    "doc": "/plays/request-desk#stop-build-clock",
    "task": "task_627"
  }
]

Did it workCopy Anchor Link

Every asker gets an answer, so no half is held back and 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; the leaf and every node above it are Not live yet (gaps #4).

{
  "$id": "decisions/decision_602",
  "$type": "Decision",
  "choice": "build-the-tool",
  "reason": "“I rebuild our turnover calendar from a spreadsheet every January” scored 8.4, 3rd of this week’s 10; Leaseline’s calendar Verb builds it from a CSV",
  "stakes": "low",
  "options": [
    "build-the-tool",
    "send-a-sample",
    "answer-in-writing",
    "not-this-week",
    "not-ours",
    "to-the-ae"
  ],
  "by": "worker_6",
  "on": "problem_23",
  "expected": "an entry Offer start from the asker within 30d",
  "reopensWhen": "the tool not live 24h after the pick"
}

Before against after reads the 56 days against the 90 days before them, scaled to 56; it is not proof, and Other Startups’ results print beside it. The leaf counts entry Offer starts within 30 days per 100 askers who got a shipped tool or Sample link.

How it moves it: each asker got the tool they asked for at a median of 19 h, in their own thread, posted by you.

Guardrails: before against after: paid per entry start, 0.57 against 1.00 (new-paying-customers per entry; 1 of 1 before), and removed posts, 0 of 16 calls against none posted before.

{
  "$id": "https://api.sb/leaseline.app/campaigns/request-desk",
  "$type": "Campaign",
  "play": "play:request-desk@1",
  "path": [
    "requester-entry-rate",
    "icp-reached",
    "new-arr",
    "net-new-arr",
    "arr"
  ],
  "experiment": {
    "metric": "requester-entry-rate",
    "unit": "per-100",
    "heldBack": 0,
    "decision": null
  },
  "readout": {
    "value": null,
    "n": 58,
    "maturing": 6,
    "interval": null,
    "readability": "inadmissible",
    "basis": "before-after",
    "pooled": true
  },
  "ledger": {
    "spend": 0,
    "workerCost": 41,
    "hours": 5.6,
    "pipelineArr": 2400,
    "wonArr": 1388,
    "projectedArr": 401,
    "paybackDays": 11
  }
}

Outside benchmark: this Play’s catalog record carries no sourced range yet, so Other Startups’ results stand in: +6.0 entry starts per 100 askers, ■■■□ Likely, n 1,880.

Before it · After it. Before it: community-answers finds the Rooms where your buyers post. After it: free-tools keeps the tools people return to, signup-interviews hears the day-30 Interview asks, and product-led holds the entry starts.

ExampleCopy Anchor Link

Leaseline ran it from 2026-08-24 to 2026-10-19 (56 days): 8 Friday calls in 2 communities, 156 requests, 64 tools built and 29 Samples sent, and every asker answered. Read every captured thread at ?threads=all; three follow the tables.

u/rentroll_rita, r/PropertyManagement, Oct 17 15:22 · “I rebuild our turnover calendar from a spreadsheet every January.”

Dana, Oct 18 10:05 · Built it: drop your spreadsheet in and it lays out every turnover for the year, free.¹ leaseline.app/tools/turnover-calendar *Posted with the Role’s disclosure line.*²

Rita, Oct 18 11:40 · ran it 4 times that week, then started a Pro trial on Oct 19.

- Glad it helped: you’ve run the owner report 23 times this week!
+ Glad it helped. If you want it to run every month on its own, say the word and I’ll show you how.

Kai at Westbrook Lofts, 2026-10-06 15:00 · “Does Leaseline do this for a whole portfolio? We have 180 units.” · Dana, 15:20 · *Good question. Priya, our account lead, answers by tomorrow 15:00.*³ The Brief went to Priya (task_644), who replied at 10:12 the next day with a Quote.

¹ The promise kept exactly: the tool, free, within the 24-hour window the call stated. ² The disclosure line, compiled from the Role’s Settings; Dana posts it by hand. ³ The routed line, compiled from the Role’s Settings.

Your settingsCopy Anchor Link

---
holdout: 0        # every asker gets an answer; it reads before-after
call: friday      # one call a week, in r/PropertyManagement and Dana’s LinkedIn
---
Build the weekly 10 within 24 hours; the last 3 slots are a logged draw. A point more for files people already keep.
Draft every reply for Dana to post by hand.

$ npx startup-builder show plays/request-desk
holdout 0 · call friday · weekly 10, 3 drawn · a point for kept files · Dana posts every reply     your file  plays/request-desk.mdx:2,3,5,6 (Ask 2026-08-24; line 5 by change_33, 2026-09-21)
worker role:content-lead, owns never · chooses 6 (2 rule, 4 read) · sequence requester-check-in · approval every-send, first-send · checks owned-by-a-person, correctness, consent-stop, claims-resolve, seeded-request, public-fetch · stops 10 · placements linkedin, x, reddit, hacker-news, github, google-search, mcp-registry    catalog  play:request-desk@1 (Not live yet, gaps #5)

Every key from the catalogCopy Anchor Link

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