Scale Paid Check
scale_paid_checkDecide whether to scale paid now by analyzing customer cohorts, churn reasons, stop rates, payback, and unit economics; return scale, capped-test, or hold recommendations per segment.
Instructions
Helps you decide whether to scale paid now: it takes your customer list (signing date, segment, monthly fee and any stop or return dates) and your churn reasons, and returns, for each customer group, scale, run a capped test, or hold, with the counts behind it, the stop rule, payback, a first draft response to each churn reason and a churn interview guide. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of pmf_scorecard when you need a paid-growth decision grounded in customer cohorts and unit economics.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"product": "<product>",
"business_model": "<business_model>",
"billing_term": "<billing_term>",
"as_of": "<as_of>",
"customers": "<customers>",
"churn_reasons": "<churn_reasons>",
"interview_persona": "<interview_persona>"
},
"name": "scale_paid_check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| as_of | Yes | The date the list was pulled (YYYY-MM-DD). Format is text in YYYY-MM-DD form. For example, "2026-11-17". | |
| metrics | No | Optional: each metric with its name, value, whether it counts customers or revenue, and its period. Format is a JSON array. For example, [{"name":"an approved anonymous manufacturer","value":12}]. | |
| product | Yes | Product in one line. Format is text. For example, "invoice review service". | |
| paid_cac | No | Optional: paid-only CAC. Format is a JSON number. For example, 24000. | |
| test_cap | No | Optional: all-in budget for a capped test. Format is a JSON number. For example, 12. | |
| customers | Yes | One row per customer (1 to 2000 items). Format is a JSON array. For example, [{"id":"account-001","signed":"2026-11-17","segment":"manufacturers with 200 to 500 employees","monthly_fee":24000}]. | |
| stop_line | No | Optional (default 0.80): share of a cohort that must still pay at month 12. 0.80 is Shashwat's example line for a $36,000 contract, not a benchmark. Format is a JSON number. | |
| blended_cac | No | Optional: blended CAC, shown for contrast only. Format is a JSON number. For example, 24000. | |
| billing_term | Yes | How customers are billed. Format is text using one of the listed labels. For example, "monthly". | |
| gross_margin | No | Optional (0 to 1): gross margin needed for the money section. Format is a JSON number. For example, 0.8. | |
| churn_reasons | Yes | Reasons in customers' words, comma or line separated. Format is text. For example, "implementation delays and unclear ownership". | |
| business_model | Yes | Business model, passed on to retention_playbook. Format is text using one of the listed labels. For example, "saas_subscription". | |
| win_rate_floor | No | Optional (0 to 1): a win rate the buyer is confident paid can reach. Format is a JSON number. For example, 0.8. | |
| win_rate_target | No | Optional (0 to 1): the highest win rate the buyer would believe. Format is a JSON number. For example, 0.8. | |
| interview_persona | Yes | Role to interview, for the interview kit. Format is text. For example, "finance director". | |
| payback_line_months | No | Optional (default 12): the longest acceptable paid payback in months. 12 is Shashwat's example line for a $36,000 contract, not a benchmark. Format is a JSON number. |