Product types & use cases

Pocketsflow is built for digital products. This guide helps you map your idea to the right setup — one-time product or subscription, which pricing model, and how to structure related offers — so you launch faster and avoid rework.

​

When to use this guide

Use this page when you are:

• Planning a new offer and deciding how to structure it.
• Migrating from another platform (for example, Gumroad or Lemon Squeezy) and mapping existing products.
• Unsure whether to use one-time purchases, subscriptions, or a lifetime deal.
• Deciding between fixed pricing, pay-what-you-want, or variants.

​

The two building blocks

Everything you sell is one of two objects. Get this choice right first; the rest is configuration. The single most important question:

Is the value delivered in one shot, or continuously over time? One shot → product. Over time → subscription.

​

One-time products

Best for:

• Guides, eBooks, and playbooks.
• Notion templates and document packs.
• Icon packs, wallpapers, fonts, 3D assets, and UI kits.
• License keys, presets, or one-off downloads.
• A standalone course with lifetime access.

Characteristics:

• The customer pays once and keeps access to the content.
• Low-friction checkout — email plus payment, done.
• No recurring billing, trials, or dunning to manage.
• Delivery is a file download, a URL you send buyers to, or a callback URL that lets your own system fulfill the order (for example, generate and email a license key).

Configuration tips:

• Choose a page layout that fits the content (see Page templates).
• Bundle related files together to raise perceived value.
• If you plan future updates, say so explicitly — “free lifetime updates” is a strong buy trigger for templates and design assets.

​

Subscriptions and memberships

Best for:

• Communities and memberships.
• Cohort-based or continuously updated courses.
• Content that ships on a cadence (weekly lessons, monthly drops, a signal feed).
• Tools or services billed monthly.

Characteristics:

• Recurring billing on a weekly, monthly, or yearly schedule.
• Access is tied to an active subscription and its status.
• Optional free trial and a self-service portal for subscribers.
• Requires clear communication about renewal, trial, and cancellation.

Configuration tips:

• Consider offering both a monthly and a discounted yearly plan (publish them as two subscriptions and let buyers pick).
• Clearly describe what subscribers get every billing period, not just once.
• Use a trial to lower the barrier to the first “yes.”

The full walkthrough is in Subscriptions.

​

Common use-case patterns

​

Courses

Courses can be structured either way:

• One-time purchase with lifetime access — the classic “buy the course” model.
• Subscription to a course library — ongoing access to a growing catalog.

Tips:

• Use a page layout with room for a curriculum or module list.
• Highlight outcomes (“Ship your first product in a weekend”), not just a module count.
• Combine with community or live sessions via upsells or bundles.

​

Communities

• Almost always a subscription — the value (access, conversation, events) is continuous.
• Deliver access with a URL (a Discord/Slack invite or members area) or a callback URL that provisions the member in your own system.
• A trial works well to let people feel the room before committing.

​

Templates and packs

• One-time products, optionally grouped into bundles.
• Emphasize what’s inside and the time it saves.
• “Free future updates” pairs naturally with template products.

​

Tools, licenses, and SaaS-style offers

• Subscription for recurring access, or a one-time product with a callback URL that issues a license key on purchase.
• Use the callback/webhook flow to activate the account programmatically.

​

Bundles and packs

Bundles combine multiple related items into a single, higher-value purchase. Best for:

• Combining related products (for example, templates + icons + a mini-course).
• Offering tiered value (starter vs. complete).

Configuration tips:

• Make the bundle’s value obvious versus buying each item separately.
• Explain how buyers access each component after purchase.

See Upsells & bundles for setup and strategy.

​

Lifetime deals

Best for:

• Early supporters, launch promotions, and “pay once, keep forever” offers.

Configuration tips:

• Model a lifetime deal as a one-time product with ongoing access.
• Be explicit about what “lifetime” means (the lifetime of the product? of your business?) in your terms.
• Lifetime deals trade long-term recurring revenue for up-front cash — use them deliberately, often as a limited-time launch lever.

​

Flexible pricing options

These layer on top of the product types above.

​

Choosing the right structure

Ask yourself:

• Is the value delivered in one shot or over time?
  • One shot → one-time product.
  • Over time → subscription.
• Do I want predictable recurring revenue?
  • Yes → subscription or membership.
  • No → one-time products, optionally with upsells.
• Will I offer multiple related products?
  • Yes → consider bundles, or a mix of one-time and subscription products.
• Do I want to lower the barrier to the first purchase?
  • Subscription → add a free trial.
  • One-time → offer a low-priced entry product with an upsell to the flagship.

​

Mapping Pocketsflow to your use case

​

What’s next

• To configure a specific product, continue to Create a product.
• To add recurring revenue, see Subscriptions.
• To maximize revenue per customer, see Upsells & bundles.
• To design the page buyers see, see Page templates.

​

Example code

Developers embedding checkout or handling webhooks can start from a runnable example — one per building block: