Presales KPIs: Capacity, Conversion, and Deal Support

A presales KPI should show how technical selling capacity is used and what happens to the opportunities it supports. Pair workload with proof-of-concept outcomes and closed-deal conversion; support hours alone cannot tell you whether the work helped a buyer decide.

Define the work before measuring it

Presales can include discovery, technical validation, security review, and proof-of-concept work. Decide which activities qualify as opportunity support, then apply that definition to every specialist. Keep enablement, internal meetings, and leave outside the support-hours numerator if they are outside the capacity denominator.

An engagement is not automatically a proof of concept. Require an agreed success criterion and a recorded outcome before calling it passed or failed. A postponed evaluation is unfinished, even if the specialist has already spent substantial time on it.

The distinction between a KPI and an ordinary metric matters here. Hours become a management measure when they answer whether the team can take on the work requested. A count of presentation files usually does not answer that question.

Use separate populations for the questions. A monthly workload report includes hours logged that month. A completed-evaluation report includes evaluations finished that month. A closed-deal conversion report includes supported opportunities closed that month. These populations can overlap without being identical.

Start with an opportunity-level support export

Consider a US business software company reviewing April 2026. Its support export has the following rows. Hours are April support hours; outcomes are statuses at April month-end. Every closed opportunity shown closed in April, and every completed proof of concept shown finished in April. The booked amount is the contract amount recorded on won opportunities, not recognized accounting revenue.

Keep the underlying time entries and opportunity IDs. If several specialists support the same deal, sum their hours to the opportunity before joining the opportunity amount. Otherwise, a deal's value repeats for every support entry and inflates the supported book.

The capacity export is separate:

Available hours are the scheduled hours designated for opportunity support after other commitments. They are inputs from the staffing plan, rather than an assumption that every paid hour can be sold.

Calculate capacity and outcomes separately

Support capacity used = Support hours / Available support hours

Completed proof-of-concept pass rate = Passed evaluations / Passed and failed evaluations

Supported-deal win rate = Won supported opportunities / Won and lost supported opportunities

The capacity calculation is 120 / 200 = 60.0%. Avery's hours are 30 + 25 + 20 = 75; Blake's are 15 + 20 + 10 = 45. The overall spare capacity does not prove that either specialist has the skills or calendar availability needed by the next request.

There are three passed evaluations and one failed evaluation. Pass rate is 3 / 4 = 75.0%. P103 is unfinished and P106 had no proof of concept, so neither enters that denominator.

There are two won and two lost opportunities. Supported-deal win rate is 2 / 4 = 50.0%. P105 passed its technical evaluation but was lost commercially. That is useful evidence that technical validation and a purchase decision are different events.

With the opportunity table in columns A:F and its detail rows in rows 2:7, these Excel formulas reproduce the figures:

=SUMIFS(C2:C7,B2:B7,"Avery")
=COUNTIFS(D2:D7,"Passed")/(COUNTIFS(D2:D7,"Passed")+COUNTIFS(D2:D7,"Failed"))
=COUNTIFS(E2:E7,"Won")/(COUNTIFS(E2:E7,"Won")+COUNTIFS(E2:E7,"Lost"))

Microsoft documents SUMIFS for summing values that meet criteria, and COUNTIFS for counting rows meeting the specified conditions. If a conversion denominator is empty, report no completed outcomes rather than zero conversion. Percentages here are rounded to one decimal place.

Prove the totals before interpreting them

Reconcile hours in both directions. Avery's 75 plus Blake's 45 equals 120. By deal status, won opportunities consumed 30 + 15 = 45 hours, lost opportunities consumed 25 + 20 = 45, and open opportunities consumed 20 + 10 = 30. Those groups also total 120.

Then reconcile the opportunity population: two won, two lost, and two open deals account for all six opportunity IDs. The $200,000 of booked amount is $120,000 + $80,000, with each won ID included once. Tie the complete support-hours export to the time record before assuming the displayed rows cover the team.

These checks establish consistency, not causation. The table does not show how the same deals would have performed without presales support. It cannot establish that adding support hours would raise win rate.

Turn the review into staffing and qualification decisions

The presales manager owns capacity definitions and assignment decisions. The example supports a discussion about moving suitable work from Avery to Blake, subject to expertise and customer schedules. It does not justify a hiring decision without examining the work that could not be accepted and the pattern over comparable periods.

Sales operations owns the deal population and the dates that determine conversion. Review technical passes that become commercial losses with the account team. A pass can remove technical risk while leaving budget, timing, or procurement unresolved.

For the broader sales scorecard, use KPI examples by team. After a deal closes, customer KPIs address the customer relationship, while helpdesk KPIs cover support delivery. Those measures should not be folded into presales conversion.

Where it goes wrong

• Counting open evaluations as failures. This mixes incomplete work with completed outcomes and penalizes a growing book.
• Repeating contract amounts across time entries. Aggregate hours separately and keep one opportunity amount per opportunity ID.
• Changing available capacity. A denominator before leave in one month and after leave in another creates a misleading utilization trend.
• Ranking specialists without assignment context. Enterprise security work and short product checks can require different effort and have different buying cycles.
• Calling booked amounts revenue. Contract value and accounting revenue answer different questions; label the source field precisely.

Covirage is not affiliated with Microsoft.

Check presales performance on your own file in Covirage

Bring your support-hours file, opportunity export, and available-capacity sheet. Covirage maps the columns, and its tools compute and check workload and outcome comparisons; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.

See Covirage for sales teams for the wider sales review.