
The 30-day verification challenge: what happens when you verify one full campaign month
A week-by-week walkthrough of what brand managers and operations heads discover when they apply real verification to a live campaign for 30 days. Most challenges end with two outcomes. A signed scale-out plan, and a difficult conversation with at least one vendor.
30 days
The minimum window required to see the full anatomy of a BTL campaign through verification eyes. By Day 18, the brand manager has data the agency PPT never showed. By Day 30, the procurement contract is being rewritten. The challenge is short. The implications are not.
A brand manager at a top-30 Indian listed FMCG signs up for the 30-day verification challenge on a Monday. One ongoing campaign: 180 outlet rollouts across 8 cities with 12 vendors. By Friday, the verification layer is live. By the end of the second week, the brand manager has more execution data than she had received in the previous 18 months of agency PPTs. By Day 30, two vendors have been moved to a watch list, one has been offboarded, and the procurement team has drafted a Proof Before Payment clause for the next contract cycle.
What the 30-day challenge actually is
| Challenge dimension | Specification |
|---|---|
| Duration | 30 days, applied to one live campaign |
| Cost to brand | Free pilot, no commitment beyond pilot |
| Onboarding | 3 to 5 days for full verification layer deployment |
| Scope | One live BTL, OOH, retail, or field force campaign |
| Output | Published gap analysis at Day 30 plus live dashboard |
| Operational disruption | Zero (parallel verification layer) |
| Behavioural change required from field force | Zero (WhatsApp-native capture) |
| Brand commitment | One pre-pilot kickoff call, one Day 15 review, one Day 30 readout |
| Decision deliverable | Scale-out roadmap with verified baseline data |
| Audit-grade output | BRSR Core ready evidence pack |
Week 1: Reporting volume looks normal
Everything looks operationally healthy
The first week is the most deceptive. The pre-pilot baseline appears to confirm the agency's narrative.
- Submissions volume: Promoters and field reps upload photos as usual
- Attendance feed: Looks complete on the dashboard
- Outlet coverage: Maps populate with green markers
- Activation status: Completed entries dominate
- Reported metrics: Align broadly with the agency PPT closeouts
- Field force adaptation: Minimal complaint, workflow unchanged
- Brand impression at end of Week 1: This looks fine. Maybe we don't have a problem.
Why Week 1 is the data-collection phase, not the insight phase
| Week 1 dynamic | What's actually happening |
|---|---|
| Verification layer establishing baseline | Submissions accumulating, patterns not yet visible |
| Field force first-week adjustment | Some honest behavioural alignment beginning |
| Vendors aware of new scrutiny | Short-term improvement skews the baseline upward |
| Sample size still small | Statistical significance not yet reached |
| Anomaly detection running silently | Flag distribution starting to take shape |
Week 2: Behavioural anomalies start appearing
The vendor honeymoon ends; the data starts telling
By Day 10, the AI anomaly detection has enough volume to surface meaningful patterns. The first uncomfortable conversations begin.
- Anomaly inbox: Begins populating with flagged submissions
- Recycled image detection: 12 to 18 submissions hash-match across the campaign
- Mock-location attempts: 4 to 9 submissions blocked at the 9-layer check
- Delayed bulk uploads: Compressed-window submissions flagged
- Identical visit duration patterns: 3 to 6 vendors show perfect pattern reporting
- Impossible travel speeds: 2 to 4 submissions flagged at route plausibility
- Brand impression at end of Week 2: Something is going on. We just didn't have eyes on it.
What Week 2 reveals about the agency's PPT
| Agency PPT claim (typical) | Week 2 verified reality |
|---|---|
| 100% submission compliance | 82–88% authentic submissions verified |
| GPS verified | 4 to 9 submissions used mock-location |
| All photos new and original | 12 to 18 recycled images detected |
| Vendors performing uniformly | Tier C and Tier D vendors emerging |
| Field force fully covered | 22 to 30% of submissions clustered end-of-day |
| Route adherence at 92% | 74–80% verified, with 2 to 4 impossible speed flags |
Start the 30-Day Verification Challenge
Pick one live BTL, OOH, or retail campaign. We deploy the verification layer in 3 to 5 days. You receive a published gap analysis at Day 30 plus dashboard access throughout. Free, no commitment beyond pilot.
3-5 days
Onboarding time
14-22% of spend
Avg gap revealed
5-8x
Year-1 ROI on scale-out
Week 3: Operational leakage becomes quantifiable
The financial picture sharpens
At the Day 15 review, the verification team shares the first quantified gap analysis. Conversations shift from 'is there a problem' to 'what is the rupee impact'.
- Verified Execution Rate established: 76 to 84% for typical campaigns
- Per-vendor scorecards: Tier A to D distribution clear
- Skipped outlets surfaced: 8 to 14% of contracted outlets unverified
- Inflated promoter hours: 18 to 26% short-duration shifts identified
- Duplicate proof submissions: Per-vendor counts emerging
- Non-compliant branding: POSM quality issues flagged with photo evidence
- Footfall plausibility: Reported vs verified gap quantified
- Estimated rupee leakage: 14 to 22% of campaign cost in first quantified estimate
- CFO involvement: Finance head joins the Day 15 review
- Brand impression at end of Week 3: We need this for every campaign going forward.
Quantification of leakage: what brands see in Week 3
| Leakage source | Typical Week 3 finding (% of campaign spend) |
|---|---|
| Recycled or duplicate proof submissions | 2 to 4% |
| Skipped outlets marked complete | 3 to 6% |
| Inflated promoter hours | 4 to 7% |
| Non-compliant POSM installations | 2 to 5% |
| Ghost activations | 2 to 4% |
| Trade scheme variance | 1 to 3% |
| Total quantified leakage | 14 to 22% |
Week 4: The organisation stops trusting static reports
The procurement and CFO conversation reshapes the relationship
By Day 22, the brand team has internal alignment. By Day 30, the conversation with the agency partner has fundamentally changed. The challenge produces decisions, not just data.
- Day 22: Vendor scorecards finalised. Tier classifications shared internally.
- Day 24: Procurement drafts Proof Before Payment clause for next renewal.
- Day 26: First difficult agency conversation around the gap data.
- Day 28: CFO presents Year-1 ROI math to leadership.
- Day 30: Published gap analysis shared. Scale-out roadmap signed off.
- Vendor outcomes: 1 to 3 vendors moved to watch list or offboarded
- Contract changes: Verification clause added to all new MSAs
- Brand impression at end of Week 4: We are not going back to PPT closeouts.
The Day 30 readout: what gets reported back
| Section of the gap analysis | Contents |
|---|---|
| Executive summary | VER, RoVE-adjusted spend, leakage estimate in rupees |
| Per-vendor scorecard | Tier A to D classification with verified execution rate |
| Per-city and per-region breakdown | Geographic distribution of verification and gaps |
| Fraud pattern analysis | Distribution of the 8-pattern detection model |
| Anomaly inbox closure summary | What was flagged, what was remediated, what remained |
| Procurement readiness assessment | 3-way matching gap, contractual changes recommended |
| BRSR Core readiness | Evidence pack structure, retention gaps |
| Scale-out roadmap | 90-day plan for full campaign coverage |
| ROI math | Year-1 recovery estimate, platform cost, net P&L impact |
| Industry benchmarking | Brand's VER vs sector baseline |
What typically gets revealed at Day 30
VER 14 to 22 percentage points below reported compliance
Reported compliance was 92–96% in PPT closeouts. Verified rate is 74–82%. The 14–22 percentage point gap is the structural finding. Most brands describe this as more data than the last 18 months of agency reporting combined.
One to three vendors with measurably worse performance than the average
Vendor variance is sharper than the agency presentation reveals. Tier D vendors (below 65% verified rate) typically represent 8 to 14% of campaign volume. They are not always the cheapest or most expensive; they are the most opaque.
12 to 22% of campaign spend recoverable with PBP
Once the verification layer is operational, Proof Before Payment can recover the leakage directly. Brands typically save 4 to 8x the platform cost in Year 1.
Procurement contracts not built for accountability
Existing MSAs typically lack verification clauses, KPI definitions, or PBP triggers. Procurement teams use the 30-day finding to redraft contract templates.
Audit committee findings can finally close
Recurring internal audit findings on marketing controls find their evidence base in the verified data. Many brands close 2 to 4 open findings within 60 days of pilot completion.
Field force productivity is actually higher than the agency reports show
High-performing field executives finally get the credit they deserve. The average hides them. Verified data exposes the top performers and creates a path to retention and incentive design.
BRSR Core readiness is materially better than expected
For listed brands, the 30-day data forms an audit-grade backbone. Limited assurance conversations with statutory auditors become substantive instead of hypothetical.
CFO becomes a marketing ally, not a gatekeeper
The data transforms the marketing line from cost to be controlled to investment to be substantiated. Most brand managers describe the CFO conversation post-Day 30 as the most productive marketing-finance dialogue they have had in years.
Typical Day-by-Day timeline inside the challenge
| Day | Event |
|---|---|
| Day 0 (kickoff) | Scope, KPIs, baseline data collection, agency notification |
| Day 1–3 | Verification layer deployment, vendor portal onboarding, field force trained on WhatsApp workflow |
| Day 4–5 | First verified submissions begin flowing into the dashboard |
| Day 6–7 | Week 1 stabilisation, brand team gains familiarity with the dashboard |
| Day 8–10 | First fraud signals start triggering. Anomaly inbox populates. |
| Day 11–13 | Per-vendor patterns emerge. Some vendors visibly improve. Some patterns persist. |
| Day 14–15 | Day 15 review meeting. First quantified gap shared with brand leadership. |
| Day 16–18 | Per-region drilldown completed. Geographic distribution of gaps mapped. |
| Day 19–21 | Vendor scorecard finalised. Initial tier classification shared with vendor management. |
| Day 22–24 | Procurement begins drafting verification clauses. First agency conversation. |
| Day 25–27 | CFO and audit committee preview of findings. Year-1 ROI math compiled. |
| Day 28–29 | Final report drafting, scale-out plan preparation, evidence pack compilation. |
| Day 30 | Published gap analysis shared. Scale-out roadmap signed off. Decision point reached. |
The 30-day challenge is not a test. It is a reset.
| What changes after the 30 days | Permanent or reversible? |
|---|---|
| Brand's view of vendor performance | Permanent. Vendor variance becomes the operating frame. |
| Procurement's contract templates | Permanent. PBP clauses get embedded in renewals. |
| CFO's stance on marketing spend | Permanent. RoVE replaces ROAS in board reports. |
| Audit committee narrative | Permanent. Verified evidence closes findings. |
| Agency relationship dynamics | Permanent. Honest agencies elevate; trust-based agencies decline. |
| Field force psychology | Permanent. Honest field executives are visible. |
| BRSR Core posture | Permanent. Evidence base established. |
| Brand manager's daily workflow | Permanent. Anomaly inbox replaces end-of-month review. |
Sample financial picture from a typical 30-day challenge
| Financial line item | 30-day campaign (₹10 Cr) |
|---|---|
| Total campaign spend | ₹10 Cr |
| Reported compliance (pre-challenge) | 96% |
| Verified Execution Rate (Week 4) | 78% |
| Verified spend | ₹7.8 Cr |
| Unverified or flagged spend | ₹2.2 Cr |
| Spend protected via PBP (typical) | ₹1.4 to 1.9 Cr |
| Time-to-payment compression | 71 to 22 days |
| Disputed invoice value (pre-challenge baseline) | ₹38 to 65 lakh |
| Disputed invoice value (post-challenge) | ₹4 to 9 lakh |
| Platform cost (30-day pilot) | Free |
| Year-1 projected ROI on full coverage | 5 to 8x |
Day 30 vs Day 0: the contrast
Day 0 (pre-challenge state)
PPT closeouts as the primary evidence. Reported compliance accepted at face value. Vendor performance treated as uniform. CFO presents marketing as cost to be controlled. Audit committee findings on marketing controls recur. Procurement contracts lack verification language.
Day 30 (post-challenge state)
Verified Execution Rate dashboard live. RoVE-adjusted spend visible per campaign. Per-vendor scorecard with tier classification. CFO presents marketing as substantiated investment. Audit committee findings closing. Procurement contracts with PBP clauses being signed.
A 30-day verification challenge does not change what is happening on the ground. It changes what the organisation can see, defend, and decide. That single shift is what makes the brands who run it never go back.
Who should run the challenge and when
| Trigger condition | Why this is the right moment |
|---|---|
| Internal audit findings on marketing controls | Verified data closes the finding directly |
| BRSR Core mandate approaching for listed parent | Evidence base required before assurance window |
| Major campaign with ₹5 Cr+ spend coming up | Pilot on this campaign for maximum learning |
| Recurring billing disputes with current agencies | Substantiation evidence resolves disputes faster |
| CFO escalation on marketing line substantiability | Provides the data to defend the budget |
| Procurement leadership change | Fresh procurement head looking to upgrade governance |
| New CMO assessing the agency landscape | Vendor scorecard becomes immediate input to the audit |
| Pre-renewal of major agency contracts | Renewal negotiation strengthened by verified data |
| Investor or acquirer due diligence in progress | Verified-execution capability shows up in valuation |
| Competitive launch from accountability-led peer | Match the standard before procurement asks |
What slows the challenge down (and how to avoid it)
| Common friction | Mitigation |
|---|---|
| Internal alignment between brand, procurement, IT | 1-day kickoff alignment workshop covers all stakeholders |
| Agency resistance to a parallel verification layer | Frame as data-collection pilot, not vendor audit |
| Field force onboarding hesitation | WhatsApp-native workflow requires zero new app or training |
| InfoSec and data governance review | Standard enterprise InfoSec checklist passes in 2–3 weeks; pilot can proceed in parallel |
| Vendor InfoSec questions | Pre-prepared vendor briefing pack with privacy and consent details |
| Initial reporting volume vs verified gap confusion | Pre-challenge baseline established to anchor interpretation |
| Slow scaling of dashboards to multiple stakeholders | Role-based dashboard access pre-configured |
| Procurement contract changes needing legal review | Template PBP clause provided; saves weeks of drafting |
Industries where the 30-day challenge is being adopted fastest
| Industry | Adoption driver in 2026 |
|---|---|
| FMCG | Trade scheme leakage + POSM compliance |
| OOH agencies | BMC 2025 Mumbai policy + procurement integration |
| BFSI (banks, NBFCs) | RBI FPC + 2026 recovery rules + BRSR Core |
| Pharma | UCPMP compliance + MR territory accountability |
| QSR and multi-outlet retail | National rollout verification + franchise tier scorecards |
| Automotive and durables | Dealer activation audit + co-op marketing claims |
| Real estate | Site visit verification + sales agent productivity |
| D2C with growing offline footprint | Event verification + influencer activation audit |
Frequently Asked Questions
The 30-day verification challenge applies to any live BTL, OOH, retail, or field force campaign across India.
The 30-day verification challenge is available across all major Indian cities.
Start the 30-Day Verification Challenge
Pick one live BTL, OOH, or retail campaign. We deploy the verification layer in 3 to 5 days. You receive a published gap analysis at Day 30 plus dashboard access throughout. Free, no commitment beyond pilot.
3–5 days
Onboarding time
14–22% of spend
Avg gap revealed
5–8x
Year-1 ROI on scale-out
Written by
gOGig Editorial
gOGig Editorial
gOGig Labs research team covering India's field execution intelligence ecosystem.
Was this article helpful?
Your feedback helps us write better content.



