There is no universal formula for the right sales-to-pre-sales ratio at an AI company. A good starting point for most B2B AI companies selling complex solutions is somewhere between 3:1 and 5:1, meaning three to five Account Executives per Solutions Engineer or Pre-Sales Consultant. But the right number for your team depends on deal complexity, your product’s technical depth, and how much your AEs can handle on their own. The sections below break down how to think through this decision clearly.
What is pre-sales and why does it matter at an AI company?
Pre-sales refers to the technical and consultative work that happens during the sales process before a deal is closed. At most B2B companies, this function is owned by Solutions Engineers, Pre-Sales Consultants, or Sales Engineers. Their job is to bridge the gap between what a prospect needs and what the product actually does, through demos, proof-of-concept projects, technical discovery, and RFP responses.
At an AI company, this role carries extra weight. AI products are rarely plug-and-play. Prospects want to understand how the model works, what data it needs, how it integrates with their existing stack, and what happens when it makes a mistake. These are not questions a typical AE can answer confidently in a first call.
Pre-sales professionals at AI companies often spend significant time on:
- Running tailored demos that reflect a prospect’s specific use case
- Scoping and managing proof-of-concept projects
- Answering technical security and compliance questions
- Collaborating with product and engineering during complex evaluations
- Translating AI capabilities into concrete business outcomes
When pre-sales is done well, it shortens sales cycles, increases win rates, and reduces the number of deals that stall in technical evaluation. When it is underfunded or missing entirely, AEs struggle to move complex deals forward, and prospects lose confidence.
What is the typical sales to pre-sales ratio in B2B SaaS?
In most B2B SaaS companies, the standard sales-to-pre-sales ratio falls between 4:1 and 6:1. This means one Solutions Engineer or Pre-Sales Consultant supports four to six Account Executives. This ratio reflects a world where products are technical but not necessarily complex to evaluate, and where AEs carry a significant portion of the discovery and demo workload themselves.
The ratio tends to shift depending on deal size and sales motion:
- SMB or mid-market SaaS: Pre-sales involvement is lighter. Ratios of 6:1 or even 8:1 are common because demos are more standardized and deals close faster.
- Enterprise SaaS: Pre-sales gets more involved. Ratios of 3:1 to 4:1 are typical because deals involve procurement, security reviews, and custom integrations.
- Platform or infrastructure SaaS: Pre-sales can be even more central. Ratios of 2:1 or 3:1 are not unusual when the product requires deep technical evaluation before any commercial decision is made.
These are directional benchmarks, not rules. The right ratio depends on how your sales process actually runs, not on what the industry average says.
How does the sales to pre-sales ratio differ for AI companies?
AI companies typically need a lower sales-to-pre-sales ratio than traditional SaaS companies, meaning more pre-sales support per AE. A ratio of 2:1 to 4:1 is common at AI-native companies, particularly those selling to enterprise buyers or in regulated industries. The reason is straightforward: AI products require more technical validation before a prospect will commit.
Several factors push AI companies toward heavier pre-sales investment:
Higher technical complexity in the evaluation stage
Prospects evaluating AI tools want to know how the model performs on their data, not just on a generic demo. This often means running a proof of concept that takes weeks, not days. Pre-sales professionals own this process and need the capacity to run multiple POCs simultaneously without quality dropping.
Trust and explainability concerns
Buyers in 2026 are more cautious about AI than they were two years ago. They want to understand how decisions are made, what the error rate looks like, and how the system handles edge cases. Pre-sales teams field these questions and, when they answer them well, they build the trust that closes deals.
Integration-heavy deployments
Most AI products need to connect to existing data sources, workflows, or enterprise systems. Pre-sales is typically responsible for scoping these integrations early in the process, which adds time and effort per deal compared to a standard SaaS product.
The implication is that AI companies that try to run a 5:1 or 6:1 ratio because that is what they saw at their last SaaS job will often find their pre-sales team overloaded, their POC quality declining, and their win rates suffering as a result.
What factors should determine your specific ratio?
The right sales-to-pre-sales ratio for your AI company depends on five factors: deal complexity, average contract value, sales cycle length, the technical depth of your product, and how much pre-sales work your AEs can realistically handle. No single factor determines the answer, but together they point you toward the right structure.
Work through these questions to find your number:
- How complex is your product to evaluate? If prospects routinely need a POC before buying, your pre-sales team will be stretched thin at a 5:1 ratio. If your product demos well without customization, you have more flexibility.
- What is your average contract value? Higher ACV deals justify more pre-sales investment per deal. A deal worth several hundred thousand euros can absorb significant pre-sales time. A deal worth twenty thousand euros cannot.
- How long is your sales cycle? Longer cycles with multiple stakeholders require sustained pre-sales involvement. If your cycle runs six to twelve months, your pre-sales team needs bandwidth to stay engaged across many deals at once.
- How technical are your AEs? Some AEs can handle light technical conversations and basic demos independently. Others need pre-sales support from the first discovery call. Your ratio should reflect the actual capability of your sales team.
- What is your win rate on deals that go to POC? If you are losing a high percentage of deals after the POC stage, that is often a pre-sales quality problem, not a sales problem. Adding more AEs without addressing pre-sales capacity will not fix it.
When should an AI company hire its first pre-sales hire?
An AI company should hire its first pre-sales professional when technical questions are consistently slowing down deals or when AEs are spending more than a third of their time on product demonstrations and technical discovery. If your sales team is regularly pulling in engineers or product managers to support sales conversations, that is a clear sign the pre-sales function needs a dedicated owner.
In practice, this moment tends to arrive earlier at AI companies than at traditional SaaS companies. A few signals to watch for:
- Deals are stalling during technical evaluation with no clear owner to move them forward
- Your AEs are strong commercially but uncomfortable with deep technical questions
- You are running POCs but no one is formally responsible for their success
- Prospects are asking for customized demos and your team is building them ad hoc
- Engineering is complaining about being pulled into sales calls too often
The first pre-sales hire at an AI company is often a generalist Solutions Engineer with enough technical depth to handle POC management, demo customization, and RFP responses. This person does not need to be a data scientist, but they do need to understand how your AI product works well enough to explain it credibly to a technical buyer.
Hiring this person too late is a common mistake. By the time the pain is obvious, your AEs are already losing deals they should have won.
What mistakes do AI companies make when scaling pre-sales?
The most common mistakes AI companies make when scaling pre-sales are hiring too late, hiring the wrong profile, and failing to define what pre-sales actually owns in the sales process. Each of these mistakes creates a different type of problem, but all of them slow down revenue growth and increase the cost of acquiring customers.
Hiring too late
Most AI companies wait until their AEs are visibly struggling before they bring in pre-sales support. By that point, deals have already been lost and the sales team has developed workarounds that are hard to undo. The better approach is to hire pre-sales slightly ahead of demand, particularly if you are entering a new market or moving upmarket toward enterprise buyers.
Hiring the wrong profile
Pre-sales at an AI company is a specific role. Hiring a former software engineer who wants to get into sales, or a generalist SaaS Solutions Engineer who has never worked with AI products, often leads to a mismatch. The right profile combines technical credibility with genuine commercial instinct. They need to be comfortable in front of a sceptical CTO and equally comfortable helping an AE navigate a procurement process.
Leaving the role undefined
When pre-sales responsibilities are not clearly defined, conflict with AEs is almost guaranteed. Who owns the POC? Who decides when to walk away from a technically demanding prospect? Who is responsible for the demo environment? Without clear answers, both functions operate less effectively and the prospect experience suffers.
Treating pre-sales as a support function rather than a revenue driver
Pre-sales professionals at high-performing AI companies are not there to carry bags for AEs. They directly influence win rates, deal size, and customer satisfaction in the early stages of the relationship. Companies that treat them as a cost center rather than a commercial function tend to underpay them, underinvest in their development, and lose them to competitors who value the role correctly.
GTM hiring at AI-native companies is genuinely harder than at traditional SaaS companies. The profiles are rarer, the role definitions are less standardized, and the margin for error is smaller. At Nobel Recruitment, we speak with hundreds of GTM professionals and hiring managers across Europe every week, and we see firsthand how the right pre-sales hire can change the trajectory of a commercial team. If you are thinking through how to structure your GTM talent search for pre-sales or Solutions Engineering roles, we are happy to share what we are seeing in the market right now.
Frequently Asked Questions
How do I know if my current sales-to-pre-sales ratio is actually hurting my win rate?
The clearest signal is a drop in win rate specifically at the POC or technical evaluation stage. If deals are progressing through early discovery but stalling or losing after a proof of concept, your pre-sales team is likely overloaded and delivering below their best quality. Track the ratio of deals entering POC versus deals closing, and compare it across periods when pre-sales capacity was higher or lower. A declining close rate after POC is almost always a capacity or quality problem on the pre-sales side, not a pricing or product problem.
Can a strong AE replace the need for a dedicated pre-sales hire at an early-stage AI company?
In the very early stages, a technically strong AE can cover some pre-sales ground, but this approach has a short shelf life at an AI company. Once deal volume increases or deal complexity grows, a technically capable AE will either burn out trying to run POCs and close deals simultaneously, or they will deprioritize one at the expense of the other. The better approach is to treat the first pre-sales hire as a revenue investment rather than an overhead cost, and bring them in before the AE is visibly struggling.
What does a good pre-sales qualification process look like for an AI company to avoid wasting POC resources?
A strong pre-sales qualification process defines clear entry criteria before any POC is approved, typically covering minimum deal size, confirmed budget, executive sponsorship, and a specific use case that your product can credibly address. Pre-sales and AEs should align on a mutual success plan with the prospect before a POC kicks off, including defined success metrics, a timeline, and named stakeholders on both sides. Without these guardrails, POCs become open-ended and resource-intensive, with no clear path to a commercial decision.
How should pre-sales compensation be structured at an AI company compared to the AE?
Pre-sales professionals at AI companies are typically compensated with a higher base-to-variable split than AEs, often in the range of 70-80% base and 20-30% variable, reflecting the fact that their impact on revenue is real but less directly tied to individual deal outcomes. Variable compensation is usually tied to team quota attainment, win rates on deals they supported, or POC conversion rates rather than individual bookings. Underpaying pre-sales relative to market rates is one of the fastest ways to lose strong Solutions Engineers to competitors, particularly as demand for AI-literate pre-sales talent in Europe continues to outpace supply.
What is the difference between a Solutions Engineer and a Pre-Sales Consultant, and does it matter which title you use when hiring?
In practice, the two titles often describe the same function, but the emphasis can differ. Solutions Engineer tends to signal a more technical profile, someone comfortable with integrations, APIs, and hands-on POC work, while Pre-Sales Consultant often implies a stronger consultative and commercial orientation. At an AI company, the title you use in a job posting will influence which candidates apply, so it is worth being deliberate. If your deals require deep technical work and integration scoping, Solutions Engineer will attract the right profiles. If the role skews more toward business case development and stakeholder management, Pre-Sales Consultant may resonate better.
How do you prevent pre-sales from becoming a bottleneck as the sales team scales?
The most effective way to prevent pre-sales from becoming a bottleneck is to build scalable assets alongside headcount: standardized demo environments, reusable POC frameworks, documented answers to common technical and security questions, and a library of use-case-specific collateral. This allows each pre-sales professional to support more deals without sacrificing quality. Pairing this with a clear escalation model, where AEs handle lighter technical conversations independently and only pull in pre-sales for qualified, complex opportunities, keeps the function focused on the work that actually moves deals forward.
At what stage of company growth should an AI startup consider splitting pre-sales into specialized sub-roles?
Most AI startups benefit from generalist Solutions Engineers in the early stages, but specialization starts to make sense once the pre-sales team reaches four to six people or when the product expands into meaningfully different verticals or use cases. Common splits include separating POC engineers from demo and discovery specialists, or creating vertical-focused Solutions Engineers who develop deep expertise in a specific industry. The risk of specializing too early is reduced flexibility and higher hiring costs; the risk of specializing too late is pre-sales professionals who are spread too thin to develop genuine expertise in any one area.
Related Articles
