Skip to content

Solo Devs

How to Sell When You Hate Selling (For Builders)

You can build the thing but freeze up when it is time to sell it. Here is why selling feels awful, why it is actually a service, and how to do it without turning into someone you would mute.

By the Does This Make Money Team

Published September 10, 2026·12 min read

beginner
Jump to a section

You can spend three weekends refactoring an auth flow nobody has asked for yet. You cannot send one message to a person who might pay you. If that sounds familiar, you are not lazy and you are not broken. You have just found the one part of building a business that feels genuinely uncomfortable, and you are doing what any reasonable person does with discomfort: avoiding it by doing something you are good at instead.

The problem is that the thing you are avoiding is the only thing that turns a project into a business. You can ship the cleanest codebase of your life and still make exactly zero dollars, because code does not find its own customers. So let us talk honestly about why selling feels awful, why most of that feeling is based on a wrong idea of what selling is, and what you can actually do about it without becoming a person you would mute.

Where does the money actually come from?

Here is the part builders skip. You cannot get money by building. Building creates the thing that gets sold. The money comes from a conversation, or a page, or an email that does the job a conversation would do. Something has to move a person from "I have a problem" to "I will pay you to fix it." That movement is the sale, and it is where every dollar enters.

Someone has a problem
        |
        v
They hear about your thing   <-- this step does not happen by itself
        |
        v
They understand it fixes THEIR problem   <-- this is selling
        |
        v
They decide it is worth the price
        |
        v
They pay
        |
        v
Revenue

Notice where the gap is. Most builders are excellent at the very top (there is a real problem) and confident at the very bottom (the product works). The two middle steps, "they hear about it" and "they understand it fixes their problem," are the entire job of selling, and they are exactly the steps that get skipped when you hide in the editor. No amount of quality in the box moves a person through those two steps. A human has to do that, at least at the start. For more on why this middle is where money actually appears, see where does online money come from.

How it actually works

Reframe the whole activity and the anxiety drops by half. You are not "selling." You are finding out whether someone has the problem you fixed, and if they do, telling them.

Think about the last time a tool genuinely saved you hours. If a friend was suffering through the exact problem that tool solved, would you feel gross telling them about it? No. You would feel like a jerk for staying quiet. That is the correct emotional model for selling your own thing. When you believe the product actually helps, staying silent is not humility. It is withholding a fix from someone who needs it.

The catch is the "when you believe it helps" part. A lot of sales anxiety is not really about selling. It is a quiet worry that the thing is not good enough, or that you would be overcharging, or that the person will see through you. That is worth listening to. If you do not believe your product helps, the fix is not a better pitch, it is a better product or a lower price or a narrower promise. Honest selling only feels bad when the thing behind it is not honest. When the thing is genuinely useful, telling people about it feels like doing them a favor, because it is one.

So the mechanics are:

  • You talk to people who plausibly have the problem.
  • You ask about the problem before you say a word about your solution.
  • If it turns out they have it and it hurts, you say "I built something for exactly this."
  • If they do not have it, you thank them and move on, and you have lost nothing.

That last point matters more than it looks. Half the fear of selling is the fear of rejection. But if you lead with questions instead of a pitch, most "no" answers are not rejections of you. They are just "I do not have that problem," which is information, not a wound.

A simple example with numbers

These numbers are made up to show the shape of the thing. They are not a promise or a typical result. Treat them as a diagram, not a forecast.

Say you built a small tool that turns messy CSV exports into clean, formatted reports, and you are charging a hypothetical $20 a month. You decide to have ten real conversations this week with people who work with spreadsheets all day. Not a blast to a thousand strangers. Ten actual humans you can reach: people in a community you are already in, former coworkers, folks who posted online asking about exactly this pain.

Out of ten conversations, maybe six of them genuinely have the messy-CSV problem. You did not pitch the other four, you just asked and they said "not really an issue for me," so you moved on. Of the six who have it, maybe two are annoyed enough to try a fix right now. One signs up.

One customer at $20 a month is not a business. But look at what ten conversations actually bought you: you confirmed six of ten people have the problem (that is huge, it means the problem is real), you heard the exact words they use to describe it (which you can now put on your landing page), and you learned why the two "maybe" people hesitated (probably your fault for explaining it badly, which is fixable). The single paying customer is almost a side effect. The information is the real return, and you only get it by talking to people. Once you have had enough of these, the pattern gets clearer, which is the whole idea behind founder-led sales and your first 100 conversations.

What you need

You need far less than the guru version implies. No funnel, no cold-calling script, no CRM, no "personal brand." At the start you need:

  • A product or service that actually solves a specific problem for a specific person. Specific matters. "Tool for developers" is nobody. "Turns CSV exports into clean reports for people who run monthly ops updates" is someone.
  • A short, plain way to say what it does and who it is for. If you cannot say it in one sentence without jargon, the person you are selling to cannot either.
  • A list of people or places where the problem shows up. Communities, forums, subreddits, old coworkers, people posting about the pain.
  • A willingness to ask questions and shut up while they answer.

Skills-wise, the one that matters is not persuasion. It is listening. The builders who get good at this fastest are the ones who treat a sales conversation like a bug report: they are trying to understand the other person's actual situation, not talk them into anything.

What it costs

Required: basically your time and a bit of nerve. Talking to people who already hang out where your problem lives costs nothing but the minutes. This is why founder-led selling is the cheapest possible way to start.

