Skip to main content
Intempt
Coming soon

Feature to paywall conversion

Reports per-feature engagement among free users and their pricing page views, to inform feature-gating strategy. It does not sequence feature use to payment or show quadrants.

Authored by Intempt Technologies

Recipe curators

Agentic workflow

Coming soon

1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Rank features by paid conversion

    Coming soon

    Blu builds a step

About this recipe

When to use it

Not every feature that free users bump into converts them. This measures, per feature, the real path from interaction to pricing view to subscription - so you can see which gates are pulling their weight and which are just friction.

What it delivers

Tracks, per feature, the percentage of free users who interact with it and subsequently both view pricing and subscribe, giving a real conversion rate to inform which features are worth gating.

How you prompt this

Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.

Tell Blu Agent what you want

“Reports per-feature engagement among free users and their pricing page views, to inform feature-gating strategy. It does not sequence feature use to payment or show quadrants.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.

Outputs

    How the recipe runs

    Blu follows the steps in order and shows you each one before anything goes live.

    1. 01Rank features by paid conversionCreate an Insights report called "Feature to Paywall Conversion". Series A: Event "Click on" filtered by target_id matching a feature pattern, scoped to free-plan users (users without a paid Subscription started), aggregation: Count Unique Users per target_id, label: "Free Users Who Tried Feature" Series B: Of the users in Series A, those who subsequently emitted a View page where Page URL contains "/pricing" within 30 days of the feature click, label: "Reached Paywall" Series C: Of the users in Series A, those who subsequently emitted Subscription started (with trial_end null: paid, non-trial) within 30 days, label: "Converted to Paid" Series D: Computed: Series B / Series A × 100, unit: %, label: "Feature to Paywall Rate" Series E: Computed: Series C / Series A × 100, unit: %, label: "Feature to Paid Rate" Breakdown: By target_id (the specific feature) Time range: Last 90 days Compare: Previous period (prior 90 days) Chart type: Scatter plot: X axis = Feature to Paywall Rate (Series D), Y axis = Feature to Paid Rate (Series E), bubble size = Series A volume (free users who tried). Each bubble is a feature. Annotations: - Quadrant labeling on the scatter: - High Paywall + High Paid: features that drive monetization (gate them, or use them as the upgrade pitch). Promote in upgrade prompts. - High Paywall + Low Paid: features that intrigue but don't close (paywall view is happening but pricing isn't compelling: pricing/positioning issue). - Low Paywall + High Paid: stealth-monetization features (users convert without going through pricing: already sold; no need to gate). - Low Paywall + Low Paid: low-monetization features (giveaways: keep in free tier, don't gate, but also don't over-invest). - Flag any feature with high free-tier usage AND zero conversion lift: these features are pure cost; consider deprecating or gating. - Highlight the top 3 features by Feature to Paid Rate (Series E): these are the paywall-optimal features. - Surface the feature with the largest Free to Paywall conversion gap (Series D much higher than Series E): pricing-perception issue specific to that feature. Use case: Kyle Poyar's (OpenView) most-shared Amplitude template. Tells the product team which features to gate behind the paywall vs. which to give away vs. which to deprecate. The single most-actionable monetization analysis a SaaS product can run. Taxonomy notes: - Click on.target_id is the canonical feature handle. - View page.Page URL filtered to /pricing identifies paywall views. - Subscription started.trial_end null distinguishes paid from trial.

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /feature-paywall-conversion in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Intempt TechnologiesDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Intempt TechnologiesPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Intempt TechnologiesReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Intempt Technologies

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Product swap in a sceneReplaces the product in a shot you already have with a different one, keeping the scene, lighting and shadow the same.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe