Using a free-alternative lens without publishing the opportunity list

This run continued with a confirmed-paid filter, but added one more question:

If we wanted to build a free product, how would we know a paid extension has an opening?

This public recap explains the evaluation method. It does not publish multiple concrete demand points. The full candidate list stays in the internal report.

A free alternative is not a clone

The goal is not to copy every paid feature. The goal is to reduce friction around one useful action.

We look for:

• A narrow workflow users can understand immediately
• Complaints about early paywalls or unclear limits
• Reliability, permission, or onboarding gaps
• A first version that can run locally with minimal account requirements

If a direction needs sensitive permissions, heavy platform dependence, or gray-area behavior, it is not a good beginner-friendly opportunity even if it has paid signals.

One anonymized example

One sample was built around a simple action: turning information the user already has into a more usable format.

It worked as an example because:

• The job was narrow
• The value was easy to understand
• A free basic version would be inexpensive to operate
• The incumbent had room to improve reliability and pricing clarity

But the public post should not include the exact extension name, competitor link, or field-level MVP design. That belongs in private research.

What is safe to publish

Public content can explain:

• Why paid-signal confirmation matters
• Why low-risk filtering matters
• Why free versions should start with one action
• How review pain becomes a product hypothesis

Public content should not reveal:

• A list of specific products to build
• Which competitors have weak ratings or review pain
• Exact MVP field designs
• Collections of competitor links

Product lesson

A good free-alternative opportunity is not simply “users do not want to pay.” More often, users are willing to pay for the outcome but unhappy with the way the current product gets them there.

That lesson is safe to share. The target list is not.

Takeaway

The free-alternative lens is useful for internal prioritization, but the opportunity map should remain private.

Public posts build trust. Internal docs preserve the edge.