Skip to the deck
LevelCraft Download PDF

What each person leaves with

AI for your team

A working automation they can run and stop, the ability to build the next one, and a one-page brief for their own work project.

01

A working automation you can run and stop

Built on your own laptop from approved sources, on a schedule you control.

02

The ability to build the next one

A repeatable way to build, and enough of what is underneath to trust it.

03

A one-page brief for your own work project

The starting point for two months of one-on-one work.

LevelCraft01 / 14

How we work together

Three clearly defined offers

01

The course

8 weeks
Group learning

Eight live classes, one a week, with guided practice after each.

Build and operate your first automation.

02

Your project

2 months
One-on-one

Twice a week with a builder, on one real workflow from your own work.

A workflow in use, owned by the person who built it.

03

Build and care

Scoped separately
Specialist delivery & care

Dedicated development, integrations, security work, and ongoing maintenance.

Scope and terms agreed separately.

LevelCraft02 / 14

Personalized to your company

Your work is the curriculum

The projects come from your work. The examples in the room are your workflows.

ILLUSTRATIVE EXAMPLES / REPLACED WITH YOUR OWN AFTER DISCOVERY
01

Weekly distribution briefing

Read last week’s channel numbers and published posts, summarize what moved, and draft three next actions for the marketing owner to check before Monday.

02

Supplier invoice triage

Match incoming invoices to their orders, flag the exceptions, and leave every approval with the person who owns it.

03

An onboarding checklist that checks itself

Read the systems a new starter touches and report which steps are done and which are waiting on whom.

In the course everyone builds the same first pattern on their own sources. In the project phase each person builds one workflow like these from their own work.

LevelCraft03 / 14
01 / The course / 8 weeks

01 / The course / Classes 1 and 2

Build something that works

Check your setup, then build a morning briefing from public data. You leave the first class with something that runs.

  1. 1A

    Your first app

    Check your setup, then build a morning briefing from public data: the weather and the news.

    Practice Run it again tomorrow and check it against the source.

  2. 1B

    Change it, break it, fix it

    A repeatable way to build: brainstorm, plan, build, verify. Make a change on purpose and recover from it.

    Practice Add one thing you want and keep the version that works.

You learn what you need when you need it, on something you actually want to work.

A risograph workbench with an open construction book and hand plane beside a small timber house frame
LevelCraft04 / 14
01 / The course / 8 weeks

01 / The course / Classes 3 to 8

Connect it. Run it. Share it.

CLASSES 3–4Connect real sources

  1. 2A

    Calendar, email, and keys

    Add your calendar and selected email, with the keys kept where the company approves. Check the output against the source.

    Practice Verify each item in tomorrow’s briefing against where it came from.

  2. 2B

    Data and rules

    What is saved, where it lives, and what the access rules allow.

    Practice Write down what your tool can and cannot touch.

CLASSES 5–6Make it run itself, and keep it safe

  1. 3A

    Make the briefing run itself

    Schedule it while your computer is on. Inspect a run, recover, and stop it.

    Practice Let it run for a week and check its runs.

  2. 3B

    History, undo, and sharing your work

    Keep a history of changes, undo a bad one, and share work with a partner. This is Git, once you have something worth protecting.

    Practice Recover an earlier version on purpose.

CLASSES 7–8Work together and plan what is next

  1. 4A

    Partner review and operating notes

    Review a partner’s tool and have yours reviewed. Write the notes someone else would need to run it.

    Practice Apply one change from the review.

  2. 4B

    Plan what is next

    Present your tool and a one-page brief for a real workflow from your own work.

    Practice Operate and improve it over the next week.

One 90-minute class each week, plus an optional office hour. About 45–60 minutes of guided practice after each class.

LevelCraft05 / 14
01 / The course / 8 weeks

01 / The course / One 90-minute class

Guided work, then your own

75 minEssential work

  1. 01 · 10 min

    Review

    Look at the previous practice.

  2. 02 · 15 min

    Demonstrate

    Explain and show the next move.

  3. 03 · 40 min

    Build together

    Participants do the work with help.

  4. 04 · 10 min

    Check and save

    Try the result and keep the work.

15 minHelp buffer

Questions, delays, and individual support.

After the class: 45–60 minutes of guided practice

Repeat the same skills with less help. Record the result and bring it to the next class.

LevelCraft06 / 14
01 / The course / 8 weeks

01 / The course / The commitment

Five people. Close support.

5

participants

One builder leads. A co-host helps anyone who gets stuck.

1 × 90 minLive class each week, plus an optional office hour
1 × 45–60 minGuided practice each week
Before class 1Laptop setup, with a guide and our help

