Planning a festival calendar for an Indian business

The usual pattern is this. Someone notices two days before Diwali that the business should post something, a generic greeting graphic gets made in a hurry, it goes out on the day alongside every other business doing the same thing, and it produces nothing. The following month the cycle repeats for the next festival.

The reason this fails is not that the greeting was badly designed. It is that a greeting posted on the day is arriving at the moment of maximum competition and minimum usefulness. Everybody's feed on Diwali morning is a wall of near-identical wishes, and a customer with money to spend on Diwali shopping made their decisions the week before.

India's festival calendar is unusually dense, which makes the improvised approach unusually expensive — there is always another one coming. Planning is not about being more elaborate. It is about arriving before the crowd and having something to say beyond the greeting.

The work is front-loaded and does not need repeating. Sit down once and write out the festivals that matter for your customers, with dates, for the next twelve months.

Two cautions on the dates. Many Indian festivals move against the Gregorian calendar and have to be looked up for the specific year rather than assumed from last year's date. And regional variation is real: the festivals that matter to customers in Kerala are not the same set that matters in Punjab, and a business serving one city should build for that city rather than for a national average.

Then sort the list into three tiers. A small number are central to the business — the ones where customers are actively buying what you sell. A larger group are worth a genuine, well-made greeting. The rest are worth knowing about so you are not tone-deaf, without posting for them.

Fifteen festivals on a calendar sounds like a lot of work until they are tiered, at which point most of them cost nothing.

For the tier-one festivals, six weeks of lead time is roughly what it takes to do something better than a greeting, and the time is not spent evenly.

The first two weeks are for deciding what the business actually has to say — whether there is an offer, a relevant product, a service that gets busy, or a genuinely useful piece of advice for the season. This is the part that gets skipped, and skipping it is why the output is a greeting.

The middle two weeks are production: photography, design, captions. Doing this while not under time pressure is the difference between usable images and a stock graphic.

The last two weeks are the campaign itself, and this is the part most businesses miss entirely. The buying happens before the festival. A business that sells anything gift-related, food-related, clothing-related or home-related has a customer making decisions in that window, and content arriving then is useful rather than decorative. The greeting on the day is the closing note, not the campaign.

The question that separates a festival post worth making from one that is filler is whether the business has a real relationship with the occasion.

Sometimes it is direct: a sweet shop at Diwali, a tailor before a wedding season, a paint retailer during pre-festival cleaning. Here the content writes itself, because customers have practical questions — what to order when, how long something takes, what is in stock.

Sometimes it is oblique but still genuine. A service business can speak to the logistics of the season: what changes about opening hours, how deliveries are affected, how to plan around the rush. That is useful information, and useful beats festive.

And sometimes there is no real connection. A software business has nothing meaningful to say about Pongal, and the honest move is a short, sincere greeting or nothing at all. Manufacturing a connection produces the posts everyone scrolls past — a stock image, a pun on the festival's name, and a product that has nothing to do with any of it.

A festival is somebody's religious or cultural occasion before it is a marketing opportunity, and the gap between acknowledging one and exploiting one is visible to the people it belongs to.

A few practical lines. Get the specifics right — the correct name, the correct greeting, the correct spelling — because getting them wrong communicates that nobody at the business knew or checked. Do not attach a discount to a solemn occasion; not every festival is celebratory, and some are days of mourning or fasting where a sale is jarring. Avoid religious imagery as decoration for a commercial message, which is the most common misstep and the one most likely to cause offence. And do not treat one community's festivals as the default and everyone else's as optional.

The useful test before publishing: would someone for whom this festival is genuinely important read this post as respectful? If nobody at the business can answer that confidently, ask someone who can, or keep it to a plain greeting.

The compounding benefit of doing this properly is that a festival calendar is an asset that improves rather than a task that repeats.

After each festival, spend a few minutes writing down what happened: what was posted, what people responded to, when the enquiries actually started arriving, and what you wished had been ready earlier. That last note is the valuable one. Most businesses discover their real lead time is longer than they assumed, and the only way to know is to have recorded it once.

Keep the assets too. A well-made festival image is reusable in later years with modest changes, and a caption that worked is a starting point rather than a blank page. This is where the front-loaded work pays off: the second year is mostly editing.

A scheduling tool like Socie can hold a queue of dated posts weeks ahead, which is what stops a planned calendar from decaying into same-day improvisation when the pre-festival rush arrives — and the rush is exactly when the business has least attention to spare.