Case Study · 02 / 10 Performance Marketing Save as PDF ↓
Reporting automation · 7-week build

The Monday morning massacre.

How a Bangalore agency stopped burning 2,100 analyst hours a quarter on weekly client reports.

ClientNorthpoint Performance LocationBangalore, India PublishedMay 2026
Industry
Performance marketing · D2C
Scale
47 clients · 5 ad platforms
Team
62 employees · ₹18 Cr ARR
Engagement
7 weeks, full rollout
Outcomes · 90 days post-launch
3h25m → 28m
Time per client report, from 3h 25m to 28 minutes
−94%
Error rate fell from 6.2% to 0.4%
5.3×
Reports per analyst per week — 5.8 → 31
§ 01 · The company

A Bangalore agency where Mondays decided everything.

The company

Northpoint Performance runs paid acquisition for 47 D2C brands across India and SEA — fashion, beauty, consumer health — on Meta, Google, and Amazon. 62 employees, roughly ₹18 Cr ARR, known internally for sharp creative and aggressive ROAS targets.

Our protagonist is Megha Iyer, Head of Client Services, who owns retention. What kept her up every Sunday night was the same thing: would Monday's reports actually go out on Monday.

§ 02 · The problem

160+ hours a week. Just to produce decks.

Weekly load

Every client expected a weekly report by Monday 10am. Eight analysts spent Tuesday through Thursday pulling data from Meta Ads Manager, Google Ads, GA4, Shopify, and Klaviyo, then stitching it in Sheets and Slides. Each report took 3 hours 25 minutes on average. Across 47 clients, that's 160+ hours a week — just to produce decks.

Internal audits flagged a 6.2% error rate, mostly attribution-window mismatches and copy-paste mistakes. Senior strategists were doing junior data work, and new-business pitches kept slipping by a week.

Breaking pointMarch

A ₹42L/year skincare client caught a ROAS calculation that overstated their performance by 22% and threatened to walk. Two analysts quit in Q2 citing burnout. Pitches kept slipping.

₹42L contract on the brink

Two senior strategists were doing junior data work. Sunday-night Slacks had become a ritual. Something had to change.

§ 03 · The solution

A unified data layer. An AI drafter. Analysts on top.

Architecture

Vynara built a unified data layer on Postgres, with nightly syncs from all five platforms via Airbyte connectors and custom pulls. Each client's data lands in a normalized schema. An LLM-driven reporting layer generates a draft narrative every Sunday night — anomalies, week-on-week swings, and underperforming campaigns flagged inline.

7 weeks, build to deployed. Analysts open the pre-built draft Monday morning, add client-specific context the model can't know (creative refreshes, market events, internal launches), and push. Data pulling, joining, charting, and baseline commentary became automated. Client narrative, recommendations, and the relationship stayed human.

Humans always handle
client-specific context AND recommendations
§ 04 · How it works

Eight steps collapsed to four.

Before · 8 steps 3h 25m / report
  1. Analyst logs into 5 tools manually
  2. Exports CSVs per client (5 exports each)
  3. Cleans and joins data in Sheets
  4. Builds charts in Slides
  5. Writes commentary from scratch
  6. Sends to senior for review
  7. Revises (often twice)
  8. Delivers Monday — sometimes Tues or Wed
After · 4 steps 28 min / report
  1. Pipeline syncs overnightautomated · Postgres · 5 platforms
  2. AI generates draft with anomalies flaggedautomated · Sunday 11pm
  3. Analyst reviews + adds client contexthuman · ~22 min
  4. Senior approves and sendshuman · ~6 min
§ 05 · The numbers

Six metrics. Same engagement. One quarter.

Time per report−86.3%
Before3h 25m
After28 min
Reports / analyst / week+5.3×
Before5.8
After31
Error rate (audit-flagged)−93.5%
Before6.2%
After0.4%
On-time delivery (Mon 10am)+27 pts
Before71%
After98%
Analysts on reporting−5 heads
Before8
After3
Reporting cost / month−62%
Before₹14.2L
After₹5.4L

The 5 analysts freed up moved to strategy + new business. Q4 pitches won went from 4 to 11.

§ 06 · The timeline

Seven weeks. 47 clients live.

Phase
W1
W2
W3
W4
W5
W6
W7
Week 1Audit workflow · schema design · 3 pilot clients
AUDIT
Week 2Platform connectors · Meta, Google, GA4
CONNECT
Week 3Shopify + Klaviyo · normalized schema
SCHEMA
Week 4Reporting AI prototype · draft generation
PROTOTYPE
Week 5Analyst feedback loop · prompt + template refine
TUNE
Week 6Roll out to all 47 clients · parallel-run cycle
ROLLOUT
Week 7Team training · documentation · handoff
LIVE
§ 07 · What they said

The hours saved are the headline. Senior people off CSV duty is the win.

"

The first Monday it actually worked, two analysts asked if they could leave early. I said no — go work on the Delhi cohort pitch. That's the real win.

MI
Megha Iyer
Head of Client Services · Northpoint
"

I was ready to quit. I came here to run campaigns, not to be a copy-paste machine. Now I'm actually building optimization playbooks again.

RS
Rishabh Shetty
Senior Performance Analyst · Northpoint
§ 08 · The takeaway

It's a workflow problem, not a headcount one.

If your senior people are doing data entry on Mondays, the bottleneck is the pipeline, not the team.

Most agencies don't have a headcount problem — they have a workflow problem. We can replicate this for any agency running 20+ clients across 3+ ad and analytics platforms.

One-liner Your analysts are billing strategy rates to do data entry. We fix that in seven weeks.
Send us a sample report →