If selling makes you cringe, you are probably picturing the wrong job. The version of sales you hate, the one where a guy in a quarter-zip talks fast and never lets you say no, is a bad fit for engineers anyway. It gets ignored, blocked, and roasted in Slack. What actually works with technical buyers is closer to a good code review. You look at the problem together, you find where it breaks, and sometimes the honest answer is that your thing does not fix it.
That is founder-led sales, and you are already better at it than any rep you could hire this year. You know the product cold. You know why the boring competitor is boring. You can answer the third follow-up question without checking with anyone. I have watched this play out inside more than 30 devtools companies, and the pattern is boringly consistent: the founder who treats sales as problem-solving closes the early deals the sales hire never could.
Why are founders the best early salespeople for a technical product?
Because the early sale is not a sale. It is a diagnosis.
An engineer evaluating your tool is running a background check the whole time. Does this person understand my stack? Can they tell me where their thing falls down? Will they waste my afternoon? A founder passes that check by accident, just by being competent. A rep who joined six weeks ago fails it, no matter how good the deck is, because the fourth technical question exposes them.
There is a second reason that matters more. Early on, you are not just closing deals, you are learning what the product is. Every objection is data. Every “we already tried something like this” is a lane you did not know existed. If you hand that to a salesperson before you understand it yourself, you outsource the most important learning in the company to someone paid to make the number, not to tell you the market hates your onboarding. Keep it. It is the cheapest research you will ever run.
Sell like you are trying to disqualify them
The single mindset shift that fixes founder-led sales: your goal on the call is to find out fast whether you can actually help. Not to win. To sort.
This feels backwards because it is the opposite of pitching. But engineers relax the instant they realize you are willing to tell them no. It signals you are not desperate, that you have other customers, and that when you do say yes it means something. Disqualifying also saves you from the worst outcome in early sales, which is not a lost deal. It is a bad-fit customer who signs, churns in ten weeks, files twelve support tickets, and tells three friends you did not work.
So open with the filter. Something like: “Before I show you anything, tell me what you are using now and where it annoys you. If we are not clearly better than that, I will say so and we can both go do something else.” You just made yourself the least threatening person they will talk to all week.
Run a real discovery conversation, not an interrogation
Discovery is where most founders either freeze or start pitching. Here is the whole move: get them describing their actual workflow in their own words, then shut up.
A few questions that do real work:
- “Walk me through the last time this problem actually bit you. What were you doing?”
- “What have you already tried, and why did it not stick?”
- “If this were solved tomorrow, what changes for you? Who else notices?”
- “What would have to be true for you to rip out what you have now?”
That last one does the most work of any question on the list. It surfaces the switching cost, the internal politics, and whether there is even budget, without you asking anything as clumsy as “do you have budget.”
Then the hard part. Count how long you talk versus how long they talk. If you are past a third of the airtime on a discovery call, you are pitching, not listening. The founders who struggle with sales are almost always over-talking because silence feels like failure. It is not. Silence is where the buyer tells you how to sell to them. Ask the question, then let it sit, even when it gets uncomfortable. Especially then.
I go deeper on how to hear what engineers are actually telling you in customer stories for engineers, because the same listening muscle that closes the deal is the one that gets you a usable case study later.
Be straight about where you do not fit
When your product is wrong for someone, tell them inside the first two calls. Out loud. “Honestly, for what you are describing, you would be fighting our tool. Go look at X, it is built for exactly this.”
Every founder I say this to worries they are giving away a deal. You are not. You are giving away a deal that was going to blow up anyway, and you are buying something more valuable: a person who now trusts every yes you give. Engineers talk. The founder who told someone “we are not right for you” gets referred to the person you are right for. I have seen a single honest no turn into three inbound intros over the following year.
This only works if you actually know your edges, which is a positioning problem before it is a sales problem. If you cannot say in one sentence who you are wrong for, fix that first. My take on positioning a technical product is the prerequisite for saying no cleanly.
How do I talk about price without flinching?
State the number, then stop talking. That is the entire skill.
The flinch is the tell. The second you hedge, soften, or start justifying before they have reacted, you have told the buyer the price is negotiable and possibly made up. So say it flat: “It is 2,000 a month for up to ten seats.” Then let the silence do its job. Do not fill it. Do not add “but we can work with you.” Let them respond.
When they push, and technical buyers will, do not defend the number. Anchor it to the pain you already surfaced in discovery. “You told me this is costing your team a day a week. This is priced against getting that day back.” You are not arguing about your cost structure. You are reminding them what the problem costs.
And if the honest answer is that they cannot afford you, say that too, and stay in touch. Half of “too expensive” is “too expensive right now.” A founder who did not grovel is the one they email when the budget shows up.
When do I hand this off to a first sales hire?
Not when you are sick of selling. When the motion is boring.
The signal is repeatability. You have run the same discovery conversation enough times that you can predict the objections, you know which questions separate a real buyer from a tire-kicker, and closing has stopped teaching you anything about the product or the market. That boredom is the green light. It means the sale has a shape a good rep can learn, because you already documented it by living it.
Hand off too early and you never learn the shape, so you hire a rep to run a process that does not exist yet and then wonder why they miss. Wait until it is boring, write down every objection and the line that answers it, and hire someone into a machine that already runs. Your first sales hire should be closing your worst deals in month two, because the good ones are the ones you already systematized.
The founders who get this right are usually the same ones who did their own early marketing before hiring for it, for the same reason. If that is where you are, the first devtools marketer covers the parallel version of this handoff.
You do not have to become a salesperson. You have to become someone who is genuinely useful to a stranger with a problem you understand better than they do, and who is honest enough to say when you cannot help. That is not a personality you fake. For most technical founders, it is the one you already have.
