Most Seed-to-Series-C startups build technical pre-sales in the wrong order. The first move is almost always the same: open a req for a Sales Engineer. That hire is usually the third piece of a repeatable motion, not the first.
The instinct makes sense. Founders are buried in demos, deals stall on technical questions, and an SE looks like the obvious fix. But an SE hired into an empty space doesn’t inherit a motion. They invent one, usually in their own image, and it walks out the door with them.
A repeatable technical pre-sales motion has five pieces. Here they are in the order that actually compounds at this stage.
A Technical Story Someone Else Can Tell
Your founder already sells technically, and probably sells well. The problem is that the motion lives in one person’s head. Step one is getting it out.
Record ten or fifteen founder-led calls and mine them. You’re looking for four things:
- The technical buyer: Who actually says yes to the architecture, and what they’re measured on.
- The discovery questions: The three to five questions that separate a real fit from a curious engineer with a free afternoon.
- The demo narrative: Problem, painful before, credible after. Not an open-ended feature tour.
- The objections: The ones that come up every week, and the answers that actually land.
The output is a written discovery guide and a demo script. The test is simple: could a sharp engineer who has never met a customer run a first call from these and not embarrass you? If not, keep going.
An Evaluation Playbook With Rules
At most early-stage companies, a proof of concept is open-ended free consulting. It starts when a prospect asks, ends when someone gets bored, and succeeds on vibes. That’s not a motion. It’s a donation.
“At most early-stage companies, a proof of concept is open-ended free consulting. It starts when a prospect asks, ends when someone gets bored, and succeeds on vibes. That’s not a motion. It’s a donation.”
— Arthur Enright · Technical GTM Practice
An evaluation playbook puts rules around it:
- A qualification gate: No POC until the prospect has passed technical discovery and a commercial sponsor is named.
- Written success criteria: Agreed with the buyer before anything is installed, not reverse-engineered afterward.
- A time box: A fixed window with a start date and an end date both sides can see.
- Named owners on both sides: Someone on their team is accountable for testing, not just “the team.”
- Exit rules: Criteria met means a commercial conversation. Criteria missed means a clear no, or a re-scoped evaluation you both sign off on.
Most importantly, this is where you define a technical win as a specific, observable event. Without that definition, you have nothing to measure an SE against later.
The First SE, Now
This is where the hire belongs. With pieces one and two in place, you’re hiring someone to run and improve a motion, not to invent one from scratch.
That changes everything about the hire:
- The interview gets concrete: Hand candidates your demo script and a mock evaluation. Watch what they do with it.
- Ramp takes weeks, not quarters: There’s a playbook to learn instead of a founder to shadow indefinitely.
- Performance is measurable: Technical win rate and POC conversion exist because you defined them first.
Now look at what happens when the SE comes first. They become a demo jockey running whatever the founder did last week. Or they build a second, slightly different story, and prospects hear two pitches. Or they do great work that nobody wrote down, then leave after a year and take the motion with them. In every version, you’ve paid for one of your most expensive early hires and still can’t tell if it’s working.
Why third and not later? Because pieces four and five need an owner, and the founder can’t be it forever. Hire someone who has built as well as sold. Your first SE will write code, stand up environments, and draft docs, not just present.
One caveat: the founder doesn’t disappear. They keep the hardest and largest deals for a while. The SE takes everything the playbook already covers.
A Reusable Asset Layer
The rule here is blunt: anything you do three times becomes an asset. Your first SE builds this layer, and it’s what lets SE number two ramp in half the time.
The assets that pay back fastest:
- Resettable demo environments: Defined as code, torn down and rebuilt on demand. Not a laptop, and not a shared tenant someone broke last Tuesday.
- Reference architectures: For your two or three most common deployment patterns, so every prospect isn’t a whiteboard session from zero.
- A security and compliance answer bank: Questionnaires arrive the moment you move upmarket. Answer them once, well, and keep the answers current.
- Integration guides: For the tools your buyers already run.
- Recorded demos: For the stakeholders who will never join a live call but still get a vote.
None of this is glamorous. All of it is leverage.
Instrumentation and the Loop Back to Product
The last piece turns pre-sales from a cost center into a source of signal. It has two halves.
The first is measurement. Track technical win rate, POC-to-close conversion, evaluation cycle time, active evaluations per SE, and loss reasons tagged as technical or commercial. These are the numbers that justify SE number two through five to your board, and they only exist because piece two defined what a win is.
[GTM-INSTRUMENTATION] Northbound Navigators Proof-of-Value Benchmark
---------------------------------------------------------------------
METRIC: Quarter-Over-Quarter Technical Win Conversion
COHORT: Tier-1 Enterprise Prospects (ACV > $75k)
BEFORE EVALUATION PLAYBOOK (SE Hired First):
- Eval Cycle Time: 84 days (Uncontrolled POC window)
- Technical Win Rate: 36% (Success criteria unwritten / reverse-engineered)
- Loss Reason Attribution: "Lost momentum / ghosted" (78%)
AFTER EVALUATION PLAYBOOK (Pieces 1-5 Sequenced):
- Eval Cycle Time: 21 days (Time-boxed 3-week evaluation)
- Technical Win Rate: 78% (Agreed success criteria validated)
- Loss Reason Attribution: 100% categorized (Commercial budget or verified feature gap)
The second half is the field-to-product loop. Your SEs hear exactly which gaps block deals, every week. Capture that in a structured way, tag it by deal size and stage, and put it in front of product planning on a regular cadence. A roadmap informed by lost revenue beats one informed by whoever complained loudest.
How It Maps from Seed to Series C
The order holds at every stage. What changes is how far along you should be.
| Stage | What You’re Building | Who Owns It | Ready to Move on When |
|---|---|---|---|
| Seed | Pieces 1 and 2 (Technical story & evaluation playbook) | Founder | The playbook has survived a handful of real deals |
| Series A | Piece 3, then early piece 4 (First SE, then initial assets) | Founder + first SE | The founder is no longer on every technical call |
| Series B | Pieces 4 and 5 mature; SE two and three onboarded | SE team, founder on top deals | Win rate and cycle time are reported, not guessed |
| Series C | Piece 5 is board-grade; dedicated pre-sales leader hired | Pre-sales leader | Headcount requests come with the data attached |
If you’re past Series A and still missing pieces one and two, don’t fire anyone. Have your SEs write them down. It’s the fastest way to find out whether you have one motion or several.
The short version: hire the SE when there’s something for them to repeat.
About the Author
Arthur Enright · Co-founder · Technical GTM & Platform Architecture
Technology and solutions leader with almost 30 years of experience in enterprise software, open source, and technical sales engineering. He advises infrastructure vendors on buyer enablement, proof-of-value design, and scaling technical sales teams.
Prior experience: Motorola · Rackspace · Capital Group · Red Hat · Docker · Nutanix · HashiCorp