Do the Things That Don’t Scale (Yet)
Momentum before scale
There’s a version of the startup story people like to believe.
Build something great. Put it online. Let the market do the rest.
It sounds efficient. It rarely happens.
Early momentum is not discovered. It is forced into existence.
Go get them
At the beginning, distribution is manual.
Not metaphorically. Literally.
You talk to people. You walk them through it. You sit with them while they use it. Sometimes you do the work for them just to get them through the first experience.
It feels small. It isn’t.
The difference between zero and something is almost always created this way.
The part most founders avoid
There are two reasons this doesn’t happen as often as it should.
It’s uncomfortable. It doesn’t look impressive.
Ten customers in a week feels trivial until you repeat it. Then it isn’t.
Compounding starts long before it looks like growth.
Fragility is the point
Early-stage startups are fragile by default.
That fragility gets treated like a problem to fix. It’s not.
It’s a signal.
You are close enough to the edge that your actions matter immediately. A single customer changes the trajectory. A missed follow-up does too.
That’s not something to smooth over. That’s something to use.
Over-deliver while it’s possible
Your first users should feel the difference.
Not in a polished way. In a personal one.
You notice things. You respond quickly. You adjust based on what they say, sometimes in real time.
It won’t scale.
That’s fine. It’s not supposed to.
What you’re building here is not just usage. It’s expectation.
Start smaller than you think
Broad markets dilute effort early.
Narrow ones concentrate it.
If adoption can happen quickly inside a small group, you create density. That density turns into momentum. Momentum makes expansion easier later.
Trying to be everywhere usually means you’re nowhere.
Build it manually first
Automation comes later.
In the beginning, you can fake the system behind the scenes if needed. You can fill in the gaps yourself. You can deliver the outcome before the infrastructure exists.
That does two things.
You move faster. You learn what actually matters.
Most of that learning is lost if you skip straight to scale.
The launch doesn’t matter
The idea of a perfect launch is mostly fiction.
Attention spikes. Then it disappears.
What matters is what happens after someone tries the product once.
If the first fifty people care, you have something to build on.
If they don’t, no amount of coverage fixes it.
Partnerships can wait
Early partnerships look strategic. They usually aren’t.
They move slowly. They depend on someone else’s priorities. They create the illusion of progress without much actual movement.
Direct contact with users teaches you more, faster.
Think in two tracks
There’s the product.
Then there’s everything you’re willing to do to get it into someone’s hands.
Those two things should be designed together.
If you rely on passive growth early, that becomes your habit. If you push for every customer, that does too.
What this actually is
The work that doesn’t scale isn’t a phase you graduate from.
It’s where the company learns how to exist.
The habits you build here tend to stay.
So do the expectations you set.
What holds
Most startups don’t stall because they lacked a clever idea.
They stall because nothing forced the first layer of reality into place.
The early work feels inefficient.
It is.
It’s also the only thing that works.
Subscribe to Amid the Noise
Amid the Noise is an ongoing body of work on signal, systems, governance, AI, and the structures that shape human judgment under pressure.
Subscribe to receive new essays as they are published.