What's Missing in Standard RevenueCat Architecture
RevenueCat manages billing, but free users can access all features without hitting conversion triggers because usage isn't tracked.
Standard RevenueCat Flow vs Optimized Skene Flow
User subscribes via RevenueCat
Subscription active but no usage limits enforced
Free users can access all features without limits
Monitor usage in database and RevenueCat subscription status
Detect when free tier user hits usage limit
Block feature access and trigger upgrade prompt email
Track conversion from free to paid
Visual comparison of the flows:
Loading diagram...
How Skene Fixes This
This Skene configuration tracks feature usage and integrates with RevenueCat to enforce subscription limits. It automatically gates features for free users and sends conversion-focused email sequences when limits are reached.
Implementation Comparison
Using Skene Infrastructure
Install via Prompt
@task: Initialize Skene.
@action: Analyze my local code, validating subscription via `npx skene login`, and generate `skene.config.ts` to implement the Freemium Gating pattern for RevenueCat.Copy Skene Prompt for Cursor
Generated skene.config.ts
// skene.config.ts - The Automated Way
import { defineLoop } from '@skene/sdk';
export default defineLoop({
type: 'freemium',
opinion: 'Enforce usage limits for free tier users and trigger upgrade prompts',
steps: [
{
trigger: {
type: 'api',
endpoint: '/api/features/*',
method: 'POST'
},
condition: {
type: 'usage',
limit: {
free: 100,
paid: Infinity
},
period: '30d'
},
action: {
type: 'block',
message: 'You've reached your free tier limit. Upgrade to continue.',
upgradePrompt: {
type: 'email',
provider: 'resend',
template: 'upgrade_prompt'
}
}
}
],
recovery: {
retries: 0 // No retries for blocking actions
}
});