A website can look entirely right and still be built on the wrong assumptions.
That is the expensive mistake. Not the colour palette, the font, or the platform. The real damage is done much earlier. The moment a website direction is approved, before anyone has properly tested how the people you want to reach will actually use it.
Before a single page is designed or developed, you must know three things:
- Who is using it
- What they are trying to achieve
- Where are they when they use it
Get those wrong, and the finished site can look polished in a boardroom while silently losing enquiries in the real world.
The question most business owners ask is whether a site should be designed for desktop or mobile. It is the wrong starting point. The better question is this:
Is the site built around the way your real customers make decisions?
If it's not, the device debate won't save you. You can have a responsive site, a beautiful design, and every internal sign-off in place, yet still end up with a website that works better for the people reviewing it than for the people expected to use it.
The mistake happens before anything is built
Most website problems do not begin in the code. They begin when the brief is agreed.
That's the point where assumptions become direction. Direction becomes page structure. Page structure becomes navigation, content, forms, templates, and calls to action. By the time those assumptions are built into the site, changing them is no longer a quick discussion. It's rework.
Before a design is signed off, you need clear answers to these questions:
- Who is the site actually for?
- What are they trying to do first?
- What decision are they trying to make?
- What evidence do they need before they trust you?
- Are they likely to be calm and researching, or rushed and distracted?
- Are they on a phone, at a desk, or moving between devices?
- What action matters most: calling, enquiring, booking, buying, comparing, or downloading?
These aren't cosmetic choices. They decide whether the website is pointed in the right direction.
A site can present beautifully in a meeting and still serve the wrong visitor, on the wrong device, in the wrong moment. If the thinking's flawed at the start, the build simply makes the wrong idea more expensive to fix later.
Your office is not the customer journey
Website designs are almost always reviewed in conditions that flatter them.
A large, hi-res monitor. Fast office Wi-Fi. A quiet room. An internal team that already knows the business inside out. A director who knows exactly where everything is supposed to be. A designer walking everyone through the layout.
That is not a real visit.
To bridge the gap between how a site is signed off and how it's actually used, look at the reality of the user journey:
| The Boardroom Sign-Off (Flattering) | The Real-World Visit (Friction) |
|---|---|
| Connection: Ultra-fast office Wi-Fi / Fibre | Connection: Patchy 4G signal on a moving train |
| Screen: Large, high-resolution desktop monitor | Screen: A cracked phone screen on a sunny street |
| Environment: Quiet room with zero interruptions | Environment: Rushed, distracted, multitasking |
| Mindset: Insider team who knows where everything lives | Mindset: Sceptical stranger with 3 competitor tabs open |
Both scenarios are valid. The mistake is assuming the comfortable conditions you use for sign-off match what your customers experience. They almost never do.
Responsive does not mean fit for purpose
Most modern websites are responsive, and they should be. But “responsive” is often treated as a checkbox that means “mobile sorted”. It does not.
Responsive means the layout adjusts to the screen. It doesn't mean the user journey works.
A responsive site can still be incredibly awkward on a phone. It can bury the phone number, hide the most critical information, stack content in a confusing order, make forms fiddly, or force people to scroll through endless material before they can act.
That isn't a technical failure. It's a business failure.
A site that doesn't break on a small screen has passed a technical baseline. It hasn't passed the more important test: can a visitor understand you, trust you, and take the next step without unnecessary friction?
Mobile design is not just desktop design squeezed into a narrower column. It must respect the visitor's situation. What matters first on a large screen may not matter first on a phone. What reads well in a calm office may be too slow for someone trying to solve an urgent problem on the move.
Your sector will not tell you how people use your site
A common shortcut is to assume that a business model dictates device priority.
“We are B2B, so people will be at a desk.”
“We sell to consumers, so everything is mobile.”
It sounds tidy, but it is frequently wrong. Your sector doesn't decide the user journey. The task does.
Example 1: The B2B Split
- The Component Manufacturer: An optics firm selling specialist components to manufacturers deals with engineers who need datasheets, tolerances, specifications, and technical depth to justify a choice to a procurement team. Strip that experience down to a quick, mobile-first summary page, and you remove the exact evidence the sale depends on.
- The Parts Wholesaler: A wholesaler selling to plumbers is also B2B, but the context is entirely different. The customer is on a phone, between jobs, in a roof space, or standing at a merchant's counter trying to find a part number, check availability, and get a price quickly. Build that journey around a slow, desktop-style browsing experience, and you lose them instantly.
Example 2: The B2C Split
- The Car Showroom: A showroom sells a highly considered purchase. Customers compare models, finance rates, running costs, and part-exchange values over several weeks, stretching across multiple devices.
- The Holiday Rental: A holiday rental site may depend almost entirely on the immediate mobile experience. Someone browses photos on the sofa, checks availability dates, shares a link, and decides based on immediate feel. If booking or payment becomes awkward in that exact moment, the enquiry vanishes.
Do not design around a generic label like B2B or B2C. Design around the specific task, the evidence required, the urgency of the decision, and the moment the visitor is in.
Your customer does not stay on one device
The choice is rarely as clean as desktop versus mobile.
The same person may discover your business on a phone during a commute, return later on a laptop to read your case studies in depth, and then send an enquiry from their phone the following morning. The device changed three times. The customer didn't.
This is where many websites break down. The mobile version has less content, the desktop version has clearer proof, or the enquiry route feels entirely different. The user is forced to rebuild trust every time they switch context.
A successful website creates continuity. The information that helps someone make a decision shouldn't vanish on mobile. The enquiry route shouldn't become convoluted on desktop. The proof that builds your credibility should never be hidden just because a screen is smaller.
The loudest voice in the room is not evidence
Website direction should never be decided by whoever has the strongest personal preference in the meeting. Before design sign-off, look at what the data actually shows:
- Which devices are your visitors using right now?
- Which devices produce the highest-quality enquiries?
- Which specific pages help people decide to trust you?
- Where exactly are users abandoning the site?
- What do your sales conversations reveal about common buyer objections?
- What does Search Console show about user intent and visibility?
Analytics will not answer everything, but they are a far better guide than opinion. CRM notes, call tracking, form submissions, sales feedback, heatmaps, and direct customer questions all expose what visitors actually need.
If the site is brand new and data doesn't exist yet, map out the likely journeys based on reality rather than wishful thinking. Talk to your front-line sales staff, review competitor journeys, and list every single question a buyer asks before they commit. The aim is not perfect certainty; it is to stop guessing when you don't have to.
Test the site like a stranger
There's a simple test that exposes weak assumptions in minutes.
Open your website on your phone. Turn off the office Wi-Fi and use mobile data. Now, try to complete the primary task a real visitor needs to achieve.
Find a specific service. Check whether the business looks credible. Locate the phone number. Send an enquiry. Download a document. Compare options.
Do it without shortcuts and without using your insider knowledge.
If the site is live, you will see the cracks immediately. If it is still in design or staging, you will catch the wrong assumption before it becomes an expensive development headache.
If your audience is genuinely deskbound, test that properly too. Sit at a desk and check whether the depth, proof, and decision-making content are genuinely there. Can a visitor easily justify choosing you over a competitor?
Do not test the conditions that flatter the design. Test the conditions that decide whether you get the conversion.
The cost stays hidden
When a website is built around the wrong assumptions, the financial loss rarely announces itself.
People don't email you to say your form was irritating, your mobile page felt thin, or your booking step made them hesitate. They simply leave. They go back to the search results and choose a competitor. You never see the enquiry you nearly had.
That is what makes this mistake so dangerous. A site can quietly underperform for years while the business blames the market, advertising spend, the economy, or lead quality. Sometimes those factors are real, but often, the website is simply making the right people work too hard.
There is also a significant brand cost. For many visitors, their mobile experience isn't just part of their impression of your business; it is their impression of your business. If the site feels clumsy, slow, or thin, that judgment transfers directly to your capabilities.
Finally, there is the impact on visibility. Google indexes and ranks your content based almost entirely on its mobile version, following Google Search Central's mobile-first indexing guidance. If your mobile experience is stripped-back, awkward, or missing critical content, the damage affects both the visitors you have and the prospects who will never find you in the first place.
Assumptions are cheap until they are built
The costly mistake is not choosing desktop over mobile, or mobile over desktop. The costly mistake is approving a website before you understand the real-world conditions in which your audience uses it.
Once wrong assumptions are built into code, navigation, templates, and forms, changing them is slow and expensive. While they are still just assumptions on paper, they cost nothing to challenge.
So challenge them before the build begins.
Because a flawless user journey only matters if people actually reach the starting line. If you want to check the assumptions underneath your current site or a new design before it costs you clients, a structured Website Review is the simplest place to start.
And if you suspect the issue isn't just how the site converts, but whether the right audience can find you at all, let's look at your website visibility.