Won back: what moves it
Won back is the ARR from former Customers who pay again after a window with no revenue.
Won back is the ARR from former Customers paying again after a window with no revenue. A re-opened Lead counts on Deals and trials opened instead.
The number
What moved won back this week, and which Play moved it?
curl "https://api.sb/leaseline.app/customers?where=status%20%3D%20%22wonBack%22&total=true" \
-H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"
# 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":"reactivated-arr","shape":"trend","breakdown":"play","window":"7d"}'import { $ } from 'startup-builder'
const { total } = await $.Customer.list({ where: 'status = "wonBack"', total: true }) // former Customers earning again
return await $.Metric.query({ metric: 'reactivated-arr', shape: 'trend', breakdown: 'play', window: '7d' }) // by the Play credited · Not live yet,npx startup-builder do Customer.list --json '{"where":"status = \"wonBack\"","total":true}'
npx startup-builder do Metric.query --json '{"metric":"reactivated-arr","shape":"trend","breakdown":"play","window":"7d"}' # Not live yet (gaps #4){
"name": "do",
"arguments": {
"code": "const { total } = await $.Customer.list({ where: 'status = \"wonBack\"', total: true }) // former Customers earning again\nreturn await $.Metric.query({ metric: 'reactivated-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 yetPreview$0 ARR won back · ■■■■ Clear · n 0 · path → net-new-arr → arr
$.Metric.query({ metric: · sample
Nothing moved it in the window: $0 ARR.
reactivated-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 | 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 |
|---|---|
| Play | Next order due · Tells a Customer the day their last order makes the next one due, with the live price and a one-click order. |
| Play | Objection watch · Records why each Customer or Deal said no, holds them from other outreach, and sends one Message, with proof, once the reason stops being true. |
| Page | More seats and upgrades |
| Page | What they tell you |
| Title | Head of customers |
The leaves
| Under it | Moved by |
|---|---|
next-outcome-acceptance | Next order due |
objection-dollars-closed | Objection watch |
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.