Sections
A technical company's website often does one job well. The animation of the process is clear, the publications page is full and every description of the technology is accurate. A scientist leaves informed. A buyer leaves without a reason to get in touch.
The usual fixes are a new button, shorter pages or more traffic. Each can help once you know where the visitor stops. Find that point first, then choose the fix that belongs to it.
Check who is arriving
Visit numbers say little on their own for a specialist B2B site. A page about an emerging technology draws students, researchers, journalists, competitors, investors and customers. Every one of them counts as a visit, and only some can start a sales conversation.
Before you decide the conversion is broken, find out whether buyers reach the site at all. Three readings from your analytics help, within what your consent settings allow.
Three readings before you judge the site
- Source
The search queries in Search Console show which questions bring people in. Read them as a buyer would. A buyer's query names an application, a specification or a problem in their process.
- Landing page
Visits that land on a general explainer and leave are one audience. Visits that land on an application or product page are another. Count them apart.
- Route
Follow the visitors who go from a product or application page to evidence, specifications or contact. That path is the one a buyer takes.
If almost nobody takes the buyer's route, the work starts with reach, through the pages buyers search for and the outreach that sends them. If buyers take the route and leave, the page is the place to look.
Find the stop
A buyer reads a technical site in a rough order. They recognise their problem, see that the page speaks to them, check the proof, find something to buy and look for a way to start. The visit ends at the first step that fails.
| Stop | What the visitor is left thinking | What you see on the page | Where the fix sits |
|---|---|---|---|
| 1. Recognition | The science is interesting and my problem is missing. | The opening explains the mechanism. The application, the beneficiary and the outcome come later or nowhere. | Message order. Move the buyer's problem and the outcome to the first screen. |
| 2. Relevance | I can't tell which part of this is for me. | Investors, research partners, manufacturers and buyers share one paragraph. | Audience and routes. Give the homepage one primary reader and each other reader a route. |
| 3. Proof | They say it works. I can't see under what conditions. | Words such as scalable, efficient or validated stand alone, with no test, reference point or stage beside them. | Evidence. Put the condition, the comparison and the stage beside the claim. |
| 4. Offer | I see what it could do. I don't know what they sell. | No product, sample, licence, development programme or evaluation is named. | Positioning and the offer, before any interface work. |
| 5. Action | I'd have to write the brief myself to get in touch. | One contact form serves every reader. | The next step. Name a step the buyer is ready for and the team can deliver. |
Fix the earliest stop first. A visitor who never recognises the problem never reaches the proof, so a new contact form leaves a recognition problem exactly where it was.
The first two stops come down to where the page starts. Thibaut Monfort-Micheo, co-founder of the seaweed packaging company FlexSea, described the same judgement for his own customers in our interview with him. "When speaking to a potential customer, I'd assume they have some knowledge and go directly to what sets us apart." A buyer's page can start where the buyer already is.
The third stop sits beyond the reach of design. In the same interview he put the standard in one line. "You need to be convincing in what you say and back your claims." Our list of ten website claims that need evidence beside them covers the words that most often stall a reader at the proof.
Run the reading test
Pick one product or application page. Find five people who resemble your buyer, such as a procurement lead, a plant manager or a technical buyer in your market. Show each of them the page with no introduction and ask five questions.
Five questions for the reading test
- What does this company sell?
- Which problem does it solve, and for whom?
- What has it proven, and what is still open?
- What would you do next, if anything?
- What would you need to see before you did it?
Write down their words, especially the misreadings. Then read the answers against the causes below.
Read the answers
- They misread what the company sellsThe cause is positioning or the offer. Agree what you sell first, then rework the page.
- They understand the offer and doubt the claimThe cause is the evidence, or where it sits on the page.
- They understand and trust it, and find no fitting next stepThe cause is the route and the call to action.
- They understand, trust it and find the next step, and still decline to buyThe cause sits outside the website. Check price, readiness, integration and the market.
Five people can show you where a page fails to explain. Measuring demand takes a larger study, so treat each answer as a clue to the cause. If the first row describes your team as well as your visitors, our guide to offer architecture shows how to choose the one offer a new customer meets first.
When the site works and the decision stalls
The last row of that test is common in industrial and science markets. A buyer can follow every page and still face switching costs, an integration they cannot staff, a supplier qualification that takes months or a budget held by someone else. A website leaves all of those in place.
When Better Communication Is the Wrong Answer works through the checks on evidence, economics, incentives, authority, capacity and regulation. If one of them fails, that is the work to do first. If the buyer needs colleagues to agree before anyone writes to you, the buying committee map shows who those colleagues are and what each one checks.
Name a step the buyer can take
A single contact form asks a serious buyer to write the brief from nothing. A named step tells them what happens after the click. For an industrial or science product, the step usually comes from this list.
Next steps a buyer can act on
- Request specifications
For a buyer comparing your product with what they use now.
- Request a sample
For a material or ingredient the buyer needs to test in their own process.
- Discuss site suitability
For equipment or infrastructure that depends on the buyer's site.
- Access qualification documents
For a buyer whose supplier approval needs paperwork before a trial.
- Arrange an evaluation call
For a buyer facing high switching costs, who needs a qualification conversation before any commitment.
Offer only the steps the team can deliver. A sample request that goes unanswered costs more trust than a plain contact form.
DNAir captures DNA from the air, a new category for most of the people it sells to. Its earlier single-page site described biodiversity monitoring, so visitors placed DNAir alongside the monitoring services it wanted to move beyond. One of five decisions we made with the founders was to give newcomers a first step. We gave them the basis for three entry offers, from a feasibility study to a pilot, and the rebuilt page moves from the air around us to six application areas, each with a practical use. The work addressed the offer and the action together. Read the DNAir case.
The Gaia AI case shows the recognition fix. The rebuilt landing page opens on the forest manager's job and ends on two routes in, a demo video and a direct line to the team.
Count the enquiries that matter
Decide what a qualified enquiry is before you change anything, so the before and after compare like with like. For a science business that might be a technical enquiry from a target sector, a sample request, a meeting with a named account or an enquiry that reaches the right person on the team. Record what happens after each one. A count of form submissions mixes all of these with the noise. How to measure the commercial value of a website redesign sets out the full plan.
When the test points at the page, the routes and the next step, our website work for science and climate companies rebuilds the structure, the words and the design around the decision a buyer has to make.
Questions people ask
How do we turn a technical case study into a page that brings enquiries?
Write it in the order a buyer reads it. Start with the problem and the context, then what was installed or tested, the method, the result, the limits and the next stage. Name the decision it helps another buyer make, and end on a route that matches that decision. Credit each later outcome only to the work that produced it.
Should we track search traffic at all?
Yes, as a reading of discovery. Search impressions and clicks show whether the right questions bring people to the site. Enquiries, sample requests and evaluation calls show whether the site helps them act, so report the two in separate columns.
Sources and further reading
- Thibaut Monfort-Micheo, FlexSea, founder interview, Brighter Future
- DNAir case study, Brighter Future
- Gaia AI case study, Brighter Future
- When Better Communication Is the Wrong Answer, Brighter Future
- Offer architecture for startups, Brighter Future
- Ten climate-tech website claims that need evidence beside them, Brighter Future
- Why your website feels confusing, Brighter Future
- Twelve decisions to make before you commission a deep tech website, Brighter Future
Brighter Future worked with DNAirRead the case study
Studio serviceWebsite design for science and climate companies
Tell us what needs to move.
Bring the brief if it is clear. If it is unclear, tell us where the work is stuck.
Bring us the problem
01
02
03
04
05