A beautiful website can sit perfectly still.
The meeting starts with a screenshot of the homepage. People discuss the button colour, logo size and movement of an image.
Those details can matter. But nobody has asked what should happen after a visit. The site is being treated as an object to admire while the business expects enquiries, sales or useful conversations. That confusion is expensive, even when the finished object looks excellent.
Brochure thinking arranges what a company wants to say about itself. It presents the story, services and references, then adds a form. System thinking starts with the visitor: why are they here, what must they understand, what is missing before they can proceed, and how will the business take over? Both approaches may produce the same pages. The function of those pages and their relationship are different.
This does not mean every website must sell immediately. For a complex service, the appropriate next action may be examining a project, checking a capability or preparing a conversation. For a simple product, it may be purchasing. A commercially useful website respects the pace of the decision. It helps a suitable visitor move forward and helps an unsuitable visitor recognise the mismatch. A form submission is not the only kind of progress.
Design contributes by creating hierarchy, improving readability, expressing positioning and making the next step clear. But an animation cannot clarify an undecided offer. A handsome photograph does not establish delivery capability. Expecting presentation to compensate for every unresolved business decision turns a project into an endless sequence of visual revisions. The commercial problem remains comfortably untouched.
Visitors arrive with different questions.
Imagine three visitors. One comes from a YouTube video where they heard your reasoning. They know a little about you and want to see what you do in practice. Another searches for an AI consultant for a business in Toulon. They are looking for a relevant provider without knowing your brand. A third arrives through a recommendation. They bring borrowed trust but need to establish whether it applies to their own situation.
Sending them all the same message can waste that context. The video viewer benefits from finding the subject they heard and an example of implementation. The search visitor needs to understand your scope, approach and suitability for their organisation. The referred visitor may want to inspect evidence quickly and contact you. None necessarily wants to begin by reading the complete history of the company.
A landing page should carry forward the promise made by its source. When a campaign addresses a specific problem and sends people to a general page, visitors must reconstruct the connection themselves. That small effort can interrupt the journey. Relevant landing pages do not mean generating near-identical pages for every keyword. They mean recognising genuinely different intentions and providing the information each needs.
Map each important source to an opening question, useful evidence and a next step. The map can fit on a sheet of paper. It often reveals campaigns with no coherent destination or several pages competing to do the same job. This diagnosis is more useful than declaring that the homepage feels dated. The starting point is the visitor's situation, not the company's preferred introduction.
An offer needs to be understood before it is admired.
“Innovative solutions for your growth” tells a visitor remarkably little about what is for sale. Many sites sound confident while remaining impossible to summarise. A clear offer explains who it serves, which problem it addresses, what it includes and how the relationship begins. The first screen need not contain every detail. It should give the reader enough direction to decide whether continuing is worthwhile.
Information architecture then follows the questions behind the decision. How do two services differ? When is this one appropriate? Which constraints should I expect? Who does the work? What remains my responsibility? These questions can lead to a service page, an example, a technical explanation or a description of the process. A menu reflects an organisation. A journey needs to reflect how someone understands an offer. Internal names are often poor external signposts. A department name familiar to employees may mean nothing to a customer. A list of technologies does little for an owner trying to reduce manual work or sell more effectively. Technical detail belongs where it helps someone assess the solution. It becomes friction when the reader must translate every line into an operational meaning.
Ask an outsider to describe the offer after reading. They should explain who it suits and what happens next, rather than repeat a slogan. If that remains unclear, increasing traffic will not help. The site first needs to supply enough information for people to recognise themselves in the proposal or rule it out honestly. Clarity does useful qualification work before any form appears.
Trust needs evidence people can examine.
Adjectives are not demonstrations. “Expert”, “bespoke” and “high-performing” can express an intention; they do not show what was done. A project becomes useful evidence when it describes a problem, constraints, choices and an observable outcome. Without a verified numerical result, show the work rather than manufacture a performance story. A thoughtful reader can appreciate a well-explained decision without a percentage attached.
Match evidence to the objection. A visually impressive project establishes design sensitivity. It may not establish competence in business software integration. A process description helps someone understand delivery. A demonstration addresses uncertainty about functionality. Identifiable people answer the question of whom the visitor will work with. These elements do not need piling onto every page; they need placing where the decision requires them.
Our work shows the role of concrete examples in that journey: people can examine what has been built rather than rely on a promise. The principle applies to any business using the evidence it actually has. A tradesperson can describe an intervention and its constraints. A software company can explain a use case. A consultant can publish reasoning that makes their method visible.
Consistency matters as well. Promising simplicity and presenting an exhausting form creates doubt. Offering a deeply personal service and responding with a context-free automated message creates another kind. Trust is not merely a testimonial section. It develops through continuity between words, interfaces and the company's behaviour after someone clicks.
Match the next action to the decision.
An immediate call invitation may suit a referred visitor who is already convinced. Someone exploring for the first time may need more information. Conversely, hiding contact behind several pages makes a ready visitor search for it. Provide a clear, accessible primary action and useful routes for people who still need to understand. This does not require six competing buttons in one screen.
A form is part of the commercial conversation. Requested information should help the business respond or qualify. Every field added “just in case” costs every visitor effort. If budget matters for routing the enquiry, explain why and allow an appropriate answer when the person is uncertain. Information that can wait until a conversation may not belong at first contact. Qualification should not feel like an interrogation.
Booking deserves the same attention. People should understand whom they will meet, why, the duration if one is defined, and what would help prepare the discussion. Confirmation should explain the next step. Online purchasing carries other expectations: availability, total price, delivery and payment. The website is preparing a transaction whose consequences the wider business must be able to deliver.
Plan for ordinary failures. An incomplete form should help someone correct it. A failed submission should say it failed. Unavailable booking times should lead to an understandable alternative. A silent interface loses an enquiry and may leave the visitor believing it was received. These cases belong to the commercial system even if they rarely appear in the mockups presented for approval.
Submitting the form is not the end of the work.
An enquiry received and forgotten is an interface conversion and a commercial failure. Organise the handover: destination, responsible person, context, response expectations and a way to follow the case. A shared inbox can work for a small team when responsibility is clear. A more elaborate platform cannot replace that clarity. Software should support the handover rather than serve as evidence that one exists.
The handover should also preserve what the visitor has already learned. If a page explains a specific engagement but the first reply asks which service they want, the company has discarded useful context. If booking follows an enquiry, the person should not have to reconstruct the same brief again. This is a small operational test with a clear commercial consequence: does each step use what the previous step established? A team can answer it by following one real request from arrival to response, noting every place where information is copied, lost or unnecessarily requested again.
Automation can preserve context. It can pass along the service viewed, assign requests according to a rule, acknowledge receipt and flag an unanswered enquiry. It should not invent a personal conversation or send follow-ups unrelated to the situation. The visitor asked for a useful next step, not a message sequence triggered simply because a technical condition was satisfied.
Acquisition quality is also visible after this handover. Numerous unsuitable enquiries suggest a targeting or messaging problem. Suitable enquiries that never become conversations invite scrutiny of the reply. Conversations that rarely progress may reveal an issue beyond the website. Following the journey to a real outcome prevents the last button receiving credit or blame for everything the business does.
BUILD → GET FOUND → CONVERT → AUTOMATE expresses this continuity. Build something useful, make it discoverable, help someone decide, then organise the work that follows. These functions reinforce one another when information passes correctly between them. Treating them as four disconnected projects reproduces the very gaps the system was supposed to remove.
Redesigning the homepage may leave the problem intact.
Before a redesign, inspect actual entry pages and the enquiries they produce. Some people never see the homepage. They arrive on a service, article or product. A project focused exclusively on the front page can leave the point where decisions stall entirely untouched. Budget follows the page's visibility inside the company instead of its role in the business.
Measure stages that correspond to useful work: viewing evidence, submitting an enquiry, making a suitable enquiry, holding a conversation and developing an opportunity. Consent, tooling limits and visits across devices make observation imperfect. Add what the sales team hears. “I couldn't tell whether you handled this kind of project” is actionable evidence even without a sophisticated dashboard. It may explain a problem that click totals cannot.
Choose an initial improvement by identifying a specific break. A page attracts suitable people but leaves an objection unanswered. A form collects useful enquiries but routes them incorrectly. A sought-after service is difficult to find. Repair that break and observe whether the journey improves. This gives you something to learn from, rather than a redesign in which every variable changes at once.
The final test is straightforward. If someone arrives tomorrow with a need we can address, does the website help them understand, believe and proceed, then help us take over? A brochure can present a business. A commercial system gives that business a dependable way to work with the people discovering it. Design that function before choosing the button colour.
End of article / 3W Insights