Is your website selling, or just watching? What the market needs from a company site

«I've had a website for two years. It looks good, it was well designed and I paid for it. But nobody calls and nobody orders. What is this website doing?»

We hear this in different forms, and the answer is rarely the design or the colours. It is a simpler, harsher question: what did the visitor come to the site to do, and did the site help them do it?

I'm Mohamed Habib, a developer. I work on websites and systems used by real people who search, compare and decide. This article isn't about a programming language or a template. It's about a short list of what the market actually needs from any company website, and how to check your site against it in a week, before you pay for changes.

In short: A company website sells when it answers four questions in the first seconds: who are you, what do you do for me, how do I reach you, and why should I trust you? And when every page has one job and one clear button, and is measured. If a site isn't measured, we can't know whether it sells.

The visitor isn't there to browse

First, let's get the picture of the visitor right. A website isn't a magazine someone reads at leisure. The visitor usually comes from a Google search, a WhatsApp link, an ad or a social profile. They're on a mission: to find out whether this is the right place for their problem, or go back to the results and open the next one.

Something often forgotten: most visits now come from mobile. In Egypt, a report carried by Egyptian Streets on 24 June 2026, citing Research and Markets and the Ministry of Communications, says social commerce reached 9.1 billion dollars in 2023 and is expected to reach 14.9 billion in 2028, with about 61.7% of it on Facebook and 31.8% on WhatsApp. That figure is about commerce, not websites, but it tells us something important: people are used to deciding and buying on their phones, inside apps. Any site that opens slowly or makes them pinch to zoom loses to an easier experience.

So the website is competing with the easiest way to buy in the visitor's head, not just with competitors' sites.

Four questions to answer in 10 seconds

Try this now: open your website on a phone and look at the first screen without scrolling. Answer as if you were a first-time customer.

Question one: who are you? The type of business should be clear from the first sentence. Not «integrated solutions» or «a pioneering vision». One clear sentence: «We install and service air conditioners for flats and offices in Greater Cairo».

Question two: what do you do for me? The benefit framed as my problem, not as your achievement. «AC stopped in the summer? A technician at your door the same day» beats «ten years of experience».

Question three: how do I reach you? The button or number is in front of me without searching, and in more than one way, because people don't all get in touch the same way: some like to call, some prefer WhatsApp, some fill in a form.

Question four: why should I trust you? At least one piece of evidence visible early: real clients, photos of actual work, a guarantee, an address, or a visible commercial registration number. Not a «we're the best» slogan.

If your site doesn't answer all four on the first screen, the visitor has to do the work for you, and most won't.

Every page has one job

The most common mistake we see: every page tries to do everything. The home page has services, team, news, blog, offers, partners and four different buttons, and the visitor stands in the middle not knowing what to tap.

The rule we follow as developers, and ask the content team to follow: one job per page, and one main button.

• Home: sends the visitor down a path (I want to order, I want to know more).
• Service page: convinces them this service fits, and ends with a request.
• Contact page: makes getting in touch easy, and nothing else to distract.
• Blog: answers questions, and points to a service page with clear link text.

The CTA (call to action), the button that asks for a specific step, should say what happens after the tap: «Book a visit», «Ask for a quote», «Message us on WhatsApp». A word like «Submit» or «Click here» leaves the visitor in the dark.

Getting in touch isn't one form

When designing how people contact you, the question isn't «form or no form». It's: which ways does our audience prefer? And: what happens after they tap?

Three common routes, and their drawbacks:

1. A form: good when you need details (type of service, size, date). Drawback: every field raises the chance the visitor gives up. Ask about each field: will we actually use it in our first reply? If not, remove it.
2. WhatsApp: the fastest and closest to how people talk. Drawback: conversations get lost if nobody owns the replies and nothing is recorded. That deserves its own article, on turning enquiries into a system.
3. A direct call: strong for urgent services. Drawback: someone has to answer, and out of hours it's lost.

One simple rule makes a difference: whoever gets in touch should get a reply within a stated, expected time. «We reply within two hours during working hours» is better than leaving them wondering. Keeping that promise matters more than any design.

A hypothetical example: an air-conditioning service company

Picture an AC service company in Cairo (the example is entirely hypothetical, to show the method). Its website has:

• A home page with a photo of a smiling team and the slogan «Always with you».
• A long «About us» page on the company's history.
• A «Services» page with a list of general bullet points.
• A contact form with eight fields.

Checked against the four questions, the problems were:

• Who are you? It isn't clear whether they repair, install, or both.
• What do you do for me? No mention of the customer's problem (the AC has stopped, it's leaking, it's noisy).
• How do I reach you? The form is on a distant page, and there's no visible number on mobile.
• Why should I trust you? No photos of work, no real reviews, no clear service area.

The change wasn't a redesign. It was rearranging:

