The founder who can't stop moving
Moving fast is the signal. It is also the blindfold.
There is a quality investors look for above almost everything else when they back a founder.
Paul Graham, cofounder of prestigious Y Combinator, called it relentlessly resourceful. Not just smart. Not just hardworking. The specific combination of someone who doesn’t stop and someone who always finds another way. Capital scarce — they find a path. Product breaks — they redesign. First ten customers say no — the fighter spirit goes up, not down.
It is rare. And it is genuinely what gets companies through the early phase. Without it, most never start. The first few rejections become the last few.
So investors screen for it. Explicitly and instinctively. When they back a founder, they are in large part betting on this quality holding.
They are right to.
What nobody has named clearly is what happens to that same quality when the environment changes - and the founder doesn’t.
After a raise, the problems look familiar on the surface. Something isn’t working. Find the cause. Fix it. Move forward.
But the nature of the problem has quietly shifted.
Before you had customers, most of what was broken lived in the parts you could design and control - the product, the process, the technology. You could reach it. Fix it. Ship it.
After you have customers operating inside their own organizations, more of what is actually broken lives somewhere you can’t touch directly. Inside other people’s incentive structures. Inside habits built over years. Inside decisions other people make based on what is good for them - not what is good for your product.
The relentlessly resourceful founder hears this and starts designing a solution. That instinct is not wrong. It is exactly what built the company.
But it has a blind spot. And the blind spot is predictable.
The activity itself becomes the evidence that the right things are happening.
Look at a portfolio of post-raise companies right now. Really look.
The team is growing. The product is shipping. New markets are being entered. The founder is genuinely busy, not performing it. There are new fires every week. Some get handled. The board updates show new activities.
And underneath all of it, the questions that actually determine whether this is a business have never been cleanly answered. Who is getting enough value from this that they will keep paying - and tell others? Can that value be delivered consistently without the founder personally holding it together? Are the unit economics moving in the right direction with each new transaction, or is growth making the underlying math worse?
Not because the founders are avoiding these questions. Because they never stand still long enough to see them.
The relentlessly resourceful founder has an innate preference for moving. It is not recklessness. It is identity. Standing still and questioning the foundation goes against everything they are wired to do. There is always another fire. Another piece of content to write. Another event to speak at. Another reason this quarter is not the right one to slow down. And always a way to read the current numbers as confirmation.
So the questions that need to be asked get carried forward. One quarter. Then another.
This is when failure gets locked in.
Not in the dramatic moment. Not when the company hits a wall. In the quiet period when everything seems to be working. When the team is hustling and some metrics are moving and the founder is doing exactly what they were backed to do.
The decisions being made in this period are expensive. Not because they are wrong. Because by the time it becomes clear they were built on untested ground, reversing them costs far more than testing them would have.
I lived this at Tørn. We were solving the right problems, with the right amount of energy. We were just solving them at the level we could control - the product, the process, the system - while the actual problem sat somewhere else entirely.
We had a store manager who used our platform well in the beginning. Then went quiet. When we finally reached him, he told us the truth: selling surplus at cost price had pushed his monthly contribution margin negative — the number his bonus was calculated on. That triggered an approval requirement from his manager he hadn’t had before.
We fixed the system. We escalated, got the rules changed, did everything correctly.
He never became active again.
Because by then something else had happened. He had learned that our platform meant friction, risk, and an awkward conversation with his boss. No system fix removes that memory. Trust moves on a completely different timescale than software.
That sequence - understand the problem, design a fix, execute it well, nothing changes — happened not once. It happened across stores, across partners, across markets.
We were moving the whole time.
So look around.
At the companies raising right now. At the ones in your portfolio, on your team, or that you advise. At the ones where the founder is building fast and the numbers are going up and everything from the outside looks like it’s working.
Ask the questions that aren’t being asked.
Who has to change their behavior for this to work at scale? What do they gain from doing it? What do they risk? Who measures them, and on what?
If the answers are clean and specific, good. Build faster.
If the answers are vague - if the honest response is “users will see the value once they try it” or “adoption will come when we have more features” - that vagueness is the most important thing in that company right now.
More important than the next hire. More important than the next feature. More important than the next raise.
Because capital doesn’t fix incentive misalignment. It funds it.
And by the time the activity stops, the damage is already done.
I’m writing a book about this. It’s called -The avoidable startup failure. If you want to know when it’s ready: anjali.no/book