About two and a half to three hours a week during the course. About ninety minutes a week in the project phase.

LevelCraft07 / 14
01 / The course / 8 weeks

01 / The course / Where it runs and what it can touch

Your company sets the boundaries

Company approval comes first

Agree the tools, the permitted sources, and where information can be stored before anything is connected. A short company pre-check before class 1 confirms licences and allowed tools.

Runs on their own laptop

Each participant works on their own machine, set up before class 1 and checked with us. Nothing is installed on company servers during the course.

Read-only, approved sources only

The course reads information from sources IT approves. It does not send replies or change company records.

Keys and saved data stay where you say

Credentials, saved summaries, and run records live only where the company approves. Participants see their own information within that boundary.

A named owner and a stop control

Every scheduled tool has an owner who can inspect a run, change it, and stop it.

LevelCraft08 / 14
01 / The course / 8 weeks

01 / The course / What each person demonstrates

A working tool. A capable owner.

01

Useful

The briefing contains information its owner needs.

02

Accurate

Dates, claims, and tasks match the sources.

03

Reliable

The owner can verify a run and recover from a problem.

04

Under control

The owner can change the instructions and stop the schedule.

READY FOR YOUR PROJECT

Your one-page brief

We review the tool, its operating notes, and the project brief. The owner makes the checks. The bar is demonstrated capability, not attendance.

LevelCraft09 / 14
02 / Your project / 2 months

02 / Your project

Two months. Your workflow.

Twice a week, one-on-one with a builder, working from the brief you wrote in the course until the workflow is in use.

2 × 45 min a week

One-on-one sessions for each participant, with a builder.

2 months to start

Continuation can be agreed as needed.

Start from your brief

One workflow, its users, and the approved sources it needs.

Build, test at work, bring back what broke

Parts that need a dedicated developer are scoped as Build and care.

The pattern from the course, read approved sources, summarize, schedule, verify, stop, is the skeleton of every workflow you build here.

Two architect lamps focused on one miniature bridge at a shared studio table
LevelCraft10 / 14
03 / Build and care / Scoped separately

03 / Build and care

The parts that need a builder

Dedicated development and ongoing care, agreed apart from the course and the project sessions.

THE WHOLE AUTOMATIONBuilder-led delivery

Ask us to deliver an agreed workflow, with clear checks and an owner who knows how to use it.

SELECTED COMPONENTSBuild alongside your team

Your people build with help in their sessions. We take the parts that need a dedicated developer.

CONNECTIONSBuild and maintain the plumbing

Access controls, credential handling, and connections to company systems.

ONGOING CAREKeep it running

Audits, security hardening, and fixes for the code and connections we own.

Agree which parts we own, the checks required, and the maintenance terms. Every project uses company-approved access.

An open specialist toolbox with precision instruments and a small mechanical assembly
LevelCraft11 / 14

Who we are

Builders who teach

LevelCraft is part of Xiao, a Delaware public benefit corporation building an institution for builders.

01

Teachers are working builders

Every teacher is actively building: enterprise projects, fellowship projects, their own. Not a training class reading slides.

02

Commercial work funds free education

Programs like this one pay for free education for young builders. We say so.

03

The bar is demonstrated capability

Not attendance. Each person shows a working tool they can run, change, and stop, and explains how it works.

LevelCraft12 / 14

The next step

A plan around your team

Confirm the people and the first projects. Agree approved access and dates.

01 / The course8 weeks
02 / Your project2 months
03 / Build and careScoped separately
01

The people

Five participants, a sponsor, and an IT contact.

02

The projects

A useful first result, its sources, and the people who will use it.

03

The support

One-on-one time, development work, and the parts we will maintain.

Who should be in the first five?

LevelCraft13 / 14

Appendix / Use case: distribution

Your marketing, built in-house

One way teams use the program: turn how you reach customers into tools your own people build and run.

01Start

Diagnosis

A marketing assessment and an AI-visibility audit: where customers come from, where the hours go, and how AI assistants describe and recommend you.

02The course, then your project

Build each piece with your team

One piece at a time, built by your people with us: a weekly distribution briefing, drafts for each channel, a weekly AI-visibility check, a report on what worked.

03Build and care

Your own AI agent for marketing

The pieces join into an agent your team runs every week, on your accounts and your data.

You own it. No agency tax.

A use case, not a separate program. Every team takes the same eight classes.

AI visibility

The weekly check asks several AI assistants the same questions your customers ask, and logs mentions and citations. What moves it is mostly good SEO plus proof from other sites. No one can guarantee a place in AI answers.