BTL & Brand Activation in Kaithoon

Kaithoon sits outside Kota's own limits but inside its metro area, which matters operationally: approvals usually run through a different local authority than Kota proper, and travel time for crew and stock has to be planned rather than assumed. Campaigns here are typically scheduled alongside other Kota metro locations so one team and one stock delivery serve several in a day.

Planning for Kaithoon has to account for it being a separate municipality inside the Kota metro rather than part of Kota proper. Approvals run through a different local authority, with its own timelines and fee structure. Crew and stock travel from Kota, so Kaithoon is normally scheduled in the same rotation as other metro locations — one vehicle, one stock drop, several venues in a day — which is what keeps the per-location cost sensible.

The formats that earn their place in Kaithoon are the ones matched to how this town actually works. Society activations and door-to-door programmes reach households directly; a market canopy works where Kaithoon has an established high street; mall formats only make sense where there is a mall drawing from the surrounding blocks. Anything outside that list tends to generate footfall numbers without generating outcomes.

Kaithoon is reported as its own line rather than folded into a Kota total. That sounds like a reporting detail and is actually the difference between a programme that improves and one that does not: a weak location inside a city-wide average is invisible until the campaign is over, while the same location on its own line is obvious in week one, when there is still budget left to move. Every Kaithoon venue carries geo-tagged, time-stamped photo proof, attendance against roster, and contacts counted on the capture tool rather than estimated at the end of the day.

Every campaign reports the same way: attendance against roster, geo-tagged and time-stamped photographs per venue, contacts engaged counted on the capture tool rather than estimated, and leads verified by callback before they are counted. Weak locations show up in the first week, which is the only point at which they can still be fixed.