Launch circuit
When should I launch, and where? In week two or three, once your first links are live: one main launch, then the small boards over two weeks.
You, to your agent
Launch us on Product Hunt in week three, then the small boards.
Draft the kit and schedule every stop.
curl -X POST https://api.sb/leaseline.app/content/draft \
-H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"kind":"launch-kit","brief":"Leaseline on Product Hunt: notices that send themselves"}'
curl -X POST https://api.sb/leaseline.app/posts/posts%2Fpost_51/schedule \
-H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"at":"2026-11-11T08:01:00Z"}'import { $ } from 'startup-builder'
const kit = await $.Content.draft({ kind: 'launch-kit', brief: 'Leaseline on Product Hunt:npx startup-builder do Content.draft --json '{"kind":"launch-kit","brief":"Leaseline on Product Hunt: notices that send themselves"}'
npx startup-builder do Post.schedule --json '{"post":"posts/post_51","at":"2026-11-11T08:01:00Z"}'{
"name": "do",
"arguments": {
"code": "const kit = await $.Content.draft({ kind: 'launch-kit', brief: 'Leaseline on Product Hunt: notices that send themselves' }) // tagline, gallery, first comment\nreturn await $.Post.schedule({ post: 'posts/post_51', at: '2026-11-11T08:01:00Z' }) // the main stop, 12:01 am Pacific"
}
}Response200
application/json{
"$id": "https:sample- Launch kit and schedule: free
- First run
- Coming
- Status
- browser agent · API
- Runs by
- nothing
- Connect once
What you get
| Field | What it says |
|---|---|
| Stop | The launch site, and whether it is the main stop or a small board. |
| Date | The day and hour it goes live. |
| Link | The kind of link the stop gives once the post is live. |
| Visits and signups | What each stop brought, from your analytics. |
How it runs
| When | What happens | Runs by | Your part | Takes |
|---|---|---|---|---|
| Week 1 | Draft the launch kit from the product kit you approved (Launch kit) | API | approve it once | the same day |
| Week 2 or 3 | Post the main stop: Product Hunt at 12:01 am Pacific, or a Show HN when people can try it without a signup (Main stop) | browser agent | answer the comments that day | launch day |
| Launch day | Post your launch on LinkedIn and X, with the link in the first reply (Launch posts) | API | nothing | the same day |
| The next two weeks | Post the small launch boards one at a time, each pointing at the main stop (Small launch boards) | browser agent | nothing | days per board |
| A week after | Read visits, signups and links by stop (Launch readout) | API | 5 minutes | the same day |
Jobs inside it
Part of Earn first links.
Where and how it runs
| Where it works | How it runs | Connect once |
|---|---|---|
| Product Hunt, Hacker News, BetaList, Reddit, X, LinkedIn | browser agent · API | nothing |
Your agent acts as you on every Venue you authorize. Where a Venue has no API, a browser agent signs in as you and does the steps.
Plays that use it
| Play | Strategy that runs it |
|---|---|
| Launch sites | Passive |
Reference
| Tool | Runs today |
|---|---|
POST /{namespace}/posts/{post}/schedule | Coming |
POST /{namespace}/content/draft | Coming |
POST /{namespace}/startups/{startup}/launch | Works today |
POST /{namespace}/posts/{post}/publish | Coming |
Compiled, not written: edit the records it reads (catalog/launch-circuit), 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.