Growing an AI orchestration platform to $3k MRR in 4 weeks

Santanu Dasgupta built an AI orchestration platform and launched it into a crowded market. Four weeks later, Meerkats.ai's MRR is over $3k.

Here's Santanu on how he did it. 👇

20 years in GTM

I’ve spent 20 years working on go-to-market for SaaS companies, across the US, Europe, and India — starting out as a developer at an Oracle mobile database spinout in the Bay Area, before moving into GTM and growth.

I later worked with startups and enterprises on scaling demand generation and revenue at Gartner Consulting and Tata Consultancy Services, where I saw firsthand how much GTM still depends on manual work, fragmented tools, and agency-heavy execution.

That insight led me to start an AI orchestration product called Meerkats.ai. We’re essentially building a digital growth agency in software. Meerkats replaces a lot of the repetitive work SDRs, marketers, and agencies typically handle — capturing and enriching relationship data, generating leads, running campaigns, and following up — all from a simple chat interface.

Startups' GTM teams are selecting Meerkats.ai over platforms like Claude Managed Agents and OpenAI Agent Harness, as they want flexibility in model choice (bringing the cheapest model that is appropriate for the task). Also, they may not have the in-house talent to build in Agent Harness, so they are offloading the entire task to Meerkats as a “Service as a Software” or even outcome-based service.

We launched the platform four weeks ago and are currently doing $3k+ MRR. To keep the lights on, we got funding from the University of Chicago Polsky Center as part of the Alumni New Venture Challenge. We also offered Agency services as part of the platform to fund operations. And we got generous credits from Azure, OpenAI, and Anthropic towards model costs.

Meerkats.ai homepage

Building V1

We built the initial system with the following components:

  1. A spreadsheet UI for viewing lead lists and an enrichment platform.

  2. Infrastructure to scale enrichments to 50K+ rows in under 30 minutes.

  3. Integrations with third-party servers, and enabling dynamic code execution based on user requirements.

  4. Autonomous Agents with full manus-like capabilities, including memory management, sandbox code execution, evals, tool selection, Skills.md, and files for a knowledge base, helped us create an end-to-end native AI platform. The entire setup is sometimes called an Agent Harness and enables Agents to work reliably at scale across multiple workflows. These systems can plan and execute open-ended tasks, pick the right tools and models for the task, handle execution errors, and request human attention when required.

The initial product leveraged AI models like Claude, Gemini, Codex, and agentic frameworks such as Claude Skills SDK, Codex, LangChain, Crew AI, AutoGen, and Google Cloud Platform (GCP). It also drew inspiration from the capabilities of OpenClaw.

As far as the rest of our stack, it's:

  • Supabase

  • Google Cloud Platform for scaling

  • Fly.io for sandbox code execution

  • React frontend and Node.js server

  • MCP servers and CLI endpoints in GCP containers

We chose Supabase because it offers the wonderful feature of Row Level Security, as well as powerful features like built-in authentication, real-time updates, and MCP server hosting. It felt much more modern than Mongo, hence we migrated.

Business model and growth channels

Our business model is consumption-based, factoring in the number of enrichments and actions an LLM performs and the task's complexity. We aim to make it very easy to start a growth flow, usually at the top of the funnel, and then help agencies or businesses with other revenue-impacting workflows. We are also seeing demand from customers for agencies to package our service as an “Outcome-as-a-service” where the customer pays the agency for a particular outcome or task completed — similar to what they would get if they hired a VA, but an Agent completes the task.

We have three growth channels:

  • We combine cold and targeted outreach to agencies in our network. We specifically target agencies that run marketing campaigns for their clients without using AI.

  • We run educational events online and offline to educate agencies on how to best leverage AI Agents for revenue.

  • We attract users through LinkedIn posts.

If I were starting over, I'd do more content marketing and build bigger audiences up front.

Threats and opportunities

Suggested header: Why content marketing is crucial for startups

The biggest challenge for us was how rapidly AI capabilities developed — the competitive landscape and differentiation changed completely.

Fortunately, we made the right architectural choices, releasing the right product at the right time.

The key lesson was this: Navigating rapid tech changes is tough for startups, but even tougher for incumbents. Startups and indie hackers should view this disruption as an opportunity, not a threat.

In my case, automation technology has been relatively stable over the past 10 years, with players like Make.com, n8n, Zapier. This stack is now considered legacy with AI orchestration, new models, and orchestration frameworks.

