The Pre-Seed Readiness Rubric: How to Score a Cohort Before Demo Day and Triage What Is Actually Fixable
A scoring tool for accelerator leads and mentors, built for companies with no revenue to measure.

Standard investor-readiness scorecards measure traction, unit economics, and LTV to CAC, none of which exist at pre-seed. Score a pre-seed cohort on eight dimensions instead: entity hygiene, IP chain of title, round coherence, structure choice, investor list quality, narrative, proof of pull, and process discipline. Six are fixable inside a program.
Standard investor-readiness scorecards measure traction, unit economics, and LTV to CAC, none of which exist at pre-seed. Score a pre-seed cohort on eight dimensions instead: entity hygiene, IP chain of title, round coherence, structure choice, investor list quality, narrative, proof of pull, and process discipline. Six are fixable inside a program.
If you run an accelerator, a founder program, or a university venture track, you have probably tried to use an off-the-shelf readiness scorecard on a pre-revenue cohort and found it useless. That is not your fault. It is a stage mismatch.
Look at what those frameworks actually measure. A representative startup evaluation checklist covers business model, traction, financial health, and financial forecasts, and states plainly that it is aimed at founders raising a first or second institutional round. Run it on a team that has been building for four months and every company scores badly on the same four dimensions, which tells you nothing about which of them to help first.
Here is a rubric built for the stage you are actually teaching.
The eight dimensions
Score each 0 to 3. Twenty-four points total. Definitions below are written so that two mentors scoring the same company independently land within a point of each other, which is the property most rubrics lack.
| # | Dimension | 0 | 1 | 2 | 3 |
|---|---|---|---|---|---|
| 1 | Entity hygiene | No entity or an LLC | C-corp formed, gaps remain | C-corp, founder stock issued, 83(b) filed | All of that plus foreign qualification and clean records |
| 2 | IP chain of title | Unclear who owns the work | Founders assigned, contributors not | All contributors assigned | Assigned and documented in a data room |
| 3 | Round coherence | No number, or a number with no basis | Number exists, not tied to a plan | Number tied to a milestone and runway | Number, milestone, runway, and hiring plan all consistent |
| 4 | Structure choice | Does not know SAFE from priced | Knows the terms, cannot defend a cap | Chose a structure and can justify the cap | Can also explain the dilution to their own cap table |
| 5 | Investor list quality | No list, or a list of famous funds | List exists, no stage or thesis filter | Filtered by stage and thesis, 40 or more names | Filtered, sourced, and mapped to warm paths |
| 6 | Narrative | Cannot explain the company in a minute | Explains the product, not the why now | Clear problem, insight, and why now | Also handles the obvious objection unprompted |
| 7 | Proof of pull | Nothing outside the building | Conversations, no commitments | Signed pilots, waitlist, or usage | Evidence someone changed behavior or paid |
| 8 | Process discipline | Ad hoc outreach | Tracks meetings in a doc | Tracked pipeline with weekly cadence | Pipeline plus recorded outcomes and follow-up system |
Scoring notes that prevent mentor disagreement
Entity hygiene is binary at each step and requires no judgment. Ask for the certificate of incorporation, the stock purchase agreements, and proof of the 83(b) filing. A founder who says it is handled but cannot produce documents scores as if it is not handled, because that is how an investor's counsel will treat it.
IP chain of title catches more programs off guard than any other item. The question is not whether the founders own the company. It is whether anyone else has a claim to the code, the designs, or the brand. The contractor who built the prototype, the friend who did the logo, the co-founder who left in month two. Each needs a signed assignment. Score 1 if only founders are covered.
Round coherence is where you find out whether the number is real. Ask three questions in sequence: how much are you raising, what does it buy, and what does that prove to a seed investor. A founder who answers the first and stalls on the second scores 1. This is the dimension where a program has the most direct effect, and the sizing logic itself is in the guide on how much to raise at pre-seed.
Structure choice at 2 versus 3 is worth the distinction. Plenty of founders can say they are raising on a post-money SAFE at a $10 million cap. Far fewer can show what their own ownership looks like after that SAFE converts alongside an option pool. The second group negotiates better and panics less.
Investor list quality at 0 and 1 look similar from the outside and are very different in practice. A list of twelve famous funds is a 0, because none of them write pre-seed checks into that category and the founder has not done the work to know that. Forty names filtered by stage and thesis is a 2. Mapped warm paths is a 3.
Narrative at 3 requires the founder to raise and answer the objection before an investor does. For a technical founder that is usually the question about what stops a large incumbent from building the same thing. A founder who waits to be asked and then improvises scores 2.
Proof of pull is the dimension where you must resist inflation. Interest is not pull. Twenty friendly conversations is a 1. A signed pilot, a waitlist with real names, or usage that continued after you stopped asking is a 2. Someone paying, or restructuring a workflow around your product, is a 3.
Process discipline is the dimension programs underweight and investors do not. A founder with a tracked pipeline, a weekly outreach target, and recorded outcomes converts a mediocre list better than a founder with a great story and no system.
Reading the total
| Score | Band | What it means | Program action |
|---|---|---|---|
| 19 to 24 | Ready | Can start conversations now | Focus on list expansion and follow-up mechanics |
| 13 to 18 | Close | Two or three specific gaps | Targeted fixes, then start in three to four weeks |
| 7 to 12 | Not yet | Systemic gaps across categories | A quarter of work, not a sprint |
| 0 to 6 | Wrong question | Not a fundraising problem | Company-building, not fundraise prep |
The band that matters most for a program director is the third one. A founder scoring 10 is not two weeks of pitch coaching away from a round. Sending them to demo day produces a bad experience for them, a wasted slot for you, and a signal to your investor network that your screening is loose. The honest conversation, delivered in week two rather than week ten, is the higher-value intervention.
Triage: what a program can actually fix
The point of scoring is deciding where to spend program time. Not all gaps are equally expensive to close.
| Dimension | Fixable in | Who fixes it | Cost |
|---|---|---|---|
| Entity hygiene | 1 to 2 weeks | Lawyer or formation service | Low, hundreds to low thousands |
| IP chain of title | 1 to 2 weeks | Founder collecting signatures | Near zero, if relationships are intact |
| Round coherence | 1 week | Mentor session plus founder work | Zero |
| Structure choice | 1 week | Teaching | Zero |
| Investor list quality | 2 to 3 weeks | Founder work, program network | Zero to low |
| Process discipline | 1 week to set up, ongoing to hold | Program cadence | Zero |
| Narrative | 3 to 6 weeks | Repetition against real audiences | Zero, but time-intensive |
| Proof of pull | A quarter or more | The company | High, it is the actual work |
Six of the eight are fixable inside a normal program. That is the useful finding. A cohort that scores badly on the first six is a program design problem, not a founder quality problem, and it is correctable this cycle.
Only proof of pull genuinely requires time that a twelve-week program cannot manufacture. Which means the honest use of this rubric is: fix everything else, then be truthful with each founder about whether their pull is sufficient for the raise they want, at the size they want, on the timeline they want.
Narrative sits awkwardly in the middle. It improves reliably with repetition against real audiences, but not with slide review. If your program is spending its narrative time on deck design, you are working on the wrong artifact.
How to run the scoring session
Score twice. Once in the first two weeks, once about three weeks before demo day. The first score sets the program plan. The second is a go or no-go. Scoring once at the end gives you a diagnosis with no treatment window.
Two scorers, independently, then reconcile. Ten minutes each per company, then a five-minute reconciliation. Where two experienced mentors disagree by more than a point, the definition is ambiguous and you should tighten it rather than average the scores.
Ask for artifacts, not answers. Dimensions 1, 2, 5, and 8 are documented or they are not. Requesting the document takes fifteen seconds and removes the most common source of inflated scores, which is a founder's sincere belief that something is handled.
Show the founder the rubric before you score them. This is not a test to catch anyone. A founder who can see the eight dimensions and the definitions can self-diagnose, and several will fix the cheap items before you ever score them. That is the outcome you want.
Report the two lowest dimensions, not the total. The total is for your program planning. The founder needs to know which two things to work on this month. Handing them a number produces anxiety and no action.
The two failure modes this catches
The polished founder with nothing underneath. Great deck, fluent narrative, scores 3 on dimension 6 and 0 or 1 on entity hygiene, IP, and pull. Programs love these founders because they present well at demo day. They generate meetings and then die in diligence, and the founder does not understand why, because the room was warm. Scoring the boring dimensions catches this in week two.
The strong company with a broken process. Real usage, real pull, defensible round, and no pipeline. Scores 3 on dimension 7 and 0 on dimension 8. This founder will raise eventually and will take three months longer than necessary, on worse terms, because they treated fundraising as a series of individual conversations rather than a process. This is the highest-return intervention available to a program, and the cheapest.
The second failure mode connects directly to a widespread misunderstanding of what demo day does. As one explanation of what investors actually decide at demo day puts it, the event is a meeting-generation moment rather than a round-closing one, and the deals it surfaces are frequently lost afterward through poor follow-up tracking and cadence. A founder scoring 0 on process discipline will convert almost none of the interest your demo day generates, which means your program's investor network gets used up producing nothing.
The dimension that predicts the rest
If you can only track one thing across a cohort, track process discipline.
Entity hygiene and IP are fixable in an afternoon of administrative work. Round coherence and structure choice are teachable in a session. Narrative improves with reps. Pull is the company's real work and cannot be accelerated by a program.
Process discipline is different because it is both the strongest predictor of closing and the most directly teachable thing on the list. It also compounds: a founder who runs a tracked pipeline at pre-seed runs one at seed, and the habit outlasts your program by several rounds.
For structuring what to teach, in what order, across a cohort, the sequenced approach in the pre-seed fundraising curriculum for educators maps reasonably well onto these eight dimensions. The beliefs founders arrive with that will distort their own self-scoring are collected in the corrections guide to pre-seed fundraising myths. And for founders already out raising who keep hearing no, the four underlying causes are separated in the diagnostic for a stalled pre-seed raise, which is a useful companion when a founder scoring well on this rubric is still getting passed.
The whole sequence a first-time founder has to run, in the order they hit it, is what The Funding Framework is built around, and it is a reasonable spine for a program that wants its founders working from one coherent model rather than eight mentors' opinions.
Frequently asked questions
Why not just use a standard investor-readiness scorecard?
How many dimensions should a pre-seed rubric have?
What is the single best predictor of whether a founder will close?
What should we do with a founder who scores low across the board?
When should we score the cohort?
Run your raise with a system, not a guess.
This is the kind of thinking The Funding Framework walks through, step by step, from story to close.