発見 · For teams · Early access

The training you'd build for your team if you had a spare week. Built from your docs, in minutes.

Hakken interviews each learner and builds a course pitched at what they know. That's live today, for individuals. For teams, we're exploring the next step: start from your material, set the bar you want, and let Hakken build and adapt the course per person against it.

It isn't live yet. We're talking to a handful of teams first — if that could be yours, tell us about it.

01

Why bother

Training is absurdly expensive to make. Most teams skip it

  • $10k–$50k

    to build one finished hour of e-learning by hand

    79 to 490 hours of work, per hour of training. Most teams never start. The ones that do build it once and let it go stale.

    Chapman Alliance benchmark, 249 organisations (2010, nominal USD)

  • 18 hours

    for a six-minute training video or podcast

    Even the fastest format is a two-day job. Hakken writes a whole module — lessons, exercises, a checkpoint, a podcast episode — in about the time it takes to make coffee.

    ATD, 264 training professionals (2020)

  • 1 in 10

    say mandatory training changed how they work

    Completion gets measured because it's measurable. A course that checks understanding, and fixes the gap when someone misses, produces a different kind of record.

    Gallup, 13,583 U.S. employees (fielded 2018)

02

What it would look like

Half of this exists. The other half is what we want to build with you.

Live today, for individuals

  • It starts by interviewing each person

    A few minutes, text or voice. What they know, what they need, how much time they have. What they know gets a paragraph, not a module.

  • A checkpoint per module, and a review lesson when someone misses

    Miss a checkpoint, get a fix. Hakken writes a short lesson on exactly what tripped them, then lets them retake.

  • A tutor that rides along — typed or out loud

    Ask, and the course changes. Hakken answers, or proposes a change to the course itself. Each module can become a podcast for the commute.

What we're exploring for teams

  • Your material, not a library

    Built from the doc you already have. The SOP, the policy, the product doc — Hakken shows you which passage each lesson came from, and what it left out.

  • A bar you set

    Say what good looks like. Checkpoints measure against your bar, not a generic quiz — evidence someone can do the thing, per person.

  • Rebuilt when the doc changes

    Update the source, not the course. The process changed Tuesday. The course follows — nobody re-records a video or reopens an authoring tool.

Learning for yourself rather than a team? Hakken is in open beta — no form needed.

03

Tell us about your team

Four questions. A person reads the answers.

We reply ourselves — no sequence. Send a doc (an onboarding guide, a process, a policy) and we'll build a course from it, then show you what came out.

How many people would learn?
Who runs training today?