Find the bottlenecks

Here's my advice:

  1. Understand agentic behavior: Focus on agents that handle processes end-to-end, not just AI wrappers.

  2. Identify customer problems where AI solutions can drive revenue and cut costs.

  3. Find tasks that are repetitive and are done manually — convert them to Agents. Start with one high-value task that is painful, directly impacts revenue, or customer experience. Use that as a wedge to rapidly expand to other tasks.

What's next?

My future goals are to build an AI-native company at scale with minimum headcount that delivers significant value to customers through rapid growth, selling more to existing customers, and reducing wasteful spend/headcount. To get there, we'll use our own agents for customer support and growth strategies.

I also want to improve agent reliability through evals and CI/CD pipelines.

You can learn more about our growth story on our blog, or connect with me on X and LinkedIn. And check out Meerkats!

Indie Hackers Newsletter: Subscribe to get the latest stories, trends, and insights for indie hackers in your inbox 3x/week.

About the Author

Photo of James Fleischmann James Fleischmann

I've been writing for Indie Hackers for the better part of a decade. In that time, I've interviewed hundreds of startup founders about their wins, losses, and lessons. I'm also the cofounder of dbrief (AI interview assistant) and LoomFlows (customer feedback via Loom). And I write two newsletters: SaaS Watch (micro-SaaS acquisition opportunities) and Ancient Beat (archaeo/anthro news).

Support This Post

20

