Cashflow Code · Application Grading · v2

Where June's 101 applicants landed, under the current rubric

Every completed application graded 1–4 against the current rubric — recalibrated against real GHL-pipeline outcomes (front-end DQ rate and show rate), replacing the original lenient-bootstrap version that proved non-predictive.

101
applications, June 1–30
(all via the Long-form app)
81
matched to a booked call
in the Bookings Log
42%
graded 3 or 4 —
the current MQL bar
58%
graded 1 or 2 —
DQ / setter-triage

Grade distribution

n = 81, matched applications

The rubric is now meaningfully stricter than the lenient first pass — the majority of applicants land in DQ or setter-triage territory, and "perfect ICP" (grade 4) is a genuinely small minority, matching what a first-principles read of this offer's fit rate should look like.

20
27
28
6
Grade 1 — DQ (20, 25%)
Grade 2 — setter triage (27, 33%)
Grade 3 — closer, can help (28, 35%)
Grade 4 — perfect ICP (6, 7%)

Q7 — "I haven't closed my first deal because ___"

the strongest single predictor found

Free-text answer length, not content, is what scores here — a terse answer is the single strongest red flag in the whole rubric (weighted +3, the heaviest single input). A substantive answer (6+ words) is required for a grade-4.

6+ wordsno flag — grade-4 eligible
53
3–5 wordspartial flag, +1
25
≤2 wordsstrong red flag, +3
23

Q8 — living situation

unchanged from the original rubric
Getting by, not savingthe modal answer
34
Struggling to pay the billsred flag, +2
26
Getting by and savinggrade-4 component
24
Thrivinggrade-4 component
17

Q9 — significant-other support

new in this version

Free text, bucketed. Only an unambiguous "No" scores a flag (+1) — a supportive partner, a single person, or an ambiguous answer don't count against the applicant.

Supportive
39
Unambiguous "No"the only bucket that flags, +1
33
Other / ambiguous
20
Blank
4
No significant other
2
"Not fully supportive"
3

Q10 — capital

unchanged from the original rubric
Resourceful / access to creditthe modal answer
51
Have the fundsgrade-4 component
28
No funds, no creditred flag, +2
22

By funnel

matched to Bookings Log, n = 81

Volume is almost entirely VSL — the other channels don't yet carry enough applications to read grade mix by channel with any confidence.

FunnelnGrade 1Grade 2Grade 3Grade 4MQL rate (3–4)
VSL (paid)74182525642%
IG (organic)5122040%
Other / Organic10010100%
LinkedIn110000%

Show rate by grade

the metric this rubric is calibrated against
Grade 4 perfect ICP
83% (5/6)
Grade 3 can help
59% (16/27)
Grade 2 setter triage
23% (7/29)
Grade 1 DQ
23% (4/19)
What "calibrated" means here

Show rate climbs cleanly from the bottom two grades (23% each) to grade 3 (59%) to grade 4 (83%) — the rubric now sorts real outcomes, not just self-reported answers. Grades 1 and 2 read the same on show rate by design (both route away from a closer's calendar); the split between them is about front-end-DQ severity, not show-rate granularity — grade 1 front-end-DQs at a materially higher rate than grade 2 even though their show rates tie.

Appendix — what changed from the original (v1) rubric

The first version of this rubric used three self-reported multiple-choice questions (Q8 living situation, Q10 capital, Q12 commitment) and counted red flags. Checked against real outcomes, it wasn't predictive: show rate by grade went 50% → 15% → 58% → 47% — grade 2 showed worse than grade 1, and grade 3 beat grade 4. The current version replaces Q12 (found to carry no real signal) with two free-text signals — Q7 answer length (the single strongest predictor found) and a bucketed read of Q9 — and switches from counting flags to a weighted score. Show rate now reads 23% → 23% → 59% → 83%, and front-end-DQ rate is 32% → 24% → 19% → 0%, both cleanly ordered.

Grade 1Grade 2Grade 3Grade 4
Show rate — v1 (retired)50%15%58%47%
Show rate — v2 (current)23%23%59%83%
Front-end DQ rate — v145%29%17%6%
Front-end DQ rate — v232%24%19%0%

Grade 1+2 share of applicants rose from 40% to 58%; grade 4 shrank from 20% to 7%. This is a deliberate, dated cutover (2026-07-01) — CPMQL/CPTQO reads from before this date aren't directly comparable to reads after it, since what counts as an MQL changed. Calibrated on June's own outcome data (some grade cells as thin as n=6) — not out-of-sample tested; scheduled for re-validation once July's outcomes resolve. Full detail: the wiki page typeform-grading-mql-handoff.md.