How a use case gets created

Use cases are created by Neuralift’s data science team as part of the engagement, typically in a working session where you agree on the business question together; see Roles & permissions. Your part is the substance; Neuralift’s part is the setup.

What you bring

• The business question: the outcome you want segments to support, such as “Q3 churn risk” or “Loyalty growth (EU)”. It becomes the use case’s name.
• The KPIs you care about: the metrics your segments will be measured against, in priority order.
• Business context: products, channels, and seasonality that make results readable for your team.

What your Neuralift team does

Your Neuralift team creates the use case and configures it with you: it starts with status pending, opens on its Definition tab, and the Desired Segments size defaults to Small; you’ll refine that in the use case definition. This is where your input matters most: the richer the context, the more useful the segments and actions.

A use case runs against a prepared dataset. If your warehouse isn’t connected yet, an admin in your organization connects it and syncs a source table first. Neuralift’s team then prepares the data and reviews the resulting data dictionary with you.

Tip. Already have a similar use case? Ask your Neuralift team to clone it instead of starting from scratch. The definition always carries over, and you can bring the input data and segment results too.

Confirm it on your dashboard

Once created, the new use case appears on your dashboard with status pending. Open it to review the Definition tab and check that the goal, context, and KPIs match what you agreed. When the definition is filled in and data is prepared, Neuralift’s team starts a run and you’ll see progress on the dashboard.