There is a moment in every first-time lifetime deal purchase where the buyer encounters the tier structure and has to make a decision they are not fully equipped to make: do I buy Tier 1, Tier 2, or Tier 3? Do I need to stack codes? What does "stack up to 3 codes" actually mean for my account? If I buy Tier 1 and outgrow it, can I upgrade later?

These questions seem simple. They are not. The answers depend on the specific deal's tier structure type, your current and projected usage, the campaign's stacking rules, and a forward-looking assessment of whether your needs are likely to scale into higher tiers within the campaign's lifetime. Getting this decision wrong in either direction — buying a tier that is too low or too high for your actual needs — is one of the most common and most avoidable sources of LTD buyer dissatisfaction.

This guide explains every dimension of the tier decision: the three types of tier structures and how each affects your choice, how code stacking works in practice, the mistakes buyers most commonly make, and a clear decision framework for choosing the right tier for your situation.

Why the tier decision matters more than most buyers think

The tier decision feels like a simple cost choice: pay more for more. But it has a time dimension that most buyers underweight. Unlike subscription software — where you can upgrade or downgrade your tier at any renewal cycle — a lifetime deal locks you into your tier at the time of purchase. Once the campaign closes, the pricing that applied during the campaign is gone. Upgrading later almost always means paying subscription pricing for the additional capacity, which can significantly erode the financial advantage that made the LTD attractive in the first place.

Here is a concrete example of this problem. A buyer purchases Tier 1 of a project management LTD during a campaign. Tier 1 covers 5 seats at $79. Their team is currently 3 people, so Tier 1 seems like enough with room to spare. Fourteen months later, the team has grown to 8 people. The campaign is long closed. Adding 3 more seats requires a subscription upgrade at $29 per month. Over the next 24 months, that's $696 of subscription cost on top of the $79 LTD payment. The buyer who had instead bought Tier 2 (15 seats) for $149 during the campaign spent $70 more upfront and saved $626 over the following two years.

The tier decision is not just about current needs — it is about projecting your trajectory and buying the tier that serves your actual 18-month need rather than your current-moment need.

The three types of tier structures

SaaS lifetime deal tiers are not all structured the same way. Understanding which type of tier structure a deal uses is the foundation of making the right tier choice.

Type 1: Seat-based tiers

Seat-based tiers differentiate primarily by the number of users who can access the account. The core features are identical across tiers — what scales is how many people can use the product simultaneously.

Example seat-based tier structure
TierPriceSeatsFeaturesStorage
Tier 1 (1 code)$793 seatsAll features50 GB
Tier 2 (2 codes)$15810 seatsAll features100 GB
Tier 3 (3 codes)$23725 seatsAll features250 GB

How to choose your tier in a seat-based structure: Count your current active users. Project your team size 18 months from now based on realistic growth plans. Buy the tier that covers your projected 18-month seat count with a small buffer (1 to 2 extra seats). If you are currently a solo user with no plans to add a team, Tier 1 is almost certainly right. If you have 3 current users and are growing, strongly consider Tier 2.

Type 2: Feature-based tiers

Feature-based tiers gate capabilities behind higher tiers rather than (or in addition to) limiting seat counts. Tier 1 provides core functionality. Tier 2 adds integrations, API access, or advanced capabilities. Tier 3 adds white-labelling, enterprise features, or premium support.

Example feature-based tier structure
TierPriceCore featuresIntegrationsAPI accessWhite label
Tier 1$99Yes5 integrationsNoNo
Tier 2$199YesAll integrationsYesNo
Tier 3$299YesAll integrationsYesYes

How to choose your tier in a feature-based structure: Map your current and projected feature requirements explicitly to the tier feature table. If any required feature is gated at a higher tier, buying the lower tier means either not using that feature or paying to upgrade later. Feature-based tiers require the most careful pre-purchase mapping because features cannot be unlocked piecemeal — you upgrade the entire tier or you go without.

The most common mistake in feature-based tiers is assuming that features shown prominently in the product demo are included at the base tier. They often are not. Map each demo-visible feature to the specific tier where it first appears before deciding your tier.

Type 3: Usage-based tiers

Usage-based tiers differentiate primarily by volume limits — how much you can do per month, not what you can do. The feature set is similar across tiers; what scales is how much storage, how many emails, how many API calls, or how many projects you can create.

