PreSales is the function in a B2B sales team that wins the technical decision. Its people — Sales Engineers, Solutions Engineers, Solutions Consultants — work alongside the account executive to understand the customer's problem, prove that the product solves it, and build the business case. Sales owns the commercial outcome. PreSales owns the customer's confidence that the solution will work.
TL;DR
- PreSales is not "everything before the sale". It is a defined role with a defined outcome: the technical win — the customer confirming that your solution fits their requirements.
- Its job is to convince, not to solve. If you're solving the customer's problem during the sales cycle, you've gone too far. Solving happens in the project.
- Sales Engineer, Solutions Engineer, Solutions Consultant, PreSales Consultant are largely the same job under different titles.
- In the P&L, PreSales is a cost center — so measure it like one: technical win rate, SE-attached revenue, win rate with and without an SE.
- AI is removing demo preparation and raising the value of discovery. The part of the role that was always the moat is the part that's left.
What is PreSales?
PreSales — also written presales or pre-sales — is the team that carries the technical and functional side of a complex sale. The term is mostly used in B2B software, where a product can't be bought from a brochure: someone has to understand the customer's processes, show the product against them, answer the architecture and security questions, and often run a proof of concept.
The textbook definition is broader and less useful. Wikipedia describes presales as "a process or a set of activities" carried out before a customer is acquired. That is true of marketing as well. What distinguishes PreSales as a function is the outcome it is accountable for: the technical win, the moment the prospect confirms that your solution meets their requirements and is the preferred technical fit — even if the deal later stalls on budget, timing or procurement.
The clearest statement of the boundary came out of our conversation with Saskia Cempel, who built the PreSales team at the SAP partner Sybit: if you're solving the customer's problem in PreSales, you're already doing it wrong. PreSales has one job — to convince the customer that your organization can solve the problem. The solving happens in implementation. The full story is in Consultant or Salesperson?.
What does a PreSales team do, stage by stage?
It turns a qualified opportunity into a proven fit. The work changes with the stage of the deal, and so does who leads.
PreSales enters after qualification, leads the middle of the deal, and stays on after the technical win.
| Stage | What PreSales does | Who leads |
|---|---|---|
| Qualification | Usually nothing yet. A useful gate: no SE time below roughly 25% win probability. | Account executive |
| Discovery | Works from the symptoms the customer describes to the business impact behind them, and quantifies it. | Solution Engineer, with the AE |
| Demo | Shows the product against the problems found in discovery — not a feature tour. | Solution Engineer |
| Proof of concept | Agrees success criteria up front, then proves them on the customer's data or environment. | Solution Engineer |
| Technical validation | Answers security, architecture and integration questions; handles the RFP's technical part. | Solution Engineer |
| Proposal and close | Supplies the business case and stays available for the buying committee. | Account executive |
| Handover | Transfers what was promised, and why, to the delivery team. | Both |
Two points in that table are where teams most often go wrong. The first is entering too early: if your SE sits in the first or second qualification call, something is broken in the sales methodology, not in the headcount plan. The second is leaving too early. The technical win is a stage, not a trophy. Most enterprise deals now carry two or three vendors on the shortlist to the very end, and there is no silver medal. We go through both in Lies in PreSales.
The order inside the table is not negotiable either: no discovery, no demo. A demo built without discovery is a guess at what matters, delivered with confidence.
What is the difference between PreSales and Sales?
Sales owns the relationship, the commercial terms and the number. PreSales owns the proof. The account executive is responsible for whether the deal closes and at what price; the Solution Engineer is responsible for whether the customer believes the product will do what they need.
| Sales (account executive) | PreSales (solution engineer) | |
|---|---|---|
| Accountable for | Revenue, forecast, contract | Technical win, solution fit, business case |
| Main skill | Qualifying, negotiating, navigating the buying committee | Discovery, demonstrating, translating between technology and business |
| Typically paid on | Individual quota | Team or territory attainment, sometimes no quota at all |
| Works on | A handful of accounts | Many deals at once — ratios of one SE to three, four or five AEs are common |
That last row has a consequence people overlook. Because one SE works across several account executives, an SE sees far more deals per quarter than any single AE. That breadth is why good PreSales people recognise patterns across industries — and why they are often the best judges of whether a deal is real.
The difference in incentives is also a feature. An SE whose pay depends less on any single deal can afford the honest sentence — "this won't work the way you want" — that an AE under quarter-end pressure finds hard to say. Sybit deliberately gave its PreSales team no sales quota at all, to protect the quality of the advice.
Which job titles belong to PreSales?
Sales Engineer, Solutions Engineer, Solutions Consultant, Solution Architect, PreSales Consultant, Value Consultant, Demo Engineer. In most companies the first four describe the same job, and the title says more about the company's history than about the work.
Where the titles do differ, it is usually in one of three ways: how technical the role is (a Solution Architect designs integrations; a Solutions Consultant leads with business process), whether it carries a quota, and how much it does after the signature. Titles are also chosen for positioning. Sybit's team calls itself "Solution Advisors" externally, to reinforce the trusted-advisor positioning rather than a sales-adjacent one.
How is PreSales measured?
By the outcome it owns, and by what it costs. The single most useful number is the technical win rate: the share of evaluated deals in which the customer confirms your solution as the preferred technical fit. It isolates what the SE actually controls from what is decided later, in a room they aren't in. Next to it sits the SE-attached win rate — how often deals with PreSales involvement close — as the lagging scoreboard. We explain why you need both in The North Star: SE-Attached & Technical Win Rate, the second part of a ten-part series on PreSales KPIs that starts with The Metrics Gap.
The other half of measurement is money. PreSales is part of cost of sales, and so part of customer acquisition cost. If you own a PreSales budget, the questions a CFO will ask are predictable: what is the SE-attached revenue, what is the win rate with an SE versus without, what is the deal size with and without. As the former CRO Eddy Frey put it to us: measurability creates manageability.
Is PreSales a cost center?
In the P&L, yes — and arguing about the label is less useful than managing the money. The costs are more than salaries: demo environments in the cloud, clusters kept running for weeks, every additional customised demo that burns hours nobody tracks.
The reason to care is the day someone says "cut 20%". A team that has never made itself measurable loses that argument on feeling. A team that can show where its capacity goes — which segments, which stages, at what win probability — turns the same conversation into a decision about allocation. How to get there without drowning the team in admin is the subject of Scaling KPIs Without Scaling Admin.
Is PreSales a good career?
It is well paid and unusually hard to plan. For the United States, the Bureau of Labor Statistics reports a median annual pay of $124,900 for sales engineers in May 2025, across 51,600 jobs, with employment projected to grow 3% from 2025 to 2035 — about as fast as the average for all occupations.
What the role lacks is a marked path. Nobody certifies Solution Engineers, and there is no degree or apprenticeship that leads into it; people arrive from consulting, engineering, customer success and sales. From there the routes run to senior and principal SE, into PreSales leadership, or sideways into product, sales or customer success. We wrote down what actually moves a career forward in How to Build a PreSales Career When There Is No Career Path.
How is AI changing PreSales?
It is splitting the role in two. The work of preparing a demo — finding industry data, configuring a scenario, branding the deck — used to take two or three days and is collapsing toward zero. If your value was defined by that preparation, it is shrinking with it.
The work that decides which demo to build is going the other way. Automation only performs as well as its input, and the input is the discovery conversation: the pain uncovered, the context mapped, the business case. As more software becomes headless and agentic, buyers stop asking "can it do X?" and start asking "should we do this, and what does it change about how we operate?" That is a conversation for a trusted advisor, not a feature presenter. We follow that thread in When the GUI Disappears.
Frequently asked questions
What does PreSales mean? PreSales is the function in a B2B sales team responsible for the technical and functional side of a deal: understanding the customer's problem, demonstrating the product against it, running proofs of concept and building the business case. Its outcome is the technical win — the customer confirming that the solution fits.
Is it spelled presales, pre-sales or PreSales? All three are in use and mean the same thing; this site uses PreSales. "Presale" without the s usually means something else entirely: early ticket or product sales.
What is the difference between PreSales and Sales? Sales owns the commercial outcome — relationship, price, contract, forecast. PreSales owns the proof that the product solves the customer's problem. They work the same deal from two sides, typically with one Solution Engineer supporting three to five account executives.
What does a PreSales consultant do? Leads discovery with the customer, designs and delivers demos, runs proofs of concept, answers technical and security questions, contributes the technical part of RFPs and proposals, and hands the deal over to delivery. PreSales Consultant is one of several titles for the role, alongside Sales Engineer, Solutions Engineer and Solutions Consultant.
Is PreSales a technical or a sales role? Both, and the mix is shifting toward the business side. Technical depth earns credibility; the conversations that win deals are increasingly with business stakeholders who care that a problem can be solved, not how.
How do you measure PreSales performance? Start with technical win rate and SE-attached win rate, then add what the function costs and returns: SE-attached revenue, and win rate and deal size with versus without PreSales involvement.
If you want your team to be the kind of PreSales this guide describes — leading discovery, proving outcomes, measured on what it owns — that is what the Trusted Advisor Academy trains, every week. If you lead the team, the Trusted Leader Academy covers the KPIs, hiring and coaching systems behind it.
Tim Brömme & Jan-Erik Jank are the co-founders of SE Rockstars, with 30+ years in enterprise PreSales and 350+ SEs coached.