My friends, Ad Badger is on FIRE lately. When we connected Ad Badger directly to

By Michael Erickson Facchin · November 16, 2026 · Curated by George's Blog

My friends, Ad Badger is on FIRE lately.

When we connected Ad Badger directly to Claude via MCP, a few SaaS founder friends asked me an honest question:

"Aren't you worried people will stop logging into your web app?"

We just pulled the last 30 days of usage against the prior 30 days.

The exact opposite happened.

Instead of replacing the web app, giving operators a direct AI connection made them use the entire platform way more:

1. Average Daily Active Users jumped +38% (and our busiest single day jumped +49%).

2. Daily operators using Ad Badger inside Claude grew +89%.

3. Daily operators using the Web App ALSO grew +19%.

4. The biggest jump on the whole board: operators using BOTH Claude and the Web App on the exact same day grew +104% (more than doubled).

5. Monthly Active Users grew +20%, and our daily-to-monthly stickiness ratio climbed +3.2 points to 24.7% (nearly 1 in 4 monthly users active on any given day).

Only one row went down: "Web app only" dropped 14%, because operators are shifting from single-surface workflows to using Claude and the web app side by side.

Why does adding an MCP layer increase web app usage instead of cannibalizing it?

Because friction is what stops people from auditing their accounts.

When it takes 25 minutes of downloading CSVs to find out why ACOS spiked, you put it off until Friday.

When you can ask Claude a 10-second question over coffee, spot the exact campaign or search term bleeding margin, and jump straight into the web app to tune your rules, you check your campaigns every morning.

How has connecting AI to your ad data changed how often you audit your campaigns?

View the original post on LinkedIn

More from Michael Erickson Facchin