Example usage-based tier structure (email marketing tool)
TierPriceSubscriber limitMonthly sendsAutomations
Tier 1$695,000 subscribers50,000 sends10 sequences
Tier 2$13915,000 subscribers150,000 sendsUnlimited
Tier 3$20950,000 subscribers500,000 sendsUnlimited

How to choose your tier in a usage-based structure: This requires the most careful projection work. Measure your current usage precisely. Then model your growth trajectory. For email marketing, project your subscriber list growth rate. For storage tools, estimate your content creation rate. For API tools, estimate call volume at your projected workflow scale. Buy the tier where your 18-month projected usage falls comfortably within the limit — ideally at no more than 70 to 80 percent of the limit to give yourself meaningful headroom.

Code stacking: the mechanics and the common mistakes

Code stacking — purchasing multiple codes during an active campaign to access higher tiers or increased limits — is available on many but not all LTD deals. Here is exactly how it works and where buyers most commonly go wrong.

How stacking works mechanically

When a deal supports stacking, the listing specifies how many codes you can purchase and what each additional code adds. The most common implementation: each code represents one tier level. Purchasing two codes stacks your account to Tier 2 limits. Purchasing three codes stacks to Tier 3. The maximum number of stackable codes is always specified — check this before planning any stacking purchase.

In some deals, stacking and tiers are separate concepts: tiers have fixed prices and stacking multiplies limits within a tier. In others, tiers are defined by the number of codes purchased. Read the deal description carefully to understand which model applies.

The timing imperative: why stacking must happen during the campaign

This is the most consequential aspect of the stacking decision: stacking is only possible during the active campaign. Once the campaign closes, you cannot purchase additional codes for a closed deal. If you buy Tier 1 during a campaign and realise six months later that you need Tier 2 capacity, your options are limited to: contacting the vendor for a discounted upgrade (sometimes available, vendor-specific, not guaranteed), or paying subscription pricing for the additional capacity (which introduces ongoing costs that erode the LTD advantage).

The practical implication: if there is a meaningful probability — say, 40 percent or more — that you will need the next tier within 18 months, buying the additional codes during the campaign is almost always the financially correct decision. The cost of buying codes you turn out not to need is lower than the cost of needing codes you cannot buy at LTD pricing.

The stacking mistakes buyers make most often

Mistake 1: Under-buying based on current needs rather than projected needs. This is by far the most common stacking mistake. Buying Tier 1 because it covers your current 3-person team, without accounting for the 8-person team you expect to have in 18 months. The solution is always to project 18 months, not to buy for the moment.

Mistake 2: Not checking the maximum stack before planning a stacking strategy. If you need 20 seats and the deal covers 5 seats per code with a maximum stack of 3, the maximum coverage through the LTD is 15 seats — not enough. Discovering this after committing to the tool is an avoidable surprise.

Mistake 3: Stacking aggressively beyond realistic needs. The opposite error — buying 5 codes for a tool you will use for solo work for the foreseeable future — wastes money. The goal is to match the tier to your actual trajectory, not to maximise the tier.

Mistake 4: Stacking codes across different campaigns. Some buyers attempt to combine codes from a deal's initial campaign with codes from a subsequent discounted offer for the same tool. This typically does not work — most stacking is limited to codes from a single campaign. Read the specific stacking rules for any deal where you are considering multi-campaign stacking.

The tier decision framework: a practical guide for every situation

Here is a decision framework that applies cleanly to any LTD tier choice, regardless of the tier structure type.

Tier selection decision framework
Your situationRecommended tier approachRationale
Solo user, stable use case, no team plansTier 1 with confidenceNo growth to accommodate; over-buying wastes money
Solo user, business growing, may add team within 12 monthsTier 2 — anticipate the growthUpgrade cost post-campaign typically exceeds tier price difference
Team of 2–3, stable team sizeTier covering current team + 1 buffer seatSmall buffer prevents hitting limit before next evaluation
Team of 2–3, growing fastTier covering projected 18-month team sizeGrowth trajectory justifies upfront investment in higher tier
Need specific premium feature (API, white label)Minimum tier that includes the required featureNo point paying for seats/volume above what the feature requires
High usage volume (email, API, storage)Tier where 18-month projected usage is at 70–80% of limitComfortable headroom avoids overage charges without over-buying
Agency managing multiple clientsHighest tier available or maximum stackClient account volume typically scales fast; under-buying for agencies almost always regretted

