Nobody is born knowing how a round works.
This is the background behind every line of your scoring report. Read it once and the score stops being a verdict and starts being a to-do list.
You are not borrowing money. You are selling part of the future.
Everything else follows from this one fact.
An investor hands you cash and receives a permanent slice of whatever the company becomes. There is no repayment schedule and no interest to negotiate away. The only way that slice pays them back is if the company is worth a great deal more later, and someone buys it or the company lists.
That is why questions that feel hostile — how big can this get, why can't someone copy it, what happens when a large AI company notices — are not doubts about you. They are the only questions that decide whether the slice is worth anything.
Each stage buys one specific thing
Pitching the wrong stage's story is one of the most common reasons a good company gets a poor read.
- Idea / pre-product: the money buys a first working version and the first proof that someone wants it. Investors are judging the team, the insight and whether the problem is real.
- Pre-seed: the money buys evidence — a product in real hands, early usage, the first signs of pull. Investors are judging whether the insight survived contact with users.
- Seed: the money buys a repeatable way to acquire customers. Investors are judging whether growth is a machine or a series of favours.
Claiming a later stage than your evidence supports does not raise your valuation. It raises the bar you are measured against, and you fail it with your own material.
What is actually decided in the first ten minutes
Four questions, in this order. Most decks answer the fourth and skip the first three.
- Is the prize big enough? Not the size of the industry — the size of the part you can actually sell to.
- Why you? What do you know, own or have built that a competent stranger does not.
- Why now? What changed in technology, regulation or behaviour that makes this possible this year and not five years ago.
- What does the money buy? Which specific milestone this round reaches, and why that milestone makes the next round raisable.
Valuation is not something you choose
It is a bet on whether the next round can be priced higher than this one.
An early-stage valuation is not calculated from your revenue. It is set by what the next investor will plausibly pay. If you price this round so high that the next round cannot clear it, you have not won anything — you have set up a down round, which damages you far more than a modest price today.
Assume you raise 500,000 on a 4,500,000 pre-money valuation. Post-money is 5,000,000, and the new investors own 10%. If you also set aside a 10% option pool for future hires, the founders' combined ownership falls by roughly a fifth in one round.
Do this twice more before the company is worth much, and the founders no longer control the outcome. That is what dilution means in practice: not the percentage, but who still has a reason to keep going.
SAFE, convertible note, priced round
Three ways to take the money in. They are not interchangeable.
- SAFE: money now, shares later. Fast and cheap, no interest, no maturity date. The price is settled at the next priced round.
- Convertible note: the same idea as a loan — it carries interest and a date by which it must convert or be repaid. That date can become a crisis if the next round slips.
- Priced round (equity): shares are issued today at an agreed valuation. Slower and more expensive in legal work, but everyone knows exactly what they own.
Two terms decide what a SAFE or note really costs you. The discount lets the early money convert at a lower price than the next round. The valuation cap sets a ceiling on the price it converts at, no matter how well the next round goes. Stack several capped SAFEs and you can be far more diluted at the priced round than you expected. Model it before you sign, not after.
Every one of these words is in the glossary if you want the one-line version.
Work out the amount backwards, never forwards
Not what you would like to spend. What the next round will demand you have already proven.
- Write down what the next round's investors will need to see before they price you higher.
- Cost out the work that gets you there, honestly, including the hires.
- Add the months it will take to raise the next round — that search is itself a cost.
- That total is your raise. If it needs more than roughly eighteen months of runway, the milestone is probably too ambitious for one round.
A round with no named milestone reads as "we will figure it out". That is the single easiest thing for an investor to decline.
What each document has to answer
Upload all of it together. A deck alone forces every reader to guess, and guesses are rarely generous.
- Deck: the problem, why now, what you built, who uses it, the plan for the money, the team.
- Financials: what you actually earn and spend, how many months of cash remain, and the assumptions behind any forecast.
- Technical material: what is genuinely built, what is bought or wrapped, and what would be hard for a competitor to reproduce.
- Cap table and existing terms: who owns what already, and any caps or discounts still outstanding.
On this platform, anything the material never addresses is marked "not covered" and left out of the score rather than counted against you. Silence is not punished — but it is also not credited.
The four questions the AI era added
Judging a 2026 company on a 2019 checklist is how investors get hurt, so the checklist changed.
- Could a general model do this next year? If your product is a thin layer over something a large model already almost does, say how you stay ahead of it.
- How long would a competent team need to copy you? Measured in weeks or in years — and be specific about what makes the difference.
- What are you accumulating? Data, distribution, workflow lock-in, regulatory clearance. Something that gets harder to catch the longer you run.
- How much of the raise goes into building software? If most of the money is engineering that a small team plus AI tooling could now do far cheaper, that is a question about the plan, not about you.
Where rounds usually die
Rarely for a dramatic reason. Almost always for one of these.
- A market size taken from an industry report with no line connecting it to what you sell.
- A list of features where a defensibility argument should be.
- A use of funds that does not add up to the milestone being promised.
- A team with no visible reason to be the ones who win this particular market.
- Forecasts with no stated assumptions, which makes the whole financial section unusable.
- No answer at all to the AI question — which the reader then answers for you.
Three real rounds, re-scored with the same yardstick
Publicly reported rounds, reconstructed from what the founders had in hand at the time. Read them as report walkthroughs, not legends.
After living on roughly $20,000 from Y Combinator and funding themselves by selling novelty cereal boxes, the founders raised about $600,000 led by Sequoia Capital at a reported pre-money valuation around $2.4 million. Before that, several well-known investors had passed — some of their rejection emails are public.
Read through the scoring dimensions:
- Why this team: they had already survived a year nobody would fund, manufactured their own runway, and could show real bookings in New York. The evidence was behaviour, not claims — the strongest kind.
- Time to copy: the website was trivially copyable. The asset that was hard to copy was supply — real hosts in real homes — which compounded with every listing. Today this would be scored as a weak technical moat wrapped around a strong accumulating one.
- Use of funds: small round, one named job — prove the model works beyond a few cities. Nothing in the raise was open-ended.
- Next-round ceiling: at roughly $2.4 million pre-money, the next round only needed the company to prove the New York numbers travelled. Priced at ten times that with the same evidence, the round would likely have failed — as the rejection emails show nearly happened anyway.
The lesson that survives: the investors who passed were not wrong about the product. They were wrong about which asset was compounding. A structured read forces that question into the open.
Re-read in the AI era: the read shifts hard. The booking website — once the visible product — is now a weekend build with AI tooling, so a code moat scores near zero. What survives is the accumulated supply, reviews and trust, which no model can generate on demand. The AI-era version of the question is blunt: is your asset the software, or what the software has accumulated?
Tope Awotona had spent his savings and years on earlier ventures that failed. For Calendly he raised a reported seed of about $550,000 only after the scheduling product was live and spreading by word of mouth. The company stayed lean for years before a 2021 round reportedly valued it at $3 billion.
Read through the scoring dimensions:
- Evidence of pull, not a forecast: the round was priced against observable usage. Nothing in the material asked the investor to believe a projection.
- Capital efficiency: the spend went to a working product with visible adoption, so the use-of-funds question almost answered itself — the milestone was "more of what is already working".
- Distribution as the moat: every booking link sent the product to a stranger. That loop is exactly the kind of "what compounds" answer the AI-era questions look for, because a copied feature does not copy the loop.
- Team credibility: the founder's story included failure and persistence in the same domain. Under a structured read, that is documented evidence of staying power — not a soft narrative point.
The lesson: a small round raised on evidence beats a large round raised on ambition, and the score difference shows up in "evidence strength", not in any charisma dimension.
Re-read in the AI era: a scheduling feature on its own now scores weak — an AI assistant replicates it in an afternoon, and calendar agents are actively absorbing the category. What still scores strong is the distribution loop sitting in millions of inboxes. The updated read separates the feature (displaceable) from the installed loop (compounding) — and it asks every feature-product founder to name their loop or take the displacement flag.
Two brothers in their early twenties raised a reported $2 million seed from investors including Peter Thiel, for a product that was then little more than a few lines of code a developer could paste in.
Read through the scoring dimensions:
- Why now: developers could sell online but payments were still weeks of bank paperwork. The wedge was a real, dated change in behaviour — the strongest "why now" there is.
- Core asset: not the code — the regulatory and banking relationships underneath it, which take years and get stronger with volume. A pure-code reading would have scored the moat low and missed the company.
- Displacement question, inverted: Stripe is the rare case where new technology lowered everyone else's cost of entry more than theirs, because they owned the layer others had to build on. Worth remembering when a deck claims the opposite.
- Team: young, but with an unusual depth of understanding of the specific problem. "Relevant depth in this market" outscored seniority — as it should.
The lesson: what is hard to copy is rarely what is visible in the demo. If your defensibility is underneath the product, your material has to say so explicitly — a reader cannot score what is never stated.
Re-read in the AI era: AI cuts the cost of building payment front-ends even further — which strengthens whoever owns the regulated layer underneath and threatens whoever only owns a thin wrapper on top. The displacement question now has to be run in both directions on every software deal: does cheap code strengthen this company's position, or erode it? The answer is scored before any other dimension matters.
Numbers above are as publicly reported and rounded; treat them as orientation, not benchmarks. What matters is the shape of the read: the same handful of questions, answered by evidence that existed at the time. That is exactly what your report does to your material — which is why uploading the financials and the technical files alongside the deck changes the read so often.
- Code is no longer a moat on its own — AI writes it too cheaply. What compounds (supply, data, relationships, regulatory positions, trust) is what survives the read.
- Polished narratives are now free to produce, so evidence discipline matters more, not less: documents and observed behaviour outrank a well-written deck.
- Every deal now carries an explicit displacement question — would an AI tool or an AI-native incumbent absorb this within a year or two? Your report scores that question by name, for every project, instead of leaving it to chance.
How this maps to your scoring report
Every section above corresponds to something the report scores.
Each judgement in your report carries an evidence label: taken from a document, partially supported, a founder claim, or not covered. A low score attached to "founder claim" usually means the belief is fine and the proof is missing — that is a document to add, not a business to abandon.
The report also gives you the gaps in your material, the milestone the next round will expect, and the conditions that would prove the report itself wrong. Work the list, upload again, and the read changes.
Term you do not recognise? The glossary covers every one used in a report.
After the close, manage the relationship as carefully as the runway
Investors cannot help with a problem they learn about after the decision has already been made.
- Send the same short operating update every month. Comparable numbers build more trust than a newly polished deck.
- Share bad news when it becomes visible, not when you have made it presentable. Bring what you know, what you do not know and when you will know more.
- Make requests executable: name the person or profile, why the fit matters, the action you want and the date it is needed.
- Take a hard question seriously without surrendering the operating decision. Ask what evidence would change the investor's view, then decide whether the test is worth running.
- Use a Portfolio Health action list to improve the company, not to optimise the score. Pick one to three priorities with owners, dates and a signal that proves the concern wrong.
The full shared workflow — meeting cadence, roles, introductions, disagreements, AI-era reviews and copyable update templates — is in the Founder × Investor partnership guide.
A low score is a list of things to fix, not a verdict on you.
We are not here to sort founders into good and bad. Most first drafts are under-evidenced rather than unworkable, and the difference between the two is usually a few documents and one honest rewrite.
So the report tells you where the reasoning breaks and what would repair it. What you do with that is yours: nobody sees your material unless you decide they should.
Every company that survives is somebody's job.