Optional: a simple landing page so people have somewhere to look after you talk to them. A way to take payment (a payment link is enough at the start). A notes doc where you paste the exact phrases people use, because those phrases become your marketing copy for free.

Nice to have, later: email tooling, scheduling links, a real site, analytics. None of it matters until you have proven a human will pay. Do not let "I need to set up my stack first" become the newest, most sophisticated way to avoid the conversation. Buying tools feels like progress and requires zero courage, which is exactly why it is such a comfortable trap.

If you want the fuller picture of how getting the product in front of people beats polishing it in private, distribution beats product makes that case directly.

How long it takes

Longer than you want and faster than you fear. The first conversation is the hardest by a wide margin, because your brain has built it into a much bigger event than it is. After five or ten, the fear does not vanish but it shrinks to a manageable size, the way it does with public speaking or code review. It becomes routine.

What actually controls the speed is how many people with the real problem you can reach, and how clearly you can describe what you do. If you are talking to the wrong people, no amount of conversations helps. If you are talking to the right people but explaining it badly, you will feel the confusion in every call, and you can fix it by the next one. Both of those improve with reps, not with more time spent building.

There is no honest timeline like "first customer in seven days." Anyone promising that is selling you the fantasy you are trying to escape. What is true: the sooner you start the conversations, the sooner you get the information, and the information is what makes the next attempt work.

What beginners usually get wrong

They pitch instead of ask. The instinct is to open with "here is my amazing product." The move is to open with "how do you currently handle X?" Let them describe the problem in their words. Then, and only then, mention that you built something for it. A question is disarming. A pitch triggers the same defensive reflex in them that selling triggers in you.

They talk to strangers before they talk to warm people. Cold DMs to people who never asked are the most anxiety-producing form of outreach and one of the least effective when done cold. Start with people who already raised their hand: someone who posted a complaint about the exact problem, someone in a community asking for a tool like yours, a former colleague you know has this pain. Warm-ish conversations are easier on your nerves and more likely to go somewhere. When you do reach out to people who have not heard of you, do it like a human, which is the whole point of a cold DM that is not spam.

They read one "no" as a verdict on their worth. A person saying no usually means the timing is wrong, the problem is not theirs, or the price is off. It rarely means "you are a fraud." Builders take it personally because they built the thing, so a rejection of the thing feels like a rejection of them. Separate the two on purpose. You are running an experiment, and "no" is a data point, not a grade.

They wait until the product is perfect. There is always one more feature. Perfecting the product before anyone has seen it is the single most respectable way to avoid selling, because it looks like diligence. It is not. It is fear with a nice haircut. The reason so many capable people never make a dollar is not a bad product, it is that they never had the conversation. Why most beginners never make a sale is almost always a distribution problem, not a product one.

How I would start

If I had built something and felt sick at the thought of selling it, here is the sequence I would actually follow, smallest step first.

  1. Write one sentence: who it is for and what problem it kills. Say it out loud. If it needs jargon, rewrite it.
  2. Make a list of ten specific people or places where that problem clearly exists. Real names or real communities, not "developers on the internet."
  3. Pick the three warmest ones. People who already complained about this, or who I already know have the pain.
  4. Message those three like a person, not a pitch. Ask how they currently deal with the problem. Do not mention my product in the first message at all.
  5. In the conversations that open up, listen for the pain. If it is there and it hurts, say "I actually built something for this, want to see it?" If they say yes, show them. If not, thank them and move on.
  6. Write down the exact words they use for the problem. Those words are my future landing page and my future emails, handed to me for free.
  7. Repeat with the next batch. The fear shrinks with each one.

That is founder-led selling, and it is the most reliable way to get from zero to a handful of real customers. The full playbook for that first stretch is in get your first 10 customers, and there is a broader map of the whole early-money picture in how making money online works. If you want a single, concrete starting point, the first customers walkthrough lays out the first moves in order.

What I would not do

I would not buy a course that promises to make selling painless. It does not become painless. It becomes familiar, and familiar is enough.

I would not build a "funnel" or automate outreach before I had talked to a single human, because automation of a thing that does not work yet just produces failure faster.

I would not copy the aggressive templates. The fake scarcity, the "quick question" bait-and-switch, the flattery-then-pitch. They work on almost nobody who is paying attention, and they make you into the exact thing that made you hate selling in the first place. You do not have to choose between being effective and being decent. The decent version outperforms the sleazy version with the kind of customer you actually want.

And I would not treat one bad conversation as proof I am not cut out for this. Everyone's first attempts are stiff. That is not a signal to quit. It is the cost of the reps that make the later ones easy.

The close

Selling is not the opposite of building. It is the second half of it. You already did the hard, uncertain part: you made something that did not exist before. Telling people about it is smaller than that, and less risky, and it is the only thing standing between "cool project" and "actual business."

You do not have to become loud, pushy, or fake. You have to be willing to ask a few people about their problem and, when the problem is real, say "I built something for that." If the thing genuinely helps, that is not a favor you are asking for. It is a favor you are doing. The people with the problem are out there right now, working around it, wishing someone had a fix. You have the fix. Go tell them.

Free playbook

Get your first 10 customers

This guide is one piece of the free First 10 Customers Playbook: the distribution game plan for builders who can ship but cannot seem to sell. Get it, plus the follow-up breakdowns, by email.

You’ll get a confirmation email first. Click confirm and the playbook is yours. You’ll also get our breakdowns for builders on getting customers. Unsubscribe anytime.