Why this exists

Signalst was built by someone who spent fifteen years working inside a large, complex organisation, and who saw Microsoft 365 Copilot across it, watched the rollout collapse, and then built a programme from scratch to fix it.

The organisation is a multinational operating across multiple countries, part of an internationally recognised university group. It is not a startup experimenting with AI tools. It is the kind of organisation that moves carefully, that has compliance requirements, that runs Microsoft 365 at scale. When Copilot licences went out to staff, the expectation was that adoption would follow.

It did not. There was a training session. Documentation was shared. People were encouraged to experiment. Six weeks later, three people were using Copilot regularly. Everyone else had tried it once, got a mediocre result on an unfamiliar task, and moved on.

The problem was not the technology. Copilot is genuinely useful. The problem was that nobody had given anyone a reason to try it again, a specific thing to try, or a way to see whether what they were doing was working. The rollout assumed that awareness creates behaviour. It does not.

The person who built it

Fifteen years inside the same organisation means understanding how change actually happens in large, bureaucratic environments, not how it is supposed to happen on a slide deck. It means knowing that the people who matter most to an adoption programme are not the early adopters but the reluctant middle majority who will never voluntarily experiment with new tools.

The AI Apprentice qualification (a formal, assessed programme covering AI tools, applications, and responsible use) informed both the challenge design and the progression model. The nine weeks are sequenced deliberately: from basic prompting through to more complex use cases, so that participants build on what they already know rather than being confronted with capability gaps all at once.

Building the programme

The first version of the Copilot Bootcamp was built over a weekend. Nine challenges, one per week, each using real work scenarios. A leaderboard in Excel. Participants grouped into pods of four so that the accountability was social, not managerial. Email templates so the facilitator could run the whole thing in a couple of hours a week.

It ran for nine weeks inside that multinational organisation. Participation held up in a way that no previous software rollout had managed. By week nine, 94% of participants were using Copilot for real work tasks, not in the programme context, but in their day jobs. The scoring system and the pod structure had done what the training session never could: built the habit.

Why it became a product

After the programme ended, other people started asking how it had been done. Not consultants, peers. CTOs and COOs who had the same problem: licences deployed, adoption stalled, no clear path forward. They did not want to hire someone to build a programme for them. They wanted the programme itself, ready to run.

That is what Signalst is. The Copilot Bootcamp Kit is the exact programme, productised so that one person in your organisation can pick it up and run it without starting from scratch. No consultants, no project plan, no wasted months.

If the data changes, the kit will be updated. If organisations find that certain challenges work better than others, that will feed back into the next version. This is a product built on evidence from a real programme, and it will stay that way.