Website Design for Indian Businesses: Strategy Before Screens

Why does strategy come before the first screen?

Most website projects begin in the wrong place. Someone shares a link to a site they admire, a designer is asked to make something in that spirit, and within a week there are screens to react to. From then on the project is a conversation about taste: this shade of green, that photograph, a larger logo. The questions that decide whether the website earns anything are still unanswered, and now they are expensive to raise.

Strategy before screens does not mean a long document or a research phase your business cannot afford. It means writing down a small number of decisions first: who the site is for, what you want them to think, what each page has to achieve, which words and pictures you will need, and how you will judge the result. Those decisions take a few conversations. Reversing them after a design is approved takes weeks.

Who is the website actually for?

The honest answer for many businesses is “everyone who might buy from us”, which is the same as nobody. A manufacturer in Coimbatore may be visited by a procurement manager at a large buyer, a distributor in another state, an existing customer hunting for a spare part number, and a candidate deciding whether to apply. All four are welcome. They cannot all own the first screen.

So rank them. Write the list in order of commercial importance, then write what each one came for and the single action you want from them. This is the shortest useful piece of strategy you can do, and it settles arguments later: when someone asks for a careers banner on the homepage, you can point at the list and ask which audience it serves.

What do you want to be known for?

Positioning is the sentence a visitor could repeat to a colleague the next day. It is not a tagline and it is rarely poetic. “Fit-out and equipment for new dental clinics, across Maharashtra, in eight weeks” is positioning. “Quality solutions with a customer-first approach” is filler, and every competitor in your city can claim it without changing a word.

A specific claim carries a risk that a vague one avoids: someone can hold you to it. That is exactly why it persuades. Decide what you are willing to be held to, then decide what proves it. Proof is photographs of finished work, a list of the sectors you serve, the qualifications you actually hold, the names of the people who will do the job, and a straight answer on what you do not do.

Write the positioning line and the three proofs before the design brief. Both will shape the first screen, the order of the pages and the photographs you need to commission. Our fictional NORTH advisory concept shows the effect: the site opens with a point of view rather than a description of the category.

Give every page one job

A website is not a brochure that happens to scroll. Each page should have one job, one main question it answers and one obvious next step. If you cannot say what a page is for, it does not need to exist, and every page you remove is a page you no longer have to write, photograph, translate and maintain.

• Home: say what you do, for whom, and offer one clear next step.
• Service pages: answer the questions that decide the enquiry, then invite it.
• Work or projects: prove the standard with real examples rather than adjectives.
• About: show the people, the premises and the reason to trust them.
• Contact: make every route work — form, phone, WhatsApp, map, opening hours.

Sequence matters as much as the list. A visitor who arrives from a search result rarely lands on the homepage, so each page has to make sense on its own and point somewhere sensible next. Our companion guide on how to plan a sitemap around the customer journey takes that further.

Why content should be written before the design

Placeholder text flatters a design. Real copy tests it. A heading that reads beautifully as three invented words often becomes four awkward lines once it says what your business really does, and a product grid designed for square studio shots looks wrong the moment your actual site photographs arrive.

Content is also the usual reason website projects slip. Design work can be scheduled; writing and photography depend on people who have other jobs. Decide who writes each page, who approves it and by when, before the design begins. Decide which photographs must be taken, and book the shoot early — a factory floor, a clinic reception or a finished flat cannot be photographed the week before launch.

Languages, phones and the WhatsApp journey

Language is a strategy decision with design consequences. If you need Hindi, Tamil or Marathi alongside English, decide it now: it changes navigation, typography, line lengths and the translation budget. Google advises that you use different URLs for each language version rather than swapping content behind one address, and to avoid redirecting people automatically based on the language you assume they want. Give them a visible way to switch instead.

Each page should also declare its own language in the code. The W3C requires that the default human language of each page can be programmatically determined so that screen readers use the right pronunciation rules and browsers render the script correctly. Half-translated pages, where the menu changes but the body does not, fail both readers and search engines.

Phones come next, and not as a smaller version of the desktop design. Google uses the mobile version of a site’s content for indexing and ranking, and recommends the same content, headings and image alt text on both. Design the phone layout first, then let the desktop layout inherit from it. Our guide to mobile website experience covers the detail.

Decide now how you will know it worked

Agree two or three measures before the build, and record where you stand today. Enquiry form completions, calls and WhatsApp taps, bookings taken, quotation requests from the pages that matter: pick what reflects the business, not what is easy to count. Without a baseline from the current site, the new one can only be judged on how it looks.

• Analytics that record the actions that matter, not only page views.
• A confirmation step for every form, so submissions can be counted honestly.
• Taps on phone numbers and WhatsApp links counted as actions.
• Search Console connected, with the current pages and their traffic exported before launch.
• A named owner and a monthly review of the same few numbers.

Be patient with search. Google’s own starter guide is blunt about it: “There are no secrets here that’ll automatically rank your site first in Google”, and it notes that some changes might take effect in a few hours, others could take several months. Judge a launch on enquiries and completed journeys first, and on search position over a longer period.

A one-page website brief you can write yourself

You do not need a strategy consultant to produce a usable brief. Ten lines, agreed by the people who can actually decide, will do more for the project than a fifty-page document nobody reads. Write it before you invite proposals, and give the same sheet to every studio you speak to, so their quotations describe the same job.

1. The audiences, in order of importance, described as real people.
2. What you want each audience to think, and the one action you want from them.
3. Your positioning in a sentence a customer could repeat.
4. Three pieces of proof you can actually show.
5. The page list, each page with one job and one primary action.
6. Languages, and who will translate and check them.
7. A content owner and a date for every page.
8. The photography and video that must be created.
9. Integrations: payments, bookings, enquiry routing, your existing tools.
10. Two or three measures, today’s baseline, and who reviews them monthly.

This is the same ground our Website Design & Development work covers before any visual direction is shown: audience, brand and business goals, then sitemap, copy and journeys, and only then design. If the harder question is what happens after the enquiry arrives — who replies, what gets recorded, which steps could be handled by a system — that is a workflow question rather than a website one, and the AI Opportunity Blueprint is the paid diagnostic that maps it.