Launch week

# 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":"launch-week"}'

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

{
  "name": "do",
  "arguments": {
    "code": "return await $.Campaign.create({ play: 'launch-week' }, { 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": "launch-week can’t start: 1 check fails and 1 warns.",
 6  "checks": [
 7    {
 8      "check": "use-when",
 9      "status": "warn",
10      "observed": "Q3: 8 visible Changes flag-on; 74 of 100 People who said yes",
11      "doc": "/plays/launch-week#check-use-when",
12      "fix": "Grow the list to 100 by planning day; the recap waits for it.",
13      "then": "Contact.subscribe"
14    },
15  …

curl "https://api.sb/leaseline.app/events?where=name%20in%20(%22Change.merged%22%2C%20%22Flag.evaluated%22%2C%20%22Change.reverted%22%2C%20%22Period.opened%22%2C%20%22Organization.announced%22%2C%20%22Version.deployed%22%2C%20%22Visitor.identified%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_1209"}'

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

 1import { $ } from 'startup-builder'
 2
 3const { events: [last] } = await $.Event.list({ where: 'name in ("Change.merged", "Flag.evaluated", "Change.reverted", "Period.opened", "Organization.announced", "Version.deployed", "Visitor.identified")', 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 (\"Change.merged\", \"Flag.evaluated\", \"Change.reverted\", \"Period.opened\", \"Organization.announced\", \"Version.deployed\", \"Visitor.identified\")","limit":1}'
npx startup-builder do Trigger.fire --json '{"like":"event_1209"}' --try   # Not live yet (gaps #7)
npx startup-builder do Decision.list --json '{"where":"on = \"change_41\""}'   # Not live yet (gaps #7)
npx startup-builder do Action.list --json '{"where":"on = \"change_41\""}'   # Not live yet (gaps #7)

{
  "name": "do",
  "arguments": {
    "code": "const { events: [last] } = await $.Event.list({ where: 'name in (\"Change.merged\", \"Flag.evaluated\", \"Change.reverted\", \"Period.opened\", \"Organization.announced\", \"Version.deployed\", \"Visitor.identified\")', 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_434",
 4    "$type": "Decision",
 5    "choice": "fix-the-claim",
 6    "reason": "`change_41` ships the owner portal; your comparison Page still says “owners get PDF reports only”, and a comparison row is yours to rewrite",
 7    "stakes": "medium",
 8    "options": [
 9      "write-the-feed-line",
10      "fix-the-claim",
11      "plan-the-week",
12      "run-the-day",
13      "swap-in-the-reserve",
14      "tell-who-asked",
15  …

action_1 is the feed line, held until the portal is on for every Customer for 7 days. action_2 sends the comparison row to you; record-copied facts it fixes itself, a comparison row it never does.

≈ +$240 ARR a month at 1 a quarter

Worth

3.5 h per week, then 15 min a week

Your time

$0 per week; ~$3 a week of Worker cost

Spend

Day 1 of the week: first week-sourced signup

First signal

6+ visible Changes a quarter, 100+ People who said yes

Use it when

Under 6 Changes: launch-sites · under 100: owned-newsletter

Not yet when

Worth’s formula: about +150 ICP Visitors per launch week (Other Startups’ results; no lift of your own to read) × 1 week a quarter ÷ 3 months × 0.008 Visitors to paid × $590 first order ARR ≈ +$236. Under First signal: Each week reads at day 5 plus 14; at 1 a quarter it reads before-after against your 12-week baseline, beside Other Startups’ results.

Start it this weekCopy Anchor Link

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

# 3 · keep it: you accept every plan and every comparison row
curl -X POST https://api.sb/leaseline.app/campaigns \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"play":"launch-week"}'

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

# off: the week stops; the drift sweep keeps running
curl -X PATCH https://api.sb/leaseline.app/campaigns/launch-week \
  -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": "launch-week can’t start: 1 check fails and 1 warns.",
  "checks": [
    {
      "check": "use-when",
      "status": "warn",
      "observed": "Q3: 8 visible Changes flag-on; 74 of 100 People who said yes",
      "doc": "/plays/launch-week#check-use-when",
      "fix": "Grow the list to 100 by planning day; the recap waits for it.",
      "then": "Contact.subscribe"
    },
    {
      "check": "baseline",
      "status": "pass",
      "observed": "118 ICP Visitors a week, 12-week baseline",
      "doc": "/plays/launch-week#check-baseline",
      "then": "Metric.query"
    },
    {
      "check": "change-feed",
      "status": "fail",
      "doc": "/plays/launch-week#check-change-feed",
      "fix": "Connect your code host so the feed reads each merged Change.",
      "then": "Integration.connect"
    },
    {
      "check": "domain-authenticated",
      "status": "pass",
      "doc": "/plays/launch-week#check-domain-authenticated",
      "then": "Domain.authenticate"
    },
    {
      "check": "mailbox-warm",
      "status": "pass",
      "observed": "the Startup’s Mailbox, warm since July",
      "doc": "/plays/launch-week#check-mailbox-warm",
      "then": "Mailbox.warm"
    },
    {
      "check": "role-unstaffed",
      "status": "pass",
      "observed": "plans and comparison rows go to the founder, Dana",
      "doc": "/plays/launch-week#check-role-unstaffed",
      "then": "Role.staff"
    }
  ]
}

A launch week costs no cash: day Pages publish on your own Site and posts go from your own Handles. The feed, the drift sweep and the kit cost about $3 a week (Worker cost). Your time is about 3.5 hours per week, plus 15 minutes a week on the feed digest.

When it startsCopy Anchor Link

{
  "$id": "https://api.sb/leaseline.app/events/event_1209",
  "$type": "Event",
  "name": "Change.merged",
  "at": "2026-10-18T16:40:03Z",
  "seq": 1209,
  "data": {
    "change": "changes/change_41",
    "title": "Owner portal: each owner signs in to see their renewals",
    "tier": 1,
    "flags": [
      "owner-portal"
    ],
    "rollout": 1,
    "drift": [
      "pages/compare-spreadsheets#row-4"
    ]
  }
}

# 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":"Change.merged","url":"https://leaseline.app/hooks/sb"}'
npx startup-builder trigger Change.merged --like event_1209   # replays the delivery through the drift sweep
npx startup-builder clock advance --by 7d   # reads whether the portal stayed on for every Customer

Who runs itCopy Anchor Link

Marketing Lead · your agent (role:marketing-lead, worker_8) holds the Key Result: it writes the feed, runs the drift sweep, plans the week, builds each day’s kit and runs the day. Each quarter’s plan and every comparison row hand to you (Dana Okafor, person, worker_1, role:founder), and you send your own posts from the tray and write every Hacker News word.

What it reads · What it may call. It reads each Change’s own description, its Flags and Evidence, and the live Site, never a watched Event in what it writes. It may call POST /{namespace}/content/draft, PATCH /{namespace}/pages/{id}, POST /{namespace}/sites/{site}/publish, POST /{namespace}/posts/{post}/publish and POST /{namespace}/posts/{post}/withdraw on your own Site and Handles. Its tools are POST /{namespace}/content/draft, PATCH /{namespace}/pages/{id}, POST /{namespace}/tasks/{task}/assign, POST /{namespace}/sites/{site}/publish, POST /{namespace}/posts/{post}/publish, POST /{namespace}/posts/{post}/withdraw, and any other call becomes an Approval under the Role’s Mandate.

You hold the Marketing Lead Key Result: 500 ICP Visitors per launch week by 2026-12-31. ← worker, metric
On each merged Change, drift or due date, choose one option and say why.         ← triggers, chooses
Name a Change only when every Flag it names is on for every Customer for 7 days. ← flag-gate
Start each line “You can now”, in 20 words or fewer, with no number the Change lacks. ← copyRules 1, 2
Lead the week with the tier 1 unit, then integrations, then templates.           ← your file, line 6
A comparison row goes to the founder; a record-copied fact you fix.              ← chooses.fix-the-claim

The slow loop, as a Change. decision_394 (2026-09-21, weekly, during planning) read Leaseline’s 4 integration Pages bringing 2 times the ICP Visits of its template Pages, so change_30 moved the Ledgerly and Porchlight unit from day 4 to day 2 (your file, line 6), and Dana merged it with POST /{namespace}/changes/{change}/merge. Replayed on Q2’s Pages, POST /{namespace}/changes/{change}/review put the week at about 450; read back at day 5 plus 14 it is 462, n 1 week, ■□□□ Too early to tell (Example, day 53).

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

npx startup-builder eval --scenario launch-week-38 --agent "claude -p" --seat marketing-lead   # seated: 0 false claims left, 0 unflagged lines sent · yours: 1 claim left on a listing, 1 line at 40 % rollout → You approve each one

What it can do nextCopy Anchor Link

When it hands to youCopy Anchor Link

Each quarter’s plan and every comparison row hand to you (Dana Okafor, person); interested recap replies go through instant-response to the AE. As captured, the comparison-row Task in your queue (brief is Not live yet, gaps #7).

[
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_524",
    "$type": "Task",
    "assignee": "worker_1",
    "due": "2026-10-19T17:00:00Z",
    "on": "change_41",
    "brief": {
      "page": "Leaseline vs spreadsheets, row 4",
      "says": "owners get PDF reports only",
      "now": "each owner signs in to the portal to see their renewals (change_41, flag on for 41 of 41 Customers)",
      "chose": "fix-the-claim",
      "why": "a comparison row is the founder’s to rewrite",
      "never": [
        "a claim about a named rival",
        "a number change_41 lacks"
      ]
    }
  }
]

You answer with POST /{namespace}/tasks/{task}/claim (Take this one) and rewrite the row, POST /{namespace}/tasks/{task}/return with a reason, or POST /{namespace}/actions/{action}/redirect; a plan with POST /{namespace}/approvals/{approval}/approve. While the row is open, drift-hold holds any post that links the comparison Page. Nobody else can rewrite a comparison in your name, so nothing goes up a Role.

On time: You: 4 of 4 comparison rows and 1 of 1 plan answered within 1 business day, median 3h 20m, n 5, ■□□□ Too early to tell beside Other Startups’ 87 %. Your queue: counted by kind: per quarter, 1 plan and 5 day lines; between weeks, about 1 comparison row a fortnight and the 15-minute weekly digest.

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 published is the day 1 thread in Example.

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "The day 1 Post did not publish: it states a number `change_33` does not hold.",
  "checks": [
    {
      "check": "fact-check",
      "status": "fail",
      "doc": "/plays/launch-week#check-fact-check",
      "fix": "Cut the number, or add it to the Change’s description.",
      "then": "Content.draft"
    },
    {
      "check": "flag-gate",
      "status": "pass"
    }
  ]
}

[
  {
    "reason": {
      "limit": "revert-withdraw",
      "observed": "`change_37` reverted at 11:12",
      "bound": "0 announced reverts",
      "window": "day 4"
    },
    "doc": "/plays/launch-week#stop-revert-withdraw",
    "task": "task_441"
  }
]

Did it workCopy Anchor Link

At 1 week a quarter, no held-back half of weeks reads, so the basis is before-after against your 12-week baseline (rule o): the columns read Now and Before, and nothing prints as Added. 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_434",
  "$type": "Decision",
  "choice": "fix-the-claim",
  "reason": "`change_41` ships the owner portal; your comparison Page still says “owners get PDF reports only”, and a comparison row is yours to rewrite",
  "stakes": "medium",
  "options": [
    "write-the-feed-line",
    "fix-the-claim",
    "plan-the-week",
    "run-the-day",
    "swap-in-the-reserve",
    "tell-who-asked",
    "not-now"
  ],
  "by": "worker_8",
  "on": "change_41",
  "expected": "the comparison row true within 1 business day",
  "reopensWhen": "no Page.updated on the comparison Page within 1d"
}

Before against after reads ICP Visitors from the week’s outputs, day 1 to day 5 plus 14, against your 12-week baseline scaled to 19 days. It is not proof; Other Startups’ results, read against a 10 % recap holdout, print beside it.

How it moves it: eight small Q3 releases landed as five dated days, each with its own Page and two posts, and the recap reached 187 People who said yes.

Guardrails: before against after: play-sourced-customers, 5 against 2, and false claims left on the Site at day 5, 0 against 3 found by the first sweep.

{
  "$id": "https://api.sb/leaseline.app/campaigns/launch-week",
  "$type": "Campaign",
  "play": "play:launch-week@1",
  "path": [
    "launch-week-icp-visits",
    "icp-reached",
    "new-arr",
    "net-new-arr",
    "arr"
  ],
  "experiment": {
    "metric": "launch-week-icp-visits",
    "unit": "count",
    "heldBack": 0,
    "decision": null
  },
  "readout": {
    "value": null,
    "n": 1,
    "maturing": 0,
    "interval": null,
    "readability": "inadmissible",
    "basis": "before-after",
    "pooled": true
  },
  "ledger": {
    "spend": 0,
    "workerCost": 24,
    "hours": 5.5,
    "pipelineArr": 2082,
    "wonArr": 2329,
    "projectedArr": 236,
    "paybackDays": 0
  }
}

Outside benchmark: none measures a startup launch week against its own baseline; Other Startups’ results, +150 ICP Visitors per week, ■■■□ Likely, n 380 weeks, stand in for one.

Before it · After it. Before it: shipped Changes and the drift sweep run every week. After it: a tier 1 Change on a rested site goes to launch-sites, refreshed listings to marketplace-listings, and a resolved loss reason to lead-reactivation.

ExampleCopy Anchor Link

Leaseline ran its first launch week from 2026-09-28 to 2026-10-02 on Q3’s 38 merged Changes: 14 internal, 16 changelog lines, 7 tier 2 and 1 tier 1, grouped into 5 days and 1 reserve. The drift sweep ran all 56 days. Read every captured thread at ?threads=all; three follow the tables.

Day 2, Sep 29, 09:00, Leaseline’s LinkedIn · You can now post each signed renewal to Ledgerly or Porchlight the day it signs.¹ The day Page shows both, live.²

Sep 29, 10:12 · a 140-unit manager read the day Page, signed up (first Source: the week’s short link) and activated on Oct 3; paid for Team on Oct 9, +$941 ARR.

- Renewals now go out 3x faster with per-owner batches.
+ You can now send each owner their own renewal batch, 60 days out.

Oct 18, 16:41 · change_41 shipped the owner portal, and the sweep found row 4 of the spreadsheets comparison still saying “PDF reports only”. The agent fixed nothing there and sent the row to Dana, due Oct 19, 17:00. · Dana, Oct 19, 09:20 · claimed it and rewrote the row; the hold on posts linking the Page released at 09:21.

¹ “You can now”, 20 words or fewer, from the Change’s own description. ² A screen the live Site serves.

Your settingsCopy Anchor Link

---
recapHoldout: 0.1     # 1 in 10 who said yes gets no recap
quarter: third-month
freeze: day-1-to-day-5
---
Lead with the tier 1 unit, then integrations, then templates. Comparison rows are mine.

$ npx startup-builder show plays/launch-week
recap holdout 0.1 · third month · freeze day 1 to day 5 · day order     your file  plays/launch-week.mdx:2,3,4,6 (Ask 2026-08-24; line 6 by change_30, 2026-09-21)
family demand · worker role:marketing-lead, owns never · chooses 7 (5 rule, 2 read) · sequences launch-week-recap, you-asked-it-shipped, week-signup-follow-up · checks owned-by-a-person, fact-check + 8 · stops 5 + 1 on ads · placements site, google-search, x, linkedin, hacker-news, gmail, outlook, yahoo-mail    catalog  play:launch-week@1 (Not live yet, gaps #5)

Every key from the catalogCopy Anchor Link

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