Enterprise enablement

At enterprise scale, you are not buying classes. You are building a training capability.

Nobody teaches forty thousand people one workshop at a time. What works is enabling the people who already do enablement: your L&D function, your internal trainers, your staff engineers. We train them, hand over the instructional design, and build a ladder of formats so the twenty-minute audience and the three-day audience both get something real.

What we scope on the first call

01

The shape of the engagement — and the price — comes out of five questions. There is no configurator, because the answers interact.

  • How many people actually need to move, and by when?
  • What level are they starting from — and is it the same across the org?
  • Do we train your L&D and delivery team, or deliver it ourselves?
  • Is there an existing enablement process to work inside, or are we designing one from scratch?
  • Do you want turnkey, or do you want to own it afterwards?

The last question moves the price more than the headcount does. Turnkey is cheaper to buy and costlier to keep; owning it costs more up front and leaves you with a capability instead of a contract.

What we hand over

02

The deliverable is the machinery for teaching this, not a set of slides. It is designed to survive us leaving.

  • Trainer enablement — your facilitators certified to run the material themselves
  • The full curriculum, licensed for internal use and cross-training between teams
  • Instructional design that works across functions, not just for engineers
  • Assessment and certification so completion means something internally
  • Quarterly refresh, because agent tooling moves and stale material is worse than none

A ladder of formats, because attention is not evenly distributed

03

The same content, cut for different audiences and different time budgets. Most enablement fails because it only ships one length.

  • 20-minute module — for the sceptical majority who will not book a day
  • Lunch-and-learn — for teams that need exposure, not depth
  • 1-Day Intensive — for the people doing the work, capped at 30 so it stays a workshop
  • 3-Day Track — for the lead team that will carry it for everyone else
  • Self-paced path — for the people who will always prefer to read

Making it land is the hard part, and it is the part we do

04

Enablement rarely fails on content. It fails on arrival — as a mandate from corporate that reads, to the people receiving it, like a plan to make them redundant or to make their craft worse. We run the change management so it lands as an offer rather than a threat.

  • Adoption design — what people hear first, from whom, and in what order
  • Executive alignment, so the message from the top matches the one in the room
  • Manager enablement, because middle managers decide whether this is real
  • Delight over compliance: a programme people opt into beats one they endure
  • Measurement that tracks capability, not attendance

We take resistance seriously, because it is usually informed

05

Every organisation has people who do not want this. In our experience they are rarely uninformed — they have concerns about job security, craft, provenance, environmental cost, and what it does to the people they manage. Steamrolling them is how programmes quietly die.

  • An honest ethical session, not a hype deck — the objections get named and engaged
  • Where a concern is correct, we say so, and we teach where the tool genuinely should not be used
  • Where it rests on a misunderstanding, we work through it rather than around it
  • Sceptics who have been argued with, rather than at, become the most credible advocates you have

This is not a soft add-on. Adoption is where the 95% failure rate lives, and resistance handled badly is the most common cause we see.

How it is priced

06

Delivery days alone cannot cover an organisation of this size, and you should be suspicious of anyone who quotes them as if they could. An enterprise programme is an annual licence for the materials and the certification, plus the delivery days needed to stand it up.

  • An annual licence, priced in bands by the number of employees covered
  • Delivery days to certify your trainers and run the lead cohorts
  • Optional bespoke instructional design where your process differs
  • One agreement, one invoice, one renewal conversation

Programmes at this scale generally start around $250,000 a year and run well beyond it, depending on how many people are covered and how much of the design you want us to own.

Who you are actually buying at this level

07

Manifold is not a training marketplace with an account manager attached. At the advisory tier the person designing your rollout is Liz Howard, who has served over 3 million students across the education organisations she has founded and run — enough of the profession to have touched the careers of roughly 1 in 14 software engineers worldwide.

3M+
students served
1 in 14
software engineers reached
  • Founding instructor at Hackbright Academy; CTO at Enki; founder of The Multiverse School
  • Programme design by someone who has run education organisations at scale, not a template
  • Change management from someone who has watched enablement succeed and fail in real organisations
  • The curriculum is hers — so it can be adapted to your context rather than delivered as fixed

The reach figure counts students served across those organisations, set against global software-developer population estimates. The platform, the materials and the certification scale. This part does not, which is why the advisory tier is capped and priced where it is.

Source: Track record and reach — lizthe.dev

Start with the scoping call.

Bring your headcount, your L&D lead, and an honest answer about whether you want to own this afterwards. We will come back with a programme, not a quote for days.

Source: MIT Media Lab, State of AI in Business 2025 — reported by Fortune, Aug 2025