• First screen: «AC leaking or stopped? A technician the same day in these areas», with two buttons underneath: «Call» and «WhatsApp».
• A page for each common problem (water leak, cleaning, new installation), each with a short description, what happens on the visit, the service area and an order button.
• A form with three fields: name, area, problem.
• Photos of real work with the clients' permission, and a clear guarantee line.

Plus measurement: how many taps on call, how many on WhatsApp, how many forms sent. After two weeks the numbers are compared with before. (These numbers come from tracking tools; we don't assume them here.)

Notice that none of these changes needs complex technology. They are all decisions about what to say, and where.

The technical side you don't see, but that matters

This is the part I'm responsible for as a developer. The business owner shouldn't have to deal with it, but should make sure it's there:

• HTTPS enabled: browsers warn about insecure sites, and visitors get nervous.
• The site works properly on mobile: not just smaller, but with buttons big enough for a finger and text readable without zooming.
• The form is actually tested: send a message through it every week and check it arrives. Many sites that «nobody contacts» have had a broken form for months.
• A thank-you page after sending: not only to reassure the visitor, but so you can count requests accurately.
• Backups: if the site goes down or gets damaged, you can restore it.
• The phone number is tappable on mobile: a small thing that costs nothing and makes a big difference.
• Measured events: the call tap, WhatsApp tap and form each have an event in the analytics tool, so we know what brought what.

This list can be checked in an hour with your developer. If an agency or developer built the site, ask them to show you each point, not just say «it's fine».

A website isn't a substitute for social media, and it isn't the same thing

A recurring question: «Our Facebook and Instagram pages are working, why do we need a website?». The answer isn't always «yes». It depends on two things:

1. Do people search Google for you or for your service? If so, the website is what shows up. Social pages don't always show in search as strongly.
2. Does buying from you take trust and detail? Services that cost more or take longer to decide (major maintenance, fit-out, business services) need people to read, compare and check, and a website is a better place for those details than a post.

There's another point in the website's favour: you own it. A social page runs on a platform's rules, which can change; the page can be closed, restricted or hit by an algorithm change. Your website's data, visitors and policies stay with you.

And if your business already runs entirely on WhatsApp and Instagram and customers are happy, we won't advise building a big website. A simple landing page that gathers everything (who you are, the service, contact, proof of trust) can be enough to start.

Anatomy of a service page: what reassures the visitor and moves them

The service page is where the visitor decides to ask or to leave. We build it in a fairly fixed order, because visitors ask their questions in the same order in their heads:

1. The heading names the problem or service in the visitor's words. Not «integrated maintenance services» but «AC leaking water».
2. Two sentences on what is actually done. No jargon.
3. What happens after the request, in short steps. (We reply, set a time, inspect, give a price.) Steps reduce fear of the unknown.
4. The price, a price range, or what sets it. If the price varies, say why.
5. A piece of proof near the button. A photo of work, a real review with the person's permission, or a clearly written guarantee.
6. Frequently asked questions, in plain text. From what you actually hear on calls, not from imagination.
7. The button. The same wording as at the top of the page.

The page doesn't have to be long. For a simple service, seven short sections are enough. What matters is the order, and that no section repeats the one before.

A point I make as a developer: don't build every service page at once. Start with the most requested one, measure it, adjust it, then copy the structure that worked to the rest. That's cheaper and faster than building twenty pages with the same mistakes.

Three numbers are enough for a monthly review

Any analytics tool can drown you in dozens of numbers. For a business website, three are enough to start, and each answers a different question:

1. Visits by source: where do people come from? Search, social, ads, direct links. This tells you which channel brings people worth having.

2. Contact taps: of the visitors, how many tapped call or WhatsApp, or sent the form? This number tells you whether the site works as a go-between. If visits are high and contact taps low, the problem is the site itself (the message, the order, or speed).

3. Requests that became sales: this doesn't come from the analytics tool. It comes from the sales book or the customer system. Compare it with contact taps: if 100 people got in touch and only two bought, the problem isn't the website, it's the reply and the offer (the subject of another article, on enquiries that don't convert).

The point: any one of the three on its own misleads. Lots of visits without contact means a weak site. Lots of contact without sales means a follow-up problem. Few sales without visits means a reach problem. The three together tell you which link to fix first.

A habit of mine as a developer: write the numbers on a fixed sheet, with dates. Not only for accuracy, but so that in three months you can say «that change made a difference» or «it didn't» without relying on memory.

Common mistakes on company websites

1. A site for the manager, not the visitor. The home page is full of vision, mission and values, while the visitor wants the service, the price and a way to get in touch. Write for the visitor first.

2. Generic stock photos. A smiling team from a stock library says «this is a site like any other». Simple real photos beat professional photos that have nothing to do with you.

3. Too much moving content. Sliders and banners that change on their own; the visitor chases them and can't find what they want.

4. No price or price range. You don't have to publish a fixed price, but «from – to» or «starting from» cuts unserious questions and saves the team's time.

5. Nothing about what happens after getting in touch. Visitors are wary of the unknown. Explain the steps: we reply, we inspect, we send an offer, we start.

