Build from systems that actually worked.

Learn directly from operators who’ve already solved the problems you’re trying to solve. Stop guessing, start executing.

Kraftrun, spelled out in portraits of the operators behind the playbooks

I was more comfortable knowing what I was implementing in my own workflow was actually proven.

Bill lockwoodFounder of kites

Why this exists

The internet is noise.
This is the signal.

Anyone can sell advice an AI wrote last night, and nothing tells you whether it ever worked. Kraftrun is the trust layer: every playbook here is filtered from the noise and built by someone who has actually done it.

What Kraftrun is

A marketplace of systems
that already ran.

Operators publish the playbook they used to get a result. You find the one for the problem you are stuck on, and run it. Free to browse.

Operators publish what worked
Not theory, and not a course. The actual sequence someone ran to get a result, with the templates they used attached where they used them.
You start from your problem
Describe what you are stuck on rather than guessing which category it lives under. The playbooks that answer it come back.
Nothing gets in unreviewed
Every operator is checked by hand, and every playbook has to come from someone who has already built the outcome it describes.

The operators

Built from the
best in the game.

Every system comes from an operator who’s already built the outcome.

Marcus Delray

View profile ↗

What you actually do

Not a document.
A system you work through.

Find the one for your problem, work through it a module at a time, and keep the ones worth coming back to.

  • 01

    Start from the problem

    Say what you are stuck on. You get the systems that solved it, instead of guessing which category it lives under.

  • 02

    Know what you have done

    Each module ends in things to do, not things to know. Mark them off so progress means implemented, not read.

  • 03

    Nothing left to hunt down

    The videos, prompts, templates and files the operator used, sitting at the step where you need them.

  • 04

    Keep what is worth running

    Save a playbook and it is in your library, so the one you found at midnight is still there on Monday.

  • 05

    Organise by what you are building

    Bundle the playbooks for one goal into a stack, so a launch or a first hire has its own shelf.

  • 06

    Always know what is next

    Run several systems at once and the next module across all of them is waiting, with who wrote it and how long it takes.

FAQs

Frequently
asked questions.

Still stuck?

The help centre covers accounts, saving, progress and the rest of what is not on this list.

Visit the help centre

General enquiries

Suggesting an operator, or anything else. Send it over and a person reads it.

Get in touch