Proposal build
Weekly Growth review · ISO week undefined · undefined undefined · undefined · Generated undefined
Skeleton — not yet built. Clearing ends when a reseller buys the lead; it does not end the customer's journey. We can't wash our hands of a lead the moment it sells — the reseller bought it, but did they do something with it, and was the customer served? This branch owns the middle: what happens between the purchase and a real proposal in the customer's hands.
It's distinct from Clearing (the market clearing, to purchase) and from Awards (the outcome). This is the backbone in between — the proposal lifecycle.
What this page will carry
- Purchase → proposal started — how quickly a reseller acts on a lead they've bought (the first velocity gate after clearing).
- Proposal in build — proposals in progress, their age, and where they stall in design.
- Completion & drop-off — how many purchased leads become a fully-formed proposal, and how many die in the reseller's hands.
- Proposal lifecycle — the aging of live proposals through to the point of award (award itself lives on Awards).
- Customer-facing velocity — time from requirement to a real proposal in front of the customer: the response velocity the customer actually experiences.
Why it matters
A lead sold but never worked is a customer let down after we took the reseller's money — worse for trust than a lead that never cleared. This branch is how we hold resellers (and ourselves) accountable for serving the customer after the sale, and where the customer's true response-velocity is measured.
Metrics, data and charts to follow — see BACKLOG.md for the intended scope.