---
canonical: https://wegoto.ai/en/insights/ai-use-cases-by-department/
language: en
status: published
author: WeGoTo.ai
dateModified: 2026-11-07
---

# AI use cases by department

A useful AI use case has a clear input, an output someone can review and a person responsible for the result. This matrix proposes one starting task for eight departments. It is a planning aid, not a ranking of measured productivity or a record of client results.

## In brief

- Focus: AI use cases by department
- Approach: A defined task and a human review
- Next step: Scope the work before choosing a format

| Department | Starting task | Required input | Human check |
| --- | --- | --- | --- |
| Marketing | Turn a brief into content options | Approved brief and brand guidance | Check claims, audience and tone |
| Sales | Draft a meeting follow-up | Approved notes and agreed next steps | Verify every promise before sending |
| HR | Explain an internal policy | Current policy and intended audience | Verify rights and escalate individual cases |
| Operations | Document a recurring process | Verified steps and actual exceptions | Check sequence and exception handling |
| Finance | Draft a management commentary | Validated figures and period definitions | Recalculate figures and challenge explanations |
| Customer service | Draft a reply from a knowledge base | Approved answer sources | Check policy and escalation needs |
| Product | Organise interview observations | Authorised notes with context | Separate observation from interpretation |
| Legal | Compare versions of a clause | Authorised documents and jurisdiction | Expert review of meaning and omissions |

## How should you choose a first task?

Prefer a bounded task that someone already understands. A short draft or internal summary is easier to evaluate than an autonomous process spanning several systems. Choose a representative example and write down what the reviewer must check.

## What makes a task unsuitable for an initial workshop?

Pause when the source is unreliable, no one can evaluate the result or the output immediately affects a person, payment or external commitment. Resolve those conditions before introducing automation. A less ambitious first task often teaches more about the organisation’s real constraints.

## How can you compare two candidate use cases?

Compare the frequency of the task, available evidence, sensitivity of the data and cost of checking the output. Avoid inventing an impact score without observation. After a pilot, compare the total effort including preparation, review and correction, not generation time alone.

## A few useful answers.

## Keep the work moving.

## FAQ

### Which department should start?

Start where the task is clear, the source is available and a manager can protect practice time. The best candidate is not necessarily the department most enthusiastic about AI.

### Are these observed productivity results?

No. These are suggested exercises. Any result must be measured in the organisation’s actual workflow, with the review effort included.



[AI for teams](https://wegoto.ai/en/workshops/ai-workshop-for-teams/)

[AI training for companies](https://wegoto.ai/en/training/ai-training-for-companies/)

[A method built around your work](https://wegoto.ai/en/method/)