How solution engineers grow deal size, not just win rate
OpineWin rate tells you whether a solution engineer (also called a sales engineer or SE) helped close a deal. Deal size tells you how much of the opportunity they actually uncovered. Solution engineers increase average deal size by widening the evaluation: validating more use cases, engaging additional teams, anchoring value in the buyer’s own numbers, and mapping the next purchase.
This guide is for presales leaders and SEs who want to move beyond win rate. It breaks down why deal size is the most overlooked growth opportunity in presales, the 5 levers SEs control to expand contract value, and how to measure that impact in a quarterly business review (QBR).
Why should solution engineers care about average deal size?
Sales engineers should care about deal size because they decide how much of the opportunity the evaluation proves. The contract rarely pays for more than what was validated, no matter how convincing the demo felt.
Most presales scorecards stop at technical win rate. That number matters, but it treats every deal as the same size. An SE who wins a one-team pilot and an SE who expands that same pilot into a three-team rollout both record one technical win. Discovery and the scope of the evaluation determine the gap between those two outcomes. Both sit firmly in SE territory.
The account executive (AE) owns the commercial negotiation. The SE decides what gets proven, for whom, and at what scale. If the evaluation proves only one use case, expect the contract to pay for only that.
Presales leaders already judge presales on top-line revenue. In a 2026 survey of 423 presales professionals by Consensus, the most common presales KPI was closed revenue or ARR, used by 78% of respondents. Technical win rate trailed both revenue and activity metrics.
If revenue is the scorecard, deal size is the part of it an SE can influence directly.
Then there’s capacity. Presales hours are finite. When your team’s effort yields larger deals, the same headcount delivers significantly higher revenue.
Benchmark data from the Alexander Group illustrates this link: sales teams with a 1:1 SE-to-rep ratio averaged $3.2 million in revenue per rep, compared to $2 million per rep for teams operating at a 1:5 ratio. That correlation underscores the core case presales leaders make when requesting headcount.
Gainsight measured this shift directly on its own team: after centralizing deal context in Opine, the presales organization reported a threefold increase in closed-won dollars per SE hour.
5 levers solution engineers can use to increase average deal size
1. Run discovery beyond the first use case
The first use case got you the meeting, but it’s rarely the only one. Treat it as the trailer and go find the rest of the movie.
Ask who else touches the system you’re replacing and which adjacent teams share the problem. Then ask what the buyer would do next if the first project succeeds.
Record every additional use case on the opportunity, even if they sit out of scope for the initial evaluation. A use case written down is a capability the AE can price.
Most teams skip this step. In that same survey by Consensus, 73% of presales teams said they run only minimal or informal discovery before a demo, despite respondents ranking discovery as the activity most likely to improve outcomes.
Go wide in discovery, stay narrow in the plan. Wider discovery doesn’t mean a bigger POC. Keep the Must-Have list to the few criteria that decide the deal, and log every other use case on the opportunity as a Phase 2 list. The evaluation stays short, and the AE still has the rest of the opportunity to price.
2. Validate with more than one team
Every extra team in the evaluation is another team that can justify budget. Budget, it turns out, enjoys company.
Invite a second group to rate the success criteria that affect them. Their sign-off turns an expansion conversation into part of the initial deal.
Breadth on the buying side correlates directly with win rates. Gong analyzed 1.8 million new-business deals closed in 2024 and found that won deals included twice as many buyer contacts as lost deals. Multi-threading also lifted win rates by an average of 130% in deals over $50K.
3. Put the value in the buyer’s numbers
Buyers discount what they can’t quantify. Tie every success criterion to a business outcome the buyer already tracks and cares about: hours saved, incidents avoided, or time to deploy.
A criterion that reads “reduces manual triage” is a feature. Rating it will require subjective opinion. One that reads “cuts triage from 2 days to 4 hours for the platform team” is a line item in the buyer’s business case that can be objectively rated and will naturally increase confidence in the value of the solution. Use the buyer’s figures, not your own estimates.
Here are more examples of how to reframe product features as buyer metrics:
| Product feature (subjective) | Buyer metric (objective) |
|---|---|
| Provides automated monitoring alerts | Cuts mean time to detection (MTTD) from 45 minutes to 3 minutes for Tier-1 apps |
| Simplifies user role provisioning | Reduces IT helpdesk tickets for access requests by 60% in Q1 |
| Accelerates report generation | Saves 8 hours per week for 5 data analysts |
Clear value moves more than the price; it changes how buyers feel about the purchase. In 2026 research by Gartner, analysts found that confident buyers are twice as likely to report a high-quality deal compared to buyers with low decision confidence.
4. Prove scale before procurement asks
Deals shrink at procurement when the buyer isn’t sure the product will hold up at full volume. If the evaluation proves performance, security, and integration at full-deployment scale, there’s less reason for the buyer to start with a smaller commitment. Add a scale criterion to every plan where the full rollout is bigger than the pilot.
5. Tie product gaps to the revenue they block
Sometimes a larger deal hinges on a feature the product can’t yet deliver. Record that gap directly against the deal along with the total revenue at stake.
Logging the blocker gives the product team a clear business reason to prioritize the fix and gives the AE an honest answer about timing. A gap that lives in a Slack thread dies there, and takes the opportunity for a larger deal with it.
How to close, and a word of caution
Be careful to note if expanding the use cases will also expand into additional stakeholders who have the power to say no or prolong your deal cycle. In those situations, landing the deal on the initial use cases and lining up the additional use cases you’ve noted for a rapid expansion is the best way to close these larger deal sizes.
What gets in the way?
The deal growth levers are simple enough. The habits that undermine them are sneakier:
- Evaluation plans are built from scratch. When every plan starts from a blank spreadsheet, SEs default to the narrowest version that will close.
- Discovery notes live in a single person’s head. Additional use cases surface on a call or in email, and often fail to reach the opportunity record or get priced.
- SE time isn’t tied to deals. When hours aren’t tracked on the opportunity, leadership can’t see if the team is over-investing in small wins or neglecting the deals with real room to expand.
- Product requests are anecdotes. Without revenue attached to them, the gap that blocks a larger deal looks like any other feature request.
How do you measure an SE’s effect on deal size?
Use metrics tracked directly on the deal record, so your numbers survive their first skeptic.
| Metric | What it tells you |
|---|---|
| Average deal size with and without SE engagement | Whether SE involvement changes how much customers buy |
| Change in deal value from first proposal to close | Whether the evaluation grew the deal or shrank it |
| Number of use cases or teams validated per evaluation | How wide the evaluation ran |
| Closed-won dollars per SE hour | Whether SE effort is aligned with deal size |
| Revenue attached to open product gaps | How much larger the deals could have been |
Compare like with like. Segment by deal type and region before comparing SE-engaged and non-engaged deals, because SEs are often assigned to the larger opportunities to begin with. Report the median alongside the average.
How Opine helps SEs grow deal size
Every lever above runs on the same thing: knowing what actually happened on the deal. Opine keeps one record per opportunity, built from the calls, threads, CRM fields, and evaluation plan behind it. That record turns the 5 levers from individual heroics to consistent collective habits.
- Evaluation plans start from your team’s success criteria library and templates, so the scale and multi-team criteria are in the plan from Day 1.
- Calendar-based technical hours sit alongside pipeline and closed-won revenue, per person and date range, in SE utilization and team activity. No timesheets required.
- Product gaps carry the revenue riding on them through revenue impact and blocker analysis.
The upshot: your presales team can prove its dollar impact using hard data from the record, not memory, which tends to be generous.
To see where your own team’s hours went last quarter and what they produced, put every technical hour next to the deal it was spent on.
FAQ
Can sales engineers really influence deal size?
Yes. The SE decides what the evaluation proves and for whom, and what gets proven usually sets what gets bought. When presales validates multi-team use cases early, the commercial contract grows by default.
What is the difference between technical win rate and deal size as SE metrics?
Technical win rate counts whether the buyer validated your solution. Deal size measures how much of the opportunity that validation covered. Tracking both keeps a team from chasing narrow, easy wins.
How do you attribute deal size growth to presales?
Compare the amount at first proposal with the amount at close, and record which use cases and teams the evaluation added. Segment by deal type so you’re not crediting SEs for deals that were large from the start.
Should SEs talk about pricing?
SEs usually leave pricing to the AE. Their job is to make the value concrete and the scale credible so the AE can price the full opportunity.
Should I report average or median deal size?
Report both. The average shows total dollars, and the median shows the typical deal. When the two are far apart, a handful of large deals is driving the number, and that is worth saying out loud in the QBR.
