Skip to main content

Beta candidates wanted About the beta

← All insights

Individuals

How to discuss AI with enterprise buyers without turning model output into evidence

ASTRA Ready editorial ·

Cover image for How to discuss AI with enterprise buyers without turning model output into evidence

An AI assistant drafts a confident answer to a customer question in seconds. The wording is cleaner than the seller's notes and the recommendation sounds plausible.

The temptation is to send it.

The problem is not that AI always invents facts. The problem is that fluent language can hide where the evidence stops.

NIST published its Generative Artificial Intelligence Profile on 26 July 2024 as a companion to the AI Risk Management Framework. The profile identifies risk areas specific to generative AI and describes actions organisations can use to manage them. [Source: NIST, 26 July 2024.] It is not a sales manual, but its core discipline is useful for customer-facing work: treat generated output as something that must be governed and evaluated, not as proof simply because it is coherent.

Start by separating four layers

The first layer is the source evidence.

That might be a test result, approved datasheet, contract term, assurance report or customer note. It is the material that can support a factual statement.

The second layer is the AI-generated draft.

The draft may organise the evidence well. It may also compress qualifications, join two facts that were never linked, or use a stronger verb than the source supports.

The third layer is the operating control.

Was the output reviewed? Who approved it? Is the AI allowed to trigger an action, or only draft? What happens when the evidence is incomplete?

The fourth layer is the customer decision.

What can the buyer reasonably decide from the evidence you actually have?

Keeping those layers separate prevents the draft from becoming its own source.

Ask the AI to show its boundary

If you use AI to prepare customer language, give it the evidence and tell it to work only from that material.

Then ask for three things: the claim it can support, the evidence behind the claim, and what it cannot establish.

This is more useful than asking, “Is this statement accurate?”

A model may answer that question from general knowledge or from patterns that sound likely. A seller needs a traceable answer tied to the material the customer or supplier is actually relying on.

Beware of helpful extrapolation

The most dangerous sentence is often not an outrageous claim.

It is the sentence that moves one step beyond the evidence in a way that sounds commercially helpful.

A pilot in one workflow becomes readiness for a wider population. A supplier control becomes evidence about the customer's configuration. A draft support response becomes an operating commitment. A successful demo becomes a statement about production reliability.

The extension may be small, but the customer can make a real decision from it.

That is why reviewing only for obvious hallucinations is not enough.

Keep model performance separate from workflow performance

Suppose an AI-assisted process produces good customer outcomes because every draft is checked by a human reviewer.

The observed result belongs to the workflow: model plus reviewer plus operating rules.

If the sales message says the model itself achieved the outcome, it removes the control that contributed to the result.

That distinction matters when customers ask whether review can be reduced, whether the workflow can be automated or whether the same result will hold at a different scale.

Enterprise buyers may ask questions about regulation, security controls, privacy terms or contractual responsibility.

AI can organise the approved material you paste. It should not become the authority that decides whether a customer is compliant, whether a legal obligation applies or whether a report proves a control it does not cover.

Route those decisions to the authorised owner.

The seller's role is to keep the question moving without turning uncertainty into a promise.

A useful final check

Before sending AI-assisted customer wording, ask:

What exact source supports the strongest sentence? Does the source cover the same customer, environment, period and population? Did a human or technical control contribute to the result? Is an approval still open? Which words would you change if the source were shown beside the email?

If the answer survives those questions, AI has helped you draft faster without weakening the evidence boundary.

That is the productive use of AI in sales: acceleration with judgment still attached.

Next step: Build evidence-led AI and technology sales judgment through the ASTRA Tech Sales Advisor programme: https://www.astraready.com/programmes/

Sources