Website redesign brief for Indian service businesses

A brief that names languages without tying them to customer tasks leaves several decisions open. Who researches the service? Who approves the purchase? Which language do they use when explaining the problem? Look at recent enquiries, conversations and proposals before choosing the page set. An Indian service business may serve customers in one city, several states or overseas, with different needs in each case.

Write one sentence for the first journey: a facilities manager needs to check the service area and request an assessment, or a business owner needs to understand an advisory engagement before booking a call. Give that journey a page, an action and an owner. Add other audiences only where the brief can explain what changes for them.

List the pages before multiplying them by languages. A translated service page can still leave a reader stranded when its navigation, form or confirmation changes language. Record the whole route, including the message someone receives after an enquiry and the language in which the team can respond.

Translation carries meaning between languages. Transliteration carries words into another script. Keep the two decisions separate for brand names, service terms and addresses. Agree approved spellings and terminology with the relevant reviewer, then use that record across pages, downloads and messages.

For genuine language versions, Google recommends separate URLs and annotations connecting their equivalents. Its guidance favours clear language choices and cautions against automatic language redirects. Google identifies language from visible content. W3C guidance separately explains how an HTML language declaration supports language aware processing; those are different jobs.

Choose a primary action for each service page. A form, telephone link, email address and WhatsApp link have different handover requirements. A WhatsApp conversation needs an owner and a fallback for people who prefer another channel. A form needs a clear success state and a destination the team actually monitors.

Record the smallest set of details needed for a useful reply. W3C's forms guidance calls for understandable labels and instructions, including the meaning of required fields. A placeholder disappears during typing, so keep important instructions available beside the field.

Define the acceptance exercise: open a service page on a phone, reach the enquiry, correct an error, send agreed test data and confirm receipt with the responsible person. Arrange those test messages with the business before sending them. Include keyboard use, language characters and longer names or addresses in the review. Device checks support acceptance; they are separate from a specialist accessibility assessment.

Ask every supplier to price the same page and language inventory. Compare what the fee buys, who supplies the content and how revisions are counted. A quote covering five English pages and a quote covering five pages in three languages describe different workloads, even when both call themselves a five page website.

Record the quoted currency, payment stages, validity period and any applicable tax treatment stated in the proposal. Check commercial or tax questions with the appropriate adviser. List tools billed in another currency separately, with their renewal terms and account owner. The purpose is an understandable commitment, rather than an invented market average.

Inventory the existing service pages, language versions and downloadable material before replacing the site. Give every old address a decision: keep it, move it to a relevant replacement, combine its content or retire it. Preserve useful content and links deliberately rather than starting from an empty navigation menu.

Google's guidance on URL changes recommends mapping old addresses to new ones, implementing redirects and monitoring the move. Search visibility can fluctuate during a migration. Assign the review and monitoring work in the scope instead of treating unchanged rankings as a launch guarantee.

Record who owns the domain, hosting, CMS, analytics and enquiry destinations. Use secure account invitations or an agreed access process rather than putting passwords into the brief. Handover should explain who can edit each language, renew the tools and restore the site when something goes wrong.

Illustrative example, rather than a client result. A maintenance firm serving factories around Pune receives technical requests in English and initial enquiries in Marathi. The owner decides to scope English service detail and a reviewed Marathi introduction with an enquiry route. The brief records this limited coverage explicitly and identifies which pages will remain English.

The language switch shows the available destination clearly. The form asks for a name, contact detail, location and a description of the service needed. A named coordinator reviews incoming requests; the page also offers a telephone option. The proposal separates source copy, Marathi language review, implementation and ongoing updates in INR.

Acceptance is concrete: the approved wording appears correctly, the intended language links work, a phone user can complete the form, and the coordinator receives the agreed test enquiry. Search traffic and qualified leads are later measurements, distinct from this launch record.

Send the current website, priority customer journey, page and language inventory, approval owners, budget range and intended launch date. Flag dependencies such as translation, photography, specialist review or a third party booking tool. A date is easier to assess when those responsibilities are visible.

Branding Tatva delivers website work remotely. Indian website projects receive a separate scope and INR quote covering the agreed writing, design, development, migration and handover. Commercial terms are shared privately in the written proposal, with brand strategy and website implementation scoped explicitly. Translation, legal review and ongoing support require explicit inclusion and confirmed responsibility in the proposal.