Skills / Raising the round / What a VC reads in you

I have no numbers yet — what are investors actually judging?

With no revenue to examine, everything else becomes the evidence — including how you answer this.

vc-red-flags

SKILL.md · 1,276 words

Verified Sept 2026

Download the folder
What your agent reads.
name
vc-red-flags
description
What investors are actually reading in a seed or pre-seed founder who has no numbers yet, and the ordinary things that quietly move a deal down the pile. Covers why a company with no results gets judged on everything except results, the questions a partnership asks about a founder behind closed doors, preparation and knowing your own business cold, holding an opinion under pressure, keeping an operating model and offering it before it is asked for, the cap table a seed company should have, and why anything unusual outside the technology, the team and the market costs attention the deal needs. Use when a founder is preparing to raise for the first time, is getting second meetings that go nowhere, is asked for a model or a cap table and does not have one ready, or is wondering what a partnership discusses after the meeting ends. Not for whom to target (who-leads-cyber-seed), sizing the round (cyber-seed-benchmarks), how the meeting itself is run (vc-meetings), or reading the paper (reading-a-term-sheet).
title
What a VC reads in you
question
I have no numbers yet — what are investors actually judging?
subtitle
With no revenue to examine, everything else becomes the evidence — including how you answer this.
summary
You have no results at this stage, so investors read everything else, and they are trying to place you against every founder they have watched succeed and fail. Know your own business cold, hold an opinion under pressure, keep an operating model and offer it, and make everything outside your technology, your team and your market as ordinary as possible.
group
raise
verified
2026-09-09
order
20

1017 / 1024 characters

This is the top of the SKILL.md file, exactly as it downloads. Your agent reads the description field to decide when to load this skill. The rest of this page is for you.

You have no numbers, and that is the whole situation. Unless you have done this before and it worked, there is no revenue to examine, no retention curve, and often no business yet. So the people across the table read everything else, and we are among them: this is what we are doing in the meeting, and it is what we are doing after it.

With no results, everything else becomes the evidence.

You are being scouted the way athletes were scouted before anyone measured anything that mattered. In Moneyball the old scouts assess a player on his swing, his confidence, his jaw, the way he carries himself — everything except whether he gets on base — because the numbers that would settle it are not in front of them.

That is the position an investor is in with a pre-seed company, and it is not laziness. There is genuinely nothing to measure yet. Building a company from nothing is among the hardest things a person can attempt, your investors have to believe you can do it, and no proof exists either way. What they have instead is pattern: they have done it themselves or watched hundreds of others try, and they have seen most of the ways it works and most of the ways it fails. They are trying to place you among those. Every part of the interaction that is not the numbers becomes the evidence, because it is the only evidence there is.

The questions being asked after you leave.

You will never hear the conversation your deal gets in a partner meeting, so it is worth knowing its shape. Who is this person. What is right with them, and what is wrong with them. Can they recruit people better than themselves, and will those people follow them. Are they difficult, and is it the useful kind. Are they impatient in a way that ships, or in a way that breaks things. Are they restless enough. Are they raising money to relax or to go at something. Can they raise the next round. Do they like the fight, and do they like to win. What actually motivates them.

None of that is written down anywhere, and all of it gets decided in ordinary interactions — how you answer a question you did not expect, how you talk about a co-founder, what you do when someone tells you that you are wrong. You are being read continuously and none of it is announced.

Know your own business cold.

You show up prepared, and preparation is the cheapest signal available to you. Know your numbers, whatever numbers you have. Know your market, including the parts that argue against you. Know what your competitors actually do rather than what your positioning says they do. Be able to answer where the money goes and what happens if a plan slips by two quarters.

A founder who has to look something up about their own company has said something, and it is not about the spreadsheet. The energy matters too, and it is not performance: a founder who is visibly tired of their own story is telling you the story stopped being interesting to them before it reached you.

Hold the opinion under pressure.

You will be pushed on something you believe, and what happens next is most of what the meeting is for. Have a view, state it plainly, and defend it when someone comes at it. Change it when the argument is good, and say so out loud.

What fails is not being wrong. The old line is that he might be wrong, but he is not confused, and that is exactly the distinction being drawn. A founder who is wrong and clear has a thesis you can argue with, which means they will notice when the market disagrees. A founder who softens under pressure into agreeing with whoever spoke last has told you their conviction is a function of the room, and every market they enter will have a louder room than yours.

Keep an operating model, and offer it.

You keep a model, and you keep it before anyone asks. Most of it will be invented at the start, and that is fine — a model is not a forecast, it is your assumptions written down where they can be argued with. It gets tighter as the company gets real, and the discipline of maintaining it is most of its value.

Offer it to investors you actually want. Doing that is a signal of operating maturity that a company your age has usually not earned yet, which is precisely why it lands. Being asked for a model and not having one is the reverse signal, and it is a bad one: it says nobody has yet made you convert the vision into numbers, and you are about to spend someone else's money without that conversion.

Keep the cap table boring.

Your cap table at seed should be founders, an option pool, perhaps an advisor, perhaps one instrument. Not several share classes. Not a stack of instruments at different prices. No warrants and nothing unusual. Cap tables get complicated on their own as a company ages, so there is no reason to start there.

The same applies to how you explain the business. You should be able to say how a sale becomes cash in about ten seconds. If it takes longer than that, the complexity is either real, in which case it is a strategy problem rather than a pitch problem, or it is invented, in which case remove it.

Everything but the technology, the team and the market should be ordinary.

You want the argument to be about your thesis, and anything unusual elsewhere takes that argument's place. An investor sees a great many companies and has a finite amount of attention for each. An unusual structure, a jurisdiction nobody recognizes, an unresolved dispute, a founder arrangement that needs a diagram — each one is genuinely interesting, and each one consumes the attention your market was supposed to get. A deal that needs a week of unpicking before the real conversation starts is a deal that gets picked up later than one that does not.

That is not a judgment on you. It is arithmetic about attention, and it is the one part of the process you fully control. Be strange about your technology, your team and your market. Be entirely ordinary about everything else.

Working the question.

  1. Write down the questions in the second section and answer each one honestly about yourself. The ones you cannot answer are the ones being decided without you.
  2. Build the operating model before you take a meeting, assumptions included, and keep it current.
  3. Time yourself explaining how a sale becomes cash. If it runs past ten seconds, fix the explanation or fix the business.
  4. Read your own cap table as a stranger would. Anything that needs a paragraph of explanation is costing you attention.
  5. List everything about the company that is unusual outside the technology, the team and the market, and remove what you can before you start.
  6. Pick your hardest objection and practise answering it without softening. Being wrong is survivable. Being unclear is not.

Working with an agent.

Give your agent your deck, your model and your cap table. Ask it for the three questions a stranger would have to ask before they could understand the business, and how long each answer takes. Those three questions are what your first meeting will be spent on instead of your market.

Install the skill.

You are reading the skill itself — this page and the download are the same files. Unzip it into ~/.claude/skills/ (or a project’s .claude/skills/) and Claude Code loads it when the question comes up; so does any agent that reads Agent Skills.

mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -sLO https://techoperators.com/skills/vc-red-flags.zip && unzip -oq vc-red-flags.zip && rm vc-red-flags.zip

vc-red-flags/SKILL.md

No terminal? Download vc-red-flags.zip and drop into your assistant’s project files.

Kevin Skapinetz

Tell us what you see.

Whether you’re thinking about starting a company, building one in stealth, or raising a round: send Kevin or Dan what you see on LinkedIn, in your words.