AI FOMO in Sales: When Customers Ask for AI Before the Product Is Ready

When customers ask for AI before the product is ready, sales answers best according to the actual maturity of the capability and with a dated plan instead of a promise. The question usually has its origin in procurement, the boardroom or a competitor, and whoever understands that origin can answer honestly and still sell. This article provides a response matrix, a checklist for customer questions and a plan for the first 90 days.

The pressure is real. In tenders and first meetings, and in renewal rounds, the question “What are you doing with AI?” now comes up regularly, and sales teams sense that silence reads as falling behind. From this situation arise promises that the product cannot yet keep. This article shows how executives and sales leadership turn the pressure into a plan that holds.

Why do customers ask for AI before the product is ready?

Customers ask for AI because the question has become standard in procurement and in boardrooms as much as among competitors, and not every question describes a concrete need. Eurostat figures published in May 2024 show that in 2023 only eight per cent of enterprises in the EU with ten or more employees used AI technologies. Curiosity is therefore far greater than experience, and many buyers ask because somebody internally asked them. A board wants to show in the quarterly conversation that the company is engaging with AI, and the procurement department therefore appends a section on AI to every tender.

Four motives usually lie behind the question. The first is an internal requirement the buyer has to meet without a need of their own. The second is a comparison with a competitor who mentioned AI in their offer. The third is a genuine use case, such as faster quotations or less manual processing. The fourth is uncertainty about the future of the customer's own supplier: the customer asks whether the vendor will still keep up in two years. Each motive requires a different answer, and the checklist below helps to recognise it within one conversation.

For executives this means that the question about AI is a signal and not a requirement. Anyone who treats it as a requirement quickly builds features no customer pays for. Anyone who reads it as a signal first clarifies which motive stands behind it and prioritises afterwards. The logic resembles what the article on AI FOMO in companies describes in general: pressure turns into a plan only when the objective and baseline are known and owners are fixed.

How should sales answer when the AI capability is not ready yet?

Sales answers on the basis of maturity: it says what is in productive use today, what runs in a pilot with customers and what is on the roadmap, each with a date and an owner. The response matrix assigns four levels.

The matrix prevents two mistakes. The first is exaggeration: a level 1 capability is sold as level 3, and after signing the customer finds that it does not exist. The second is silence: a company at level 1 or 2 gives away credibility because it does not show its actual experience. An honest level 2 report with a measurable figure carries more weight in negotiations than a general announcement.

With the maturity level in hand, sales also knows where to ask targeted questions. Which of the customer's processes would benefit from AI? Which measure is to change? Who decides on its use? These questions turn a signal into a conversation about business results. That is the conversation that justifies an offer, and it succeeds only if sales receives the answers from product development. The article on AI washing describes the other side: customers increasingly test vendors for empty promises.

What does an over-promise cost in sales?

An over-promise costs sales the value of unplanned development time and a customer's trust, which cannot be measured. The calculation shows the measurable side. The example is illustrative.

1. Contract value: a customer signs an annual contract for 120,000 euros, with a verbal promise of an AI feature.
2. Development effort: the feature needs 400 development hours at 90 euros fully loaded, that is 36,000 euros, plus effort for testing and support.
3. Displacement: those hours are missing for planned product work, for example a feature promised to several customers.
4. Risk: if the feature slips by a quarter, the customer threatens to cancel or asks for a discount. A 15 per cent discount removes a further 18,000 euros.
5. Result: 54,000 euros of extra cost or lost revenue face a contract value of 120,000 euros, before follow-on orders and reference value are considered.

The calculation is a pattern and can be filled with your own values. It shows that a promise makes sense only if the capability is backed by a date and capacity. And it shows why executives must set the framework: individual sales staff cannot commit development capacity. The article on checking AI success stories shows how to assess the other side, the claims made by competitors.

How do executives turn the pressure into a plan?

Executives turn the pressure into a plan by collecting customer questions, ordering use cases by value and feasibility and fixing owners and dates for the first two initiatives. The plan covers 90 days and has four steps.

1. Weeks 1 to 2, collect questions: sales documents in a simple list which customer asked which question about AI and with what motive. After two weeks patterns appear.
2. Weeks 3 to 4, determine maturity: product management and engineering set the maturity level of each AI capability with sales, using the matrix, and write the standard answers.
3. Weeks 5 to 8, assess use cases: the executive team rates the cases by value and feasibility and selects two at most. How to tell whether competitor pressure is real is described in the article on AI competitive pressure.
4. Weeks 9 to 13, pilot with customers: one use case starts with two or three customers, with one measure and one owner. After the pilot the report becomes a reference in sales.

The plan has a further benefit: it gives sales a story. Sales can tell the customer: “We are piloting in the fourth quarter with two customers and will report the results to you.” That is concrete and verifiable, and it gives the customer the reassurance behind the question.

Supporting AI FOMO in sales with Niehues Consulting

Niehues Consulting is a consultancy for AI management and organisation design from a delivery perspective, based in Düsseldorf. Founder Marin Niehues brings AI into operations, in projects from VC-funded scale-ups to DAX 40 groups and in more than 20 countries on six continents. In the service area of AI management the work includes business analysis and the business case as well as the selection and sequencing of applications, which are exactly the steps that turn customer pressure into a dependable sequence.

The approach follows the Niehues Delivery Model with its three phases of Understand, Build and Introduce. Three of its test questions matter for handling customer questions about AI: Which business result is to change measurably? Does the prototype prove the benefit in the real process with real data? Which measure shows after 90 days that the solution has landed? The entry point is a free initial consultation of 30 minutes, which you can arrange via the contact page.