Inside the Jagran Events build — a 7-month playbook

Jagran Events called us in early 2026. Sanjay Sinha had a specific brief: redo the website and the landing pages, run social, run lead generation. The hard part of the brief was the qualifier on the end. He wanted one accountable team, not three vendors stitched together with weekly status calls.

Seven months in, here is the honest version of what we did, what worked, and the parts I would run differently from scratch.

The setup, briefly

Jagran Events is the events arm of the Dainik Jagran group, India's largest Hindi media network. The flagship is the Career Horizon Conclave, a multi-city, multi-format conference that lives or dies by registrations.

The starting state was the same starting state most established Indian brands have. A site that loaded slow and barely converted on mobile. A social presence producing posts without a system. A lead pipeline that could not tell organic from paid from referral. Nothing broken, but nothing compounding either.

Month one: the audit nobody asks for

I sent a 19-page audit before the contract was signed. Tech stack, page speed, social-handle hygiene, what the last three campaigns actually returned. It cost me a weekend. It bought us the next six months of trust.

People keep asking why I lead with the audit when it gives away half the proposal. The answer is that good clients want the diagnosis before the prescription. If you cannot show you understand the body, no one trusts your pills.

Month two: a strategy doc, not a deck

Eight pages of plain prose. What the events arm of a Hindi media giant should sound like, look like, and rank for. Where the next four campaigns should sit. Where the spend should go. The doc was approved with two small edits and zero meetings.

A note on this. I have stopped doing pretty pitch decks for serious clients. The Jagran team is not impressed by gradients. They wanted to know I had thought about the thing. Plain prose beat slides because the strategy was readable on a phone and there was nowhere to hide a vague idea.

Months three and four: the rebuild

We rebuilt the events site. The previous build was a WordPress theme stretched into shapes it was never meant to take. We swapped it for a clean PHP shell with the same content model, a faster page-load story, and proper schema for events and tickets.

A few details that mattered more than they look on a slide.

Event schema markup, so Google could surface start times and venues directly in search. UTM hygiene wired into every share asset, so the social team stopped flying blind on attribution. A mobile-first registration flow. The previous form had five fields on a 360-pixel screen. Conversion went up the day we cut it to two.

These are not glamorous wins. They are the kind of thing that does not show up in a case-study photograph. They are also the difference between a campaign that runs hot for a week and one that compounds for a year.

Month five: the Career Horizon Conclave campaign

This was the test. A multi-city conclave with a press release calendar, paid on Meta and Google, organic on LinkedIn and Instagram, a couple of influencer outreaches, and a microsite for registrations.

What worked. Warm retargeting from earlier event attendees was the cheapest qualified registration source by some distance. LinkedIn was the most expensive cost per lead but produced the highest actual show-up rate, which is the metric that matters for an event.

What did not work. A Reels-first organic strategy I had argued for. The format was fine. The audience was wrong. Reels for a B2B-skewed conclave audience attracted the wrong kind of traffic, fast. We pivoted to LinkedIn carousels in week three and the qualified-registration line bent up within a week.

I would rather a post that admits this than one that pretends every line of the strategy was perfect. They were not.

Months six and seven: the handoff

The brief I had been given was "build us a backbone." The hardest part of that brief is not the building. It is the handing-off. A backbone that breaks the moment the agency leaves is not a backbone. It is a crutch.

So we shipped a Notion ops manual the in-house team owns, a monthly review template that anyone on the team can fill in without me, and a small Loom library for the things you only need to do once a quarter and never remember the next time. The system is the gift. Anyone can ship one campaign. The trick is whether you have left the room better than you found it.

What I would do differently

A few things I would change if I started the engagement again.

I would push harder on the analytics setup in month one, not month three. We lost six weeks of clean attribution because GA4 was set up with the default events firing and not enough custom ones. By the time we wired it up properly, the first campaign was already mid-flight.

I would have negotiated a single "kill switch" rule into the contract. Halfway through month five, an internal stakeholder who had not been part of the strategy review appeared and asked for a Reels-heavy direction the team had already vetoed. We absorbed two weeks of pivoting that did not need to happen. A standing rule of "the same person who approved the strategy is the only person who can change it" would have saved that fortnight.

I would have published the strategy doc internally to all stakeholders on day one, not the steering committee only. Most of the friction we saw later was between people who had not read the doc and people who had.

What the work taught me

Two things stuck.

First. The work that moves the needle for a brand of this scale is rarely the work that shows up in the case-study photo. Schema. UTM hygiene. Form-field reductions. The handoff document. The conclave was the moment. The system is the durable thing.

Second. Senior in-house teams want to be respected, not replaced. The Jagran team is sharp. They knew the answers to several of the questions I was hired to answer. My job was not to be smarter than them. It was to make their answers happen on schedule, with the technical work and the writing they did not have time to do themselves. The brands that hire well figure this out early, and they do not pay agencies to perform expertise. They pay them to execute it.

Where the work goes next

The next chapter is the Career Horizon Conclave 2027 build, which we are scoping now, plus a content engine for the events vertical that runs without anyone holding it up.

If you are a media or events brand thinking about a similar build, the contact form is the easiest place to start. Tell me what you are trying to make true. I read every brief.

— Shubhanshu