Case studies are the most persuasive content you can publish, and the hardest to get. Clients don’t always want their name on a story, least of all one where they looked slow or unsure about AI. There’s a way round that: become your own first case study. Microsoft calls it being “customer zero”. Experiment with Copilot on your own business, transform a process, measure it, and tell that story, warts and all. It’s the most believable proof you can offer, and the one no competitor can copy.
Everyone knows a case study is the strongest thing they can put in front of a buyer. And every Partner we work with knows how hard they are to do.
The client is mid-transformation and doesn’t want to look half-finished. Or the results are good but the journey was messy, and nobody wants the messy part on record. Or legal takes one look and the whole thing dies in approvals. Copilot makes this worse, because admitting you needed help adopting AI can feel, to a customer, like admitting you were behind. So the best stories, the ones with a real before and after, are often the ones you’re least allowed to tell.
There’s a way around it that solves the permission problem and hands you a differentiator at the same time. Stop waiting for a client to say yes, and make the first case study about yourself.
Become customer zero
The idea comes from Kwadwo Benko, who leads transformation and change for Microsoft UK and Ireland, and who ran Microsoft’s own internal Copilot adoption. His argument to a room of Partners at a recent IAMCP event in London was simple: you can’t credibly sell a transformation you haven’t been through.
“You essentially have to be frontier yourselves,” he said, using Microsoft’s term for an organisation that has genuinely put AI to work. Do it on your own business first, and you become the proof. You’ve walked the walk, and you can talk about it from experience rather than a slide deck.
That’s the permission problem gone. No client sign-off, legal review, or worrying about making someone look bad. The subject is you, and you can be as candid as you like.
Walk the walk, and keep the warts in
The candour is the differentiator. Benko was blunt that Microsoft’s own adoption was no fairy tale. People didn’t want to touch the tool. Some feared for their jobs. His first attempts failed: he plastered prompts everywhere on the theory that repetition would build habit, it worked for two months, then everyone ignored him. Later, when Microsoft let everyone build agents, people built them for everything, including jobs Copilot already did. Yet, real change, he said, only came when teams sat down weekly to pull a process apart and rebuild it around the tools.
He now tells this story to his external facing customers, false starts included, and he refuses to polish it: “We don’t want people to feel like it was all jolly at Microsoft, they started day one, the whole organisation was using it. No, it wasn’t the case.”
That honesty is what makes the story land, and it’s why your own case study will beat a competitor’s glossy one. A buyer has heard every Partner claim a flawless rollout and believes none of them. Tell them where yours stalled and what you changed, and you sound like someone who has actually done it. As Benko put it, “Your own AI story is probably your most credible case study.”
How to run it: pick a stall, transform it, measure it
So, how do you start? The temptation is to sprinkle Copilot across the business and call it adoption. Benko’s warning was that this proves nothing: “It’s easy to report that 400 people have used AI, but that means nothing.” Usage isn’t transformation.
Our suggestion is to pick one of the known problems with Copilot rollouts, this is something we covered in an earlier piece: the four challenges that stall almost every Copilot rollout — cost, skills, pricing and fear. Choose the one that bites hardest in your own business, set a baseline before you touch the process, rebuild the process around Copilot rather than bolting it on, and measure the outcome in money or capacity rather than hours saved. Record the false starts while they’re fresh, because they’re the believable part. For the shape of the finished piece, we set out what to include in a Copilot case study separately.
The case study is also a service
Here’s the part that makes the effort pay twice. When you transform one of those four problems in your own business, you don’t just get a story. You get a service. You’ve now solved a specific, named problem in a way you can repeat for a client, which means you can package it, scope it and price it. The case study proves it works, because it worked on you.
That’s the move Benko was pushing: your own transformation isn’t an internal efficiency project, it’s practice development. Do it once, properly, and you walk into a customer conversation able to say “here’s what we did, here’s what it cost us, here’s what changed, and here’s how we’d do it for you.” That’s a reference and an offer in one.
Where we come in
There’s a catch, and it’s the reason most Partners never publish the story they’re sitting on. When you lived it, you can’t see it. The false starts feel like things to bury, not the most valuable part. The number that would stop a buyer in their tracks is sitting unremarked in someone in your team’s head, because to the person who achieved it, it just felt like a Tuesday. Seeing the wood for the trees is hard when you’re in the thick of it.
That’s the stand-back we bring to your team. We were in the room when Microsoft set out this approach, we understand the Copilot landscape your story sits in, and, as journalists by training, we come at your business from the outside. We interview the people who ran your rollout, ask the questions that surface what actually happened, and know which details a Copilot buyer will care about. We’ll find the arc you can’t see, and write it up as a case study that reads like a reference, not a brochure.
Then, once you’ve chosen which of the four problems you’re building your service around, we’ll turn the story into the content programme that sells it, planned as one campaign your Co-op will fund.
So, the question you need to ask yourself, like the one Benko put to the room: is your own business using Copilot in a way you could explain to a customer, and can you say what changed? If yes, that’s your first case study, and it’s better than anything brochureware content Microsoft has shared with you in Partner Center. If not yet, pick one of the four problems and make solving it your next month.
You don’t need a client’s permission to tell the best Copilot story you’ve already got. You just need to have lived it, and a bit of help telling it. That second part is where we come in. Need help? Let’s talk.
FAQs
How can I create a Copilot case study when my client won’t be named?
Make the first one about your own business. Run Copilot on one of your own processes, measure the before and after, and write that up. It sidesteps client permission, NDAs and the reluctance of a customer who doesn’t want to look behind on AI, and it’s often more persuasive, because you can be fully candid about what worked and what didn’t. Feature clients too when you can get sign-off, but your own transformation is the story you can tell in full and start today.
What is a “customer zero” or “frontier firm” in Microsoft’s Copilot messaging?
Both come from Microsoft’s push to get Partners using AI themselves before selling it. A frontier firm is an organisation that has genuinely put AI to work in its processes, not just bought licences. Becoming customer zero means being your own first case study: experimenting with Copilot on your own business, transforming a real process, and measuring the result. Microsoft’s argument, in the words of its transformation lead Kwadwo Benko, is that “you essentially have to be frontier yourselves” to credibly help a customer become one.
Should a Microsoft Partner use its own business as a case study?
Yes, and it’s often the strongest option. It removes the permission and NDA barriers that kill client case studies, lets you tell the story warts and all, and doubles as proof for a service you can then sell, because you’ve solved a problem you can repeat for customers. A buyer trusts a Partner who has clearly been through the thing they’re being asked to buy more than one presenting a flawless-sounding client win.
Why do client case studies fall through?
In our experience it’s usually a permission issue. The client is mid-transformation and doesn’t want to look half-finished, the messy parts that make a story credible are the parts they want removed, or the whole thing stalls in legal approval. AI case studies are harder still, because a customer can read “we helped them adopt Copilot” as “they were behind.” Making your own business the subject removes every one of those blockers.
