Writing for an Indian small-business audience

There is a register that works for business writing aimed at Indian small-business owners, and it sits in a narrower band than writing for some other markets. Too casual reads as unserious — a supplier who addresses a business owner as though they were a friend has misjudged a relationship that is, at that point, entirely commercial. Too formal reads as bureaucratic, and bureaucratic language carries a specific association: forms, departments, delay. Neither register is a failure of politeness; both are failures of calibration.

The workable middle is plain, direct, complete sentences, without the elaborate courtesy formulas that have accumulated in Indian business correspondence. "Kindly do the needful at your earliest convenience" is recognisable, widely used and almost content-free, and its cost is not that it is old-fashioned but that a reader skims past it looking for the actual request. The same applies to "we are pleased to inform you" and "please find attached herewith". Removing them does not make writing curt if what remains is specific and courteous. It makes the request findable, which is the courtesy that a busy reader actually notices.

This sounds too obvious to state and it is a persistent problem, because a great deal of business writing template material originates elsewhere and arrives with dollar figures, dollar-scaled examples, and thresholds that make no sense locally. An example priced in dollars asks the reader to do a conversion before they can judge whether the number is large, and in that moment of arithmetic you have lost the point you were making.

Use the rupee symbol and use the local grouping convention — lakh and crore — where that is how your reader thinks about the amount. Somebody running a small business does not mentally hold twelve hundred thousand; they hold twelve lakh. Where a piece will be read by people outside India as well, a figure can carry both forms, but the local one should lead. The same principle extends past currency to every unit and reference that carries an assumption: financial years that end in March rather than December, weeks where Saturday is a working day, festival seasons that shift demand, and delivery timelines that depend on distances and infrastructure a foreign template did not consider.

An example does its work by letting the reader map it onto their own situation, which means the example has to be a business they can picture. A textile wholesaler in Surat, a café in Bengaluru, a clinic in Pune, a hardware shop in a district town — each of these is immediately concrete to an Indian reader, and each carries a set of assumptions about scale, staffing and customer behaviour that you do not have to explain. An example built around a software startup with venture funding does not, for the great majority of readers.

There is a hard line to observe here, and it is the difference between an illustration and a claim. Naming a plausible kind of business to illustrate a point is legitimate and useful. Attaching a result to it is not: a sentence claiming a particular clinic reduced missed appointments by some percentage is a fabricated case study, however plausible the number sounds, and it is fabricated regardless of whether the business is named. Keep illustrations qualitative — this is the kind of business where this problem shows up, and this is the shape it takes. If you want a number attached to an outcome, it has to come from a real, identifiable source you can point at.

Business English in India is not a second language for most of this audience; it is the working language of commerce, and treating readers as though they need everything simplified is both inaccurate and mildly insulting. But the vocabulary is not evenly distributed, and the useful distinction is not about English competence at all — it is about which terms have entered ordinary business conversation and which belong to a professional discipline.

GST needs no explanation to anybody running a business, and neither do invoice, credit, stock, margin or turnover; these are the daily working vocabulary. Terms borrowed from marketing and finance disciplines are different: churn rate, attribution, customer lifetime value, working capital cycle, cohort. A reader who learned business by running one rather than by studying it may not have encountered these, and the cost of a brief gloss is one clause while the cost of losing them is the paragraph. The version that works is a definition folded into the sentence — "churn, meaning the share of customers who stop buying each month" — which serves the reader who needs it and does not delay the one who does not.

Beyond vocabulary, imported business writing carries structural assumptions that quietly misfit. It tends to assume card payments are the default rather than one option among several, that credit terms are documented rather than negotiated by relationship, that a business has separate people for separate functions rather than an owner doing four jobs, and that decisions are made in scheduled meetings rather than continuously.

Writing that assumes the wrong operating reality is not offensive, it is just useless — a reader recognises within a paragraph that this was not written for a business like theirs and stops. The corrective is to be specific about the situation you are describing rather than universal. Advice framed for a business where the owner approves every purchase reads as accurate to that owner, even if it does not fit a larger organisation. Advice framed for nobody in particular fits nobody in particular. This is the same discipline as choosing a recognisable example, applied at the level of the whole piece: name the reader's circumstances plainly, and let the readers it does not fit identify that quickly rather than slowly.

An Indian audience is multilingual in a way that a single language of publication cannot fully serve, and it is better to decide deliberately than to drift. English reaches a wide business readership across regions and is the safe default for written commercial material. It is also genuinely a barrier for some of the market, and pretending otherwise in order to avoid the cost of translation is a decision disguised as an oversight.

What does not work is a mechanical translation nobody has read. Business writing is full of idiom, and machine-translated idiom produces sentences that are grammatical and slightly wrong in a way that damages credibility more than English would have. If you translate, have somebody who works in that language read the result as a business reader, not as a proofreader. If you cannot, publishing in English and being useful is a reasonable choice — and if a specific piece matters enough to reach beyond the English-reading audience, that is the piece to spend a real translation budget on rather than translating everything badly.