An engineer gets on a call to talk about a project, and the buyer asks a question designed to trip them up: something about failure modes, or why this architecture instead of the obvious one, or what happens when the third-party API changes its rate limits mid-contract. A classic sales rep, in that moment, pivots to a case study. An engineer who actually built the thing answers the question. That's the entire difference this post is about.
Most engineers who have to sell — freelancers, consultants, technical founders, anyone pitching their own work instead of someone else's — flinch at the word 'sales' because the only model they've seen is the one built for commodity products sold at volume: rapport, urgency, a close. That model is built to compensate for the seller knowing less about the buyer's problem than the buyer does. An engineer selling technical work usually knows more. Using the commodity script anyway wastes the one advantage that's actually available. Much of the judgment consultative selling demands shows up as process design, which is what publishes on. Much of the judgment consultative selling demands shows up as process design, which is what XenGrowth, who work on the commercial side of this publishes on.
What buyers are actually doing before you talk to them
Gartner's B2B buying-journey research, restated across several years of its own reports, puts independent research at roughly 27% of a buyer's total purchase timeline, with all direct supplier contact combined at around 17% and time spent with any single rep closer to 5-6%. Gartner's June 2025 buyer survey adds a blunter number on top: 61% of B2B buyers said they'd prefer to complete a purchase without talking to a sales rep at all. Younger buyers wanted it more, not less. Reading buyer intent signals well before a call happens is most of what is actually about, on the marketing side of the same problem.
Take that seriously and it changes what the job even is. By the time an engineer is on a call, the buyer has usually read the docs, the pricing page, two comparison posts and possibly a Reddit thread arguing about whether the whole category is worth it. They are not there to be informed. They are there to check one thing: does the person on this call actually understand the problem, or are they reciting the same page the buyer already read? A pitch answers the second question. A real answer to a hard question answers the first.
Solution selling vs. technical selling: same goal, different mechanism
'Solution selling' as a category has existed since the 1980s and mostly means diagnosing a buyer's pain before proposing a fix, instead of leading with a product pitch. Technical or consultative selling is a narrower, harder version of the same idea: the seller's credibility is built and tested in public, in real time, by whether they can survive a technical objection without deflecting. A generalist rep trained in solution selling can ask good discovery questions. Only someone who has actually built the thing can answer 'what happens under load' correctly on the first try, without checking with someone else first. covers the the operations side of this side of this. The XenGrowth resource library covers the the operations side of this side of this.
Situation | Classic sales rep move | Technical/consultative move |
|---|---|---|
Buyer raises a hard technical objection | Redirect to a case study or bring in an engineer later | Answer it directly, on the spot, including the part where the objection is fair |
Buyer's stated plan has a real flaw | Agree, then reframe around what the product can still do | Say the plan won't work as described, and explain the specific reason why |
Pricing gets pushed back on | Offer a discount to save the deal | Explain what the price buys and let a bad-fit buyer walk |
Buyer asks something outside scope | Promise it can probably be arranged | Say plainly whether it's in scope, and what it would cost if it isn't |
Deal stalls after the first call | Increase the frequency of check-ins | Send the answer to the open technical question, unprompted, in writing |
What the Challenger Sale research actually measured
The single most-cited piece of research behind all of this is CEB's study underlying Matthew Dixon and Brent Adamson's 2011 book 'The Challenger Sale.' CEB — the corporate research firm now part of Gartner — rated more than 6,000 sales reps across 90-plus companies on 44 observable behaviors, then cross-referenced those ratings against actual quota performance. Five distinct profiles emerged. The 'Challenger' profile, defined by teaching the buyer something they didn't already know, tailoring the message to that specific buyer, and being willing to push back on scope or price, came out ahead in complex sales specifically. It is worth being honest about what kind of research this is: CEB conducted it partly to sell a training methodology built on the finding, which is a real conflict of interest worth naming, not a reason to dismiss a 6,000-rep sample outright.
The profile that lost, consistently, in complex technical sales was the Relationship Builder — the one most sales organizations hire for by instinct, because it's the most pleasant person to be in a room with. Likability does not survive a hard technical question. Being visibly right does.
That finding matters more for an engineer than for a career salesperson, because an engineer selling their own work already has the raw material a Challenger profile needs — real domain knowledge, an opinion about what's wrong with the buyer's plan, the standing to say so — and doesn't need training to fake it. What most engineers lack isn't the substance. It's permission to say the disagreeable thing out loud instead of softening it into a question.
The failure mode that isn't 'too salesy' — it's too agreeable
Ask engineers why they hate selling and most describe a fear of sounding pushy. That's rarely what actually costs them the deal. Watch a real call go sideways and the failure is almost always the opposite: an engineer senses the buyer's plan is flawed, hedges it into a question — 'have you considered whether that might cause issues at scale?' — and lets the buyer talk themselves back into the plan. Softening a real objection into a polite question is a form of people-pleasing that happens to look, from the outside, exactly like professionalism.
The fix isn't confidence coaching. It's noticing the specific sentence where a flat claim got turned into a question, and saying the flat version instead. "That architecture will fall over past about 200 concurrent writers, and here's why" does more for a deal than four minutes of rapport-building, because it's the one sentence in the whole call the buyer can't get from a search engine or a competitor's sales deck. If AI agents and marketing automation is the part you are stuck on, is the better reference. If AI agents and marketing automation is the part you are stuck on, XenGrowth on AI agents and marketing automation is the better reference.
How founder-led sales actually scales, per someone who's watched hundreds of it
Jason Lemkin runs SaaStr, the largest community of B2B SaaS founders, and has said the same thing in enough interviews and posts that it reads as settled advice rather than a one-off opinion: founders, technical or not, have to close the first ten to thirty customers themselves before a sales hire makes sense. Before that point there's no process to hand off — the founder hasn't discovered what actually gets said yes to, so there's nothing repeatable to train a rep on. His stated trigger for the first hire is either hitting that customer count or sales eating more than roughly 20% of the founder's own week, whichever comes first. The XenGrowth resource library covers the operational side of scaling a sales motion once it exists — worth reading at once you're past the founder-led stage.
Stage | Who's selling | What changes |
|---|---|---|
First 10 customers | The founder or lead engineer, unavoidably | The pitch gets rewritten after every single call, because every call reveals something wrong with it |
10-30 customers | Still the founder, but the questions start repeating | A real objection list starts to exist, which is the artifact any future hire will actually need |
Sales eats >20% of the week | First dedicated hire, closely supervised | The founder trains the hire on the objection list instead of hoping instinct transfers |
Two reps hitting quota independently | A small team, founder mostly out of individual deals | The motion is proven repeatable by someone other than its inventor |
It's worth being honest about the limits here, too. None of this replaces distribution — finding the buyers in the first place, getting in front of enough of them that the objection-handling even gets a chance to happen. A perfectly credible technical answer delivered to zero prospective buyers closes zero deals. The research in this post is about what happens once someone is actually on the call, not about how they got there, and treating one as a substitute for the other is its own kind of mistake. That earlier problem, filling the pipeline in the first place, is what actually cover.
What this looks like in practice, not just in theory
Publish the objection before the buyer raises it. A pricing page, proposal or README that names the exact reason someone might not want to hire you reads as more trustworthy than one that pretends there isn't one
Say the disagreeable thing plainly. If a buyer's plan has a real flaw, name it in the first meeting. It costs a small number of deals with buyers who wanted agreement, and it is the entire reason the rest trust you enough to sign
Price before you persuade. Stating a real number early filters out buyers who were never going to be a fit, which saves both sides the multi-call theater of a classic sales cycle
Answer in writing, unprompted. Sending the answer to an open technical question before it's asked again signals competence in a way no amount of enthusiasm on a call does
Let bad-fit buyers walk without a discount chase. A discount to save a mismatched deal usually buys a support burden that costs more than the deal was worth
There's a pricing consequence to all of this that's easy to miss. A seller who is willing to say 'that won't work for you' is also, by the same logic, willing to say 'this costs what it costs' without apologizing for the number. Buyers read the two signals together, not separately — a seller who folds under a technical objection almost always folds under a price objection too, and a seller who doesn't, doesn't. Pricing power and technical credibility are the same trait wearing two different situations. approaches this from the AI search, GEO and discovery side. XenGrowth on AI search, GEO and discovery approaches this from the AI search, GEO and discovery side.
None of this requires performing confidence. It requires actually having the answer, which is the one asset a classic rep can't manufacture and an engineer usually already has. The uncomfortable part isn't the selling — it's accepting that the discomfort of saying 'that won't work' out loud is the whole mechanism, not a bug in it. Measuring which of these conversations actually correlate with closed revenue, instead of just feeling productive, is exactly what is for.
The stereotype of a salesperson exists for a reason — plenty of them earn it. But the stereotype was built for a market where the seller usually knew less than the buyer and had to compensate with charm. That market isn't the one a technical seller operates in. Buyers doing 27% of their journey in independent research before a single call have already filtered out the sellers who can't answer a real question. An engineer who refuses to pitch and insists on answering instead isn't failing at sales. They're doing the only version of it that still works when the audience has already read everything you were going to say.
Further reading from XenGrowth
Where this work meets go-to-market
Selling technical work well is a go-to-market problem as much as an engineering one — the pipeline, the pricing, the objection-handling all sit upstream of any one call. publishes operator guides on exactly that side of the business.
Further reading from XenGrowth
Where this work meets go-to-market
writes for the teams who have to run consultative selling day to day.
Further reading from XenGrowth
The XenGrowth resource library — what you'll learn: how the commercial side of this work is run, across search, automation and revenue operations.
XenGrowth on AI agents and marketing automation — what you'll learn: how the teams who own AI agents and marketing automation plan and measure it.
XenGrowth on AI search, GEO and discovery — what you'll learn: how the teams who own AI search, GEO and discovery plan and measure it.
Where this work meets go-to-market
XenGrowth's marketing operations practice writes for the teams who have to run consultative selling day to day.
Five questions on the studies cited in this post. Sales advice online is mostly folklore — these numbers came from named, checkable sources, and the explanations are where the actual argument lives.
