How to Evaluate a BTL Activation Proposal

Reading past the bottom line

The number at the bottom of a proposal is the least useful number in it. Two proposals with the same bottom line can represent very different scope, risk allocation and included service, and two proposals with different bottom lines can represent the same actual campaign priced with different assumptions about city tier or team ratio. Evaluating a proposal properly means taking it apart into its components, regardless of how the vendor chose to present it, and comparing those components against what the campaign actually requires — not against each other's totals in isolation.

This matters most exactly where it is hardest to do — when one vendor sends a clean, itemised breakup and another sends a single confident number with a short paragraph of inclusions. The instinct is to compare the two numbers directly, because that is the fastest comparison available and deadlines rarely allow for much more. The right approach, which costs perhaps twenty minutes more, is to reconstruct the lump sum into the same cost heads the itemised proposal already uses, and only then compare like with like.

It is worth being honest about why this step gets skipped in practice: it feels like extra work for a decision that already has a clear favourite on price alone, and nobody wants to be the person who delayed a sign-off to re-derive someone else's arithmetic. But the twenty minutes spent reconstructing a lump sum is almost always cheaper than discovering, three weeks into the campaign, that the 'inclusive' quote excluded the one line that turns out to matter most.

What an itemised quote should break out

A properly itemised BTL quote separates cost into heads that map to real, auditable spend — not into vague categories that could mean anything to anyone reading them months later, once the person who wrote the proposal has moved on to other accounts and the only record left is the document itself.

The test for whether a breakup is genuinely itemised, rather than itemised in appearance only, is whether each line could be independently checked against an invoice once the campaign runs. A manpower line that names roles, headcount and a day rate can be checked against attendance records; a manpower line that simply says "staffing" cannot be checked against anything, because there is nothing in it to verify.

• Manpower: roles, headcount, day rate per role and number of days, not a single "staffing" figure
• Fabrication and materials: what is being built, its size or quantity, and the per-unit or per-square-foot basis
• Venue and permissions: the specific venue fee and the specific permission or NOC cost, not folded together
• Logistics: transport, storage, setup and dismantling, usually the smallest line but still worth seeing separately
• Reporting and technology: the cost of the dashboard, data capture tool or geo-tagging proof, which is easy to omit silently

Which lump sums hide what

A lump sum is not automatically dishonest — some genuinely reflect a fixed-scope deliverable that is hard to break into components, like a single experiential installation built to a one-off design. But certain lump sums reliably hide the same few things, often for entirely ordinary commercial reasons rather than any intent to mislead.

• A "staffing" line that does not disclose supervisor ratio, which — as shown in a companion guide — can represent a 20%-plus swing on the same headcount
• A "venue and permissions" line that bundles a negotiable commercial fee (society or mall rent) with a fixed statutory fee, hiding which part you could actually negotiate
• A fabrication line with no size or material basis stated, which prevents you from sanity-checking it against a per-square-foot range
• A single "production" figure with no logistics or reporting line at all — meaning one of those two was either absorbed elsewhere or simply left out of scope

Sanity-checking a total against typical cost shares

Even without a full breakup, you can sanity-check a quoted total against the typical share each cost head occupies in a BTL budget. If a vendor's partial breakup puts a disproportionate share of the budget into one head, that is worth a direct question before anything else, because real campaigns tend to cluster within these bands across a wide range of formats and cities.

A worked comparison of two proposals for the same brief

This is the most useful exercise in evaluating any shortlist: take a lump-sum proposal and an itemised proposal responding to the same brief, and reconstruct the lump sum into the itemised proposal's own cost heads. The exercise below shows exactly how to do it, step by step, with every number traceable back to a published rate.

Assumptions worth interrogating directly

Beyond the reconstructed total, a handful of specific assumptions are worth confirming with every vendor on a shortlist, because a proposal's number only means what it appears to mean once these are pinned down in writing.

• Which city tier was assumed for every venue and manpower line — ask for it explicitly if it is not stated
• Whether GST is included or additional on the quoted figure
• Whether venue and permission fees are quoted at actuals or as a fixed estimate — and what happens if actuals come in higher
• What supervisor ratio is embedded in the manpower line
• What happens to the quote if the campaign runs a few days longer or shorter than planned

Comparing proposals structured differently

When two proposals use different structures — one by cost head, one by deliverable, one as a single day rate — normalise both before comparing, following the same sequence each time so the comparison itself does not introduce a fresh set of inconsistent assumptions on top of the ones already baked into each vendor's own document.

This normalisation step is where most proposal comparisons quietly go wrong, because it is tempting to compare the two documents as they were received rather than taking the extra step of re-expressing them on common terms first. A proposal priced by deliverable and a proposal priced by cost head can describe the exact same campaign and still look incomparable until both are translated into the same five headings.

1. 1

   Re-express every proposal in the same five cost heads

   Manpower, fabrication, venue/permissions, logistics, reporting — even if the vendor's own structure does not use these labels.

2. 2

   Convert to a per-venue-day basis

   Divide each total by the number of venue-days it covers, so a 7-day proposal and a 10-day proposal for a similar campaign can be compared on the same footing.

3. 3

   Check what GST status each quote assumes

   A quote stated inclusive of GST and one stated exclusive can look ₹18 in every ₹100 apart for no real reason.

4. 4

   List what is explicitly excluded in each

   An exclusion list tells you what will show up as a change order later — often the real difference between two headline numbers.

5. 5

   Check payment milestones against deliverable milestones

   A proposal asking for a large upfront payment before any deliverable is confirmed carries a different risk profile than one tied to go-live and completion.

The evaluation is a conversation, not a scorecard

None of the steps above are meant to produce a single winning number. They are meant to turn a vague feeling — this one seems cheaper, this one seems more serious — into specific questions you can put back to each vendor, and specific answers you can hold them to once the campaign begins, in writing, rather than as an impression carried over from a pitch meeting.

A vendor's willingness to walk through this reconstruction with you, line by line, without defensiveness, is itself one of the more reliable signals in the whole evaluation — arguably more reliable than the number it eventually produces.

The question a proposal should survive is not 'is this the lowest number' — it is 'can I rebuild this number from its own stated inputs, and does it still add up.'