Should I raise VC at all — and what problems won't the money solve?

You are asking whether to take money, and the better question is what the money is for. We invest for a living, and we have watched a round solve some problems completely and leave the most important one exactly where it was. What follows is the honest sort.

Money does not answer the demand question.

You will be told to deploy the round into sales and marketing, and a sales organization cannot discover whether anyone wants the product. It can only scale demand that already exists. Hiring it early turns a search problem into a management problem and burns the runway the search needed, and with several unproven things moving at once, a miss cannot be attributed to anything, so the diagnosis defaults to slow execution rather than to demand that never existed.

The fastest lever for a company that has not found its fit is not more selling. It is less. We have watched companies cut their sales organization and their marketing spend, extend their runway dramatically, and find that the revenue line did not get materially worse. That absence of any effect is the cleanest evidence available about whether the demand ever existed. Run the cut as a deliberate experiment early rather than as a surrender late, and it becomes the most informative action you have.

Money does not fix the other things either. It will not resolve a founding team that disagrees about who decides, and it will not clarify roles nobody has written down. What money does have is inertia — it finds its own way to spend itself. A plan appears, the plan has headcount in it, and the headcount arrives before the question is answered. Do not raise your way out of a problem. Raise to accelerate one you have already solved.

What the money buys.

You raise to buy time on the problems that do not go away with better tools: finding the buyer, building the team, earning trust. In security those are set by the buyer's clock. The security review of a security vendor, the proof of concept on production data, and the budget cycle each take their own time, and no amount of building shortens them. A round buys the sales cycles that have to close before the business proves itself. If your buyer's cycle is short and the product is paid for on the first invoice, you may not need it.

A round is an obligation, not a win.

You do not win by closing a round. You take on an obligation: a mortgage against a future you cannot see yet, and it comes due. Everyone around you will treat the close as the finish line — the press does, your competitors' announcements do, and your team will want to celebrate. Celebrate, then be clear with yourself that the money arrived as a debt, not a trophy. The price is a milestone you agreed to hit. The round is a clock. The board is an evaluation of whether you can run a company, and it starts recording at the first meeting. The cut you resist when the plan misses is always smaller than the cut you eventually take, and a raise turns a search into a plan on the day it closes, so a founder who is still searching finds the plan in the way.

Size the obligation to the risk you are actually willing to carry, rather than to the largest number on offer. A company can do well raising a great deal at once, and a company can do well raising smaller checks across more rounds; the calibration is to your market, your team, your own experience, and how steep a cliff you want to stand on. There is a wide middle between bootstrapping and taking everything anyone will give you, and almost nobody describes it to you.

The honest reasons to stay small.

You stay small, without apology, when the first product is mostly services and the margin is in the work. You stay small when the buyer pays quickly and each invoice funds the next one. You stay small when the category is one the platforms will absorb, because a small profitable company is worth more than a funded one that got noticed. And you stay small when you want to own the outcome more than you want to enlarge it. None of those is a failure. We back some companies and tell others not to raise, and the second conversation is often the better one for the founder.

Know the odds you are choosing, though. Bootstrapped founders get written about because it worked and because it is rare, and the ones for whom it did not work are not written about at all. If you are building where a competitor's capital buys deployment you cannot match, staying small is a decision with a cost, not a way of avoiding one.

The honest reasons to raise.

You raise when the buyer's sales cycle is a year and you cannot fund a year of cycles on revenue. You raise when the product must run inline and be as reliable as a phone carrier before anyone will pay for it. You raise when funded competitors will arrive two quarters after the category gets named, and the accounts you deploy before then are your only defense. And you raise when the team you need cannot be hired on revenue. Then you raise enough to be wrong for two quarters, and you take the lower clean price.

If you raise, know what you are selling.

You are selling a milestone along with the equity. The SAFEs all convert on one day, the bridge round is the normal outcome between a seed and a priced round, and the structure you accept in order to close fast is a price cut with interest. Read all of that before you sign, and treat the cap as the bar for your next round rather than as a prize.

Plan the deployment before you take the money.

You write down how the capital gets spent and over what period, before it lands. The plan will be wrong — probably very wrong — and that is not the point of writing it. It puts you in the right frame of mind about someone else's money, and an investor reading a founder who has thought carefully about deployment is reading an operator, which is most of what they are trying to determine.

Plan eighteen to thirty-six months and add a cushion. Things take longer than the plan says, in almost every case, which means you spend more getting to the point where the next round is raisable. Plan for that rather than discovering it. And know the asymmetry: you can step on the gas and raise burn later, at any time, in a week. You cannot undo it.

The test.

You write two lists before you take a meeting. The three problems the money will solve, and the three it will not. If the demand question is on the second list, do not raise yet. Raise to accelerate, and only once three things are true: the mission is clear, the team is unified behind it, and the market you are addressing is real. Find the buyer who will pay first, then raise for the sales cycles that follow. The money is for the problem. It cannot choose the problem for you.