Someone reads the log
Every week, named
The watch log has a reader with a name against it. Fifteen minutes on a Monday, written down, including the weeks where nothing went wrong — an empty log and an unwatched agent look identical.
Level 3 of three · 32 hours · online, own pace
One customised project — from nothing to something — built for the company's benefit and chosen with the company's own numbers. Your team builds it, learns to monitor and maintain it, keeps the evidence that stands up to a question, and takes it commercial: a project that takes hours out of the administration, or one that adds a line of income — the system does the research and brings back about three feasible options — clients served overseas, and margin back in the price.
L3 is level 3 of the OwnYourAI corporate AI training path. It is 32 hours of online, own-pace learning delivered as 4 modules, and it is the point where your team builds a system the company owns and runs on its own server.
L3 · 4 modules · not open yet · part of a 72-hour path
Before you book this level
Level 1 is running now. L3 is designed; its sessions are still being written into the course.
We will not take your money for a level we cannot hand your team to work through, so L3 is not on sale until its sessions are in the course and a learner can open them. Nothing is charged for L3 today. The price above is what it will cost when it opens, not a bill, and the assessment is free.
Bring your team to the assessment anyway: it decides the right starting point, and if that is L3 we will tell you the moment it opens — before you are asked to pay anything. Plenty of companies start on Level 1 while the next level is being written, which is why most take one level at a time.
Session by session
Every session is online learning at the person's own pace, with a scheduled live touchpoint inside it and a trainer present. Each one ends with something your company keeps: 32 hours in total for L3.
| # | Session | The one thing it settles | What your company keeps |
|---|---|---|---|
| 1 | The project, chosen on the company's own numbers | Which work to fix first — the administration that eats the most hours, or a new line of income, with the system bringing back about three feasible ways to add it | A one-page project case with its numbers, the person who owns it, and the researched options beside their figures |
| 2 | The boundary, and where the data will live | What the system never decides, who each exception goes to, and the hosting choice: an existing server, a rented one, or one bought for the job | The boundary page signed by the process owner, and the written hosting decision with its reason |
| 3 | The machine, specified and quoted | What the hardware must be for this job, where it sits, its power and backup, and who may touch it | The server specification, the quotation request, and the equipment register |
| 4 | Install day: the model running on your own machine | The company's AI running on hardware it controls, with nothing leaving the building | The running system, its model card, and the written access list |
| 5 | The doors, the locks, and the team's way in | Who may reach it, over what, and the lock-down in order: two-factor, keys not passwords, three ports, the model never exposed to the internet, updates, sign-ups off, and a private network for staff | The locked-down configuration sheet, the access list, and a backup restored once to prove it |
| 6 | The company's own documents, and answers that cite the paragraph | Which papers go in, scanned files included, what is never loaded, and how an answer shows the exact text it came from | The document collection with its do-not-enter list, and the citation test sheet with its pass line |
| 7 | The paperwork that files itself | Which recurring jobs the system takes first, and what still needs a person | The automation list, each with its trigger, its owner, and the first date it ran |
| 8 | The four jobs we suggest first | The jobs a private AI does for a company at once: the weekly report written for the team, the contract form that pulls out the key dates, the support inbox sorted with a drafted reply, and a question answered from the company's own papers | The first two running end to end, each with a real sample of it working, and the rest listed with owners |
| 9 | Guarding a system that is entirely yours | With no outside provider holding any of it, the company carries every rule: the approval gate, the never-list, and the person told when it fails | The in-house guardrail document, the incident drill report, and the one rule that changed because of it |
| 10 | The daily routine and the watch log | The ten-minute check, who reads the log, and what a bad week looks like before it becomes a bad month | The watch log with its first entries filled in, and the reader's name |
| 11 | Records that stand up, and what it gave back | What a client, an insurer or an auditor would need, and whether the hours promised in session 1 came back | The evidence pack, answerable by a single named date, and the before-and-after on the company's own numbers |
| 12 | The customised project, demonstrated live | Whether the company can run, defend and maintain the system it built | The project record, and the assessment result part by part |
The standard every run is held to
A company that cannot produce these three has an agent running on trust. They are written in the sessions, by the people who operate it, in the company's own words.
Someone reads the log
The watch log has a reader with a name against it. Fifteen minutes on a Monday, written down, including the weeks where nothing went wrong — an empty log and an unwatched agent look identical.
Every failure has a written correction
The confident wrong answer, the right answer with the wrong detail, and the output that widens its own scope each get a written fix, stamped so the company can say which version produced which output.
The record is answerable by date
What the agent did on a named day, under whose authority, and who signed it. The evidence pack is assembled once, for real, and read back at the assessment.
The assessment
The assessment is delivered live online with a trainer present. It is not a multiple-choice quiz, and it does not test whether someone remembers AI theory: it tests whether they can do the thing on their own desk.
| Part | What the person does | Time | Marked by |
|---|---|---|---|
| A. The project on fresh input | Runs the customised system on two inputs the assessor supplies fresh at the assessment, and states the boundary it works inside | 20 min | Trainer |
| B. The citation | Answers a question from the company's own documents and shows the paragraph it came from | 10 min | Trainer |
| C. The record | Produces the evidence pack for a single named date, and says who may read it | 10 min | Trainer |
| D. The machine and the rules | States what the system runs on, who may reach it, and what happens in the first hour of a failure | 10 min | Trainer |
A. must produce a usable output on the inputs supplied fresh at the assessment: a prepared demonstration does not pass. B., C. and D. must each be answered correctly. Anyone who misses a part is assessed again on that part at no extra cost, and that re-assessment is recorded as such. The assessor is named on the record, with the date.
Per person, kept together and retrievable on its own: the identity record, attendance at each session, progress at each session with the work produced, the assessment result part by part, the artefact that was demonstrated, and the name of the assessor with the date. Everything on that list is written by a named trainer, not by the learner. What we keep, and who can read it is set out on its own page.
A quick look at what you can build
The Level 3 project, screen by screen, on top of the five Level 2 systems it builds on - with the before-and-after for each.
On illustrative data: no client's system and no client's data appears on those pages.
What this level is for
Before this level
In practice most teams do L2 first, because L2 gives them the ground this level builds on. If your team already has it, the assessment will say so and we will start you here.
After this level
You are not obliged to continue. Plenty of companies stop here, run with it for a quarter, and come back when they need the next piece.
What your team can do afterwards
These are the skills that travel between companies, which is why the level is written around them. About 70% of every level is that shared skill; about 30% is your own workflows.
| Skill | What the learner hands in |
|---|---|
| Artificial Intelligence Ethics and Governance | The record that stands up to a question: who decided what, when, and on what evidence. |
| Generative AI Model Evaluation | The monitoring sheet: drift checked on a schedule, the readings kept, and the action taken when a reading moved. |
| Generative AI Model Development and Fine Tuning | The customised project, built and running on the company's own numbers. |
| Workflow Digitalisation | The business process it took over, written down end to end, with the manual steps that remain. |
| Business Innovation and Improvement | The plan that turns it into a second revenue stream, with the price and the margin worked out. |
| Commercialising an AI Project | The first outside client, or the first month of the new revenue line, evidenced. |
| What | Detail |
|---|---|
| Level | L3 of three — A Customised Project — Build, Monitor, Grow |
| Hours | 32 hours |
| Delivered as | 4 modules, online and own pace |
| Scheduled touchpoints | Yes — online, booked in advance inside the level |
| Working language | Plain English. No technical background needed. |
| What you keep | The work produced, the written record, and the skill in your own staff. |
A result, how it is measured, when it lands, and what happens if it does not.
L3 — questions
Previous: L2 — Build Your Company's Own AI System ·
Next step
The assessment tells you whether L3 is the right place to start, and what it would cost for the seats you actually need.
Ask us for a free quotation for the seats you need — nothing is charged before you approve it.