AI sales evaluation

AI sales pilot KPIs and how to evaluate them

Which KPIs should an AI sales pilot measure?

An AI sales pilot should measure qualified replies, meetings, exclusion reasons and human review time alongside send volume. Use consistent denominators when comparing rates, and record counts and working time separately. Agree definitions and continuation criteria before starting.

Who this is forSales managers and operations staff planning a short AI sales validation

Two to four weeks is an indicative validation period. The time needed to track deals depends on the offering's buying cycle.

Agree continuation criteria before the pilot

A proof of concept is a small trial to assess effectiveness and operational workload before adoption. For AI sales, this involves running prospect selection, research, message review, sending and reply handling in practice.

Two to four weeks is one indicative period. An offering with a long buying cycle may not produce a deal during that time. Review reply content and staff time as well as completed deals.

Record counts, rates and working time separately

Scroll horizontally to view the table.

Metric What to record What to check when aggregating
Valid sends Sends excluding unknown recipients and delivery failures Keep separate from the number of drafted messages
Qualified replies Replies that can lead to the next conversation Separate automated replies and opt-outs
Meetings Cases that progressed to scheduling Decide the counting stage before starting
Exclusion reasons Offering mismatch, timing or the wrong contact Reflect these in future selection and exclusion criteria
Human review time Time spent reviewing recipients and wording and handling replies Record separately from the proportion automated

Use consistent denominators when comparing reply rates. For example, if valid sends are the denominator, use the same definition for each period. A rate using drafted-message count as its denominator is not directly comparable.

Qualified reply rate is calculated as qualified replies ÷ valid sends × 100. This formula does not apply to working time or exclusion reasons. Record counts, rates, time and reasons separately.

Distinguish replies by content

Replies include interest, questions, introductions to another contact, unsuitable timing and opt-outs. A total reply count mixes these different responses. It cannot distinguish replies requiring further action from contacts that should be excluded.

Review actionable replies to progress toward meetings. Use out-of-scope replies to revise selection criteria and wording. Do not count opt-outs as results; add them to the exclusion list.

P2GM recorded interim and final results

During the P2GM validation, the interim figures were 173 valid sends, six replies, two meetings and one order. At the end of four weeks, the figures were 203 sends, seven qualified replies, two meetings and two deals.

Interim and final figures can differ. Record sending, reply, meeting and deal dates so that progress after the initial send can be evaluated.

These results reflect specific conditions, including P2GM's offering and target companies. Other engagements may not achieve the same outcomes.

Decide whether to continue, retest or stop

After the pilot, decide whether to continue under the same conditions, revise the conditions and retest, or stop for now.

High send volume does not justify scaling if out-of-scope replies continue and review takes too much time. Also check whether specific questions and meetings arise, and whether the reason for choosing each prospect can be explained.

Read the P2GM validation conditions and results alongside this guide.

Evidence and sources

Based on CosmoSketch's evaluation approach and a four-week initial validation at P2GM Inc.

Author

CosmoSketch Inc.MAILGORI development and operations team