Writing — Operator Playbook

Selling Is Part of Building

November 14, 20265 min readBy Milan Cheeks

Bootstrapping taught me that selling is not a job after building. It is how a builder learns what is worth finishing.

Selling Is Part of Building

For a long time I treated selling as the part that came after the real work. Build the thing first, I told myself. Make it good. Then find the words for it. Then ask people to care. That order sounds clean. It also kept me comfortable, because building is where I feel most in control. A screen does not ask what something costs. A screen does not tell you no and leave you to sit with why.

Running my own companies ended that comfort. I founded SELF Labs, and I build Manifest Anything as a separate company from SELF Labs Inc. There is no large team standing between me and the people I hope to serve. If I do not explain the work clearly, nobody else will do it for me. Bootstrapping makes that lesson hard to avoid. Every week you spend building in silence is a week you chose without any evidence that anyone wanted the result.

The myth of build first and sell later

The myth says selling corrupts building. It says a pure builder should focus only on the product and let the product speak for itself. I understand the appeal. But a product cannot speak for itself to people who never see it, and it cannot answer the questions a real person brings to it. Only a conversation can do that.

Selling, done honestly, is not a performance laid on top of the work. It is a test of whether the work makes sense outside my own head. Inside my head, every feature has a reason. A stranger does not carry that history. If I cannot explain the value in plain words, the problem is not always the listener. Often the product is still carrying ideas that are clear to me and muddy to everyone else.

Selling is the moment a private conviction has to survive a public conversation.

What selling actually teaches

A good sales conversation teaches faster than a month of guessing. People tell you what they thought you built, which is often different from what you thought you built. They tell you which part made them lean in and which part made their eyes move on. They ask about price sooner than you expect, not because they are shallow, but because price is part of understanding whether a thing fits their life.

I learned to listen for the problem underneath the request. A person rarely wants a platform for its own sake. They want time back. They want a task to stop being painful. They want to create something they could not create before. With Manifest Anything, the point is that a player with an idea should be able to describe a game and begin making it. If a conversation pulls me back to that human point, it did its job.

Listen before you pitch

My rule now is simple. Ask first. Let the other person describe their situation in their own words before I describe mine. Their words become the test for my words. If my explanation does not connect to the problem they just named, I should not push harder. I should listen longer or admit the fit is not there.

That admission matters. A clear no can be a kindness. It saves the other person money and attention, and it saves me from shaping good work around the wrong need. Trust grows when people learn your yes means something because your no is real.

Charge a clear price and respect it

Bootstrapping also taught me that vague pricing is a form of hiding. If I will not state a price plainly, I am asking the other person to do the hard part for me. I offer consultations at $300 for 60 minutes. The number is public, the time is defined, and the person can decide without a maze. That clarity respects both sides. It also forces me to make the hour worth what I said it was worth.

Selling without pretending

I build in public because it keeps my selling close to the truth. When people can see work in progress, they can also see the gaps. I do not have to pretend a thing is finished when it is not. I can show what exists, say what is next, and let people judge the distance between the two. That record becomes the pitch, and it is stronger than any claim I could polish in private.

The practice I keep

Each week I try to put the work in front of people while it can still be shaped by what I hear. I explain it in plain language. I listen for confusion and I treat confusion as information, not as an insult. I state the price and the limits. I follow through on what I said I would do, and when I miss, I say so and repair it.

None of this is separate from building. It is building, done with other people in the room. The code matters. The systems matter, and as a systems architect I care about how the pieces fit. But a system that never meets a person stays a theory. Selling is how the theory earns the right to become real.

If you are a founder who loves the build and avoids the ask, try changing the order this week. Show one person the work before you feel ready. Explain it without hiding behind jargon. Name the price if there is one. Then listen more than you speak. What you hear will not just help you sell the thing. It will help you finish the right thing.

If you are planning an event and want a speaker who builds in public and talks plainly about what it takes to ship, I invite you to book me for a keynote via https://www.milancheeks.com/#contact

← All writing Book Milan →
The Newsletter

The frontier, in your inbox.

One email when a new essay drops — the Kardashev roadmap, AI-native building, and coexistence, written as it happens. No noise, unsubscribe anytime.

You're on the list.