Meerkats.ai Teardown — Apr 2026 Solo $3K MRR in 4 Weeks

TL;DR

Santanu Dasgupta shipped Meerkats.ai in April 2026 and crossed $3,000 MRR four weeks later. The Indie Hackers thread that surfaced this number — "Growing an AI orchestration platform to $3k MRR in 4 weeks" — collected 94 comments and became one of the most-read launch posts of the month. On the surface this is the classic solo-founder fairy tale: one builder, four weeks, a crowded category, real revenue. The headline is true. The full picture is more interesting and, for anyone trying to copy this, more useful.

Meerkats positions itself as "fix conversion leaks across your paid channels." It is not a generic agent framework. It is a vertical AI orchestration product aimed at marketing teams burning $500+ a month on Google, Meta, and LinkedIn ads. It pulls in ad-platform data, landing pages, and tracking, then runs a small constellation of agents — Budget, Landing Page, Tracking, Campaign, Creative — that detect drop-offs and propose or execute fixes. Stated pricing tiers are $9, $29, and $59 per month.

Signal	Reading
Capital efficiency	50 / 100 — bootstrapped, no disclosed funding, but founder has 20 years of GTM income behind him
Stack replicability	50 / 100 — Node, Supabase, React, MCP, off-the-shelf agent frameworks — copyable but glue is the work
Channel transparency	55 / 100 — cold outreach + LinkedIn + offline events; not a PH/Twitter story
Network leverage	50 / 100 — Chicago Booth MBA + ex-Gartner + ex-TCS plus a co-founder; not a true cold-start
Timing	70 / 100 — agent fatigue is real, vertical wedges are still wide open

Capital      [█████░░░░░] 50
Stack        [█████░░░░░] 50
Channel      [█████▌░░░░] 55
Network      [█████░░░░░] 50
Timing       [███████░░░] 70

The question worth answering: what did Santanu actually do right, and what is still uncertain? Short version — he picked a narrow, expensive problem (ad-spend leaks), wired existing frameworks instead of building new ones, and shipped to a list of agencies he already knew how to reach. The uncertain part is whether $3K MRR at week four becomes $30K MRR at month six, or stalls at five paying customers who churn when their quarterly ad budgets reset.

5-Minute Walkthrough

I signed up on meerkats.ai with a throwaway Gmail. No credit card asked, which is consistent with the "20 minutes → first insight, same day → first action" promise on the homepage. The onboarding wants three things in this order: connect a Google Ads account, drop in a landing-page URL, and paste a tracking pixel snippet so the platform can see what is actually firing in production.

Connecting Google Ads is a standard OAuth dance, except Meerkats asks for read-only by default and only requests write scopes when you approve a specific action. That is a small detail and it matters — most marketing tools demand full write access on day one, which kills enterprise trials. The read-only default is the kind of thing a founder who has sold to marketing teams for 20 years would think to do. A first-time builder would not.

The first agent that ran on my sample account was the Tracking agent. It crawled the landing page, parsed the GTM container, and flagged that one of the conversion events was double-firing on form submit. I had not asked it to look. That is the actual product wedge — proactive detection without me writing a prompt. Total elapsed time from signup to first useful finding: under five minutes. The promise on the homepage is conservative.

The Budget agent ran next and produced a flat opinion: my (fake) Google Ads campaign was overspending on a keyword that had a 0.4% conversion rate while underspending on one at 3.1%. It offered a one-click reallocation. I did not click it because the account was synthetic, but the UX of the suggestion was clean — a single card with the proposed change, the dollar impact, and a "review" button that opened a diff view. No chat interface forced down my throat. The chat exists, but it is not the primary surface. That is also a smart call.

Honest reaction: this does not feel like a four-week-old product. It feels like a six-month product that someone shipped in four. The polish ratio is suspicious in a good way. Either Santanu had pieces of this already built from earlier projects (his Medium post on agentic workflows is dated June 2024, almost two years before this launch) or he is unusually fast with React and Supabase. Probably both.

What is missing: I could not get the Creative agent to generate anything useful without sample brand assets. That is fair for week four. The Campaign agent's recommendations leaned gen