Access model
Separate products, clear promises
Pricing should be understandable before checkout: Premium is a tool subscription, clean export credits are one-time export access, and future store packs are creator/content purchases.
Subscription access for premium workspace tools, ad-free usage while active, advanced diagnostics, richer export controls, and priority creator utilities.
A one-time watermark-free export credit for a specific export flow, separated from Premium so users know exactly what the credit buys.
Future paid boot packs, bundles, or creator drops remain separate content purchases with attribution, compatibility notes, and clear access labels.
Creator bundles and featured drops should reward reliable metadata, original work, review quality, and maintained compatibility notes.
Manual grants, refunds, test access, and entitlement corrections belong in protected support workflows with audit evidence.
Future hosted demo mirrors, admin dashboards, client sites, or white-label deployments can become separate business products without confusing app Premium.
| Premium | Recurring subscription for app/tool capabilities while active. |
|---|---|
| Clean export credit | One-time entitlement for a clean export use case; not a creator pack purchase. |
| Store pack | Future creator/content purchase with attribution and compatibility notes. |
| Creator revenue | Future admin-reviewed payout/bundle lane; not public until billing, tax, and dispute rules are ready. |
Billing clarity
What users should never have to guess
Every paid path needs plain language around access type, renewal, refund/support route, and what happens when a subscription ends.
Show whether the item is subscription, one-time credit, free pack, or future paid pack.
Keep Premium benefits separate from Boot Store creator content.
Keep receipts, refunds, grants, and entitlement repair in private support.
Use Play-safe billing wording and avoid promising unsupported install outcomes.
Monetization roadmap
From launch-safe access to creator economy
CRYA can grow monetization in stages without making current users feel misled.
Premium and clean export credits stay simple, supportable, and Play-safe.
Use store review, creator badges, compatibility notes, and support evidence to prove pack quality.
Promote reliable creator packs, seasonal collections, and free/featured drops before paid creator sales.
Add paid packs only when access labels, refunds, creator terms, and dispute handling are ready.
Explore SaaS-style admin tools, demo hosting, export wizards, and managed CRYA deployments later.
Policy guardrails
Revenue features must stay reviewable
Pricing is part product page, part compliance promise. The private admin layer should hold the evidence behind every entitlement decision.
Store order IDs, entitlement state, refunds, and manual grants belong in private support/admin records.
Refund and correction paths must be clear before users contact public community channels.
Paid pack plans need ownership, licensing, takedown, attribution, and dispute rules before launch.
Billing, ads, root tools, and install language must stay aligned with current store policy review.