100 School
Rebuild
Early access

Rebuild how your teams work. One workflow at a time.

A cohort programme for the people best placed to change how their team works. Each picks one real workflow the team shares, rebuilds it with AI, and measures what changed for everyone it touches.

Early access. We're shaping the first cohorts now.

An example of a rebuilt workflow: a marketing team's weekly campaign report going from five hours to one every week, rebuilt with AI, with three hours back for the marketing analyst, one hour back for the campaign manager and fewer errors for the head of marketing.

People are faster. The team still works the same way.

One person can only take AI so far on their own. Then they hit the work they share: the handovers, the sign-offs, the data someone else holds. That's where the bigger return is, in the workflows a whole team runs.

Most companies try to get at it with a champions network. Tips in a channel. Lunch-and-learns. Lots of activity. It's mostly theatre, and very little changes in how the work gets done, for four reasons.

The wrong people.

Chosen for enthusiasm, not for who's best placed.

No mandate.

It sits on top of the day job, so it's the first thing dropped.

A blank page.

"Go and find AI opportunities" produces pet projects.

Nothing lasts.

A demo that works most of the time, built by someone who then moves on.

None of that is the champions' fault. It's how they were set up.

The work your engineers will never get to. And shouldn't.

Every organisation has two kinds of AI work. Rebuild is for the second kind.

Above the line · not us

A handful of deep workflows

Heavily integrated, run through everything. Your engineers and your vendors own these. We don't touch them.

the engineering line

Below the line · Rebuild works here

The long tail nobody owns

The work every team shares, week in, week out. Frequent, painful, low-risk, and too small to ever justify an engineer. There are dozens in every department.

  • Weekly client report
  • Month-end checks
  • Renewals forecast
  • New-starter onboarding
  • Campaign reporting
  • Supplier queries
  • Contract review prep
  • Board pack
  • Tender responses
  • Customer handovers
  • Invoice matching
  • Rota planning

One workflow each, from idea to running live.

1

Pick

Each person chooses one workflow their team runs every week.

2

Map

They write down how it works today and time it.

3

Rebuild

They redesign it with AI until it's reliable, not a demo.

4

Run

The team uses it for real.

5

Measure

Before and after, with a named owner.

We guide and record. Your people build.

We don't do the work for them or sit inside your tools, so the skill stays with you.

Then it runs again, every quarter.

A new cohort, the next workflows, and a sharper picture of where to look.

Proof you can point to.

Workflows running live.

Each with an owner, a before-and-after measure, and a record of who it changed things for.

A ranked map.

Where the value sits, department by department, including what was tried and stopped.

People who can do it again.

Next quarter, the next workflow.

From each person's work to the whole team's.

Baseline

15 Days of AI

Everyone, into the habit.

See how 15 Days works →

Apply

Beck

Beta

Each person, on their own work.

See how Beck works →

Transform

Rebuild

Early access

Each team, on the work they share.

It only works with a real mandate.

What it asks of you

  • A named senior sponsor.
  • Protected time for each person.
  • A small group, chosen for who's best placed, not who's keenest.

Not the right fit if

Your people haven't built the basic habit yet. Start with 15 Days of AI.

You want someone to build it for you.

Know which workflow you'd rebuild first?