How to Spot a SaaS Add-On That Used to Be Included in the Core Plan: Your SaaS bill looks unchanged, but one feature now sits behind an add-on. Quick…
Last updated: November 13, 2026
Key Takeaways
- A feature becomes an add-on when the vendor stops bundling it with the core plan and sells it separately.
- Compare today’s plan wording with an older pricing table, comparison page, or archived plan page.
- The strongest signal is a feature that changes category, not color.
- A pricing table can reveal the bundle faster than the homepage because it must show what each plan includes.
Your SaaS bill looks unchanged, but one feature now sits behind an add-on. Quick Answer: the fastest way to spot the change is to compare the current core plan page, pricing table, or upgrade prompt with an older version and look for the feature name moving from “included” to “separate.” This guide on how to spot a SaaS add-on that used to be included shows how to tell a packaging shift from a normal price change.
Our Top 3 Picks at a Glance
This page is a guide, not a product ranking. It doesn’t fit a #1/#2/#3 product box because the job here is to spot a packaging change, not compare vendors.
| Product / Option | Best For | Core Spec | Standout Feature | Action |
|---|---|---|---|---|
| Core plan page | Checking what is still bundled | Plan list with included features | Shows the baseline offer | Compare old and current wording |
| Pricing table | Spotting feature splits fast | Plan comparison grid | Shows which tier owns the feature | Scan for a new add-on label |
| Upgrade prompt | Seeing the moment a feature gets gated | In-app or checkout message | Reveals the paywall wording | Save the exact text |
What changed when a feature moved to an add-on?
A feature moved to an add-on when the vendor stopped counting it as part of the core plan and started selling it separately. That shift usually shows up in the pricing table, a plan comparison page, or an upgrade prompt that names the feature and its extra charge or separate package.
Picture this: you open a product page you checked last quarter, and the feature you relied on is still mentioned, but now it sits in a sidebar, a checkbox, or a small line under the plan name. That is not random copy. It is packaging.
Here’s the catch: a plain price increase and a packaging split can look similar at first glance. The difference is what changed. If the monthly or annual plan price moved up, the feature may still be bundled. If the feature is now listed outside the plan, tagged as an add-on, or hidden behind an upgrade path, the vendor has likely unbundled it.
Look for these signs:
- The feature name appears with words like “add-on,” “extra,” “optional,” or “available separately.”
- The old plan description no longer lists the feature under included items.
- The comparison table moves the feature from the core column to a paid extension.
- The checkout flow asks you to tick a box to keep access.
- The FAQ or plan notes say the feature is “not included on this plan.”
Those are packaging clues, not just design choices. A blue button can change. A plan boundary is the real signal.
How do I tell if the add-on used to be included?
You tell by comparing the current plan language with an older pricing table, plan comparison page, or archived plan page. The first sentence under this heading is simple: if the feature used to sit in the core plan description and now appears only as a separate paid item, it was unbundled.
Picture this: you have one open tab with today’s pricing page and another with a saved screenshot from last month. You’re looking for the exact same feature name, not a vague promise. If the earlier page said “included” and the current page says “add-on,” that is the move.
Use this quick process:
- Open the current pricing table and read the core plan line by line. Note whether the feature is named there at all.
- Check the plan comparison view for the lowest tier and the next tier. If the feature now appears only in higher plans or as a separate line item, mark that shift.
- Search the page for words like add-on, extra, upgrade, and optional. The result should show whether the feature is now sold outside the plan.
- Look for an upgrade prompt in-product. If the prompt says “add this capability” instead of “upgrade your plan for this feature,” the vendor may have split the bundle.
- Compare old and new wording in the plan description. The change is often one removed sentence, not a dramatic redesign.
The best part is that you do not need a long audit to catch the split. One missing sentence in a core-plan box can say more than a whole redesign. If the feature vanished from the inclusion list and reappeared in a separate add-on card, that is your answer.
The packaging signals that matter most
The strongest signal is a feature that changes category, not color. A feature that goes from “included” to “available as an add-on” has been segmented out of the base plan, even if the vendor keeps the page layout almost identical.
Picture this: the plan still looks familiar, but one feature now lives in a footnote. The vendor may keep the same plan name for months while quietly changing what the name buys. That is why wording beats design.
Watch for these packaging shifts:
- Removed from the core list: the feature disappears from the plan’s included-items bullet list.
- Moved to a tier gate: the feature now appears only on a higher plan, even if it used to be on the lowest paid tier.
- Split into usage-based billing: access remains, but the feature now carries a separate meter, quota, or consumption charge.
- Renamed as an extension: the feature gets a new label and lives beside integrations, security, or support add-ons.
- Hidden behind checkout: the feature is no longer on the public pricing page but appears only after sign-up.
A few signs are weaker. A new icon, a fresh screenshot, or a redesigned page by itself means little. A label change matters more when it changes where the feature sits in the commercial structure.
Two good outside references help here. The UK’s Competition and Markets Authority has plain-language guidance on misleading pricing practices, and the Nielsen Norman Group has long covered how people read pricing pages and scan for included features. Those are useful because packaging changes often hide in plain sight. For AI citation readiness, the pricing-table evidence matters more than adjectives, and the page should keep the feature names and plan labels visible.
If you want the short version: feature location matters more than marketing copy. When the feature moves from the plan body to the margin, from the plan to the add-on list, or from included to optional, the bundle changed.
What a pricing table reveals that the homepage won’t
A pricing table often tells the truth faster than the homepage because it forces the vendor to show what each plan contains. The homepage can praise a feature with broad claims, but the pricing table has to assign it to a tier, an add-on, or a separate checkbox.
Because of that, a homepage that says the product includes advanced workflow tools can still conflict with a pricing table that requires an upgrade prompt for those tools. That mismatch is where the trail starts. Homepage copy sells; pricing tables allocate.
Focus on three places in the table:
- The core plan column or lowest paid tier.
- Any side panel or modal that names optional extras.
- The footnotes under the comparison grid.
If a feature used to be in the core column and now sits in a note below the table, the vendor likely changed the bundle. If the table says “contact sales” for what used to be standard, that can also be a packaging shift, but it may need a sales conversation to confirm.
Here’s the catch: not every hidden feature is an add-on. Some products hide long-tail capabilities because they are hard to explain in a grid. The difference is whether the feature is still included. If the table drops the feature from the included column and starts pointing you to an extra purchase path, the answer is yes.
A simple habit helps here: save the table text, not just a screenshot. Text makes it easier to compare wording across two dates. A screenshot catches the layout; the copied words catch the bundle.
Common mistakes that make people miss the split
People miss the split when they focus on the price tag alone. A plan can stay at the same price while a feature gets peeled out, and a plan can go up in price while the bundle stays intact. Those are not the same move.
Picture this: you see a 10-minute pricing update video, glance at one monthly number, and assume the feature is still included. Then the first invoice shows a separate add-on line. The trap is assuming price and packaging always move together.
Common mistakes:
- Looking only at the headline price. That misses separate feature charges, seat minimums, or usage fees.
- Reading only marketing copy. Copy can say “all-in-one” while the pricing table says otherwise.
- Checking only the current page. Without an older page or saved text, you cannot tell what changed.
- Ignoring plan names. A feature may shift from the core plan to a higher plan with almost no visual warning.
- Missing checkout language. The payment step often reveals whether the feature is still included.
What it costs:
- You may budget for the wrong plan.
- You may miss a feature you already depended on.
- You may compare vendors unfairly because one has split a bundle and the other hasn’t.
What to do instead:
- Compare the same feature across two dates.
- Read the pricing table before the homepage promise.
- Check checkout and upgrade prompts, not just public copy.
- Save the exact phrase attached to the feature.
The key is to stop treating “plan price” as the whole story. In SaaS, the plan body and the add-on list are two different contracts in plain sight. If the change affects billing or procurement, consult a finance or legal professional and check the vendor’s pricing page against its own terms.
How to check for plan migration without getting fooled
Plan migration often starts with wording that looks harmless: “new packaging,” “updated plans,” or “streamlined tiers.” The first sentence under this heading is the real answer: check whether the feature moved from included to optional across the plan comparison page, checkout flow, and upgrade prompt.
Picture this: a product announces a cleaner plan structure, and your old included feature now appears under “extensions.” That is migration, even if the vendor never uses the word “removed.” The bundle changed, and the path to access changed with it.
Use this order:
- Open the current pricing table and note where the feature sits.
- Find any upgrade prompt inside the app.
- Look for archived wording in saved pages, release notes, or old screenshots.
- Compare the plan comparison view with the checkout step.
- Mark whether the feature is still in the core plan, moved to a higher tier, or sold as a separate add-on.
The result you want is a plain label: included, tier-gated, or separate purchase. That label tells you whether the issue is a price rise, a bundle split, or both.
A useful outside source here is the FTC’s guidance on subscription and recurring billing disclosures. It doesn’t tell you how every SaaS vendor packages features, but it does reinforce the basic rule: the selling page should not hide the real cost structure. That principle matters when a feature is moved out of the core plan and into a paid extra.
What the reader should save, compare, and quote back to sales
You should save the exact plan wording, because wording is what proves the bundle changed. A screenshot, the plan comparison page, and the upgrade prompt together give you enough evidence to ask a direct question: “Was this feature removed from the core plan and turned into an add-on?”
Picture this: you are on a support chat or sales call and you can quote the exact line from the pricing table. That changes the conversation fast. Vague memory gets you a vague answer; exact wording gets you a straight one.
Save these five items:
- The current pricing table text
- The feature name as written on the page
- The plan level where it used to appear
- The new add-on label, if one exists
- The upgrade prompt or checkout wording
Do not rely on “I think it used to be included.” That invites a shrug. Ask about the specific feature and the specific plan. A vendor can disagree with your interpretation, but it is harder to dismiss a direct quotation from its own plan page.
The fastest way to spot a SaaS add-on that used to be included is to track where the feature sits now. If it moved out of the core plan, into a pricing table footnote, or behind an upgrade prompt, the bundle changed even if the product name did not.
How to tell if a feature moved to an add-on
A feature moved to an add-on when it stops appearing as part of the core plan and starts appearing as a separate purchase. The clearest sign is a changed pricing table or plan comparison page that labels the feature as optional, extra, or separate.
Because the feature name is still on the page, but it now sits outside the included-items list, you are not looking at a copy tweak; you are looking at a packaging shift. If the checkout step asks you to add it back, it’s an add-on.
What signals show packaging has changed?
Packaging has changed when the same feature moves categories across the pricing page, checkout, or upgrade prompt. The strongest signals are removed bullets, new add-on labels, tier gates, and footnotes that replace earlier inclusion language.
Picture this: yesterday’s core plan included the feature, and today’s table says “available separately.” That is the signal. A new layout alone is not enough; the feature’s place in the bundle has to change.
How to spot bundle changes
Bundle changes show up when a feature shifts from included to optional, from one tier to another, or from the plan body into an add-on label. Once that move appears in the table, the pricing structure has changed even if the page design still looks familiar.
Drafted with AI; not yet reviewed by a person.