# Choose a useful AI task for your team

> Find practical starting points in marketing, sales, operations and client work, with inputs and review criteria.

Start with a task that occurs often, has accessible source material and produces an output someone can check. A narrow task such as “draft a follow-up from approved notes” is easier to improve than “automate sales”.

## Compare a few starting points

These are example tasks, not promises that MAIA can access your systems or complete an entire business process without review.

| Team            | First task                         | Provide                                             | Check before use                                       |
| --------------- | ---------------------------------- | --------------------------------------------------- | ------------------------------------------------------ |
| Marketing       | Draft a campaign brief             | Approved product facts, audience and brand guidance | Claims, tone and unsupported promises                  |
| Sales           | Prepare a client follow-up         | Call notes and the current proposal                 | Commitments, prices and dates                          |
| Operations      | Summarize an internal process      | Current procedure and exceptions                    | Missing steps, ownership and outdated rules            |
| People teams    | Draft an onboarding checklist      | Approved policies and role requirements             | Applicability, completeness and sensitive information  |
| Client services | Compare a brief with a deliverable | Requirements and the latest draft                   | Evidence for each match or gap                         |
| Legal teams     | Organize facts from a document set | Permitted documents and a defined question          | Source accuracy and professional review of conclusions |

Use synthetic or appropriately approved material for training. A professional remains responsible for decisions that require professional judgment.

## Score suitability, not excitement

For each candidate, answer these questions:

1. How often do we do it, and who needs the output?
2. Can the intended users access reliable source material?
3. Can a reviewer identify a wrong or incomplete result?
4. Is the first version reversible, for example a draft rather than a sent message?
5. Who will maintain the method when the source or process changes?

Prefer a task with clear answers over a visually impressive demo. If the review depends on expertise nobody on the team has, choose a different starting point.

## Example: Acme Corp's weekly update

Jane Doe prepares a weekly client update from project notes. The first pilot produces a draft with three sections: completed work, unresolved questions and next steps. It does not send the message.

> Use the attached project notes to draft this week's client update. Distinguish completed work from plans. For every next step, include an owner and date only where stated. Add a separate list of missing information. Keep client-facing text concise and avoid internal speculation.

The reviewer checks that planned work is not presented as completed and that no date or owner was invented. If the draft is useful across several weeks, keep the project context in a [project](/en/docs/maias-features/projects/) and consider a [Skill](/en/docs/maias-features/skills/) for the writing method.

## Grow the task carefully

Start with a chat and reviewed output. Add a repeatable method only when you understand what works. Introduce [connectors](/en/docs/integrations/using-connectors/) when access to a service is actually needed, and [workflows](/en/docs/workflows/) when the process benefits from explicit steps.

Use the [pilot brief](/en/docs/guides/templates/) to record scope and the [evaluation guide](/en/docs/guides/evaluate-results/) to decide whether the method is ready for more people.