Leave a Comment

  1. 1

    This is fascinating. 'Digital growth agency in software' — that's a bold positioning. $3k MRR in 4 weeks is solid for a launch.

    Quick question — you mentioned agencies are a key customer. When you cold outreach to agencies, what's the one thing that gets them to reply? Are they scared AI will replace them, or excited to use it to serve more clients?

    I'm building Bexra — Helping entrepreneurs find, build & grow. Still pre-launch. Your point about 'start with one high-value task that impacts revenue' is exactly what I'm trying to figure out for my own GTM.

    Also curious — you said you'd do more content marketing earlier. What kind of content has worked best for you? Technical deep dives? Case studies? Founder stories?

    Thanks for sharing the real numbers and the stack. Supabase + Fly.io is an interesting combo.

  2. 2

    4 weeks to $3k is wild — was there a specific angle or niche within AI orchestration that gave you that initial traction, or did you find product-market fit more gradually?

  3. 2

    The niche wedge point really resonates.

    You mentioned starting with one high-value, painful task as a wedge — that's exactly the approach I'm taking with what I'm building now (automated CRM for aesthetic clinics, starting with WhatsApp response automation).

    The temptation is always to build broad from day one, but watching how Meerkats focused on agency GTM pain first makes the case for going deep before going wide.

    Curious: at what point did you feel confident enough to expand beyond that first use case? Was it a revenue threshold, or more about seeing a pattern in how customers were stretching the product?

  4. 1

    The Outcome-as-a-Service framing is the actual story here. Consumption-based feels clean until customers realiz they can't predict the bill. Outcome-pricd agents land better because the buyer knows what they're getting before the meter starts.

  5. 1

    20 years of GTM experience and still shipping at this pace — respect.
    The “digital growth agency in software” angle is smart, especially for agencies who don’t want to build their own agent harness.

    One thing I noticed: you launched into a crowded market (AI orchestration) and hit $3k MRR in 4 weeks. That’s solid. But crowded markets eat startups that guess instead of validate.

    I built TrendyRevenue – an AI tool that validates startup ideas in 10 seconds (market demand, competitor gaps, revenue potential, trends). It’s the “go/no-go” filter before you build or pivot.

    For Meerkats.ai, if you ever test new features or target a new agency vertical, run it through the free tier (one analysis, no card). It’ll tell you which sub-niche has real demand vs just hype.
    The Pro plan ($39/mo) adds source-cited competitor gaps + revenue modeling — the “why” behind the signal.

    Since you’re already doing cold outreach and LinkedIn, imagine layering that with data-backed positioning. Your GTM would get even tighter.

    Either way, congrats on the launch. The University of Chicago backing is a nice signal. Keep building in public — it helps everyone.

  6. 1

    five intelligence agencies just published agent guidance. first word in the title: careful. curious if meerkats has a stance on the silent-failure case - agent runs, consumes tokens, returns 200, produces nothing. that's the one exception escalation rules weren't built for.

  7. 1

    One thing I think a lot of people are underestimating right now is how quickly “AI tooling” is turning into “AI operational infrastructure.”

    The interesting part of your story is not just the $3k MRR in 4 weeks. It’s the shift from isolated AI features to end-to-end workflow ownership.

    Most companies are still treating AI as a productivity layer sitting beside existing operations. But the real leverage starts appearing when the system begins owning execution loops across GTM, follow-up, enrichment, qualification, reporting, etc.

    Your point about “service-as-a-software” is especially important. I think a lot of SMBs do not actually want more tools. They want outcomes without needing to hire larger teams or orchestrate fragmented systems themselves.

    Also agreed on the architectural timing point. The pace of change right now heavily favors smaller teams that can adapt quickly without enterprise inertia slowing them down.

  8. 1

    Great example of how deep GTM experience + fast execution can still win in crowded AI markets. The focus on solving repetitive revenue workflows instead of just building “AI wrappers” really stands out. Also interesting to see content marketing mentioned as the one thing they’d double down on earlier.

  9. 1

    The "Service as a Software" framing is interesting - it's a smarter wedge than just selling a platform.

    Agencies are already comfortable paying for outcomes, so packaging it that way removes the "Rebuilding workflows" objection entirely.

    The point about rapid AI capability shifts being harder on incumbents than startups is underrated.

    Make.com and Zapier spent years building moats that are now partially irrelevant , a four-week-old product can leapfrog them architecturally because there's no legacy to protect.

    One thing I'm curious about , you mentioned targeting agencies that run campaigns without AI.

    How are you finding that pitch lands? Are agencies generally open to the idea that their manual workflow is the problem, or do you have to reframe it as "we make your team faster" rather than "we replace what your team does"?

  10. 1

    Yes, automation technology has been relatively stable over the past 10 years and helped a lot of SaaS companies. Good job.

  11. 1

    "We're in a similar spot. How did you get your first users?"

  12. 1

    Curious about the Outcome-as-a-Service piece. How are you actually pricing it when the agent completes a task vs a human VA would? Feels like this is where the agency model breaks, and I'd love to hear how others here are thinking about it too.

  13. 1

    Going from launch to $3k+ MRR in 4 weeks with a GTM automation platform is a strong early signal, especially with that hybrid SaaS + service angle.

    Curious—what’s actually driving most of that revenue right now: product usage, agency services, or a mix of both?

    If useful, I can map your funnel (lead → onboarding → service/product split → Stripe revenue) and show where you might be leaking or underpricing—free.

  14. 1

    Super impressive — $3K MRR in 4 weeks is no joke. Love how you focused on real workflow orchestration instead of just another AI wrapper. The service-as-software angle feels especially powerful. Curious how you’re thinking about long-term defensibility in such a fast-moving space?

  15. 1

    It's really nice, and the growth channels you mentioned are kinda perfect for this kind of platform. content marketing would also attract alot of small scale agencies, but specific funnels like email marketing and events filter out realistic paying audience. Really gave me a new perspective.

  16. 1
    1. Nice concept. I’m helping test DealDoctor — a tool that gives founders brutally honest feedback on positioning and startup blind spots.

  17. 1

    Reading this from the other side — engineer building solo, prepping launch, GTM is the part I'm least comfortable with. The line that hit hardest: "if I were starting over, I'd do more content marketing and build bigger audiences up front."

    Is that purely a distribution call, or did you find content also sharpened your thinking on positioning along the way?

  18. 1

    The "Service as a Software" framing is really interesting and I think it's where a lot of the AI tool market is heading. Especially for small teams who don't have dedicated marketing ops people but still need the output that a full agency would deliver.

    What caught my attention is the agency services layer on top of the platform. That's a smart funding mechanism but also a product insight. Most AI tools try to be fully self-serve from day one and then wonder why activation is terrible. The reality is that someone still needs to configure the workflows, define the ICP, set up the sequences. Having humans do that setup while the platform handles execution is probably the right hybrid for this stage.

    I run a marketing agency and we use AI heavily in our workflows now. The tools that actually stuck for us were the ones that handled one specific task really well, not the ones that tried to replace the entire agency function at once. Enrichment is a great starting wedge because the output is immediately verifiable. Either the data is accurate or it isn't. That builds trust fast.

    Curious about the $3k MRR breakdown. Is that mostly from the platform subscriptions, the agency services layer, or a mix? And how are you thinking about the transition from agency-supported onboarding to fully self-serve as you scale?