Late in a deal, the buyer stops asking whether your product is good and starts asking whether they can live with switching to it. How long will this take. What will slow it down. How much of my team’s time will it eat. These questions rarely go to your sales rep, because the buyer knows the rep’s answer will be optimistic. More of them now go to an AI engine.
So in November I asked Google AI Mode three of them, about three well-known products: a conversation intelligence platform for sales teams, an HR and payroll platform, and a compliance automation tool. Each question gave a team size and asked for a realistic timeline and what delays it. Then I read every source behind each answer.
Two answers came mostly from other people
The sales platform’s answer used 10 sources. Three were the vendor’s own: its homepage, its community forum and a legal page on implementation services. The other seven came from five software companies that sell to the same sales teams, several of them direct alternatives.
The headline, 6 to 8 weeks to roll out and 3 to 6 months to real value, was attributed first to a rival’s post titled around why the product takes six months and costs $200K to implement. A claim that one CRM integration takes far longer than another came from a second rival’s blog. One of the delays it listed came from reviews compiled by two of the rivals. The vendor’s community forum supplied advice about reps pushing back. Its legal page supplied a catch: a clause saying implementation sessions must be used within 30 days of the contract starting.
The HR platform’s answer used 7 sources. One was the vendor’s own, a general blog post about HR system implementations. Two were from the payroll provider the buyer said they were leaving, including that company’s own guide to switching to this exact rival. Two were from a consultancy that runs these migrations. The rest were comparison blogs. The answer laid out a clear eight-week plan, and the section on what usually delays the move cited the provider being left first.
That one is worth pausing on. The buyer was leaving a company, and that company’s pages explained to them how hard leaving would be.
One answer came mostly from the vendor
The compliance tool was Vanta, and its answer was different. Of 9 sources, 3 were Vanta’s own: a page on SOC 2 audit timelines, a guide to SOC 2 for startups, and an explainer on what SOC 2 is. The headline, 4 to 8 weeks to get set up and audit-ready, was attributed to Vanta first. A consultant’s LinkedIn post, an audit firm, a few competitors and other sites filled in detail.
Vanta did not win this by saying its product is fast. It had published a specific page on the exact question, how long a SOC 2 audit takes, and the answer it led with was not flattering: weeks to be ready, months to have a Type 2 report in hand. That is the answer the buyer was looking for, so the engine had no need to find it elsewhere.
Why this matters more than it looks
Implementation time is where a late-stage deal quietly dies. The buyer has picked you, then the timeline sounds like a quarter of their team’s attention, and the decision slides to next year. If the number they heard came from a competitor’s “why it takes six months” post, you lose the deal at the point you thought it was won.
It is also a question vendors tend to avoid in public. The honest answer depends on the customer, so the safe move is to say nothing and let sales handle it. But the engine will answer anyway. When you have not published a realistic timeline, the realistic timeline it quotes is someone else’s, and the people most motivated to write one are your competitors and the vendor you are replacing.
This is the same mechanism we found with integration questions and with pricing. A buyer asks something specific, and the engine builds the answer from whoever wrote the most specific page.
What to do
Ask the question the way your buyers ask it. “How long does it take to implement [you] for a [size] team.” “Moving from [incumbent] to [you], what delays it.” Use team sizes and incumbents from your real pipeline. Run each several times, and note every source.
Publish a realistic timeline page. Not “live in minutes”. The page that worked here answered the exact question with an honest range. Give a range, split it into phases, say what the customer’s team has to do in each, and name the things that cause delays. Do it per segment if the answer genuinely differs, for a small team and a large one, or for one integration and another. If your typical rollout is six weeks, say six weeks. A credible six from you beats an alarming six months from a rival.
Name the delays before a competitor does. Every answer had a “what slows it down” section, and most points in it were things the customer controls: messy CRM data, security approvals, migrating mid-year, getting staff to finish setup. Write that list yourself, with what you do to help. It reads as expertise, not weakness.
Write the migration guide from each incumbent. If buyers are moving to you from a specific product, the most specific page about that move should be yours. Otherwise the incumbent’s “how to switch” guide becomes the reference, as it did here.
Check your contract terms read the way you mean. One point the sales platform’s own site supplied was a 30-day deadline on implementation help. That was a legal page doing customer communication. If a term like that exists, explain it in plain words on a page buyers will read, before the engine quotes the legal version.
What I got wrong
I assumed the engine would treat a vendor’s own timeline as marketing and lean on third parties regardless. The Vanta answer showed otherwise. When a vendor has published a specific, honest page on the exact question, the engine leads with it. The vendors that lost the answer were not out-argued. They simply had not published the page.
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, not a measurement. Run your own questions before you act on mine.
Where this leaves you
Late in the deal, your buyer asks an engine how long rolling you out will take. If you have published an honest timeline, they will probably read yours. If you have not, they will read a competitor’s, or the incumbent’s guide to how hard leaving is. You know your real rollout time better than anyone. Write it down where the engine can find it.
If you want to see what the engines tell your buyers about rolling you out, and who wrote it, that is part of the engagement, and it runs on a documented method.
1 response