Your website quits at the shortlist

Evaluation is now the longest stage of a B2B software purchase, having overtaken research for the first time. Once a vendor has been chosen, the single biggest source of delay is IT security review, cited by 39% of buyers and by 50% of enterprise buyers. Budget approval follows on 32% and implementation planning on 25%. The figures come from the G2 2026 Buyer Behavior Report, published in July.

Most B2B websites are built for the stage that is no longer the bottleneck. The homepage, the positioning, the case studies, the single confident call to action: all of it is engineered to get a company onto a list. Once it is on the list the site runs out of things to say, and the buyer spends the longest and most fragile weeks of the purchase reading documents nobody at your end has written.

Getting on the list got cheaper

82% of buyers in the same survey had sourced software recommendations from an AI chatbot in the previous two years. Discovery is faster, wider and only partly under your control, which means being found is no longer the scarce thing. Surviving the fortnight after being found is.

That is an odd place for a budget to stop. The front of the site gets attention, iteration and a redesign every few years. The part of the process where deals now actually die gets a PDF and an email address.

Your champion is not the one reading

By the time a security questionnaire lands, your champion has stopped reading the website. They are already convinced. They have spent internal credit making the case and are now defending it to people who were not in the room.

Those people arrive with different jobs. An IT reviewer has a list of questions and a deadline. A finance director is looking at a renewal cycle and a number: nearly half of software buyers in that survey said their CFO vetoed a deal the team had already approved in the last year. Somebody in operations is trying to guess how many weeks implementation will take.

None of those readers is looking for a reason to buy. They are looking for a reason to stop, because stopping is free and being wrong is not. An unanswered question is a reason to stop.

Your champion has stopped reading. The people reading now are looking for a reason to stop.

Write the answers down

Most of a security questionnaire is the same questionnaire every time. Where customer data is physically stored, and under whose law. Who inside the company can see it, and how that access is logged. What happens to the data when a contract ends. Which subprocessors are involved. Which certifications are held, and which are not. What the incident history is, and where it is published. What contract lengths will genuinely be agreed.

Those are pages. Dated, at stable URLs, written in the same voice as the rest of the site, maintained by whoever would have had to answer the email anyway. They are dull, and they are read more carefully than anything else you publish.

Hosting worked this out a long time ago

In hosting none of this is novel. Providers tend to publish their stack, their data centre locations, a live status page and a documented migration process, because a technical buyer will go and check rather than ask, and vagueness reads as something being hidden. That is the audience we spend most of our time designing for, and it is a useful one to borrow from. Technical buyers punish decoration and reward a page that answers the question.

The rest of B2B is now meeting the same reader, just later in the process and with less warning.

A gate is a week

The instinct is to gate all of it. Contact us for our security documentation. That adds a round trip to the stage that is already the longest one in the purchase. Your buyer sends an email, waits two days, receives a PDF, finds it does not answer question fourteen, and sends another email. Every gate is a week, and you are being compared with somebody whose answer did not need an email at all.

There is a second reason now. Buyers who source a shortlist from a chatbot will point the same tool at your documentation, and paste what comes back into a deck. A public page written in plain sentences can be quoted. A PDF behind a form cannot be quoted, because it was never read.

The same logic applies to the second largest delay on the list. Budget approval stalls when the first real number appears in week five, which is most of the case for putting prices on the site.

None of this is a redesign

It is four or five pages nobody wanted to own, written once and then kept true. No new navigation, no new template, no discovery phase, no agency required for most of it.

They will never be the pages anyone shows off. They are the pages that decide whether the ones you do show off were worth building.