Your customers ask AI about you before they renew. It coaches them to pay you less.

/ 7 min read / By Faz

Most of what gets written about AI search is about winning new buyers. But the people asking the engine about your product include the ones already paying you. A renewal notice lands, the price has gone up, and someone on the customer’s team types the question they would not ask your account manager: is it worth switching, and how hard is it to leave?

I wanted to know what they hear. In November I asked Google AI Mode three questions, written the way a customer would ask them, about three well-known products: a help desk platform, a CRM, and a work management tool. Each named the product, the renewal, and the worry. Then I read every source behind each answer. I have left the products unnamed, because nothing here is a criticism of their teams. It is a pattern any established vendor could find in its own answers.

The answers mostly said stay

I expected the engine to push these customers toward competitors. It did not. None of the three answers said to leave.

The work management answer opened with “Do not switch” unless the tool was actively blocking the team or the price rise could not be justified, and pointed out that three years of habits, templates and project history are expensive to recreate. The CRM answer said moving with two months to go was risky, and that migrating and retraining often costs more in lost productivity than the first year of savings. The help desk answer said it depended on team size and complexity, and described migrating as moderately hard, because data moves but every automation has to be rebuilt by hand.

That sounds like good news for the vendor. Read on and it is less so.

Then they told the customer how to pay less

All three answers gave the customer a plan for the renewal conversation, and every plan cost the vendor money.

The CRM answer suggested auditing seats, removing inactive users, and checking whether the team really used the features in its tier. If not, it said, dropping to the lower tier would cut the bill by roughly 80 percent with no migration at all. The work management answer did the same: audit unused licences, and move from the upper paid tier to the lower one if the team did not use the features that justified it. It named the features and the prices.

Two of the three told the customer to bring quotes from competitors to the account manager as leverage. The help desk answer added that pricing varies widely across similar accounts, so pushing back at quarter-end could secure real discounts, and offered a middle path: keep the product for ticketing and buy a cheaper AI add-on from someone else.

So the threat these answers pose is not churn. It is contraction. The customer stays, on a smaller plan, with a discount, or with a rival’s add-on bolted on. The engine is acting as a negotiation coach, and it is coaching the other side of your renewal.

Who wrote the coaching

The three answers drew on dozens of sources between them. The vendors’ own sites appeared twice, and both times it was the pricing page. In the CRM answer, not a single page from the vendor was cited.

Everything else came from people with a reason to write it. For the help desk renewal, the sources included a rival’s guide to migrating away from the product, two more migration guides from other software companies, a rival’s pricing comparison page, and a guide to negotiating that product’s renewal specifically. For the CRM, they included three rivals’ pricing pages, a rival CRM’s post about the product’s hidden costs, and another rival’s explainer of its pricing. For the work management tool, pricing explainers from several software companies, some of them rivals, plus a thread in a competitor’s subreddit about moving across.

The details the customer heard were about contracts and packaging, not product. A 30-day notice period before renewal. Renewal prices allowed to rise to the current list price. A full data export that is off by default and has to be requested. A monthly cap on included AI requests, with a charge for each one over. I have not checked whether each of those is true today. The point is that every one of them reached the customer through a third party, in that third party’s words.

Why this lands at the worst moment

A renewal is when a customer is most likely to go looking, and least likely to ask you. The questions in these tests are not ones a customer puts to their account manager. They go to the engine, and the answer they get sets the agenda for the call.

We have written about buyers who arrive quoting AI to your sales team. Renewals are the same thing at the other end of the relationship, and the stakes are your existing revenue, not a pipeline number. Your customer success team walks into the renewal call while the customer holds a script that someone else wrote.

What to do

Ask the renewal questions yourself, in your customers’ words. Take the phrasing from your cancellation reasons, your churn notes and your support tickets. “Is it worth switching from [you].” “[You] renewal price went up.” “How hard is it to migrate off [you].” Run each several times, because the answer moves, and do it before the renewal season and not during it.

Treat your pricing page as a retention page. It was the only page of these vendors’ own that the engine read. These answers were already telling customers which tier to drop to and what they would save. So make the page say what each tier is for, which features justify the higher one, and who genuinely does not need it. That last part matters. If a customer would be fine on the lower tier, saying so honestly is more credible than pretending otherwise, and the engine already knows. The goal is that the customers who do need the higher tier can see why. This is the same idea as giving the engine a true anchor on pricing, applied to the customers you already have.

Publish your terms plainly. Notice periods, how renewal pricing works, how a customer exports their data. These answers learned all of that from rivals and from a negotiation guide. If your export takes a request to support, the engine will describe it in a rival’s words, as friction. The honest fix is to make exporting simple and say so plainly. A customer who knows they could leave easily and stays anyway is a better renewal than one who feels trapped.

Correct what is wrong at the source. If a “hidden costs” post or a migration guide has your terms wrong, get it corrected where it lives. A page on your own site will not outvote several pages written by people who want your customers.

Give your customer success team the answer before the call. Show them what the engine tells a customer in your category at renewal: the downgrade it suggests, the discount argument, the export detail. A renewal call that starts by addressing those points honestly goes better than one that discovers them halfway through.

What I got wrong

My starting assumption was that customers asking AI at renewal would be told to leave, and that the job was to win them back from the alternatives list. I had already written about what to do about your own alternatives page and expected this to be the same problem from the other side.

It was a different problem. The answers mostly argued for staying, and the damage came from how they told the customer to stay: smaller, cheaper, and with competing quotes in hand. Had I gone with my assumption, I would have told you to build pages about why customers should not leave, when the more useful pages are the pricing page and your terms.

These were single runs of three questions about three products on one engine, and Google offered to rerun them without personalisation. Treat this as a read of the pattern and not a measurement. Run your own renewal questions before you act on mine.

Where this leaves you

Your customers are asking the engine about you at the exact moment the contract comes up, and the answer is mostly written by your competitors and by people helping your customers negotiate. The engine may well tell them to stay. It will also tell them how to pay you less. Make your pricing page and your terms the clearest sources on your own product, so the coaching your customer hears is at least accurate.

If you want to see what the engines tell your customers at renewal, and who wrote it, that is part of the engagement, and it runs on a documented method.

Want this run for your B2B SaaS?

Founding pricing for the first 5 clients. Methodology fully public. Month-to-month, cancel anytime.

Apply to work together

1 response

Leave a comment

Your email address will not be published. Required fields are marked *