The company is moving faster than I am

Vinci didn't exist 30 days ago.

That sentence should feel more significant to me than it does.

In one month, an idea became a company with customers, infrastructure, a team, real expenses, and people outside the company expecting it to work tomorrow.

From the outside, that probably looks fast.

From inside, almost none of it feels finished.

When I look at what happened, I don't naturally see what we built.

I see the things that are late, the decisions we haven't made, the mistakes we need to correct, and everything that could already be better.

The company is moving faster than I can emotionally process it.

I'm starting to think this may be one of the defining realities of building a company now.

Thirty days is a long time now

A month used to feel short.

It was enough time to make progress on something.

Maybe launch a feature, sign a customer, or reach a decision that had been moving slowly through a team.

Now a month feels like an era.

Something we believed four weeks ago can already feel naive.

A decision from last week can belong to a version of the company that no longer exists.

A plan made on Monday can be overtaken by Wednesday - not because the plan was careless, but because the available information changed.

AI accelerated the work itself.

A small team can research, design, build, test, write, and revise at a pace that would have required far more people a few years ago.

But it also accelerated the number of decisions.

Every capability creates another possible direction.

Every hour saved creates room for another experiment.

Every experiment creates evidence, and every piece of evidence asks you to update your view.

The bottleneck moves from producing work to deciding what deserves to exist.

That sounds like a good problem.

It's still a problem.

The founder never sees the announcement

Other people see what shipped.

The founder sees every version that almost shipped instead.

I remember the arguments, the failed attempts, the uncomfortable tradeoffs, the things we cut, and the night when the answer was still unclear.

By the time something becomes public, I've usually lived with it long enough that it already feels old.

The announcement may be someone else's first encounter with it.

For me, it's the end of a decision I've already moved past.

This creates a strange distance from your own progress.

People congratulate you for something, and your first instinct is to explain why it isn't as impressive as it looks.

Sometimes that's honesty.

Sometimes it's an inability to let anything count.

Those are not the same thing, and I don't always know which one I'm doing.

I've spent much of the last month feeling behind while moving faster than I ever have.

That's a dangerous combination.

It can produce extraordinary output.

It can also make dissatisfaction feel like discipline.

Speed can imitate conviction

Moving quickly feels decisive.

You choose. You ship. You get evidence. You adjust.

There's something clean about it, especially compared with companies that can spend months discussing a decision that should take a day.

But movement and conviction are not the same thing.

Sometimes you move fast because the answer is clear.

Sometimes you move fast because sitting still would force you to admit that it isn't.

At startup speed, action can become a way of avoiding reflection.

The calendar stays full. The company keeps producing.

There's always another urgent problem available when you don't want to examine the larger one.

What are we actually trying to become?

Which parts of the current direction are conviction, and which parts are momentum?

If nobody saw what we shipped this week, would we still believe it was the right thing to build?

These questions don't produce a dashboard.

They don't make a satisfying progress update.

They can feel indulgent when everything else is moving.

They're also the questions that determine whether speed is taking you somewhere or merely keeping you occupied.

I don't want to slow down

The obvious conclusion would be that I should slow down.

I don't think that's the right answer.

This is a rare period when the technology, the market, and the shape of companies themselves are all changing at once.

Small teams have opportunities that didn't exist a year ago.

Moving slowly doesn't make a decision more thoughtful by default.

Often it just delays the moment when reality can correct you.

Speed is one of our real advantages.

I want to keep it.

But speed can't become the company's only value, because speed doesn't tell you what deserves to remain stable.

Tactics should be allowed to change in a day.

Principles should not.

A product can be replaced. A plan can be abandoned.

An assumption should die as soon as the evidence does.

But the standard for telling the truth can't depend on the week.

How we treat people can't be rewritten every time the company is under pressure.

The reason we're building can't simply become whatever justifies the thing already in motion.

The faster the outer layer changes, the more clearly the inner layer has to be understood.

I don't think I've fully built that inner layer yet.

That's the more honest answer.

The company assumes I'm ready

Companies don't wait for their founders to feel prepared.

A decision arrives, and someone has to make it.

An expense becomes real. A person depends on your judgment.

Something breaks publicly.

A choice that felt theoretical yesterday suddenly has consequences.

The company simply assumes you're the person capable of carrying it.

Then you either become that person or discover where you're not yet ready.

I've changed more in the past seven months than in several years before them.

Some of that change was intentional.

A lot of it was demanded by situations I had never encountered before.

The strange part is that personal change is difficult to perceive while it's happening.

Internally, you still feel like the same person.

You remember every hesitation and every mistake.

Other people may see the decisions, but you can still see the uncertainty behind them.

Maybe that's healthy.

The dangerous founder is probably not the one who occasionally wonders whether he's ready.

It's the one who stops wondering.

But permanent doubt isn't humility either.

Eventually you have to accept that the responsibility is already yours, whether or not your identity has caught up with it.

You don't become ready and then take on the work.

The work is what makes you ready.

What I need to protect

I don't have an elegant system for processing all of this.

I'm not going to pretend I meditate for an hour every morning, maintain a perfect journal, or end each week with complete clarity.

Most weeks still end with more open questions than they began with.

But I think I need to protect enough distance to ask three things regularly:

What changed?

What remains true?

What am I doing only because it's already in motion?

The first question keeps me adaptable.

The second keeps me from becoming purely reactive.

The third is probably the hardest.

Founders talk a lot about starting things and not enough about the courage required to stop them.

Motion develops its own constituency.

A project has sunk cost. An announcement created expectations.

An idea became part of how you describe yourself.

Ending the wrong thing can feel more frightening than beginning the right one.

At high speed, that distinction becomes even more important.

Otherwise the company accumulates every earlier version of itself until movement becomes weight.

There is no caught up

I kept assuming there would be a point when the last month made sense.

After the next launch. After the infrastructure was stable.

After the team settled into a rhythm.

After we had enough information to know what the company really was.

That point hasn't arrived.

I'm beginning to understand that it probably never will.

If the company works, the decisions will become larger.

More people will depend on them.

The distance between what I know how to do and what the company requires will keep reopening.

That's not a temporary problem on the way to becoming a founder.

That's the job.

The company is moving faster than I am.

For now, I think that's okay.

A company should stretch the person building it.

The danger is not that I sometimes feel behind it.

The danger would be moving so quickly that I stop noticing the distance - or stop becoming the person capable of closing it.

My job is not to feel caught up.

There is no caught up.

My job is to keep enough of myself outside the motion that I can still tell where it should go.