The Copilot Champion job description: copy-paste template for SMBs

Most Copilot rollouts that stall in month three didn’t stall because the technology was wrong. They stalled because there was nobody whose actual job it was to make them work. The license was bought, the email was sent, the Microsoft Learn link was shared. Then everyone went back to Outlook.

The single biggest predictor of whether a Copilot rollout crosses 60% adoption is whether you have a named, paid, accountable Copilot Champion— not a volunteer, not an “AI enthusiast,” not the IT director who’s already running three other projects. A real role with real hours and a real success metric.

Here is the job description we recommend clients post when we tell them to hire one. Copy it, edit it, ship it. The whole role typically pays for itself inside six months at a 100-person firm.

If nobody owns adoption, nobody is doing adoption. Copilot rolls out into a vacuum and stays there.

When you need this role (and when you don’t)

You need a dedicated Copilot Champion when you cross roughly 50 licensed seatsor when Copilot is part of three or more business processes. Below that, the role can sit inside an existing operations or L&D manager — 6–8 hours a week, ring-fenced, with a written adoption target.

Above 50 seats, the part-time arrangement breaks. Office hours get cancelled because the day job comes first. The prompt library goes stale. Adoption telemetry stops being reviewed. By month four you have a $40K/year licence spend with 22% weekly active users and no champion to fix it.

The job description (copy-paste ready)

Use this verbatim, swap the company name, and add your own location and benefits language at the bottom. We’ve tested this exact wording with three clients in the last twelve months and it pulls strong candidates from internal applicants (which is usually who you want).

About the role

We’re looking for a Copilot Champion to own the adoption, governance, and continuous improvement of Microsoft 365 Copilot, Copilot Studio, and the wider Microsoft AI estate across the business.

This is nota technical role in the traditional sense. You will not be writing code, configuring tenants, or running the SharePoint migration. You will be the person who makes sure that every team in the business knows how to use the AI tools we’ve invested in — safely, productively, and with measurable impact on the work they actually do.

Success in this role looks like:

• Weekly active Copilot users at 60%+ of licensed seats by month six (industry baseline is ~25%).
• At least 12 documented “hours saved” use cases across at least four functions, with named owners and replicable prompts.
• Zero data-leakage incidents attributable to Copilot output or oversharing.
• A live, maintained internal prompt library with at least 50 business-specific prompts contributed by users across the organisation.
• One quarterly executive readout with adoption metrics, ROI estimates, and a forward-looking improvement plan.

Responsibilities

Adoption & enablement

• Run weekly 30-minute Copilot office hours, rotating across functions (finance, sales, ops, HR, client services).
• Build and maintain function-specific prompt playbooks — not generic Microsoft examples, but prompts that match how our teams actually work.
• Onboard every new licensed user within their first ten working days, including a 1:1 walkthrough and follow-up at the 30-day mark.
• Identify and recruit per-function “Copilot deputies” — super-users who carry the conversation when you’re not in the room.

Governance & safety

• Co-own the AI acceptable-use policy and the nine-document governance pack with the COO, Head of IT, and DPO/legal counsel.
• Triage user-reported AI incidents within one business day and feed lessons learned back into training.
• Coordinate with IT on Microsoft Purview oversharing reports and sensitivity-label coverage of crown-jewel content.
• Maintain a public register of approved AI tools and the deprecation list of tools we’ve decided not to use.

Measurement & reporting

• Own the Microsoft Copilot Dashboard. Review weekly. Surface adoption gaps and dormant seats.
• Drive a quarterly “seat reclaim” cycle — reassign unused licences to high-leverage workflows.
• Produce a quarterly executive ROI estimate based on documented hours saved, costed at fully loaded salary.
• Prepare board-ready material on AI posture, adoption, and roadmap on request.

Continuous improvement

• Stay current on the Microsoft AI roadmap — new Copilot features, Copilot Studio capabilities, agent patterns, Purview changes.
• Identify candidate workflows for Copilot Studio agents or Power Automate flows, and partner with IT or external delivery on build.
• Run a quarterly retrospective on what’s working, what isn’t, and what to deprecate.

