How to lead a team that works with AI agents: a 6-step guide for commercial managers
The short answer
Leading a team that works with AI agents means managing the judgement around the work as well as the output. Decide what agents do and what stays with people, agree a shared standard for good, coach the thinking behind each piece of work, and change the questions you ask in 1-to-1s. Then build in a review step and plan how to use the time saved.
Key takeaways
- Within five years, leaders expect their teams to be training AI agents (41%) and managing them (36%) (Microsoft Work Trend Index, 2025).
- Managers make the biggest difference to how well AI gets used. Gallup's CEO described a manager actively championing it as the strongest predictor of adoption after technical integration (Gallup, reported by HR Dive).
- Most of what a manager needs here isn't technical. It's a shared standard for good, better questions, and time set aside to coach.
Most commercial managers learned to lead by doing the job first. You were a good rep, a good marketer or a good BD lead, and you got promoted partly because you exceeded targets, performed consistently well and knew what good looked like. You know how to develop good proposals that land with clients because you've written hundreds of them yourself.
Now a lot of that first draft is being done by an agent, including research packs, outreach, call notes and proposal outlines. Your team's job is shifting towards briefing, checking and building on what comes back, and yours is shifting with it. Microsoft's 2025 Work Trend Index describes a new kind of role it calls the "agent boss", someone who builds, delegates to and manages agents to get more done (Microsoft, 2025).
Very few managers have been shown how to lead this. The six steps below are what I'd work through with any sales, marketing or BD manager whose team's output looks fine but whose results aren't tracking in line with expectation.
What leaders expect their teams to be doing within five years
Share of leaders who expect their teams to be doing each of these
Step 1: Decide what the agents do, and what remains the responsibility of your people
Before anything else, be clear about which parts of the work you're happy for an agent to draft and which parts need a person. In my experience the split falls quite naturally. Agents are good at gathering and first drafts, such as pulling together account research, summarising call notes or drafting a first version of an email or proposal. People need to own the judgement calls and the relationship, which means deciding which accounts matter, developing the thinking around what a customer really needs, and having the conversation.
Write it down, even as a simple list, as you would with your 'human' job descriptions, so the two line up alongside each other. When the split is left unspoken, some people hand over far too much and others won't let the tool near anything, and you end up with an accountability gap.
You'll end up with: a short list of tasks agents can draft, and clarity on which decisions remain with people.
Writing down the split
- Account research packs
- Summaries of call notes
- First drafts of emails and proposals
- Which accounts matter
- The thinking around what a customer really needs
- The conversation and the relationship
Step 2: Agree what good looks like, as a team
This is the step most teams skip, and it's the one I'd put the most time into as part of the Embedded Adoption stage. If the standard for good only exists in your head, or in the heads of your two best people, everyone else is guessing. Pull together three or four real examples of strong work, perhaps a proposal that won or an outreach message that got a reply, and talk through what made them good. Then do the same with a couple that fell flat. More heads are always better than one here, and this needs to be done in a 'learning and building on what's good' mode, so it's psychologically safe for the team to work on it together. There are still blind spots when it comes to deciding what good looks like.
From that conversation you'll get a handful of plain-English tests the whole team can use. Does this reflect what we know about this specific customer? Is the thinking underneath it sharp, or does it only look polished on the surface? Could I explain why it's good? And could I train my own AI tool to achieve this standard?
You'll end up with: a shared set of examples, and three to five questions that define good for your team.
Step 3: Coach the thinking behind each piece of work
When you review AI-assisted work, the most useful thing to look at is what happened between the first draft and the finished piece. What did the output tell them, what did they add, and what did they change? That's where you can see whether someone is building on the tool or passing its work straight through. I wrote about this gap in more detail in why teams stop using the AI tools they rolled out.
I've found it helps to ask each person to talk you through one piece of work a week in this way. It takes ten minutes and tells you far more about their judgement than reviewing twenty emails for tone.
You'll end up with: a weekly ten-minute walkthrough with each person, focused on their judgement.
From experience
I've watched a manager review a team's outreach, see a consistent format with nothing obviously wrong, and approve it. Three months later the results were still uneven and still concentrated in the same two people. The review had checked how the messages looked, but nobody had asked whether they said anything specific to the customer. This also needs to be developmental rather than punitive, and it's more successful when coaching is an accepted part of the manager-team culture.
Step 4: Build a review step into the workflow
Decide where a person checks AI-assisted work before it reaches a customer, and who that person is. For a new starter it might be every proposal for the first month. For someone experienced it might be a spot check of a few pieces a week. What matters is that everyone knows where the check sits and what it's looking for, which is the standard you agreed in step 2.
Keep it light, because a review step that adds two days to every proposal will be worked around, regardless of how you position it.
You'll end up with: a clear, agreed point where work is checked, and by whom.
Step 5: Decide what to do with the time you get back
If agents are saving your team time, somebody needs to decide where that time goes. BCG's 2026 AI at Work research found that 66% of employees still get limited or no guidance on what to do with the time they save (BCG, 2026). Left alone, it tends to disappear into more activity, whether that's more emails, more meetings or more of the same.
Help them identify the work that needs a person: more time preparing for important conversations, more time with existing customers, and more time thinking about the accounts that matter most. Encourage consultation around what this could be, so that adopting tools becomes performance-enabling and an exciting opportunity for career growth rather than a threat.
You'll end up with: an agreed plan for where saved time goes, reviewed once a month.
Step 6: Change the questions you ask in 1-to-1s
If your 1-to-1s still run through activity numbers and pipeline, people will carry on working the way they always have. The questions you ask tell your team what you value, so try adding a couple that focus on judgement and learning.
You'll end up with: two or three new questions in every 1-to-1.
| A question you might ask now | A question that coaches judgement |
|---|---|
| How many emails went out this week? | Which piece of work are you proudest of this week, and why? |
| Is the proposal done? | What did the first draft get wrong, and how did you fix it? |
| How's pipeline looking? | Which account do you understand better than you did last week? |
| Are you using the tool? | Where did the tool save you time, and what did you do with it? |
| How many opportunities are you managing? | Where did you hear the customer valuing what you shared, and what was it that made the difference? |
Some people take to this straight away and others need more structure for a while, which is normal. Some of your team will be most comfortable working from a clear playbook, relying on what they've always done, and some will be ready to form their own view of a situation and push back when the standard approach doesn't fit. I explored this in Insight is the new currency. Both need coaching, in different ways.
Quick checklist
- The tasks agents draft, and the decisions people own, are clear and written down.
- Examples of good work are regularly shared and discussed as a team.
- Each person walks you through one piece of work a week.
- There's a clear review step before work reaches a customer.
- There's a plan for where saved time goes.
- Your 1-to-1s include questions about judgement as well as activity.
Where to start
If you only do one thing this month, make it step 2. A shared view of what good looks like makes every other step easier, and it's the one that stops quality sticking with the same two or three people. If you'd like help getting your managers there, that's the kind of thing we work through together.
Sources
- Microsoft, 2025 Work Trend Index: The Year the Frontier Firm Is Born (April 2025)
- HR Dive, reporting Gallup's State of the Global Workplace 2026 (April 2026)
- BCG, AI at Work 2026: Why Strategy Matters More Than Tools (June 2026)
Where this fits in WISE: this is part of Intelligence development. See how the full WISE system works.
Questions people also ask
What is an agent boss?
It's a term from Microsoft's 2025 Work Trend Index for someone who builds, delegates to and manages AI agents to get more done. In practice, most commercial managers are becoming a version of this, whether or not anyone has named it.
Do managers need to be technical to lead a team using AI agents?
You don't need to be technical. The most important skills are ones good managers already have: knowing what good work looks like, asking useful questions and coaching people. What's new is applying them to work that started as an AI draft.
How do you stop AI-assisted work from all sounding the same?
Agree a shared standard with real examples, brief the tool with the customer's actual situation, and ask people to explain what they added to each draft. Sameness usually comes from generic briefs and reviews that only check format.
What should a manager do when AI tools aren't working for the team?
Look at how the team is being led before blaming the tool. Make sure someone owns the new way of working, coach on real examples in 1-to-1s and give people time to practise. I cover the five most common reasons in why your team stopped using the AI tools you rolled out.
Seeing this in your team?
30 minutes on what's getting stuck. No pitch deck, no prep needed.
Book a 30-minute call