Where to start with AI on your team
In brief
Most teams should start with AI, and most should start smaller than they think. How to find the one boring, frequent task that proves the value in 30 days, and which tasks to leave alone for now.
Contents
Most managers asking "is AI worth it for my team?" have already seen the demos. Claude writes a whole email in seconds. It summarizes a 40-page document instantly. Then a few weeks in, nobody uses it for anything that matters, and someone asks why you spent time on this.
The honest answer is: probably yes, but not for the reasons you've been shown. The value is real. It just lives in unglamorous places, and you find it by starting with one task, not a general "go try Claude."
Where the real value is
The value comes from three places, roughly in this order of reliability:
1. Repetitive drafting that matters. Emails you write five times a day with small variations. Proposals that follow a template but need tailoring. Status updates to senior people that need to be tight. These burn 30 to 60 minutes each, and the gap between a rushed draft and a polished one actually costs you something.
2. Pulling information together. Competitor summaries, customer feedback themes, a long contract to review, background on an account. Claude compresses the gathering and structuring. A person still judges the result.
3. First drafts of structured documents. Job descriptions, meeting summaries, project briefs, feedback templates. Work with a known format and known inputs, where the hard part is starting.
None of these are the demos. They are where the hours come from.
Where the value usually isn't, yet
- Tasks you do once a month. Halving a rare task is real but nobody notices it.
- Work where your internal knowledge is the whole job. Claude doesn't know your customers, roadmap or pricing until you give it that context. Until you do, it is a collaborator at best.
- Anything where a wrong answer is hard to spot. If an error can reach a customer without anyone catching it, you will lose more trust than the hours saved are worth.
- Anything that acts without a person checking. Messages sent straight to customers, data entered into finance or legal systems, decisions about people. These aren't off limits forever. They are the wrong first step, because failures are harder to catch and cost more.
How to pick your first task
A good first task scores well on all four of these:
- It happens often. At least weekly per person. Volume turns small savings into real ones.
- The input is predictable. "Summarise this support ticket" works. "Handle this however seems right" doesn't.
- A person reviews the output before it goes anywhere. First drafts are perfect. Fully automatic sends are not.
- You can tell if it worked. "Replies drafted in under 10 minutes" is measurable. "Better" isn't.
Tasks that usually pass: first-draft replies to common requests, summaries of meetings and long threads, research briefs, reformatting content for different channels, turning rough notes into a clean document.
The question to ask your team
Get the team together and ask one question: "What takes longer than it should?"
Not "what would you like help with?" That produces a wish list. "What takes longer than it should?" produces friction points, and friction points are where Claude creates value. The person who has done the job longest usually knows the answer straight away.
Score the answers against the four criteria. Pick one.
What it costs to find out
Very little: half an hour to set up a shared Project, a few hours of the team trying it over two to three weeks, and one conversation about what worked. If it doesn't work, you'll know specifically why. If it does, you'll have a real example instead of a demo.
The flashy use case is easy to sell. The boring one is what sticks.
Next: What Claude Projects are and why your team needs one. When you're ready to test it properly, Running your first AI pilot has the 30-day plan.