Follow Up After a Trial With Evidence

A trial is only as useful as the question it was meant to answer. A follow-up that asks whether the buyer liked it can miss the result entirely.

Read the signal

Trial users may have logged in but not performed the target task. Usage alone does not tell you whether the workflow worked, and nonuse may reflect a setup obstacle rather than rejection.

Make the next move

Review the agreed test plan and actual activity with the buyer’s permission. Ask what was attempted, what failed, and who can judge the outcome. Schedule a result discussion before the trial ends when possible.

Language you can adapt

Illustrative wording:

We agreed to test the approval flow with three users. Did they complete that task, and where did the process differ from what they expected?

The wording is a starting point. Replace the problem, evidence, and request with details the buyer actually gave you. If those details are missing, ask a question before sending a polished message. Specificity makes it easier for the buyer to correct your understanding and easier for you to see whether the opportunity is moving.

Decide what happens next

If the test did not happen, decide whether a limited reset is justified. Do not report the trial as successful merely because access was granted.

Write the result in your deal notes as an observable fact: who responded, what they agreed to do, and when. A friendly reply is useful, but a decision, a named owner, or a scheduled review tells you more. If the next step remains vague, treat that as information about the deal rather than a reason to send the same follow-up again.

Use these examples responsibly. Describe your product, pricing, and customer results accurately, and adapt every suggestion to the buyer’s stated process.