6. Forgetting mobile in testing. The developer works on a big laptop; the visitor is on a small phone. Test on the customer's kind of device.

7. A site that's built and forgotten. A website isn't a project that ends. It's a product that gets reviewed and improved regularly, based on numbers.

Objections we hear

«The website is expensive, we can't change everything»

Most of the changes above aren't heavy development. Rearranging the first screen, cutting form fields, adding call and WhatsApp buttons and writing clearer sentences is hours of work, not weeks. The big spending comes from rebuilding from scratch before understanding the problem.

«Our customers come through referrals, not the website»

True, and very many customers visit the website after the referral, to check. A weak or missing site weakens a strong referral. Here the website doesn't bring the customer; it keeps them.

«We'll do SEO first, then sort out the site»

If visitors arrive and don't find what they want, you've paid for visits that go to waste. Better to sort out the site first so every visit converts as well as it can, then increase the visits.

«How do I know the website is working?»

By measuring. Pick three numbers and review them monthly: visits from each source, taps on contact buttons, and actual requests that became sales. The third number may come from the sales book rather than the tool, and it's the most important one.

How to ask your developer for a change without misunderstanding

Most frustration between business owner and developer comes from a vague request. «Make the site better» isn't a request. This format works better:

• State the problem, not the solution. «People reach the page and don't tap the button» beats «make the button bigger». The button may not be the problem, and the developer may find another cause.
• Give the current number and the goal. «WhatsApp taps are 12 a week now, and we want to know if the new layout increases them».
• Agree how you'll know the change worked before it starts, not after.
• Ask for one change at a time if you want to know its effect.
• Ask about time and the effect on everything else. A change that looks small can break another page.

In return, you're entitled to ask your developer simple questions and get clear answers: «How long will this take? What could break? How do we roll back if it goes wrong?». A developer who answers these clearly saves you hours of meetings.

If the website is new from scratch

Everything above applies to an existing site. If you're about to build a new one, the order changes a little, and it starts before the developer opens any tool:

1. Write down the three questions: who the visitor is, where they come from, and what they want to do. Without them, any design is a guess.
2. Decide which pages you really need. Most small businesses start with five: home, one or two services, about, and contact. The rest gets added once you see the numbers.
3. Write the copy before the design. A design built on placeholder text breaks when the real text arrives.
4. Start with a small version that goes live quickly, review it against real numbers, then grow it.

A small, measured version is far better than a big one that's months late and that nobody knows is right.

When not to build a new website

Sometimes the honest answer is that there's no need. If the four questions can be solved by rewriting copy, or if a broken form is the only problem, fixing it is cheaper and faster than building a site. We see a full rebuild as justified only when the problem is in the foundations: a site that doesn't work on mobile, can't be edited without a developer every time, or is built on an old system that no longer gets updates. Otherwise, sort out what you have first, measure, then decide.

The one-week check: a seven-step sheet

If you want to start today, here's a plan for a week, not a project:

1. Day one: open the site on a phone and answer the four questions on the first screen. Write down what's missing.
2. Day two: ask three people from your audience (not people you know) to open the site and say, after 10 seconds, what you do. Write down their exact words.
3. Day three: make sure every contact button works, send a test message through the form and check it arrives.
4. Day four: define each page's job, and give each page one main button.
5. Day five: agree the tracking events with your developer: call, WhatsApp, form.
6. Day six: rewrite the vague copy (solutions, vision, pioneers) into sentences you'd say to a customer.
7. Day seven: record the current numbers as a baseline, and set a review date two weeks out.

Don't wait for a new website. This check shows you which small changes are enough and which problems need building.

A table: each page and its job

The table is an exercise: put your own pages in it, and see which page has no clear job or no button.

Website review checklist (ten points)

• Does the first mobile screen say who we are and what we do in one sentence?
• Is the benefit written as the customer's problem, not as our achievements?
• Is the contact button visible without scrolling, in more than one way (call, WhatsApp, form)?
• Is there at least one piece of proof early (clients, photos of real work, a guarantee, an address)?
• Does every service page have one job and one main button?
• Is the form short (name, contact method, subject), and does it actually send when we test it?
• Have we tried the site ourselves on a real phone, on an ordinary connection?
• Do we know where visitors come from, and how many get in touch each month?
• Are the photos, numbers and names on the site real and up to date?
• Is someone responsible for updating the site every month?

The bottom line

The website that sells isn't the best designed. It's the one that answers the visitor's questions quickly, gives them a clear step, and measures what happens. The changes that make a difference are usually in order, wording and measurement before they're in technology.

One last question to leave you with:

If a stranger opened your website on their phone today, and after 10 seconds we asked them «what does this company do, and how would you get in touch?», what would they say?

If you're not sure, try it on three people before any change. The answer will save you a lot of decisions.

Want a company site that brings in enquiries? One of our experts is ready to listen. The first call is free.