When the maximum tier still is not enough

Sometimes the maximum tier or maximum stack of a lifetime deal simply cannot cover your requirements. If your projected 18-month seat count exceeds the maximum stack coverage, or if your usage volume will exceed the maximum tier's limits before the break-even period ends, this deal cannot serve you at LTD pricing.

This is not a reason to buy a tier you know will be inadequate, hoping that something works out. It is a reason to move on and look for a deal with higher tier ceilings, or to accept that the subscription model is genuinely the right fit for your scale of usage.

There is no shame in determining that an LTD tier structure does not fit your needs. The goal is not to make LTDs work for every situation — it is to use them in the situations where they genuinely work and to use subscriptions in the situations where they genuinely work. A buyer who correctly determines that a deal's maximum tier is insufficient for their needs and moves on has made an excellent decision, even though it looks from the outside like they "passed" on a deal.

Real examples of the tier decision done right and done wrong

Example 1: Getting it right — the email marketing upgrade decision

A newsletter operator had 4,200 subscribers and was growing at roughly 300 new subscribers per month. Tier 1 of an email marketing LTD covered 5,000 subscribers for $69. Tier 2 covered 15,000 subscribers for $139. The operator's 18-month projection: 4,200 + (300 × 18) = 9,600 subscribers. Tier 1's 5,000 limit would be exceeded in roughly three months; Tier 2's 15,000 limit provides comfortable coverage for the full projection period. The decision to buy Tier 2 for $139 instead of Tier 1 for $69 was correct: $70 more upfront avoided hitting the limit in three months and paying subscription pricing — which would have been $29 per month — for the remaining 15 months of the projection period ($435 in avoided subscription costs).

Example 2: Getting it wrong — the unnecessary agency stack

A freelance designer with a one-person business bought three stacked codes of a design tool LTD "because it was such a good deal at that tier." The cost: $297. Tier 1 at $99 would have covered everything they needed for years. The designer never used the higher-tier features. Three years later, the tool is still excellent — but they paid $198 more than they needed to for no benefit. Over-buying is less catastrophic than under-buying, but it is still a mistake: a waste of $198 that could have gone toward another well-chosen LTD.

FAQ

What is the difference between Tier 1, Tier 2, and Tier 3 in a lifetime deal?

Tiers are different pricing levels offering progressively more features, seats, or usage limits. Tier 1 is the entry-level option. Higher tiers offer more of whatever dimension the deal uses to differentiate tiers — seats, features, or usage volume. The specific differences vary entirely by deal — read the tier comparison table for each deal individually rather than assuming standard definitions.

Should I start with Tier 1 and upgrade later if I need more?

Almost never the right strategy. Once a campaign closes, upgrading to a higher LTD tier is typically not possible. Upgrading later means paying subscription pricing for additional capacity, which can quickly exceed the cost difference between tiers during the campaign. If you have a reasonable probability of needing a higher tier within 18 months, buy it during the campaign.

How do I know how many codes to stack?

Project your usage 18 months from now — seats, storage, or volume depending on the tier type. Find the tier where your projected usage falls comfortably within the limit (at 70 to 80 percent of the limit for safety). Buy the number of codes needed to reach that tier. If your projected needs exceed the maximum stack, this deal's tier structure cannot serve you at LTD pricing.

What happens if I buy the wrong tier?

If you under-buy: you will hit the tier's limits before you expected, and upgrading will cost subscription pricing rather than LTD pricing. If you over-buy: you have spent more than necessary for benefits you are not using. Under-buying is more costly in the long run; over-buying is a one-time overspend. Both are avoidable with the right projection work before purchase.

Is Tier 1 ever the wrong choice even for a solo user?

Yes — if the solo user's workflow requires features that are gated at Tier 2 or above. Feature-based tier structures sometimes lock features essential to your specific use case at higher tiers regardless of your team size. Check what each tier unlocks, not just how many seats it provides. A solo user who needs API access may need Tier 2 even if Tier 1's seat count is more than sufficient.

HS

HaveSaaS Editorial Team

The tier decision framework in this guide was developed from real purchase history — including specific instances of under-buying that led to expensive post-campaign subscription upgrades, and over-buying that spent more than necessary. Both mistakes are common and both are avoidable with the projection-based approach described here.