Seed is the new Series A, and what that means if you are raising pre-seed

Something has shifted in the way investors assess early-stage startups, and the shift is structural rather than marginal. Most pre-seed founders are still preparing for the stage as it was defined a few years ago.

Here is what happened. Building software has become dramatically cheaper. What used to take eighteen months and a sizeable engineering team can now be prototyped in weeks. That compression has shortened the distance from idea to demonstrable product, which means investors at the seed stage are now looking at companies that, two or three years ago, would have been Series A candidates. More polish, more evidence, more traction.

The result is that seed-stage expectations have crept backward. Investors who once backed a credible founder with a credible thesis now want evidence of product-market fit. Early signals. Real conversations with real customers. The question has changed from “do you understand the problem?” to “can you show that someone has this problem badly enough to act on it?”

Pre-seed founders are caught in the middle. They are raising at a stage that still looks like the old seed, early and unproven and figuring it out, while being assessed against criteria that belong one stage up.

What this looks like in practice

This plays out in almost every founder conversation we have at DM & Associates.

A founder came to us recently building an edtech product. Thoughtful person, genuine conviction. Their go-to-market logic rested on one number: the addressable market was large, so even 1% penetration would be significant. The product was built and the pitch was ready. What was missing was any honest interrogation of whether the market needed what they were building, and whether the specific segment they were targeting had a problem urgent enough to pay to solve.

Learning habits have shifted. The way people consume education today is different in structure from five years ago. A 1% assumption built on aggregate market size ignores whether your product lands in the part of the market that is actually moving, actually searching and actually willing to pay. That is not a pitch problem. It is a validation problem, and it surfaces in front of investors in ways founders rarely anticipate.

A second conversation, the same week, in a different domain. A deep tech founder in defence technology, with genuinely impressive engineering, came in to demonstrate what they had built. The technology was real and the intellectual property was defensible. What did not exist was any mapped market. The approach was research-first: build the capability, then look for where it fits, and hope to find a problem worth monetising.

That is a research project with commercial aspirations rather than a startup. Investors at seed are not funding the search for a problem. They are funding early execution against a problem already found.

Why good technology is not enough

The clearest case we return to is a client building end-to-end infrastructure for EV fast-charging. The technology was well engineered. The market thesis, that EVs would proliferate and charging infrastructure would be needed, was correct in aggregate. What the team had not validated was the specific behaviour of the customer they were building for.

People who own EVs in cities largely charge them at home, overnight, at low speed. Fast chargers solve a real problem, but a narrower one: a highway problem, a long-distance problem. At the stage and scale this company was operating at, urban fast-charging infrastructure was not where the behaviour was. The market was real and the product was real. The fit was not.

The failure was not technical. It was that a foundational question, whether the target customer experiences the problem urgently enough to pay for this solution, was never rigorously answered before significant capital and time went in.

Validate before you build

This is what we tell every pre-seed founder. Before the product, before the pitch, before approaching a single investor, talk to the segment you think you are serving. Not to validate the solution, but to understand whether the problem you think you are solving is the problem they are actually experiencing.

Market validation is underrated because it feels like a delay. It is not. It is the work that turns a technology into a business, and it is increasingly what separates founders who have done the thinking from those who have only done the building.

Three questions to ask before you raise

Come back to these before every investor conversation.

1. Can you name the specific person who has this problem? Not a demographic. Not a market segment. A person: their role, their industry, the moment in their week when this problem costs them something real. If you cannot name them, the market is not validated yet.

2. Have you watched someone try to solve this problem without your product? What do they do today? What workaround are they living with? A customer who has built a workaround has a real problem. A customer who has not noticed the problem is not your early adopter.

3. Would they pay for the solution before it is built? Not “would they be interested.” Interest is free. Payment, even a letter of intent or a paid pilot, is the signal that tells you the problem is urgent enough to act on. If they would not pay before it is built, ask why. The answer is your next validation task.

These are not investor questions. They are founder questions.

---

Seed used to be a bet on a founder’s conviction. Today, at the seed stage, investors want evidence of that conviction in the market rather than in the founder’s reasoning alone. Pre-seed founders need to meet that bar earlier than the round itself requires.

Founders who understand this tend to build better companies, because they are solving real problems for identifiable people rather than building toward a market they have imagined.