Skip to main content
Intempt
Coming soon

Power user concentration

Ranks users by event volume and shows each user's share of total events.

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

    Chart activity by user percentile

    Coming soon

    Blu builds a step

About this recipe

When to use it

If 40% of your product activity comes from 1% of users, that's either your best growth lever or your biggest concentration risk, depending what you do with it. This chart tells you the real number.

What it delivers

Builds a Pareto chart showing what share of total event volume comes from the top 1%, 5%, and 10% of users by activity, quantifying real usage concentration.

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

“Ranks users by event volume and shows each user's share of total events.”

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. 01Chart activity by user percentileCreate an Insights report called "Power-User Concentration". Series A: Event "Session start" (or use the User.Total events computed attribute directly, which is system-maintained), aggregation: Count by user Series B: Computed: rank users by Series A descending; for each percentile bucket (top 1%, top 5%, top 10%, top 25%, top 50%, bottom 50%), sum events in bucket and divide by total events × 100, unit: %, label: "Share of Total Events" Time range: Last 30 days Breakdown: By Plan (saas) or by User.Lifetime value bucket (ecommerce) Compare: Previous period (prior 30 days) Chart type: Pareto bar chart: bars showing share of total events per user-percentile bucket, with cumulative line overlay Annotations: - Flag the share of total events generated by the top 1% of users: values >25% indicate heavy-tail concentration. - Flag the share of total events from the bottom 50%: values <10% indicate the long tail isn't engaged. - Highlight whether concentration is increasing or decreasing vs. previous period. - For ecommerce mode: substitute "events" with "revenue": sum Placed order.total_price per user, then run the same percentile decomposition. SaaS products want lower concentration (broad activation); ecommerce often has natural high concentration (loyal whales) but tracking the change matters more than the absolute level. Taxonomy notes: - Users.Total events is a system-computed attribute (real, on the Users object). Use it directly for the per-user totals. - For revenue-side concentration, sum Placed order.total_price grouped by customer_id.

    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 /power-user-concentration 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