What's Missing in Standard Paddle Architecture
Paddle manages billing, but free users can access all features without hitting conversion triggers because usage isn't tracked.
Standard Paddle Flow vs Optimized Skene Flow
Standard Flow
1
User subscribes via Paddle
2
Subscription active but no usage limits enforced
3
Free users can access all features without limits
Skene Flow
1
Monitor usage in database and Paddle subscription status
2
Detect when free tier user hits usage limit
3
Block feature access and trigger upgrade prompt email
4
Track conversion from free to paid
Visual comparison of the flows:
Loading diagram...
How Skene Fixes This
We built a Skene Prompt that installs freemium gating for Paddle. It monitors usage in your database and Paddle subscription status, automatically blocking features and triggering upgrade prompts when free users hit limits.
Implementation Comparison
Using Skene Infrastructure
Auto-managed state. Installed via Prompt.
Install via Prompt
cursor.mdc
@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 Paddle.Copy Skene Prompt for Cursor
Generated skene.config.ts
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
}
});