Allow to mark some Products as private/hidden

Currently, we display all products available in the customer portal, so customers may upgrade/downgrade to any of those products.In some circumstances, this is not desirable: we might want to have a "private" product that's only available through a checkout link or the checkout API.I suggest we have a "State" for product: * Draft — Product is not yet available to purchase * Public — Product is available to purchase and displayed in the customer portal * Private — Product is available to purchase only from a dedicated Checkout Link or Checkout Session * Archived — Product is no longer available to purchase

GitHubToolAISource
0Sign in to voteCopy link

FL score

59

out of 100

Verdict

VALIDATE

high confidence

Competition

5

competitors found, emerging market, funded players

Trend

8 community mentions

A niche feature to manage private product visibility in customer portals for subscription businesses, particularly relevant for open-source AI companies.

The pain

Businesses offering subscription products currently expose all options in their customer portal, limiting their ability to offer private betas, custom deals, or manage deprecated products without complex workarounds or customer confusion.

The gap

While core billing platforms provide APIs for product management, user-friendly UI controls for granular customer portal visibility are often lacking, creating a gap for a specialized feature or add-on, especially for niche platforms like PolarSource/Polar.

Build angle

A micro-SaaS or feature-as-a-service providing a simple dashboard to set product visibility states (Draft, Public, Private, Archived) that integrates seamlessly with existing subscription billing systems and their customer portals.

Strengths

  • Highly specific and clear problem statement.
  • Solves a real operational pain for certain business models.
  • Feasible for a solo builder to create an MVP.
  • Clear value proposition for businesses that need this functionality.
  • Low direct competition from dedicated tools, though features exist within larger platforms.

Risks

  • Lack of strong direct market validation (few online complaints/discussions).
  • Niche market size, potentially limiting scalability.
  • Incumbent billing platforms could easily build this feature, limiting long-term moat.
  • Reliance on integration with third-party billing APIs.
  • The competitive data provided is irrelevant, pointing to a potential misunderstanding of the true market.

Next steps

  1. Conduct direct interviews with SaaS founders and product managers using subscription billing systems to validate the severity and frequency of this problem.
  2. Gauge willingness to pay for a dedicated solution versus relying on existing platform workarounds or custom code.
  3. Research existing customer portal customization options in popular billing platforms (Stripe, Chargebee, Recurly) to understand current limitations in depth.
  4. Explore potential partner integrations with platforms like PolarSource/Polar directly.

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Allow to mark some Products as private/hidden”.

Open FlyBot