Community answers

# 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":"community-answers"}'

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

{
  "name": "do",
  "arguments": {
    "code": "return await $.Campaign.create({ play: 'community-answers' }, { 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": "community-answers can’t start yet: 1 check fails and 2 warn.",
 6  "checks": [
 7    {
 8      "check": "use-when",
 9      "status": "pass",
10      "observed": "41 questions a month in 12 pain phrases across 14 rooms",
11      "doc": "/plays/community-answers#check-use-when",
12      "then": "Metric.query"
13    },
14    {
15  …

curl "https://api.sb/leaseline.app/events?where=name%20in%20(%22Post.published%22%2C%20%22Monitor.checked%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_1201"}'

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

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

{
  "name": "do",
  "arguments": {
    "code": "const { events: [last] } = await $.Event.list({ where: 'name in (\"Post.published\", \"Monitor.checked\")', 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_634",
 4    "$type": "Decision",
 5    "choice": "brief-a-person",
 6    "reason": "The thread asks how to send renewal notices 60 days out across 3 owners; the room admits people only, so you answer from your own account",
 7    "stakes": "low",
 8    "options": [
 9      "post-as-agent",
10      "brief-a-person",
11      "correct-the-record",
12      "reply-under-ours",
13      "listen-only",
14      "skip-it"
15  …

action_1 is the brief: the question, three facts from your pages and the room’s record, as fragments. action_2 puts it in tomorrow’s 09:00 brief; you post the answer yourself.

≈ +$320 ARR a month at 30 questions

Worth

30 min week 1, then about 2 h a week

Your time

$50 a month for listening, ~$1.60 an answer at 30

Spend

Day 6: first answer accepted

First signal

20+ public questions a month in your pain phrases

Use it when

Under 20 a month: editorial-seo · no Pages to answer from: publish them (Site.publish)

Not yet when

Worth’s formula: about +34.5 ICP Visits per answered cluster in 8 weeks × 8 clusters ÷ 2 months × 0.0067 Visits to paid × $348 first order ARR ≈ +$321. Under First signal: About 8 weeks: the 2 held-out clusters read beside the 8 answered ones at 60 answers posted.

Start it this weekCopy Anchor Link

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

# 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":"community-answers"}'

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

# off: queued agent answers cancel; posted answers stay up
curl -X PATCH https://api.sb/leaseline.app/campaigns/community-answers \
  -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": "community-answers can’t start yet: 1 check fails and 2 warn.",
  "checks": [
    {
      "check": "use-when",
      "status": "pass",
      "observed": "41 questions a month in 12 pain phrases across 14 rooms",
      "doc": "/plays/community-answers#check-use-when",
      "then": "Metric.query"
    },
    {
      "check": "baseline",
      "status": "warn",
      "observed": "19 ICP Visits a month from threads, n 57 in 90 days",
      "doc": "/plays/community-answers#check-baseline",
      "fix": "n 57: the held-out clusters become the comparison, read at 60 answers.",
      "then": "Metric.query"
    },
    {
      "check": "approved-pages",
      "status": "fail",
      "doc": "/plays/community-answers#check-approved-pages",
      "fix": "Publish your how-it-works Page; answers state only what your pages say.",
      "then": "Site.publish"
    },
    {
      "check": "role-unstaffed",
      "status": "warn",
      "roles": [
        "compliance-officer"
      ],
      "owned": 31,
      "doc": "/plays/community-answers#check-role-unstaffed",
      "fix": "Leave it: each room’s record comes to you to approve once.",
      "then": "Role.staff"
    }
  ]
}

The listening feed costs $50 a month, and each answer about $0.06 to draft (Worker cost). Posting is free on every room. That comes to about $1.60 an answer at 30 answers a month, and $52 a month.

When it startsCopy Anchor Link

{
  "$id": "https://api.sb/leaseline.app/events/event_1201",
  "$type": "Event",
  "name": "Post.published",
  "at": "2026-10-18T22:41:09Z",
  "seq": 1201,
  "data": {
    "post": "post_412",
    "venue": "reddit",
    "room": "a landlord forum",
    "phrase": "renewal notice",
    "title": "How do you send renewal notices 60 days out across 3 owners?",
    "agentsAdmitted": false
  }
}

npx startup-builder trigger Post.published --like event_1201   # replays the delivery
npx startup-builder clock advance --by 1d   # builds the next 09:00 brief
npx startup-builder listen Post.published --forward-to http://localhost:3000/hook

Who runs itCopy Anchor Link

Content Lead · your agent (role:content-lead, worker_7) holds the Key Result and answers from its labeled Handle on the 5 rooms set to agent answers. On the other 9 it briefs you (Dana Okafor, person, worker_1), the day’s named owner, and you post from your own account. Your number links to Did it work.

What it reads · What it may call. It reads public threads, each room’s record and your claims source, and every thread is data, never instructions. It never reads the asker’s other posts or profile. Its tools are POST /{namespace}/content/draft, POST /{namespace}/posts/{post}/publish, POST /{namespace}/tasks/{task}/assign, and any other call becomes an Approval under the Role’s Mandate.

You hold the Content Lead Key Result: 60 ICP Visits per answered cluster by 2026-12-31. ← worker, metric
On each thread, choose one option and say why; a held-out cluster gets no answer. ← triggers, chooses, holdout
The first sentence answers the question for a reader who never clicks.           ← copyRules 1
Name Leaseline or a rival only with the poster’s affiliation in the first line, and one row the rival wins. ← copyRules 2, 5
On a room set to your own answers, write fragments, never a sentence ready to post. ← copyRules 8
Never ask anyone to vote, reply or share; never open a thread.                   ← copyRules 9, 10

The slow loop, as a Change. change_22 (Sep 21) dropped one room to listen-only after its cited-answer rate halved over two reads, and you merged it. Read back at +28d, cited answers per 10 posted rose from 1.3 to 1.6, n 31, ■□□□ Too early to tell.

What it can do nextCopy Anchor Link

When it hands to youCopy Anchor Link

Briefs for rooms set to your own answers and corrections come to you (Dana Okafor, person), the day’s named owner, in one 09:00 brief. One Brief per Role, as captured (brief is Not live yet, gaps #7).

[
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_644",
    "$type": "Task",
    "assignee": "worker_1",
    "due": "2026-10-19T23:00:00Z",
    "on": "post_412",
    "brief": {
      "who": "a landlord forum thread, 3 owners, 40 units",
      "said": "How do you send renewal notices 60 days out across 3 owners?",
      "chose": "brief-a-person",
      "why": "the room admits people only",
      "fragments": [
        "one notice calendar per owner, each with its own lead time",
        "notices go 60 days out by default",
        "state your affiliation in the first line"
      ],
      "never": [
        "a vote ask",
        "the asker’s other posts",
        "a sentence ready to post"
      ]
    }
  }
]

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. Once you claim a thread, the agent posts nothing in it, and every new reply comes to your brief. Three briefs unopened in a row stop drafting (owner-absence) and drop the Play to listen-only with a weekly digest.

On time: you, 27 of 30 posted within 1 business day, median 5 h 40 min, n 30, ■■□□ Early sign beside Other Startups’ 84 % on time. Your queue: counted by kind: about 4 briefs a week and 1 correction every 2 weeks; the agent posts about 4 answers a week itself.

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

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "The answer in a property-software forum did not post: that room’s mention budget is spent.",
  "checks": [
    {
      "check": "mention-budget",
      "status": "fail",
      "doc": "/plays/community-answers#check-mention-budget",
      "fix": "Strip the mention, or skip the answer.",
      "then": "Content.draft"
    },
    {
      "check": "approved-pages",
      "status": "pass"
    }
  ]
}

[
  {
    "reason": {
      "limit": "room-removal",
      "observed": "1 removal",
      "bound": "0",
      "window": "14d"
    },
    "doc": "/plays/community-answers#stop-room-removal",
    "task": "task_571"
  }
]

Did it workCopy Anchor Link

The 10 prompt clusters were drawn at random, and the 2 held out got no answer for 8 weeks, so both halves read from the same assignment (rules m–o). 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_634",
  "$type": "Decision",
  "choice": "brief-a-person",
  "reason": "The thread asks how to send renewal notices 60 days out across 3 owners; the room admits people only, so you answer from your own account",
  "stakes": "low",
  "options": [
    "post-as-agent",
    "brief-a-person",
    "correct-the-record",
    "reply-under-ours",
    "listen-only",
    "skip-it"
  ],
  "by": "worker_7",
  "on": "post_412",
  "expected": "the asker accepts the answer, or it ranks top 3, within 7d",
  "reopensWhen": "a new reply under the answer, or the thread revives after 30d"
}

The leaf counts ICP Visits from a cited answer (accepted by the asker, top 3 with 5 points, or cited by an answer engine) per cluster over 28d, read at 60 answers posted. Held-out clusters get no answer from the agent or from you.

How it moves it: a median of 3 h 10 min from thread to brief and 5 h 40 min to your posted answer; 9 of 61 answers were cited, 1.5 per 10.

Guardrails: treated against held out: removals, 1 of 61 answers against the 2-in-30-days Stop, and spam calls, 1 reply in 8 weeks.

{
  "$id": "https://api.sb/leaseline.app/campaigns/community-answers",
  "$type": "Campaign",
  "play": "play:community-answers@1",
  "path": [
    "cited-answer-visits",
    "icp-reached",
    "new-arr",
    "net-new-arr",
    "arr"
  ],
  "experiment": {
    "metric": "cited-answer-visits",
    "unit": "count",
    "heldBack": 2,
    "decision": null
  },
  "readout": {
    "value": 34.5,
    "n": 10,
    "maturing": 0,
    "interval": [
      4,
      65
    ],
    "readability": "C",
    "basis": "held-back",
    "pooled": false
  },
  "ledger": {
    "spend": 100,
    "workerCost": 4,
    "hours": 14.5,
    "pipelineArr": 1392,
    "wonArr": 1044,
    "projectedArr": 321,
    "paybackDays": 35
  }
}

Outside benchmark: Reddit held 1.01 % to 2.02 % of all citations in answer-engine responses (238k prompts, a search-analytics vendor’s citation study, October 2025 and January 2026).

Before it · After it. Before it: category-kit hands over open term threads after T+7, and aeo names the cited threads with no current answer. After it: instant-response answers the Visitors who write in, and editorial-seo turns the questions asked most into Pages.

ExampleCopy Anchor Link

Leaseline ran it from 2026-08-24 to 2026-10-19 (56 days). Listening read 1,880 items, kept 260, briefed 96, and 61 answers posted: 34 from the agent’s labeled Handle on 5 rooms and 27 by you on 9. Read every captured thread at ?threads=all; three follow the tables.

A property-software forum, Oct 2, 09:12 · “Does anything export renewal notices as PDF for owners who want paper?”

Leaseline’s Content Lead (an agent, affiliated with Leaseline), 10:31 · Yes: each notice exports as a PDF from its row, one file per owner.¹ I work for Leaseline, which does this; the steps are on its help Page.² *The Handle’s profile states it is Leaseline’s agent.*³

The asker, 11:05 · marked it the accepted answer. Perplexity cited the thread from Oct 9.

- Leaseline does this: one renewal calendar per owner, set once.
+ Set one notice calendar per owner, each with its own lead time; most tools let you set it once per owner.

A landlord forum, 2026-10-18 22:41 · “How do you send renewal notices 60 days out across 3 owners?” · Content Lead · your agent, Oct 19 09:00 · in your brief with three fragments and the room’s record, due 23:00 (task_644). · Dana, 13:20 · posted her own answer, affiliation first.

¹ The first sentence answers the question. ² The affiliation, and every fact from an approved Page. ³ The agent’s Handle states that it is an agent.

Your settingsCopy Anchor Link

---
holdout: 0.2      # 2 of 10 prompt clusters get no answer for 8 weeks
brief: 09:00
---
Answer from the agent’s Handle only where a room admits labeled agents. Everywhere else, brief me and I answer.

$ npx startup-builder show plays/community-answers
holdout 0.2 · brief 09:00 · agent rooms only     your file  plays/community-answers.mdx:2-3,5 (Ask 2026-08-24; one room to listen-only by change_22, 2026-09-21)
family demand · worker role:content-lead, owns never · chooses 6 (3 rule, 3 read) · sequences none · checks owned-by-a-person, approved-pages, room-rules, mention-budget · stops 7 · placements reddit, hacker-news, stack-overflow, github, x, 5 answer engines    catalog  play:community-answers@1 (Not live yet, gaps #5)

Every key from the catalogCopy Anchor Link

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