RevenueCat in
Current subscription events and customer state
Spinning FalconPrivate beta
Revenue recovery operations for RevenueCat apps
Turn RevenueCat events into revenue recovery campaigns.
Detect failed renewals, canceled trials, and win-back opportunities. Create and send email, push, and in-app messages directly from Spinning Falcon—then measure the subscriptions that return.
✓Email, push & in-app built in✓Guided channel setup✓Existing tools still welcome
Recovery logic
Prebuilt cohorts, eligibility, and suppressions
Campaigns out
Coordinated email, push, and in-app actions
Revenue confirmed
Renewals, uncancellations, and reactivations
How it works
From subscription event to recovered revenue.
Spinning Falcon sits between RevenueCat and customer engagement. It supplies the recovery-specific operating layer: what happened, who is still eligible, what to send, when to stop, and which subscription event confirms the result.
A recovery journey
One event becomes a coordinated campaign—not another webhook to babysit.
RevenueCatAction needed
BILLING_ISSUE
Customerapp_user_8472PlanPro AnnualReceivedjust now
Recovery logic
Should we send?
Subscription still at risk✓Yes
No recovery already recorded✓Clear
Customer contactable✓Ready
One campaign
Three coordinated moments
Outcome
✓↻
RENEWAL
Subscription recovered
£39.99
Revenue confirmed
Illustrative customer journey · Actual outcomes are confirmed by subscription events
Messaging is built in
Set up email, push, and in-app without assembling another messaging stack.
Spinning Falcon includes channel setup, message creation, templates, previews, test sends, activation controls, and delivery history. Launch directly—or connect the tools your team already prefers.
Channel launch path
Configure once. Reuse across recovery plays.
SF
Payment recovery campaign
What your customer actually sees
EmailPushIn-app
Inbox · sam@example.com
SFSAMPLE APP
SubscriptionAction needed
Keep your subscription active
Hi Sam, we couldn’t renew your subscription. Update your payment method to keep your plan active—your saved progress is still here.
Sent automatically from your verified domain
Email · responsive preview
9:42
SF
Sample App
now
Keep your subscription active
Update your payment method to keep access to your plan.
Push · deep-linked
SF
Let’s keep your plan active
Update your payment method and pick up where you left off.
Maybe later
In-app · state-aware
01
Compose once
Shared recovery intent
02
Preview every surface
Desktop and device views
03
Stop when recovered
Current state checked before send
Verified-domain delivery
Add your sending domain, copy the provided DNS records, verify it, and choose the sender customers see.
- Starter templates
- Desktop and mobile preview
- Test sends before activation
Firebase-backed delivery
Push
Connect your Firebase sender once. On iOS, the optional push package handles permission and app-install token registration in one call.
- Deep links and images
- Dashboard test sends
- Per-app delivery controls
Native app experiences
In-app
Choose a placement and trigger, then create a message, banner, or survey and test it against an app user.
- Messages, banners and surveys
- Theme and CTA controls
- Test before activation
Your choice
Use Spinning Falcon end to end, or keep your current providers. The recovery state, audience rules, channel coordination, and subscription measurement stay in one operating layer either way.
Recovery flows
Build the recovery logic once. Let subscriber state run it.
A flow combines the RevenueCat trigger, audience eligibility, message timing, channel sequence, stop rules, and the subscription event that proves recovery.
Illustrative flow
Failed-renewal rescue
- 01
BILLING_ISSUE
RevenueCat opens a recoverable case.
- 02
Still eligible?
Check subscription state before every action.
- 03
Email → push → in-app
Coordinate timing and content across channels.
- 04
RENEWAL
Stop the flow and confirm recovered revenue.
Built for developers, operated by growth
A small technical handoff—not a permanent integration project.
Engineering connects subscription state and app delivery once. Spinning Falcon then gives the operating team a reusable workspace for flows, messages, testing, suppressions, and outcome reporting.
- 01
Connect RevenueCat
Add the Spinning Falcon webhook and keep the same app user ID across RevenueCat and the SDK.
- 02
Add the app SDK
Install the Swift package for lifecycle events and in-app placements. Add the optional push package for one-call iOS push setup.
- 03
Configure delivery once
Verify the email sender domain, connect Firebase sender credentials, and define the in-app placements your product exposes.
- 04
Hand control to growth
Teams can compose, test, activate, and review future recovery flows without shipping new campaign logic each time.
SpinningFalconSetup.swift
import Foundation
import SpinningFalcon
import SpinningFalconPush
let sf = SpinningFalconClient(
config: SpinningFalconConfig(
baseURL: URL(string: "YOUR_API_BASE_URL")!,
workspaceId: "YOUR_WORKSPACE_ID",
appId: "YOUR_APP_ID",
apiKey: "YOUR_SDK_KEY"
)
)
// Use the same ID passed to RevenueCat.
sf.identify(appUserId)
// Optional one-call iOS push setup.
try await sf.enablePushNotifications()
// Ask SF which in-app experience is eligible.
let message = try await sf.evaluateInAppPlacement(
placementKey: "recovery_offer"
)RevenueCat
Subscription state
App SDK
Push + in-app
Dashboard
Build + measure
Why Spinning Falcon
Focused on the recovery job—not every marketing job.
The advantage is more than channel delivery. It is a RevenueCat-native recovery model—with built-in email, push, and in-app tools—that helps a small team get from signal to measurable action without rebuilding the operating logic.
RevenueCat
Subscription source of truth
Spinning Falcon operationalises RevenueCat events across multiple recovery plays and customer channels, then brings the outcomes into one recovery view.
Messaging platforms
Built-in delivery or bring your own
Spinning Falcon can create, test, and deliver email, push, and in-app messages itself. If you already use a messaging platform, it can remain in the stack while Spinning Falcon supplies the recovery states, audiences, suppressions, and outcome model.
Custom recovery stack
Maximum control, maximum ownership
Spinning Falcon removes the need to maintain webhook routing, recovery cohorts, flow logic, channel coordination, and revenue reporting from scratch.
Built in, without lock-in. Send through Spinning Falcon or keep existing engagement tools as the delivery layer. RevenueCat remains the subscription source of truth.
Time to value
Stop rebuilding the same recovery system.
Spinning Falcon is designed to reduce both the engineering work required to launch recovery and the ongoing operational work required to keep it accurate.
The promise we can defend today
A clear path from RevenueCat connection to one tested recovery play—without building a custom lifecycle pipeline. Measured setup-time savings will come from the founding pilots.
Build it yourself
Six jobs to own forever
Webhook routingAudience queriesFlow logic3 channel toolsSuppressionsRevenue joins
engineering + ops overhead
With Spinning Falcon
One recovery operating layer
→
Recovery
logic
→logic
✓ Email✓ Push✓ In-app
Connect once, then let growth operate campaigns without rebuilding the subscription-state logic.
State before send
Every action checks the subscriber’s current recovery state before another message is sent.
Channels work together
Email, push, and in-app steps share one recovery intent instead of becoming separate campaigns.
Outcomes over clicks
The result is confirmed by a subscription event—not simply an open, click, or attributed session.
Simple, usage-aligned pricing
Start small. Scale with your app.
Choose a plan by monthly downloads. Every plan is built around RevenueCat recovery campaigns and the subscription outcomes they return.
Planned launch pricing. Private-beta applicants will confirm their plan before any paid service begins.
Free
$0/mo
For apps with up to 500 monthly downloads.
- Connect RevenueCat
- Launch one recovery flow
- Basic lifecycle tracking
- Spinning Falcon branding
Starter
$49/mo
For apps with up to 2,000 monthly downloads.
- Trial and renewal recovery
- Email and push automation
- Subscriber-state suppression
- RevenueCat outcome tracking
Growth
Most popular$149/mo
For apps with up to 10,000 monthly downloads.
- Everything in Starter
- Win-back campaigns
- Subscriber segmentation
- Multi-channel automation
Scale
$399/mo
For apps with up to 30,000 monthly downloads.
- Everything in Growth
- Multi-product support
- Priority support
- Custom integrations
More than 30,000 monthly downloads? Contact us for custom pricing.
Recovery Lab
Decision-useful guidance for RevenueCat operators.
Practical guidance connecting subscription state, customer action, and a measurable revenue outcome.
Browse the Recovery Lab →Questions, answered
Know what you are joining.
The private beta starts with one recovery problem and one measurable outcome, so setup and proof stay focused.
What does Spinning Falcon do?+
Spinning Falcon turns RevenueCat subscription events into recovery operations. It identifies recoverable moments, prepares the right cross-channel campaign, keeps the audience aligned to current subscription state, and measures renewals, uncancellations, and reactivations.
Does it replace RevenueCat?+
No. RevenueCat remains the subscription source of truth. Spinning Falcon uses those lifecycle events to operate and measure recovery campaigns.
Does it replace OneSignal, Customer.io, or our email platform?+
It can, but it does not have to. Spinning Falcon includes tools to create, test, send, and review email, push, and in-app messages directly. If you already use OneSignal, Customer.io, or another delivery platform, it can remain in the stack while Spinning Falcon operates the RevenueCat-specific recovery logic and measurement.
How difficult is setup?+
The setup is guided by channel. For email, add a sending domain, copy the supplied DNS records, verify, and send a test. For push, connect Firebase sender credentials and let the SDK register app-install tokens; iOS supports one-call push setup. For in-app, add the SDK, choose a placement and trigger, then test the experience against an app user. Push and in-app delivery require the relevant app SDK if it is not already installed.
How does Spinning Falcon save time?+
It replaces repeated integration, audience, flow, suppression, copy, and reporting work with a recovery system already structured around RevenueCat subscription states. We will publish measured setup-time and operational-savings claims after the founding pilots.
Can I use it today?+
Spinning Falcon is in private beta. We are onboarding a small number of RevenueCat apps directly, starting with one high-value recovery play and one clearly defined outcome.
Private beta applications open
Launch one measurable recovery play. Without building the recovery stack.
Apply with a few aggregate details about your RevenueCat app. Qualified teams receive direct onboarding, built-in channel setup, a focused first campaign, and outcome reporting built around the subscription event that proves recovery.