How to get founders and engineers selling without being pushy

Get founders, engineers and customer success people selling by asking them to do something they already do: notice a problem a customer has and offer to help. Give them three simple questions, an easy way to pass the opportunity on and a small reward when they find one, and keep sales targets away from them.

I first wrote about this in 2012, for small businesses that couldn't afford a sales team. A startup still in founder-led sales is in much the same spot, and the people who aren't in sales are often the ones buyers see most.

Founder-led sales works for a reason

If you're a founder, you're often a better salesperson than the professionals you'll hire, and you probably don't trust it. The most persuasive thing in any sale is someone who understands the problem and cares about solving it, and nobody understands or cares about your problem more than you do. You built the product because the problem bothered you enough to spend years on it. Buyers can tell.

That's why founder-led sales works so well, and why companies often stall a little when the founder stops. Don't be in a hurry to hand it off. The good news is that what makes you persuasive is spread across your team. The engineer who built the integration and the customer success lead who hears about customers' problems every week both understand them better than most reps ever will.

Your non-sellers are already in the room

In a seed or Series A company, the founder runs most of the demos. An engineer joins the technical call. Customer success runs onboarding, support answers tickets, and product runs feedback calls. Every one of those conversations is a chance to hear about a problem you could solve.

Two numbers make this harder to ignore. A Gartner survey of B2B buyers published in March 2026 found 67% prefer a rep-free experience. A buyer who'd rather avoid a rep still has to talk to the people who implement and support what they bought. And Benchmarkit's 2025 SaaS benchmarks, drawn from 563 companies, found B2B SaaS businesses get 40% of their total new ARR from existing customers, up from a 25% median in 2022. A good share of next year's revenue starts in conversations your sales team isn't part of.

Don't ask them to sell

Tell an engineer to "go out and sell" and they'll picture the pushy, back-slapping stereotype nobody likes, and recoil. Fair enough. That stereotype was always a bad way to sell.

So drop the word. Ask them to keep an eye out for problems the company can help with, and when they spot one, to offer to help. They already do this everywhere else: when a friend mentions a problem they know something about, they offer what they know.

My example in 2012 was a delivery driver for a food logistics company, on a break at a café, who notices the café's own supplier keeps turning up late with half the order wrong. Hand that driver a sales target and they'd panic. Ask them to be curious about it, and to mention that their company is good at exactly this, and you've got a lead. The software version happens every day. An implementation engineer sees a new customer wrestling with something another part of the product would fix in a minute, and says so.

Some of the best sellers I've met would be offended to be called salespeople. I remember a support lead who'd spent years solving customers' problems and started, almost by accident, mentioning when something they were struggling with could be handled better. Customers bought more from that support lead than from people whose job was selling. Nobody had ever taught them to pitch or pressure, so they just helped, and helping sold beautifully.

Give them open, probe, confirm

Three moves are enough for someone who's never sold:

1. Open. An easy question that invites the customer to talk about their world. "How are you handling that at the moment?" or "What's that process like for you today?"
2. Probe. Gently find the shape and cost of the problem. "What happens when that goes wrong?" "How often does it come up?" "What does it end up costing you?"
3. Confirm. Say back what you heard. "So if I've got this right, the issue is X, and it's costing you Y?" It proves you listened, lets them correct you and makes them feel understood, which builds trust on its own.

There's no pitch in it. The offer to help comes last: "Would it help if I asked our founder to give you a call?" In 2012 that call came from the business owner. In a startup it's the founder, or your account executive if you have one. The engineer never has to close anything, and knowing that makes the first question much easier to ask.

AI helps here too. The tools will prep a nervous engineer before a customer call (the same prep I described in how to prepare for a first sales meeting), draft the follow-up they were dreading, and point out afterward what they missed. What no tool supplies is the decision to care about the person on the other end. The same software will help one founder blast a thousand messages and another help twenty of the right people.

Reward the spotting

In 2012 I suggested a $100 voucher for every opportunity someone uncovers and something like $500 when one becomes a customer. I'd still do it. The amounts are small on purpose. They tell people the company wants them looking, and they say thanks without turning anyone into a commission-chaser.

A few rules I'd add:

• Pay for the spot promptly. The first reward lands when the opportunity is passed on, whether or not it closes, so nobody feels they need to push a customer to get paid.
• Close the loop. Tell them what happened. A lead that vanishes into the CRM is the fastest way to make sure there isn't a second.
• Make it easy to log. One Slack message or a short form that creates the CRM record. If it takes ten minutes of admin, expect very few.
• Keep it away from quotas. If your customer success team carries an expansion number, that's a sales job and needs a proper sales comp plan. This is for everyone else.

Write down what you do before you hand it over

At some point the founder can't be the only one selling, and much of what makes founder-led sales work is invisible, even to the founder. So write it down: the questions you always ask, the problems you always probe for, how you describe the problem, and the objections you hear most. The curiosity, honesty and questions can be taught. Your command of the product and your founder's credibility can't, at least not straight away.

Then hire a first seller who's curious about the problem, honest and coachable enough to carry your way of selling. A polished closer who doesn't care about the problem will sell against everything you've built. Turning a founder's instinct into a motion other people can run is a big part of what we do as a fractional VP of sales, and founders stay in the early deals either way.

Watch the drift as revenue pressure grows. A bit more pressure in the sequence, a bit more manufactured urgency, a demo that shows more and listens less. In Curiosity I warn founders about turning into the pushy vendor they set out not to be, and a reward scheme can drift the same way once it feels like a target.

Your engineers won't call any of this selling, and there's no need to correct them.