App Pricing Models
LaunchMyStore supports multiple pricing models for your app. Choose the model that best fits your value proposition and customer expectations.Available Models
Free
No charge. Good for lead generation or basic utility apps.
One-Time
Single payment for lifetime access. Good for tools and templates.
Recurring
Monthly or annual subscription. Most common for feature-rich apps.
Usage-Based
Pay per use (API calls, orders, etc.). Good for volume-dependent apps.
Free Apps
Free apps don’t charge merchants but can still generate value:- Lead generation for your other products
- Simple utilities that build goodwill
- Apps funded by other revenue (affiliate, data)
- Open source projects
Free apps are great for building reputation in the marketplace. Many developers start free and add paid tiers later.
One-Time Purchase
Single payment for permanent access:- Theme modifications
- One-time setup tools
- Templates and presets
- Migration utilities
- No recurring revenue
- Customer expects lifetime updates
- Lower total revenue per customer
- No ongoing relationship
Recurring Subscription
Monthly or annual billing, the most common model:Annual Billing
Offer discounts for annual commitment:Free Trial
Let merchants try before buying:| Option | Description |
|---|---|
days | Trial duration (7, 14, or 30 days) |
requirePaymentMethod | Require card upfront (reduces cancellations) |
Usage-Based Pricing
Charge per real-world event — per SMS sent, per AI generation, per shipping label printed. Declared as ausage block on a recurring
plan (LaunchMyStore does not have a standalone usage_based model —
metered always rides on top of a Stripe subscription, even if the flat
monthly price is 0):
cappedAmount = $50 default monthly limit), idempotent
event reporting, and end-of-period invoice handling are wired into the
platform.
See Usage-Based Billing for the full event →
invoice flow and Usage Records API
for endpoint references.
Hybrid Models
Combine models for flexibility:Freemium
Free tier with paid upgrades:Base + Usage
Flat monthly subscription plus a per-event metered component — this is the most common shape. Both items appear on one Stripe subscription; the merchant sees a combined invoice each period.POST /api/v1/billing/usage call adds one UsageRecord to the
Stripe metered item; at period end Stripe sums the records, multiplies
by unitAmount, and bills monthlyPrice + total_usage.
Pricing Best Practices
Anchor with a higher tier
Anchor with a higher tier
Show a premium tier even if most customers choose the middle option. It makes the mid-tier feel like a good value.
Limit the free tier
Limit the free tier
If offering freemium, make sure the free tier has meaningful limits that encourage upgrades as the merchant grows.
Offer annual discounts
Offer annual discounts
15-20% annual discount reduces churn and improves cash flow. Frame it as “2 months free.”
Avoid too many tiers
Avoid too many tiers
2-3 tiers is ideal. More than 4 creates decision paralysis.
Price based on value
Price based on value
Price based on the value you create, not your costs. A 500/month is a good deal.
Test pricing
Test pricing
A/B test pricing pages. Small changes can significantly impact conversion.
Displaying Pricing
Use the pricing display components in your app listing:Price Changes
When changing prices for existing customers:- Grandfather existing customers - Keep them on old pricing
- Give notice - 30 days minimum for price increases
- Explain value - Communicate what’s improved
Currency Support
LaunchMyStore supports multiple currencies:Revenue Share
LaunchMyStore takes a percentage of app revenue:| App Type | Revenue Share |
|---|---|
| Public apps | 20% |
| First-party apps | 0% |
| Private apps | 0% |
See Also
- Stripe Integration - Set up payments
- Usage-Based Billing - Implement usage metering