sethserver.com Subscribe
A star being pulled in by a black hole. The star is bright yellow with a happy face, and the background is a cosmic scene with vibrant colors like purple and blue. The black hole has thick black outlines and is surrounded by colorful stars and planets. The overall style is whimsical and surreal, with a minimalist approach to the characters.

Startup Momentum: Building Stable Systems That Don't Rely on Motivation | Startup Strategy & Product Development

By Seth Black • Updated: September 17, 2026

Startups · 4 min read

Like this kind of writing? Get one email a week with notes on startups, AI, and the occasional strong opinion about Python: subscribe to the newsletter.

Startups are chaotic. Not the fun kind. More like the "our roadmap is a Ouija board and the CEO just asked if we've considered blockchain" kind.

I've been thinking about that while reading about orbital mechanics and black holes. Earth doesn't stay in orbit because it believes in itself or has a vision board. It stays in orbit because it has momentum, and the system is stable enough that random noise doesn't knock it into the sun.

Startups don't get that for free. You build it, or you drift.

Stable systems don't rely on motivation

I once joined a hardware startup right after their Kickstarter blew up. The genius programmer who built the prototype took the fame, landed at Google, and disappeared. That left a crater in the software team. I walked into a codebase that looked like someone had coded it while running from a building fire.

Hardware is expensive in ways software people don't feel in their bones yet. Parts lead times are real. Contract manufacturing negotiations can eat a year. And pre-ordering parts feels smart until you learn what "revision B" means. You can't "pivot to SaaS" like you're changing shirts. The hardware still exists. The customers still want the thing they paid for. The factory still wants money.

Stability matters more than cleverness. Not as a value statement. As a survival constraint.

Death flails vs. actual pivots

Real pivots happen. Sometimes you find a better customer, a clearer problem, a simpler product.

A death flail is different. It's the company thrashing from "medical billing SaaS" to "daycare video conferencing" because one prospect asked a question and the CEO got excited. It looks like motion. It's mostly panic.

Here's what it looks like up close:

Momentum is mass × velocity

Physics gives you a clean formula:

momentum = mass × velocity

Business isn't physics, but the shape still fits:

One email asking for feedback per month is basically nothing. That's not momentum. That's you yelling into a closet.

Ten to fifteen outreach emails per day, five days a week, for six months is different. Now you have a system. You get replies. You see patterns. You start hearing the same pain points in the same words. You can build around that.

Keep it going and distractions stop being fatal. They're just annoying.

Four places I keep screwing up momentum

Internal communication

I've worked for a CEO with a full-on cult of personality. People did things they knew were wrong because they liked the guy. I ask too many questions. That makes me a terrible cult member.

The fix is stupidly simple:

Not once. Constantly. Predictably. If you only communicate during emergencies, your team learns that silence means danger. Then every ping feels like bad news.

I've messed this up plenty. I'll ship a bunch of code and forget that my team can't read git commits for reassurance that everything's fine.

Outbound communication

The internet is filling up with AI sludge. If you're building something real, you have to prove you're a person with a pulse and a point of view.

Post something. Prove you're human.

A process beats a heroic burst. Record a short video. Write up a customer problem you keep seeing. Share what broke and what you changed. Keep it small enough that you'll do it again.

Inbound communication

Customer feedback is how you know if you're building the right thing.

Customers aren't always right. They're still useful because they'll tell you what they thought they were buying. That gap between expectation and reality will kill you.

Make feedback normal:

Once that loop is moving, other things get easier. Internal updates stop being vibes. Outbound posts stop being empty. You have actual material.

Product stability

This is the stable-orbit part.

Know your core value proposition. Know your ideal customer. Write it down like you mean it. If you can't say who the product is for without adding "and also," you're already drifting.

Product stability is what lets you say no:

Building momentum feels like doing nothing

The boring part is the point. Stability looks like repetition. It looks like sending the emails even when you don't feel like it. It looks like posting the update even when it's not a big announcement. It looks like asking for feedback even when you're pretty sure you won't like the answer.

Momentum is what keeps the system moving even when life interrupts and things fall apart.

-Sethers

Share this post
Newsletter

One email, once a week.

Notes on databases, systems, and the occasional strong opinion about Python. No spam, unsubscribe anytime.

Seth Black
Written by

Seth Black

Engineer and founder based in Texas. Writes about databases, AI, and running things in production. Embeds in small teams as lead engineer.

More from Startups

View all →
Startups

What Actually Goes in a Consulting Contract

Sep 17, 2026
Startups

Productizing a Service: From Hours to Licenses

Jul 26, 2026
Startups

The MVP That Is Not a Product

Jul 11, 2026