New paying customers
Customers who started paying in the last month, the window where onboarding decides whether they stay.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Install now1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Build the new-customer list
Install nowBlu builds Segment
About this recipe
When to use it
The first 30 days after someone starts paying are different from the first 30 days after signup. This segment isolates that post-subscription window so paid onboarding can be tailored instead of reusing the free-trial playbook.
What it delivers
Segments customers in their first 30 days post-subscription, isolating a paid-onboarding cohort distinct from the generic recently-signed-up segment.
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
“Customers who started paying in the last month, the window where onboarding decides whether they stay.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
- 01Segment
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Build the new-customer listBuild a segment of users named "New Paying Customers". A user is in the segment only when all of these are true: - they did the Subscription started event at least once in the last 30 days - their Plan attribute is not "free" - their Plan attribute is not "trial"Segment
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /new-paying-customers in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyAccounts at churn riskPaying accounts the health score has flagged as at risk, with no renewal deal in flight, so your CSMs can step in before they leave.View recipe Sid ChaudharyHealthy accounts with no open dealCustomer accounts with no open deal and account-level health attributes, plus per-user recent session activity, so AEs can review expansion whitespace.View recipe Sid ChaudharyDiscount-only buyersCustomers who have never bought anything without a discount code, so you can keep them out of full-price campaigns and protect your margin.View recipe 