Profile we’re looking for

Must-have

• 3–7 years in an internal enablement, L&D, business analyst, or operations role — ideally within professional services, financial services, or another knowledge-work-heavy industry.
• Demonstrated experience driving adoption of any business software at a 100+ person organisation. Specific Microsoft AI experience is a bonus, not a requirement.
• Strong written communication — you can explain a Copilot use case in three sentences to a non-technical executive.
• Comfortable holding the line on governance. Will say no to a senior stakeholder when a request crosses a policy line, and bring a constructive alternative.
• Genuinely curious about AI — experimenting in your own time, following the Microsoft roadmap, reading more than the marketing material.

Nice-to-have

• Hands-on time with Microsoft 365 Copilot, Copilot Studio, or Power Automate in a previous role.
• Microsoft AI-900, AI-102, or PL-200 certification.
• Background in instructional design or technical writing.
• Familiarity with Microsoft Purview sensitivity labels and DLP policies.

Explicitly not required

• A computer science degree.
• Coding experience.
• Prior consulting experience.
• The phrase “AI thought leader” anywhere on your CV.

Compensation guidance

The market for this role is still forming. Based on the hires we’ve helped clients close in the US and UK in the last twelve months:

• US (metro markets, full-time): USD 95K–135K base, plus standard benefits and 5–15% bonus. Higher-end for finance, legal, or healthcare verticals.
• UK (London, full-time): GBP 65K–90K base.
• Part-time / 0.6 FTE: pro-rata, plus a 10–15% premium for the senior judgement involved.
• Internal promotion path: if you’re elevating an existing L&D or ops manager, add 8–12% to their current base and write the new title into a six-month performance plan with the adoption metrics above.

Interview structure that works

Three rounds, two weeks end-to-end. We’ve seen this structure consistently identify the right hire and consistently lose the wrong one:

1. Round 1 (45 min, hiring manager): career history, why this role, walk-through of a previous adoption initiative they led. Listen for ownership language vs. participation language.
2. Round 2 (60 min, working session): give them a real prompt they’d encounter on the job — e.g. “Our finance team isn’t using Copilot. What’s your first 30 days?” — and have them present back. This is the single most discriminating round.
3. Round 3 (45 min, exec sponsor + IT lead): two-on-one. The candidate will need to work with both. Watch how they navigate the natural tension between “push adoption fast” and “don’t break governance.”

Skip take-home assignments. They self-select for people with the most free time, not the most judgement.

What to expect in the first 90 days

A good Champion will not start by running training sessions. A good Champion will start by listening:

1. Weeks 1–2: sit with five teams. Watch them work. Ask what takes the most time. Don’t mention Copilot.
2. Weeks 3–4: publish the “ten prompts that would have saved each of those teams two hours last week” document. Real prompts, real teams, real time savings.
3. Weeks 5–8: start office hours, function by function. Sales first if the company is sales-led; finance first if it’s ops-led.
4. Weeks 9–12: first quarterly readout. Adoption number, three use cases with quantified savings, three things that aren’t working, the plan for the next quarter.

If at the 90-day mark you don’t have a quarterly readout with a real adoption number and at least three documented use cases, the hire isn’t working. Have the conversation early, not at the one-year review.

If you’re reading this because you need to hire one

Two practical next steps:

• Inside your business already? The strongest candidate is usually an internal one — the operations manager, the L&D lead, the business analyst who’s been quietly building Copilot prompts on the side. Post the role internally first.
• Don’t know if you’re at the threshold? Our free AI Readiness Assessment includes an adoption-staffing recommendation. 30 minutes, written follow-up, honest read on whether you need this role today, in six months, or not yet.

Whichever way you go: name the role, write the metrics down, give them the hours. Copilot rolls itself out about as well as Salesforce did. Which is to say: it doesn’t.