Skip to content

AI Citizen Builder Programme

Turn the people who know the work into builders.

Each of 12 non-technical people brings a real business problem from their own team and works on it for the full 10 weeks. They learn by doing, and finish with an agent their team uses.

  1. Weeks 1–4

    A real business problem

    Value stream mapped with the team, what good looks like agreed, a target set

  2. Weeks 5–7

    Agent built

    Instructions, knowledge and tools

  3. Weeks 8–9

    Tested and safe

    Eval set, permissions and a named owner

  4. Week 10

    In use, creating value

    Measured against the target

  • 10 weeksOn a real problem from your own team
  • 12 buildersPer cohort, nominated by you
  • Live onlineOne session a week
  • £20,000 + VATPer cohort, £1,000 per extra builder
  • Early 2027First cohort starts

A real problem, from day one to done

Builders don't practise on made-up examples. Each one brings a problem from their own team, and every session moves it forward. The value starts during the programme, not after it.

  1. Weeks 1–4

    Bring a real business problem

    Each builder maps their team's work as a value stream, picks the problem worth solving, agrees what good looks like and sets a target to measure.

  2. Weeks 5–9

    Build while you learn

    Every skill goes straight into their own agent: instructions, knowledge, tools, testing and security.

  3. Week 10

    Put it to work

    The agent is in use, measured against the target, and shown to leaders at the show and tell.

~500 hours

a month, from one citizen builder

For the last two years I've worked with a FinTech firm, supporting their AI journey. There we helped one citizen builder free up roughly 500 hours a month. They were allowed to build with AI, and they had the safety guardrails to do it properly, and they built a value multiplier.

Their agent takes about 3 minutes off each second-line support ticket. The team handles around 10,000 a month.

Jack Ridge, Refactor

What builders learn

The programme is for people who know the work, not developers. Each builder uses a real problem from their own team as the material.

Fast flow

Understanding how work flows, and where to apply AI and where not to.

Agent building

Prompts, instructions, skills and evaluations in Microsoft Copilot Studio, so builders make agents that perform well, not just agents.

Building safely

Which connectors and tools to use, version control, and looking after an agent once it's live.

Only 39% of people using AI at work have been trained by their employer (Microsoft and LinkedIn, 2024).

The 10 weeks

Live, online, one session a week. Each builder starts with their own team's work and finishes with an agent their team uses.

  • Weeks 1–4 See the flow
  • Weeks 5–9 Build the agent
  • Week 10 Show and tell
  1. Weeks 1–4

    See the flow

    Value stream map how your team's work really moves. Pick the business problem worth solving, agree what good looks like, set a target to measure, and shape a first agent idea.

  2. Week 5

    Your first agent

    A tour of Copilot Studio, then building an agent with clear instructions: its role, its tone, what it should refuse and when it hands off.

  3. Week 6

    Knowledge and design

    Grounding the agent on the right sources, knowing which data it can and can't use, and handling the main paths of a conversation.

  4. Week 7

    Tools and connectors

    Getting the agent to do real work in other systems, using approved connectors, agent flows and the right level of access.

  5. Week 8

    Testing, evals and cost

    Writing an eval set, reading the results, and keeping the agent lean so it's affordable to run every day.

  6. Week 9

    Security and publishing

    Permissions, versioning, publishing to Teams or Microsoft 365 Copilot, and who looks after the agent once it's live.

  7. Week 10

    Graduation, show and tell

    Builders show what they built and what it changed for their team.

Questions buyers ask

Something not covered here? Book a call and ask.

Who is it for?

People who know the work in their team but aren't developers, such as operations, finance, HR or customer service staff. You nominate 12 people for each cohort. Each person works to solve a real business problem that exists within their team.

Do builders need technical skills?

No. The programme is designed for business staff, not developers. Copilot Studio is taught from scratch, starting in week 5.

What does each builder finish with?

An agent built on a real problem from their own team, taken from idea to working solution, with an eval set showing how well it works and a named owner to look after it. Their team uses what they build, so the value multiplies.

How much time is needed from each participant?

Workshops take around two hours a week. From week 5, we advise doubling that to allow time for building.

What do we need to have in place?

Copilot Studio licences, your internal guidance on connectors and tool policy for us to reference and follow, and a provisioned route to production across your environments, for example dev, test and prod.

Where do the sessions run?

Live and online, one session a week, in Microsoft Copilot Studio inside your own Microsoft 365 tenant.

How much does it cost?

£20,000 + VAT for a cohort of 12, and £1,000 + VAT for each extra builder.

Can we run more than one cohort?

Yes, you can run as many cohorts as you wish.

Programme completed badge

The first cohort starts early 2027

Tell us about your team and we'll tell you whether it's a fit.