Review requests

# 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":"review-requests"}'

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

{
  "name": "do",
  "arguments": {
    "code": "return await $.Campaign.create({ play: 'review-requests' }, { 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": "review-requests can’t start yet: 1 check fails and 2 warn.",
 6  "checks": [
 7    {
 8      "check": "use-when",
 9      "status": "pass",
10      "observed": "41 Customers; 14 reached a renewed lease in 90 days",
11      "doc": "/plays/review-requests#check-use-when",
12      "fix": "Keep 10 or more Customers at an outcome, or run written-references.",
13      "then": "Metric.query"
14    },
15  …

curl "https://api.sb/leaseline.app/events?where=name%20in%20(%22Outcome.delivered%22%2C%20%22Review.published%22%2C%20%22Monitor.matched%22%2C%20%22Change.merged%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_9104"}'

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

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

{
  "name": "do",
  "arguments": {
    "code": "const { events: [last] } = await $.Event.list({ where: 'name in (\"Outcome.delivered\", \"Review.published\", \"Monitor.matched\", \"Change.merged\")', 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_752",
 4    "$type": "Decision",
 5    "choice": "ask-on-one-venue",
 6    "reason": "their first lease renewed from a Leaseline notice on Oct 17; Capterra holds 6 Reviews against a threshold of 10, so it is this month’s Venue",
 7    "stakes": "low",
 8    "options": [
 9      "ask-on-one-venue",
10      "answer-the-review",
11      "low-score-to-a-person",
12      "correct-a-fact",
13      "show-on-your-pages",
14      "not-now"
15  …

action_1 reads each Venue’s Review count against its threshold. action_2 is the ask in Cobalt Street’s own thread, held 2 minutes: the same words every Customer gets, with their outcome and the Capterra link.

≈ +$120 ARR a month at 11

Worth

20 min week 1, then 10 a week

Your time

$0.04 per ask, ~$0.45 a month at 11

Spend

Day 3: the first Review published

First signal

10+ Customers at an outcome, a Venue listing

Use it when

Under 10 Customers: written-references · no outcome Event: declare one (Offer.publish)

Not yet when

Worth’s formula: about +12 Reviews per 100 asks over asking by hand (Other Startups’ results; no lift of your own yet) × 11 asks a month × 21 people reached per Review × 0.012 reached to paid × $347 Pro ARR ≈ +$115. Under First signal: At 11 asks a month, 90 days can tell only +30 per 100 or more, so your file starts at holdout: 0 and reads before-after.

Start it this weekCopy Anchor Link

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

# 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":"review-requests"}'

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

# off: no ask sends; Reviews still get an answer from you
curl -X PATCH https://api.sb/leaseline.app/campaigns/review-requests \
  -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": "review-requests can’t start yet: 1 check fails and 2 warn.",
  "checks": [
    {
      "check": "use-when",
      "status": "pass",
      "observed": "41 Customers; 14 reached a renewed lease in 90 days",
      "doc": "/plays/review-requests#check-use-when",
      "fix": "Keep 10 or more Customers at an outcome, or run written-references.",
      "then": "Metric.query"
    },
    {
      "check": "outcome-event",
      "status": "fail",
      "observed": "Leaseline Pro declares no delivered-outcome Event",
      "doc": "/plays/review-requests#check-outcome-event",
      "fix": "Declare “a lease renewed from a Leaseline notice” as the outcome, then publish.",
      "then": "Offer.publish"
    },
    {
      "check": "baseline",
      "status": "warn",
      "observed": "1 Review from 6 asks by hand in 90 days",
      "doc": "/plays/review-requests#check-baseline",
      "fix": "n 6: it reads before-after, not proof, until volume allows a held-back half.",
      "then": "Metric.query"
    },
    {
      "check": "role-unstaffed",
      "status": "warn",
      "roles": [
        "success-manager",
        "customer-lead"
      ],
      "owned": 4,
      "doc": "/plays/review-requests#check-role-unstaffed",
      "fix": "Staff the CSM, or leave it: low scores come to you, and Priya’s 4 get drafts.",
      "then": "Role.staff"
    }
  ]
}

Each ask costs $0.04 from your Domain (Worker cost), and reading Reviews and drafting replies about $0.02 each. The Venues charge nothing to be reviewed. That comes to about $0.45 a month at 11 asks.

When it startsCopy Anchor Link

{
  "$id": "https://api.sb/leaseline.app/events/event_9104",
  "$type": "Event",
  "name": "Outcome.delivered",
  "at": "2026-10-17T14:30:00Z",
  "seq": 9104,
  "data": {
    "customer": "customer_23",
    "outcome": "lease renewed from a Leaseline notice",
    "lease": "lease_4471",
    "first": true
  }
}

npx startup-builder trigger Outcome.delivered --like event_9104   # replays the outcome
npx startup-builder clock advance --by 14d   # runs the ask’s day-7 reminder and closes it at day 14
npx startup-builder listen Review.published --forward-to http://localhost:3000/hook

Who runs itCopy Anchor Link

CSM · your agent (role:success-manager, worker_5) holds the Key Result. Low scores go to the CSM Role, which has no person, so you (Dana Okafor, person, worker_1); stale-fact corrections on forums are yours to post; and the 4 Customers AE · Priya Shah (person) owns get drafts in her queue. Your number links to Did it work.

What it reads · What it may call. It reads the outcome Event, each Venue’s Review count and the Reviews themselves. An ask names only the outcome the Customer saw in Leaseline, never anything watched. Its tools are POST /{namespace}/conversations/{conversation}/answer, POST /{namespace}/issues/{issue}/triage, POST /{namespace}/tasks/{task}/assign, POST /{namespace}/reviews/{review}/publish, and any other call becomes an Approval under the Role’s Mandate.

You hold the CSM Key Result: 35 Reviews per 100 asks by 2026-12-31.              ← worker, metric
At the outcome, ask every Customer the same way, on this month’s one Venue.      ← triggers, chooses, copyRules 1
Ask for an honest Review; never for stars or kind words.                         ← copyRules 2
Answer every Review within a day; a 1 to 3 goes to Dana.                         ← your file, line 4; reply-hold
Show a Review on our Pages only with the reviewer’s yes.                         ← copyRules 10; display-consent
A held Customer gets Not now; their CSM sees them first.                         ← keep-first

The slow loop. The weekly Decisions kept the outcome Event and the Venue rule, and no Change was merged in the window, so there is no replay or read-back to print. October’s Venue moved from G2 to Capterra by the rule itself, at G2’s 14th Review.

Bring your own agent (folded) starts at It does it, you can stop it for asks when it matches the seated agent on the eval suite; replies stay at You approve each one. POST /{namespace}/roles/{role}/staff seats it.

npx startup-builder eval --scenario review-requests-22 --agent "claude -p" --seat success-manager   # seated: 40.9 per 100, every Customer covered, 0 Checks failed sent · yours: 36.4, 1 ask that named a score

What it can do nextCopy Anchor Link

When it hands to youCopy Anchor Link

Low scores, held Customers and forum corrections come to you: the CSM Role has no person, and the founder seat posts corrections in your own name. One Brief per Role, as captured (brief is Not live yet, gaps #7).

[
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_781",
    "$type": "Task",
    "assignee": "worker_1",
    "due": "2026-10-03T16:00:00Z",
    "on": "customer_31",
    "brief": {
      "who": "Tidewater Rentals, on Pro",
      "said": "2 stars on G2: notices went out in the wrong time zone",
      "chose": "low-score-to-a-person",
      "why": "a 1 to 3 never gets an agent reply",
      "issue": "issue_58: the time zone on scheduled notices",
      "never": [
        "anything offered for an edit",
        "their account details in public"
      ]
    }
  },
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_766",
    "$type": "Task",
    "assignee": "worker_1",
    "due": "2026-09-25T17:00:00Z",
    "on": "thread_19",
    "brief": {
      "who": "a 2025 forum thread that cites Leaseline",
      "said": "Leaseline Pro is $19 a month",
      "chose": "correct-a-fact",
      "why": "the live Price is $29, since 2026-03-01",
      "draft": "the dated fact and its source, posted by you, no opinion on the thread"
    }
  }
]

You answer 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 you claim a low score, the agent drafts nothing more for that Review. 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, 5 of 5 within 1 business day, median 3 h, n 5, ■□□□ Too early to tell beside Other Startups’ 95 % on time. Your queue: in week 1, 10 asks to approve and 1 weekly review; then about 2 Review replies and 1 low score or correction a week.

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 reply that posted is the Tidewater thread in Example.

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "The agent’s reply to Tidewater’s 2-star Review did not post: it offers a free month for an update.",
  "checks": [
    {
      "check": "reply-hold",
      "status": "fail",
      "doc": "/plays/review-requests#check-reply-hold",
      "fix": "Have a person answer it, and offer nothing for an edit.",
      "then": "Task.assign"
    },
    {
      "check": "claims-resolve",
      "status": "pass"
    }
  ]
}

[
  {
    "reason": {
      "limit": "coverage",
      "observed": "1 Customer at the outcome with no ask and no reason",
      "bound": "0",
      "window": "the week of Sep 14"
    },
    "doc": "/plays/review-requests#stop-coverage",
    "task": "task_759"
  }
]

Did it workCopy Anchor Link

At 11 asks a month no held-back half reads within 90 days, so 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_752",
  "$type": "Decision",
  "choice": "ask-on-one-venue",
  "reason": "their first lease renewed from a Leaseline notice on Oct 17; Capterra holds 6 Reviews against a threshold of 10, so it is this month’s Venue",
  "stakes": "low",
  "options": [
    "ask-on-one-venue",
    "answer-the-review",
    "low-score-to-a-person",
    "correct-a-fact",
    "show-on-your-pages",
    "not-now"
  ],
  "by": "worker_5",
  "on": "customer_23",
  "expected": "a Review on Capterra within 14d",
  "reopensWhen": "no Review.published matched to customer_23 within 14d"
}

Before against after reads one window against the 90 days before it, scaled to 56 days; it is not proof, and Other Startups’ results print beside it. The leaf counts Reviews published on the target Venue within 14 days of an ask, per 100 asks delivered.

How it moves it: every Customer at the outcome got the same ask in their own thread within 2 minutes, on the Venue furthest under its threshold.

Guardrails: before against after: logo-churn, 0 of 22 asked Customers gone against a trailing 2.1 % a month, and opt-outs from asks, 0 of 22.

{
  "$id": "https://api.sb/leaseline.app/campaigns/review-requests",
  "$type": "Campaign",
  "play": "play:review-requests@1",
  "path": [
    "reviews-per-100-asks",
    "icp-reached",
    "new-arr",
    "net-new-arr",
    "arr"
  ],
  "experiment": {
    "metric": "reviews-per-100-asks",
    "unit": "per-100",
    "heldBack": 0,
    "decision": null
  },
  "readout": {
    "value": null,
    "n": 22,
    "maturing": 2,
    "interval": null,
    "readability": "inadmissible",
    "basis": "before-after",
    "pooled": true
  },
  "ledger": {
    "spend": 0,
    "workerCost": 2,
    "hours": 1.1,
    "pipelineArr": 0,
    "wonArr": 694,
    "projectedArr": 115,
    "paybackDays": 1
  }
}

Outside benchmark: this Play’s catalog record carries no sourced range yet, so Other Startups’ results stand in: 31 Reviews per 100 asks, ■■■□ Likely, n 6,900.

Before it · After it. Before it: usage-upsell and run-beside bring Customers to the outcome. After it: directory-listings reads the Review counts, aeo the corrected facts, and written-references asks the reviewers who said yes; keep-first holds a Customer at risk.

ExampleCopy Anchor Link

Leaseline ran it from 2026-08-24 to 2026-10-19 (56 days): 26 Customers reached the outcome, 2 were held by keep-first and 2 by another Play’s open ask, and 22 were asked, on G2 in September and Capterra in October. Read every captured thread at ?threads=all; three follow the tables.

Leaseline → Cobalt Street’s office, Oct 17 14:32 · Your first lease renewed from a Leaseline notice this week.¹ Would you leave an honest Review of Leaseline on Capterra? It takes about 3 minutes: capterra.com/leaseline.² *Signed with the Role’s disclosure line.*³

Cobalt Street, Oct 18 09:10 · 4 stars on Capterra: “Renewals finally go out on time.” Leaseline’s reply, Oct 18 11:02 · Thank you; glad the notices land on time.

- Sorry about that! We’d love to give you a free month if you’d update your review.
+ Thank you for telling us. Notices now use each property’s own time zone, as of Oct 6. — Dana, founder

Tidewater Rentals on G2, 2026-10-02 12:00 · 2 stars: “Notices went out in the wrong time zone.” · The agent, 12:01 · opened issue_58 and assigned the Review to you (task_781), due tomorrow 16:00 · Dana, 15:20 · posted the reply after the fix shipped.

¹ The outcome the Customer saw in Leaseline, never anything watched. ² An honest Review, on one Venue; no stars asked for and no reward. ³ The fixed signature line, compiled from the Role’s disclosure Setting.

Your settingsCopy Anchor Link

---
holdout: 0        # 11 asks a month is too few to hold half back; it reads before-after
---
Ask when a Customer’s first lease renews from a Leaseline notice, on the Venue furthest under its threshold.
Answer every Review within a day; anything under 4 stars comes to Dana.

$ npx startup-builder show plays/review-requests
holdout 0 · outcome: a lease renewed · one Venue a month · under 4 stars to Dana     your file  plays/review-requests.mdx:2,4,5 (Ask 2026-08-24)
worker role:success-manager, owns never · chooses 6 (4 rule, 2 read) · sequence review-ask-email · approval first-send, every-send · checks owned-by-a-person, keep-first, customer-ask-cap, reply-hold, display-consent, claims-resolve · stops 7 · placements gmail, outlook, yahoo-mail, g2, capterra, trustpilot, google-business-profile, app-store, google-play, shopify-app-store, chrome-web-store, reddit    catalog  play:review-requests@1 (Not live yet, gaps #5)

Every key from the catalogCopy Anchor Link

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