Use cases

This section answers the question every new user has: "What can I actually use this for?"

Each use case is a concrete recipe: the business question, who's asking, the data you need, how to phrase it in Reasoning, what the answer looks like, and how to convert it into a recurring tracker.

Use cases are grouped by team. Today the section covers Performance marketing; other teams will be added as we capture their workflows.

How to read a use case

Every page follows the same shape:

1. The question — the actual business question, the way it gets asked.
2. Who asks it — the persona; the team and the meeting where it surfaces.
3. Frequency — daily / weekly / monthly / quarterly / one-off.
4. Data you need — exact source types and table contents.
5. How to ask it in the platform — the question to type, with example phrasings.
6. What you'll get back — the structure of the answer.
7. How to make it recurring — tracker recipe with cadence and thresholds.
8. Pitfalls — common failure modes and how to avoid them.

Why use cases beat feature tours

A feature tour tells you what the platform can do. A use case tells you whether the platform solves your problem. If you're skim-reading: jump straight to the use case nearest to a problem you actually have. Come back to concepts only if you need to.