# Firefox Add-ons paid function disclosed on listing

> State on the listing when payment unlocks any feature, so the install does not feel like a bait-and-switch after the review queue clears.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/firefox-add-ons-paid-function-disclosed-on-listing/
- Source: [extensionworkshop.com](https://extensionworkshop.com/documentation/publish/add-on-policies/)
- GrowthDex source hub: [Firefox Extension Workshop: Add-on Policies](/sources/firefox-extension-workshop-add-on-policies-extensionworkshop-com/)
- Last checked: 2026-06-06T12:04:00Z
- Rarity: rare
- Budget: free
- Channels: Marketplaces, Revenue, Brand
- Stages: browser extensions, firefox add-ons, pricing clarity, review trust


## Why this can grow

Extension monetization often fails through surprise rather than price. Mozilla removes the ambiguity here by requiring listings to disclose when payment is needed to enable any functionality. That is a growth advantage if the team leans into it. The buyer can qualify themselves before install, the support queue gets fewer angry "why is this paywalled" threads, and the review surface feels more honest. Clear commercial boundaries beat a clever install spike that turns into churn and one-star reviews.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where firefox add-ons paid function disclosed on listing can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Revenue channel.
3. Use the evidence from extensionworkshop.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Mozilla's Add-on Policies require AMO listings to disclose when payment is required to enable any add-on functionality.

## Adjacent tactics in the same lane

- [Firefox Add-ons no-surprises copy before install](/growth-ideas/firefox-add-ons-no-surprises-copy-before-install/) - same source, 2 shared channels, 2 shared stages
- [Firefox Add-ons source package with build steps before review](/growth-ideas/firefox-add-ons-source-package-with-build-steps-before-review/) - same source, 1 shared channel, 2 shared stages
- [Firefox Add-ons name earns the slug](/growth-ideas/firefox-add-ons-name-earns-the-slug/) - 2 shared channels, 2 shared stages
- [Safari extension in-use screenshots, not title art](/growth-ideas/safari-extension-in-use-screenshots-not-title-art/) - 2 shared channels, 2 shared stages

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Firefox Add-ons page should remove the surprise before install](/blog/the-firefox-add-ons-page-should-remove-the-surprise-before-install/) - marketplaces, SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.