Outbound
Weekly Growth review · ISO week undefined · undefined undefined · undefined · Generated undefined
Are we recruiting paying resellers fast enough — and where is the pipeline leaking this week?
Fact · Cause · Action
AI-generated — stub. Behind pace on signups with the mid-July deadline close — but it's one fixable leak, not a broad problem, and the fix is already in flight. The table is the whole story; the sections below just let you validate each fact and cause.
| Section | Fact | Cause | Proposed action |
|---|---|---|---|
| Outbound funnel forward rates | Reply → Positive stuck at 21%, below its 25% floor. | The opener lands replies but attracts the wrong people — a message-fit problem, not effort. | Hold the rewritten opener one more week; if it stays below the floor, escalate to a targeting review. |
| Outbound pipeline movement | 28 contacts sat all week without moving; the pipeline is growing faster than it clears. | Stalled deals aren't being pushed to a decision, so they silt up instead of closing either way. | Force the stalled pool to a yes / no decision so it flows. |
| Stuck by stage | Call held aging from 22% to 46% past target over eight weeks. | Only ~9 warm, near-signature contacts — small volume, so slippage rather than a systemic block. | Targeted nudge to those 9; no system change, watch the rate next week. |
Sign-ups over time
This week. Sign-ups held around the 13-week average after the opener rewrite went live (22 Jun), then dipped — and that dip is the volume drop, not the opener. · AI stub
Catalog Error: Table with name supply_outbound_kpi does not exist!
Did you mean "main.duckdb_columns"?
LINE 3: from demo.supply_outbound_kpi order by week_start
^Sign-ups waterfall
This week. 8 signups vs a ~12 average — the ~4 gap is mostly volume: fewer contacted cost ~4 and the Reply → Positive leak another ~2, with ~2 clawed back elsewhere. More contacts plus the opener fix gets you back to average. · AI stub
Catalog Error: Table with name supply_signup_bridge does not exist!
Did you mean "pg_catalog.pg_settings"?
LINE 2: ... SELECT * FROM (select label, base, rise, fall, total from demo.supply_signup_bridge order by bar_order
^Outbound funnel
This week. 1,240 contacted narrowing to 8 signed. The shape is normal bar one pinch — Replied → Positive — which is where the funnel is leaking. · AI stub
Catalog Error: Table with name supply_funnel does not exist!
Did you mean "pg_catalog.pg_type"?
LINE 2: ... SELECT * FROM (select stage, count, ln(count) as size from demo.supply_funnel order by stage_order
^Outbound funnel forward rates
This week. Counts are down at every step (fewer contacted feeds through), but rates hold at or above average everywhere except Replied → Positive, which breaches its floor. Volume is the shortfall; quality is fine bar that one leak. · AI stub
Catalog Error: Table with name supply_step_conversions does not exist!
Did you mean "pg_catalog.pg_constraint"?
LINE 4: from demo.supply_step_conversions order by step_order
^Outbound sign-up velocity
This week. Down from 26 days in April to 18 now — comfortably under the 21-day target and still falling. · AI stub
Catalog Error: Table with name supply_velocity does not exist!
Did you mean "pg_catalog.pg_proc"?
LINE 4: from demo.supply_velocity order by week_start
^Outbound pipeline movement
This week. Of 76 in the pipeline a week ago, only 18 reached a decision and 30 progressed a stage — but 28 sat all week, and 22 new arrived on top. It's growing faster than it clears: force the stalled pool to a yes or no. · AI stub
Catalog Error: Table with name supply_pipeline_flow does not exist!
Did you mean "pg_catalog.pg_type"?
LINE 2: DESCRIBE SELECT * FROM (select source, target, value from demo.supply_pipeline_flow
^Where is velocity decaying? — stuck by stage
This week. Call held reads deep red (22% → 46% aged) but it's only ~9 people; Contacted looks calm yet holds the biggest backlog (~80), mostly expected non-response. So nudge the 9 warm Call-held contacts — don't rebuild the system. Open question: fewer chase touches, or a specific objection? · AI stub
Catalog Error: Table with name supply_stage_age_heat does not exist!
Did you mean "pg_catalog.pg_type"?
LINE 5: from demo.supply_stage_age_heat order by stage_order, week_start
^Catalog Error: Table with name supply_stage_age_heat does not exist!
Did you mean "pg_catalog.pg_type"?
LINE 5: from demo.supply_stage_age_heat order by stage_order, week_start
^