Growth Experiments

Each experiment starts with a hypothesis, runs autonomously, and concludes with measured results. The agent designed and executed these, including the "agentic" experiment where it autonomously researched the landscape, identified an opportunity, and created content to fill the gap.

content-series

running

Hypothesis: Publishing a multi-part tutorial series drives more engagement than standalone posts

Metric: posts_published Channel: blog
Tactic

Write a connected series of tutorials on a single RevenueCat feature area

Output: 3 posts published
Results:
Note Three-part series published. Engagement comparison vs standalone posts not yet measured — no analytics instrumented.
Output Metric posts_published
Output Value 3
Pending ['Page views per post vs standalone articles', 'Read-through rate across series', 'Return visitors from part 1 to parts 2-3']

agentic

running

Hypothesis: Vibe coders represent 35%+ of new RevenueCat signups but face a well-documented "monetization gap." Creating comprehensive content targeting "vibe coding monetization" search intent — combining MCP server workflows, Web Billing setup, and paywall configuration into end-to-end guides — will fill a content gap that neither RevenueCat's existing docs nor competitors currently address.

Metric: content_pieces_with_citations Channel: agent_determined
Tactic

Created 2 content pieces targeting the vibe coding monetization gap: (1) An agent playbook providing a step-by-step 30-minute workflow from AI-built app to live subscriptions using RevenueCat MCP + Paywalls + Web Billing, and (2) An analysis/case study diagnosing the 3 specific technical gaps killing vibe-coded app revenue and positioning RevenueCat as the solution. Both pieces include 15+ citations from RevenueCat docs and third-party sources.

Artifacts:
Findings

Market Signal Confirmed: Multiple 2025 sources confirm the vibe coding monetization gap is real and growing. Key data points:

  • RevenueCat powers 50%+ of AI-built iOS apps (TechBuzz/TechCrunch)

  • AI-referred signups surged from <5% to 35%+ of new customers in one year (Q2 2024→Q2 2025)

  • 63% of vibe coding users are non-developers (State of Vibe Coding 2025)

  • Multiple articles ("Everyone is vibe coding. Nobody is making money.") confirm unmet monetization need

Content Gap Identified: RevenueCat has 3 separate doc assets (MCP server, SDK Quickstart, Web Billing) but NO unified content that stitches them into a single monetization workflow for vibe coders. The existing vibe coding landing page (revenuecat.com/class/vibe-coding) is marketing, not a technical playbook. Competitors (Adapty, Qonversion) have zero vibe-coding-specific content.

Specific Gaps Filled: 1. No existing content shows the complete MCP→SDK→Web Billing workflow in sequence 2. No content connects the April 2025 court ruling on external payments to the vibe coder audience 3. No content quantifies the fee comparison (3% web vs 30% App Store) for this audience 4. The "3 technical gaps" framing (store config, paywall design, economics) doesn't exist elsewhere

Competitive Advantage: RevenueCat's MCP server + Test Store combo is uniquely suited to vibe coders because it means an AI agent can configure AND test subscriptions without the developer leaving their IDE. No competitor offers this workflow.

Results:
Note Content produced and published. Engagement and search ranking tracking pending — no analytics instrumented yet.
Output Metric content_pieces_with_citations
Output Value 2 pieces, 24 total citations
Pending ['Search ranking for target keywords', 'Page views / time on page', 'Inbound links or shares']