Growth Campaign Plan + Early Receipts

RevenueCat Growth Brief — Growth Campaign

Goal

Drive awareness and adoption of RevenueCat's Charts API among AI agent developers and growth communities by launching RevenueCat Growth Brief as a practical operator workflow.

Primary launch wedge

An AI agent for weekly subscription ops, powered by RevenueCat's Charts API.

This wedge is more novel and specific than "brief-first monetization operator" alone. It targets the exact audience RevenueCat wants to reach: developers building AI-powered products who need subscription analytics.

Target audiences (ranked by fit)

Tier 1 — Growth operators and subscription founders

Tier 2 — AI agent developers

Tier 3 — Indie mobile/web app builders

Campaign sequence

Day 1 — Launch

  1. Push final repo state
  2. Publish blog post
  3. Post launch thread on X (Post 1: hook + proof)
  4. Post on RevenueCat Community — launch announcement with operator workflow angle
  5. Post on Indie Hackers — builder-style post

Day 2 — Deepen

  1. Share video demo
  2. Post technical angle on X (Post 3: agent/dev angle)
  3. Post RevenueCat-specific angle on X (Post 4)
  4. Post on one founder subreddit (r/SaaS or r/SideProject) if community-fit is strong

Day 3–5 — Sustain

  1. Post remaining social angles
  2. Engage with replies across all channels
  3. If HN-quality bar is met, submit Show HN

Communities (at least 3 required)

1. X / Twitter

2. RevenueCat Community

3. Indie Hackers

4. AI builder Discords (selective)

Budget allocation ($100)

SpendAmountPurpose
Design polish: demo screenshot + OG image$25One compelling visual asset for social/community CTR — screenshot of the contradiction finding with annotation
Video captioning + 30s cutdown clip$25Captions for accessibility, plus a 30-second highlight reel for X/Discord embeds
Micro-creator placement$35Reserved for a small paid test if a niche newsletter supports low-budget placements; otherwise reallocated to creative production or held unspent
Contingency: boost only after organic proof$15Hold for paid amplification only after one organic post proves traction (>50 engagements)

Principle: spend nothing on paid amplification until organic performance validates the creative. The $15 contingency only gets spent if a post earns attention on its own first.

Direct outreach plan (10 people)

In addition to community posts, directly share the project with 10 specific people who are likely to find it genuinely interesting:

  1. 3–4 indie mobile founders who have publicly discussed RevenueCat or subscription analytics pain (find via X search for "RevenueCat dashboard" or "subscription metrics")
  2. 2–3 AI agent builders who have shipped agent-analytics projects or discussed structured data feeds for agents
  3. 2–3 DevRel/growth practitioners who write about developer tooling or subscription growth

Each DM is personalized: "Built this on RevenueCat's Charts API — thought you'd find the approach interesting given [specific thing they've posted about]. No ask, just sharing."

This is not spam. It is targeted sharing with people who would genuinely benefit from seeing the project.

Per-community angle customization

CommunityLead angleWhat NOT to do
XContradiction hook + real numbersDon't lead with "I built a thing"
RevenueCat Community"Here's a practical Charts API use case with implementation learnings"Don't pitch — teach
Indie Hackers"What I learned building on RevenueCat's API in 48 hours" — builder storyDon't post as a launch; post as a build log
AI builder Discords"An AI agent built this operator tool — here's the pattern for structured analytics"Don't oversell the AI angle; focus on the deterministic design choice

Measurement plan

Primary metrics

Secondary metrics

What to watch first

  1. Does "weekly growth brief" or "Charts API for agents" resonate more?
  2. Which audience tier engages most?
  3. Does the proof-driven social post outperform the conceptual ones?

Why this campaign is credible

This is a concrete distribution plan. It targets communities where subscription builders already spend time, operator workflows are relevant, and a public repo + launch post can realistically attract useful attention.

The $100 budget is small. The strategy optimizes for organic reach first, with paid amplification only on the best-performing organic asset.

Launch receipts — live distribution (Day 1)

These are real posts made by Kit as part of this campaign. All include agent disclosure.

X / Twitter (@Kit4crf)

PostTypeURL
"I'm an AI agent that analyzes subscription data…"Original postx.com/Kit4crf/status/2034004264755073399
"3 ways MRR lies to you"Original post@Kit4crf timeline
Reply to @wickedguro (Postiz, $60k MRR churn)ReplyThread
Reply to @beingecom (coffee subscription churn audit)ReplyThread
Reply to @pstavirs (annual MRR question)ReplyThread

Reddit (u/KitTheRevenueCat)

ThreadSubredditApproach
MRR tracking gets weird with annual prepaymentsr/SaaSHelpful comment + tool link
Just crossed 200 MRR todayr/AppBusinessAnalyzed OP's RevenueCat screenshot + tool link
The change that helped us cross $50k MRRr/SaaSPure value comment (no tool push)

RevenueCat Community (KitRCAdvocate)

ThreadCategoryURL
Using the Charts API to detect when revenue and MRR tell different storiesDashboard & Toolscommunity.revenuecat.com

Early signals

Note: This is Day 1 early data. Results should be revisited after 48–72 hours for meaningful signal.