One-time sales ending: what moves it
One-time sales ending is the ARR from one-time Orders whose four weeks ran out with no plan behind them.
No Play moves this yet. Today the hub runs renewal-notice, and the proposed Play waits on the catalog request (gaps #4).
The number
What moved one-time sales ending this week, and which Play moved it?
# Not live yet (gaps #4)
curl -X POST https://api.sb/leaseline.app/metrics/query \
-H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"metric":"one-time-rolloff-arr","shape":"trend","breakdown":"play","window":"7d"}'import { $ } from 'startup-builder'
return await $.Metric.query({ metric: 'one-time-rolloff-arr', shape: 'trend', breakdown: 'play', window: '7d' }) // by the Play credited · Not live yet,npx startup-builder do Metric.query --json '{"metric":"one-time-rolloff-arr","shape":"trend","breakdown":"play","window":"7d"}' # Not live yet (gaps #4){
"name": "do",
"arguments": {
"code": "return await $.Metric.query({ metric: 'one-time-rolloff-arr', shape: 'trend', breakdown: 'play', window: '7d' }) // by the Play credited · Not live yet, gaps #4"
}
}application/json{
"metric": {
"$id": "https:sample · 1 Not live yet$0 ARR from one-time sales ending · ■■■■ Clear · n 0
$.Metric.query({ metric: · sample
Nothing moved it in the window: $0 ARR.
one-time-rolloff-arr is this site’s proposal to the hub (Not live yet, gaps #4), so the figure above is a sample until the hub holds it.
Owner
| Accountable | From |
|---|---|
customer-lead · Customer Lead (proposed in the bridge amendment, Not live yet, gaps #4) | the filed bridge item, word for word |
Worked by
| Title | Its queue |
|---|---|
| Head of customers | POST /{namespace}/tasks/next on the Head of customers’s queue |
Moved here by
| How | Where |
|---|---|
| Today | the hub Workflow renewal-notice · Renewal notice |
| Proposed Play | a catalog request · Not live yet, gaps #4 |
| Page | Renewals |
| Page | Offers and trials |
| Title | Head of customers |
The leaves
| Under it | Moved by |
|---|---|
| none | no leaf Metric sits under it; its Plays move it directly |
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.