> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blackmountain.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Identifying Use Cases

> Find the tasks where 48° helps your teams most, and turn them into assistants

The right first use cases decide whether a rollout sticks. Look for tasks that are frequent, text-heavy and easy to check, then turn the best ones into assistants your teams can reuse.

![Use cases](https://mintcdn.com/blackmountaingmbh/XFag3CE4nO-WN3UD/images/screens/en/assistants/use-cases.png?fit=max\&auto=format\&n=XFag3CE4nO-WN3UD\&q=85\&s=49dfd7c71b40ffc52e7c05b6b32eec38)

## What makes a good use case

A good first use case is:

* **Frequent:** done every week or every day, not once a quarter.
* **Text-heavy:** reading, writing, summarizing, translating or comparing documents.
* **Easy to check:** the person doing the task can quickly tell if the result is right.
* **Low risk:** a mistake is caught before it reaches a customer or a decision.
* **Owned:** someone on the team wants it to work.

Avoid starting with tasks that need exact figures with no review, or decisions that can't be checked.

## Find use cases with your teams

1. **Ask about the week.** In a short session, ask each team: "Which tasks take the most time and involve a lot of reading or writing?"
2. **List candidates.** Write down each task with how often it happens and how long it takes.
3. **Score them.** Rate each task from 1 to 5 for frequency, time spent and ease of checking. Start with the highest totals.
4. **Test quickly.** Try the top three in a normal chat. If the results are close to useful, it's a good candidate.

## Examples by team

| Team | Use case | Useful features |
| - | - | - |
| Sales | Prepare for a customer meeting from the website and recent news | [Web search](https://docs.blackmountain.io/chat/tools/web-search.md), [Deep Research](https://docs.blackmountain.io/chat/tools/deep-research.md) |
| Marketing | Draft posts and newsletters in your company's voice | [Assistants](https://docs.blackmountain.io/assistants/introduction.md), [Skills](https://docs.blackmountain.io/editor/skills/introduction.md) |
| Customer service | Draft replies to common requests | [Prompt Studio](https://docs.blackmountain.io/chat/prompt-studio.md), [Assistants](https://docs.blackmountain.io/assistants/introduction.md) |
| HR | Draft job ads and answer policy questions from your handbook | [Projects](https://docs.blackmountain.io/chat/projects.md), [Attachments](https://docs.blackmountain.io/chat/attachments.md) |
| Finance and controlling | Summarize reports and explain changes in spreadsheets | [Attachments](https://docs.blackmountain.io/chat/attachments.md), [Document generation](https://docs.blackmountain.io/chat/tools/document-generation.md) |
| Legal and compliance | Compare contract versions and list deviations | [Attachments](https://docs.blackmountain.io/chat/attachments.md), [PII enforcement](https://docs.blackmountain.io/admin/security/pii-enforcement.md) |
| Management | Get a weekly briefing on market topics | [Radar](https://docs.blackmountain.io/radar/introduction.md), [Scheduled tasks](https://docs.blackmountain.io/scheduled-tasks/introduction.md) |
| All teams | Turn notes into a presentation or report | [Document generation](https://docs.blackmountain.io/chat/tools/document-generation.md), [Editor](https://docs.blackmountain.io/editor/introduction.md) |

## Turn a use case into something reusable

Once a use case works in a chat, make it easy for others to repeat:

* **A prompt template** for a single, repeatable request. See [Prompt Studio](https://docs.blackmountain.io/chat/prompt-studio.md).
* **An assistant** for a role with its own instructions, model and reference files. See [Assistant Studio](https://docs.blackmountain.io/assistants/assistant-studio.md).
* **A skill** for instructions several assistants or chats should share, such as a writing style. See [Creating skills](https://docs.blackmountain.io/editor/skills/creating-skills.md).
* **A scheduled task** for work that repeats on a schedule. See [Scheduled tasks](https://docs.blackmountain.io/scheduled-tasks/introduction.md).

## Use the Use Cases page

If your organization has it enabled, the **Use Cases** page in the sidebar offers guided tours that run in the real app, for example **Create an assistant**, **Save a prompt for your team** and **Schedule a recurring task**. Point new members there after the kickoff.

## Measure the result

After a few weeks, check in [Control Tower](https://docs.blackmountain.io/admin/control-tower/analytics.md) whether the teams use 48° regularly, and ask how much time each use case saves. Keep the use cases that work and share them with the next teams.

## Related

> [card] [Rollout playbook](https://docs.blackmountain.io/admin/rollout/playbook.md)
>
> Plan the rollout in phases.

> [card] [Assistant Studio](https://docs.blackmountain.io/assistants/assistant-studio.md)
>
> Build an assistant.

> [card] [Prompting basics](https://docs.blackmountain.io/resources/prompting-basics.md)
>
> Write better prompts.

> [card] [Feature overview](https://docs.blackmountain.io/get-started/feature-overview.md)
>
> Everything 48° can do.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.