Skip to main content
Intempt
Coming soon

Ecommerce lifecycle and retention

Shows lifecycle distribution, when shoppers reorder, and whether discount codes add revenue or eat into it.

Authored by Sid Chaudhary

Founder & CEO at Intempt

Agentic workflow

Coming soon

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

  1. 1

    Build the lifecycle board

    Coming soon

    Blu builds a step

About this recipe

When to use it

Lifecycle distribution, replenishment timing, and discount cannibalization are usually tracked in isolation, which hides how they interact. This puts them together in one retention view.

What it delivers

Combines lifecycle distribution and migration, replenishment timing, discount cannibalization, and post-purchase paths into a single CRM / retention dashboard.

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

“Shows lifecycle distribution, when shoppers reorder, and whether discount codes add revenue or eat into it.”

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. 01Build the lifecycle boardCreate a Dash board (12-column composition canvas) titled "Ecommerce Lifecycle". Persona: CRM Lead, Retention Marketer, or Loyalty/Lifecycle Manager. Question answered: "How are customers progressing through their lifecycle, and where do I intervene?" Distinct from Customer 360: Customer 360 is the "who are my customers" overview; Lifecycle is the "how do I move them" operational view (migration, replenishment timing, discount mechanics, post-purchase touchpoints). Board-level configuration: - defaultDateRange: last_90_days - exclusionPeriod: incomplete_periods - visibility: project - boardFilters: none by default - boardBreakdowns: Lifecycle score (canonical 6-stage enum) Layout: 4 rows. Row 1: Lifecycle health KPIs (heightPx: 200, four metric cards at widthUnits: 3): - Card 1: Insights metric to source recipe: customer-lifecycle-distribution, vizType: metric, titleOverride: "% in Champions" - Card 2: Insights metric to source recipe: customer-lifecycle-distribution, vizType: metric, titleOverride: "% in At Risk" - Card 3: Insights metric to source recipe: customer-lifecycle-distribution, vizType: metric, titleOverride: "Largest Migration Last 30d" - Card 4: Insights metric to source recipe: discount-impact-on-aov-and-margin, vizType: metric, titleOverride: "Net Revenue Impact of Discounts" Row 2: Lifecycle distribution + migration (heightPx: 480, full-width single card at widthUnits: 12): - Card 1: Insights to source recipe: customer-lifecycle-distribution, displayMode: chart (stacked bar + migration flow side panel: the centerpiece) Row 3: Operational levers: timing and discount mechanics (heightPx: 400, two cards at widthUnits: 6): - Card 1: Insights to source recipe: post-purchase-second-order-velocity, displayMode: chart (histogram: informs replenishment journey timing) - Card 2: Insights to source recipe: discount-impact-on-aov-and-margin, displayMode: chart, vizType: bar (per-discount-code AOV impact and net revenue effect) Row 4: Post-purchase journey (heightPx: 400, two cards at widthUnits: 6): - Card 1: Path to source recipe: post-conversion-onboarding-paths, displayMode: chart (what newly-converted customers do) - Card 2: Retention to source recipe: purchase-retention, displayMode: chart, vizType: retention_curve (cohort repeat-purchase by first-order category) Annotations: - Row 2 (lifecycle distribution + migration, full-width) is the strategic centerpiece. - Row 3 turns insight into operational levers. - Row 4 closes the loop: post-conversion paths + retention by category. Taxonomy notes: - Users.Lifecycle score is the canonical 6-stage enum. - All source recipes use canonical events: Placed order, discount_applied, View page, Session start, Subscription started.

    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 /ecommerce-lifecycle-dashboard 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

    Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost 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 Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Sid Chaudhary

    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 Return rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    Got a play worth sharing?

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

    Submit a recipe