Activation rate: what moves it
Activation rate is the share of new Customers who reach your activation Event, and the Plays that raise it.
Activation rate is the share of new Customers who reach the activation Event your Offer names. Onboarding works it.
The number
What moved activation rate this week, and which Play moved it?
curl "https://api.sb/leaseline.app/customers?where=status%20%3D%20%22trialing%22&total=true" \
-H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"
curl -X POST https://api.sb/leaseline.app/metrics/query \
-H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"metric":"activation-rate","shape":"trend","breakdown":"play","window":"28d"}'import { $ } from 'startup-builder'
const { total } = await $.Customer.list({ where: 'status = "trialing"', total: true }) // trials that have not reached the activation Event
return await $.Metric.query({ metric: 'activation-rate', shape: 'trend', breakdown: 'play', window: '28d' }) // by the Play credited
npx startup-builder do Customer.list --json '{"where":"status = \"trialing\"","total":true}'
npx startup-builder do Metric.query --json '{"metric":"activation-rate","shape":"trend","breakdown":"play","window":"28d"}'{
"name": "do",
"arguments": {
"code": "const { total } = await $.Customer.list({ where: 'status = \"trialing\"', total: true }) // trials that have not reached the activation Event\nreturn await $.Metric.query({ metric: 'activation-rate', shape: 'trend', breakdown: 'play', window: '28d' }) // by the Play credited"
}
}application/json{
"metric": {
"$id": "https:samplePreview65 % activated · ■■□□ Early sign · n 26 · path → new-paying-customers → arr
$.Metric.query({ metric: · sample
| Credited to | This window | Customers |
|---|---|---|
| Product-led growth | 71 % | 14 |
| No Play credited | 58 % | 12 |
The hub defines it: activation-rate. This page adds the Plays and seats that move it.
Owner
| Accountable | From |
|---|---|
team: · the hub’s Product team, as the reused id keeps it | the hub Metric, unchanged |
Worked by
| Title | Its queue |
|---|---|
| Onboarding | POST /{namespace}/tasks/next on the Onboarding’s queue |
Moved here by
| How | Where |
|---|---|
| Play | Developer relations · Developer relations fixes what coding agents read, call by call, and ships each fix only when the suite and time to first call agree. |
| Play | Product-led growth · Gives free Customers enough to reach the result twice, then shows the upgrade inside the task at the Limit, with the real Price. |
| Play | Waitlist interviews · Interviews each Waitlist signup with your disclosed agent, admits by fit under a published cap, and sends a result built on their company. |
| Page | AI answers |
| Page | Signup flows |
| Title | Onboarding |
The leaves
| Under it | Moved by |
|---|---|
interview-activation-rate | Waitlist interviews |
time-to-first-call | Developer relations |
Compiled, not written: edit the records it reads (metrics/bridge.ts; cap), 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.