Workshops

Flagship

AI champions programme

Six weeks to train a small group inside your team to build, run and improve AI workflows, so the capability stays after we leave.

Request this workshop See the agenda
Format
Cohort programmeweekly build sessions
Duration
6 weeksabout 3 hours a week each
Group size
4 to 8 championsplus a leadership sponsor
Who it's for
Curious operatorsnominated by their leads
Delivery
Hybridon-site kickoff, remote weekly

Who it's for

A small group of practitioners who are curious about AI and respected by colleagues, plus the leader who sponsors them.

  • Marketing managers
  • Content leads
  • Growth and performance
  • Marketing ops
  • Analysts
  • A leadership sponsor

The problem it solves

One workshop builds momentum. It does not build a habit.

After training, use often fades within weeks, because nobody inside the team owns the workflows, fixes them when they break, or teaches the next person. Champions are that ownership. This is the format for teams that want AI working in six months, not only in the room.

  • We had a great workshop. Three months later, nothing was running.
  • Two people are good at this, and everyone asks them.
  • We do not want to depend on an outside partner for ever.

Syllabus

Six weeks, one shipped workflow each.

Every week has a build session, a deliverable and a review. By week six each champion owns a workflow that runs, and has taught it to colleagues.

  1. Week 1

    Choose the work

    Map two candidate workflows each, separate judgement from repetition, and time the baseline.

    Ships: a workflow map and a baseline time

  2. Week 2

    Prompt systems and context

    Brand voice, examples, constraints and test cases, built as reusable systems rather than one-off prompts.

    Ships: version one of the team library

  3. Week 3

    First agent build

    Build an agent for the chosen workflow, with inputs, steps, checks and a human sign-off point.

    Ships: a working agent in a test setting

  4. Week 4

    Test, break, guard

    Run it on twenty real inputs, log every failure, and add guardrails for brand, claims and data.

    Ships: a test log and a guardrail checklist

  5. Week 5

    Roll out to the team

    Write the one-page operating guide, teach two colleagues, and hand over day-to-day use.

    Ships: the guide, and two colleagues trained

  6. Week 6

    Measure and hand over

    Re-time the workflow, complete the adoption scorecard, and present to leadership with a backlog.

    Ships: the scorecard and a leadership readout

Every week

Build session90 minutes, live, with the whole cohort.

Office hoursFor blockers, between sessions.

ReviewWritten feedback on every champion's build.

Outputs

What you leave with.

Tangible, on your systems, owned by your team. Nothing here is a slide.

  • People

    Trained internal champions

    Four to eight people who can build, test and improve workflows without us.

  • Agents

    A workflow per champion

    Each one running on real work: owned, documented and measured.

  • Library

    Team prompt and agent library

    Versioned, organised by workflow, with test cases.

  • Guides

    Operating guides

    One page per workflow: what it does, who owns it, what a person checks.

  • Scorecard

    Adoption scorecard

    Use, hours saved and quality for leadership, with the method shown.

  • Plan

    Next-quarter backlog

    The next workflows to redesign, ranked by value, with champions as owners.

How it runs

Before, during and after.

The session is the middle of the work, not all of it.

Before

Choose the people and the work

The right champions and the right workflows decide most of the outcome.

  • a sponsor call to set goals
  • champion selection with team leads
  • baseline times on candidate workflows

During

Six weeks of building

Small cohort, real work, written feedback every week.

  • weekly build session and office hours
  • a review of every build
  • a mid-point check with the sponsor

After

Readout and a 30-day check

The work stays with your team, and we confirm it is still running.

  • a leadership readout in week six
  • a 30-day check on what is still in use
  • champions keep the library and guides

How we measure it

Measured, not estimated.

We track a few numbers that show whether the work changed. No vanity scores, no satisfaction surveys passed off as results.

Adoption

Weekly users of champion-built workflows across the wider team.

Measured by usage data from your tools and the champions' log.

Hours saved

Time per task on each workflow, baseline in week one, re-timed in week six.

Measured by timing the same real task twice.

Workflows shipped

Workflows in regular use at week six, and again at the 30-day check.

Measured by the library and operating guides.

Capability

Colleagues taught by champions, and fixes made without outside help.

Measured by the champions' log, reviewed with the sponsor.

We agree the baseline with you before we start, and we report what we measure, including what did not stick.

Guardrails

The rules are set before anyone builds.

Champions become the people who keep these rules once we have gone, so they learn to apply them first.

  • Your data stays in your accounts

    We work inside the tools you already licence, on accounts you control. Nothing is copied to ours, and any sample data is data you approve.

  • Your brand and compliance rules apply

    Your voice guide, claims rules and regulatory limits are written into every exercise and every system we build.

  • A person signs off

    Every workflow has a named owner on your team. Nothing reaches a customer without a human approving it.

  • No new tools required

    We start with what you already pay for. Where a gap matters, we explain it and leave the choice with you.

Led by practitioners, not trainers.

Sessions are led by Rajeev Pandey and the ThinkPivot team, who design and run these workflows for clients every week. The examples come from live operating work, not a course library.

Champions work directly with the practitioners who run these systems for clients. The weekly reviews are written by people who build, not by a course administrator.

Meet the team

FAQ

Questions buyers ask

Something not covered here? Ask us directly; Rajeev reads every first enquiry.

General workshop questions
Who makes a good champion?

Someone curious, respected by colleagues and close to the work. Credibility matters more than seniority. We help team leads choose before week one.

How much time does it take?

About three hours a week for each champion: the 90-minute build session plus time building on their own workflow. The sponsor needs a short check-in every two weeks.

Do champions need technical skills?

No. They need to be comfortable with spreadsheets and willing to test things. We teach the rest, and set up any connectors with them.

Is this a certification?

No. Champions are trained and judged on what they ship, not on a test. What counts is a workflow running on real work.

What if a champion leaves?

Every workflow has a written guide and a second person who has been taught it, so the work does not leave with one person.

Can it run across several teams or offices?

Yes. Champions can come from different teams or locations. Build sessions are remote, and we recommend an in-person kickoff.

How does leadership see progress?

Through a mid-point check with the sponsor and the adoption scorecard in week six, with the method behind every number shown.

Other formats

The other two ways in.

Compare all three formats

Build the capability inside the team.

Tell us how many champions, which teams they come from and what should be running in six weeks. We reply personally, usually within two working days.

Request this workshop