Every founder who needs a sales engineer runs into the same wall before they get to hire one: convincing a co-founder or board member who has never sat in a stalled technical evaluation that the money is worth it. I lost two six-figure deals to "we'll circle back once we finish evaluating internally" during the exact three weeks I was still deciding whether to even bring the hire up.
The pitch that finally worked wasn't longer or more polished. It swapped vague urgency for three specific numbers and a script built around the one objection that kills this conversation almost every time.
Why the usual pitch stalls in the room
Most founders pitch a sales engineer hire the way they'd pitch any headcount: here's the role, here's market rate, here's why we're stretched thin. That framing asks a co-founder to take your word for the problem. It doesn't show them the problem.
A board member or co-founder who isn't on the sales calls doesn't feel technical evaluations slipping. They see a pipeline number that still looks fine on a dashboard. The pitch has to make the invisible cost visible before it asks for the money.
The three numbers to bring into the room
- Deals lost or stalled specifically at technical evaluation, last two quarters. Pull this from CRM stage history, not memory. Most founders guess low.
- Founder or AE hours spent per week answering technical questions a specialist would clear in a fraction of the time. Timesheet it for two weeks before the meeting if you don't already track it.
- The cost of one more lost deal at your average contract value, multiplied by how many similar deals are in-flight right now.
These three numbers turn "I think we need this" into "here's what not deciding is already costing us," which is a different conversation entirely.
The script
- Open with the cost of inaction: "In the last two quarters we lost three deals worth $180K after the prospect's engineering team got involved. In every case, the deal died in the two weeks after that call, not before it."
- Present three scenarios: "Here's what changes if we hire a sales engineer this quarter, what changes if we wait a quarter, and what changes if we never hire one." Walk through each with a rough dollar impact.
- Name the actual ask: "I want to hire one sales engineer at $150K OTE, funded by closing one of the three deals currently stalled in technical evaluation."
- Preempt the trade-off question before it's asked: "The alternative is I keep spending ten hours a week on this instead of running the rest of sales, and deals keep stalling at the same stage."
The objection every co-founder raises first
"Can't the existing team just handle this?" comes up in almost every one of these conversations. The honest answer isn't that your team can't handle it. It's that handling it is already costing you a founder's or AE's time that has a higher-value use elsewhere, and the deals still stall because a part-time answer to a full-time problem is still a part-time answer.
Bring the hours number from step two here. It makes this objection answer itself instead of you having to argue it out loud.
If the answer is "not yet"
A "not yet" usually means the three numbers weren't specific enough, not that the case is wrong. Ask what number would change the answer, then go get exactly that data before the next attempt. Founders who get this hire approved on the second try almost always come back with a sharper number, not a longer pitch.
Frequently asked questions
What's the strongest number to lead with when pitching a sales engineer hire?
Deals lost or stalled specifically at the technical evaluation stage, pulled from CRM history rather than memory. It's concrete, it's yours, and it's the hardest number to argue with.
How do I justify a sales engineer's salary to a co-founder who controls the budget?
Tie the hire's cost to a single stalled deal in your current pipeline that's worth more than the salary. Funding the role from one recoverable deal is easier to approve than funding it from a general growth narrative.
What if I don't have clean CRM data on stalled technical evaluations?
Spend one week tagging every deal update that mentions a technical question, integration concern, or engineering stakeholder. A week of manual tagging is enough to build a credible first version of this number.
Should I bring a candidate to the pitch meeting?
No. Get the hire approved before you're sourcing candidates. Bringing a specific person into a budget conversation shifts the discussion to that individual instead of the underlying case for the role.
What's the most common reason this pitch gets rejected?
Vague urgency without dollar figures. "We need more technical support" is easy to defer. "We lost $180K to this exact gap last quarter" is not.
The pitch I wish I'd used the first time took forty minutes to prepare and about four minutes to deliver. Most of that prep time was just pulling the three numbers out of a CRM I'd been ignoring for months. Do that homework once, and the same numbers work whether the answer is yes on the first try or you're back in the room a quarter later with a sharper case.