The raise readiness audit founders should run before outreach
A raise readiness audit checks story, proof, list, materials, process, and follow-up before investor outreach starts.
The first cold investor reply is a stress test you did not schedule. A partner answers in four hours, asks for the deck and a time, and now the round is real on their calendar before it is real on yours. You send the deck you meant to revise. You book the call before you have decided what the call is supposed to prove. Three days later they ask for your data room and you are assembling it live, link by link, while they wait.
Nothing here was unknowable. The deck was always the old one. The data room never existed. The follow-up tracker was a Gmail folder. Outreach did not cause these gaps. It exposed them, at the one moment when fixing them costs you momentum instead of a quiet afternoon.
Founders treat the start of a raise as a marketing event: send the first wave, see who bites. The first wave is a load test. Every weak part of the round gets pulled forward and inspected by the people you most want to impress. The fix is boring and it works: audit the round against itself before anyone outside sees it.
What founders do instead
Most pre-outreach prep collapses into deck polishing. The deck is visible, it feels productive, and it absorbs unlimited hours. So the founder spends two weeks on slide transitions and zero minutes on whether they can answer "who else is in the round" or find the notes from the angel call six weeks ago.
The round is not one artifact. It is a system with at least six parts, and the deck is one of them. When a founder optimizes the visible part and skips the rest, the round looks ready and behaves like it is not. The investor does not see the deck in isolation. They see the deck, then the reply speed, then the diligence answer, then the second follow-up, and they are scoring the whole sequence.
A readiness audit checks every part the round will be judged on, not just the one that is fun to work on.
The six domains
A founder-led round is judged across six domains. Each one fails differently, and each one has a binary test you can run in a few minutes.
1. Narrative. Can you state, in three sentences, what you do, why now, and why you. Not the deck version. The version you say out loud when a partner asks "so what is this" before you have opened anything. If it takes you four tries, the narrative is not ready, and every meeting starts in a hole.
2. Target list. Do you have a named, ranked list of investors with a reason each one fits this round. Not a scraped list of 200 funds. A list where you can say why this person, at this fund, for this company, now. A list without reasons is a list of strangers.
3. Source context. When an investor's name lands in your inbox, can you reconstruct the history in under a minute. Who introduced you, what they said last time, what objection they raised, what you promised to send. If this lives only in your memory, it does not survive the third concurrent conversation.
4. Materials. Deck, one-pager, data room, and the specific numbers behind your three headline claims. Not "a deck exists" but "the deck I would send today, with last month's numbers, and the spreadsheet I would open if asked to defend the top-line metric."
5. Follow-up system. When a meeting ends, does a next move get recorded with a date, or does it dissolve into good intentions. Rounds die in follow-up far more often than in the meeting. If your system is "I'll remember," you will not.
6. Diligence responses. The eight questions you will be asked every time: churn, CAC, runway, the competitor question, why the last hire left, the legal cleanup, the cap table, the use of funds. Can you answer each in two sentences without scrambling. If a standard question makes you improvise, it reads as a gap whether or not it is one.
The scoring rubric
Score each domain 0, 1, or 2. No half points. The constraint forces an honest call instead of a hopeful one.
| Score | Meaning |
|---|---|
| 0 | Does not exist, or you cannot do it on demand right now |
| 1 | Exists but is rough, stale, or partial. Would slow you down under pressure |
| 2 | Ready. You could use it in the next hour with no prep |
| Domain | Pass/fail test | Score |
|---|---|---|
| Narrative | State it in 3 sentences, out loud, in one take | ___ /2 |
| Target list | 15+ named investors, each with a one-line fit reason | ___ /2 |
| Source context | Reconstruct any investor's history in under a minute | ___ /2 |
| Materials | Send-today deck, one-pager, data room, top-3 metric backups | ___ /2 |
| Follow-up system | Every meeting produces a dated next move, recorded | ___ /2 |
| Diligence responses | Answer all 8 standard questions in 2 sentences each | ___ /2 |
Total: ___ / 12
Reading the score:
- 10–12: Start outreach. Your weak spots are minor and fixable mid-flight.
- 7–9: One or two domains will hurt you. Fix the 0s and 1s before the first wave, not during it.
- 0–6: You are not raising yet. You are about to learn your gaps in front of investors. Spend three days here first.
The rubric is deliberately harsh on 0s. A single 0 in source context or follow-up leaks deals across a 40-investor round, and it never shows up as one dramatic failure. It shows up as a slightly worse close rate you cannot trace.
The 30-minute audit
You do not need a week. You need 30 honest minutes and a willingness to write 0 next to something you wish were a 2.
- Minutes 0–5 — Narrative. Set a timer. Say your three sentences out loud, once, no restarts. Record it if you can. Score it. Most founders score this a 1 the first time and are surprised.
- Minutes 5–10 — Target list. Open your list. Count named investors with a fit reason. Under 15 with reasons is a 0 or 1. A spreadsheet of fund names with no "why" is a 0.
- Minutes 10–15 — Source context. Pick two investors you have already talked to. Try to reconstruct each history from your actual records in under a minute. If you are reconstructing from memory, score it 1 at best.
- Minutes 15–20 — Materials. Open the deck you would send right now. Check the date on the numbers. Confirm the data room link works and is populated. Pull up the backup spreadsheet for your single biggest claim. Any missing piece caps this at 1.
- Minutes 20–25 — Follow-up system. Look at your last three investor conversations. Does each have a recorded, dated next move. If two of three are "I think I owe them something," score it 1.
- Minutes 25–30 — Diligence. Read the eight questions. Answer each out loud in two sentences. Any question that makes you improvise for more than ten seconds is not ready.
Add it up. The number tells you whether to send the first wave tomorrow or spend three days closing 0s. Either answer is useful. The expensive outcome is not knowing.
Where the audit usually breaks
In practice, narrative and materials tend to score high, because they are visible and founders over-invest in them. The 0s cluster in the unglamorous middle: source context, follow-up system, diligence depth. These are the parts no one rehearses and everyone is judged on.
The reason is structural. Narrative and deck are things you make once. Source context and follow-up are things you have to maintain across dozens of parallel conversations, every day, while also running the company. They decay. A list that was a 2 in week one is a 1 by week three because three new threads moved and nothing got written down.
That decay is the part worth designing for. Not the deck. The system that keeps the other five domains from sliding back to 1 while you are mid-round and out of attention.
Where RoundOS fits
The audit is a manual exercise and it should stay one. You can run it today with a timer and this rubric. The product question is what happens to the three domains that decay: source context, follow-up, and diligence readiness.
RoundOS pulls the round in from where it already lives. Email, calendar, meeting notes, investor spreadsheets, decks, LinkedIn exports, founder notes. It builds the investor and fund context from those sources, so reconstructing any conversation's history is a lookup, not a memory test. That is domain three scored to a 2 and held there. It flags stale threads and surfaces the next move per conversation, which is domain five. It keeps your standard diligence answers and the numbers behind your claims attached to the round, which is domain six.
So instead of running the audit once and watching the score slip, you start at a higher baseline and the three decaying domains stay scored. The narrative and the deck are still yours to write. The system stops the rest from sliding back to 1 while you are looking at slides.
Audit the raise before you trigger it.
Use RoundOS to check story, proof, list quality, materials, and next-step discipline before outreach creates live demand.