The AI Training Kit — Complete Deliverables

The kit contains eleven deliverables designed to work as an integrated system. You deploy them on a six-week timeline. Here's what each one is, what it contains, and what it does.

D-01: Executive Briefing Document

6-8 pages. Read alone. Not for distribution.

This is your foundation. You sit down and read this first, by yourself, before you tell anyone else what you're doing. It's written for you to understand the landscape without hype, to see the actual risk categories, and to understand what companies your size are already doing.

The briefing covers: what AI is and what it isn't, the real capabilities and the real limits, the liability categories that matter to small businesses, what approaches your peers are taking, and most importantly, where your company actually stands before you make any decisions.

This is not cheerleading. It's not cautionary either. It's analytical. You read this so that when you talk to your team, you're speaking from a position of informed clarity, not reactive panic and not naive optimism.

D-02: AI Acceptable Use Policy Template

3-4 pages. Editable Word document.

The single most important document in the system. This is your written policy on what employees can and cannot put into AI tools. It covers: approved tools, prohibited data types, what happens if someone violates it, and a signature acknowledgment block.

It's templated. You open it, drop in your company name, review it with your lawyer if you want to, and deploy it. When an employee signs it, you have documented that you told them what the boundaries were. That changes the liability conversation.

The policy covers what everyone needs to know: customer information, financial data, employee records, proprietary processes, and contracts are off limits. Everything else requires judgment. The template gives you language you can edit and customize.

White-label: your company name, your contact person for questions, your consequences. Ready to sign and file.

D-03: Employee AI Safety Training Email Series

5 emails, 400-600 words each. Self-deploying.

This is the core training mechanism. One email per week for five weeks. Employees read them on their time. No trainer required. No meeting. No workshop.

Email #1: What is AI and what is it not. Demystification without dumbing down.

Email #2: What not to put in AI tools and why. Specific examples of data that should never go in. Context on why free tools are public services.

Email #3: What these tools are actually good for. Real use cases so people stop treating AI as either magic or useless.

Email #4: Your company's policy, explained. This is where your specific policy goes into plain language and people understand what they're expected to do.

Email #5: Where to go from here. Resources, glossary reference, and the ongoing support structure so people don't feel abandoned.

Self-deploying: you set up the scheduling through Outlook or Gmail. Five emails, one per week, landing in everyone's inbox. White-label the company name throughout. No manual deployment required on your part after setup.

The tone is direct, zero condescension, short paragraphs, specific examples. These are written for manufacturing employees who are tired of corporate-speak. The voice is the same voice as everything in the system: someone who has actually done this, not someone who is selling you something.

D-04: Executive Risk Audit Card

1 page. Laminated format.

A three-question decision tree for any AI-related request or scenario that crosses your desk. You're not trying to become an expert. You're trying to make good decisions quickly.

The three questions walk you through: Is this about a new AI tool? Is this about data we might put in something? Is this about how we're using something we already approved?

Each path leads to a clear decision or action. You laminate this, put it on your desk, and when someone asks you to approve something AI-related or a problem surfaces, you answer three questions and know what to do.

It's reference material, not a manual. One page. Three minutes to use.

D-05: Staff Rollout Deck "The Upgrade Briefing"

12-15 slides with full speaker notes.

The optional all-hands briefing at the start of rollout. You don't have to do this. But if you want your team to hear from you directly that this is coming and why it matters, this is what you use.

The speaker notes are written so that any manager can deliver this. You don't need to be an AI expert. You don't need to prepare. The notes tell you exactly what to say, why to say it, and what to show on each slide.

It's 30-45 minutes for a full team. It covers: why you're doing this, what the policy actually means, what the training will look like, what you expect to happen, and where people can ask questions.

The tone matches everything else: direct, honest, no hype. Your team knows whether you actually care about this or you're just checking a box. This deck assumes you care and that you've thought through the business reason.

White-label: your company name, your situation, your timeline. The deck adapts to your context.

D-06: Prompt Vault — 50 Role-Specific Prompts

5 job categories, 10 prompts each. Copy-paste ready.

Solves the most common problem after training: "I understand the policy. I understand the risks. But what am I actually supposed to use this for?"

The vault covers five roles: operations, quality, HR, supervisors, and finance. Each has 10 ready-to-deploy prompts for actual work. Copy the prompt, paste it into the tool, feed it your specific context, and you have a starting point.

Each prompt includes context: what kind of information to feed it, what to watch for in the output, and the most common mistake people make when using it. This isn't theory. These are prompts that work because they came from actual work.

Operations examples: creating a shift handoff template, writing a preventive maintenance schedule, structuring a root cause analysis.

Quality examples: designing a checklist, writing audit notes that make sense, creating an SOP summary.

HR examples: drafting job descriptions, writing offer letters, structuring exit interview notes.

Supervisor examples: delegating tasks effectively, writing performance feedback, building a schedule.

Finance examples: organizing cash flow projections, building a simple P&L template, creating a budget summary.

Each prompt is specific enough to be useful immediately. Each is flexible enough to adapt to your company. Copy-paste ready means you're using these on day two, not three weeks in.

D-07: Buy vs. Build Decision Matrix

1 page. Three columns.

The most common mistake small businesses make: spending time or money on a custom solution to a problem that a $20/month subscription already solves.

The matrix has three columns: consumer subscription, business/enterprise tier, and custom API integration. Each column shows decision criteria and rough cost ranges. It answers the right question at each tier: are you choosing the right tool, or are you over-engineering?

This is one page. It sits in your decision folder. When someone proposes a new AI tool or capability, you spend two minutes checking it against the criteria and you know whether you're making a good choice or over-complicating.

Most small businesses need the consumer tier or the business tier. Very few need custom integration. This matrix prevents you from accidentally choosing the expensive path because you didn't know the simpler path existed.

D-08: AI Glossary Plain Language Edition

50-80 terms, 8-12 pages.

Every term your employees will encounter, defined without jargon. Manufacturing-relevant examples throughout. This is a translation document, not a tech document.

Employees hear terms like "hallucination," "tokens," "prompt engineering," "fine-tuning," "RAG," "model," "parameters." They have no idea what any of this means and they don't want to sound dumb asking. So they nod and move on.

The glossary defines every term they'll encounter using actual language, with examples. A hallucination is "when an AI tool confidently gives you information that's completely made up." A token is "basically a word, though technically it's smaller pieces than that, but thinking of it as a word is close enough." Fine-tuning is "training a model on your specific data so it learns your context."

Manufacturing examples throughout so the term makes sense in context. This is meant to be shared. Employees read this so they stop pretending to understand things they don't.

It's not comprehensive. It's practical. It covers the terms they'll actually hear.

D-09: Lead Magnet "5 Things Happening Right Now"

1-2 pages. Updated periodically.

Five AI developments that directly affect small businesses in the next 6-12 months. Updated periodically so it stays current. Designed to be shared, read in five minutes, and understood without technical knowledge.

Examples of what goes in here: new tools launching in your industry, policy changes that affect small businesses, capability improvements that matter for operations, industry-specific use cases that are becoming standard, and security issues that are worth knowing about.

This is marketing material that actually educates. It's meant to be something you share with your team, your peers, or your clients who are asking the same questions you are. It demonstrates that you're paying attention without needing them to become experts.

D-10: Sample Training Email

One email from the series, ~500 words. Formatted as deployment.

Email #2 from the training series, published in full at the sample page so you can read exactly what the tone and content are before you commit to the kit.

You see this first. You read it exactly as your employees would receive it. You judge whether the voice is right, whether the content is appropriate, whether this is something you'd want your team reading.

No summary. No condensed version. The full email.

D-11: Rollout Timeline Template

1 page. Gantt-style format.

Week-by-week sequence showing what gets sent, who sends it, and what to track. Fills in around your calendar and your preferences.

If you're doing the all-hands briefing, you see when that happens. The policy deployment date. The email schedule. When to monitor for questions. When to send the glossary reference. When to make the prompts available.

It's flexible. You can compress it or stretch it. But it gives you a clear sequence so nothing falls through the cracks and people know what's coming.

How It All Works Together

Day one: you deploy the policy and employees sign it. Your team knows the boundaries.

Week one: if you're doing the all-hands briefing, run it. Otherwise, the email series starts.

Weeks two through six: one training email per week. Employees read, they ask questions (you answer them), they learn.

Throughout: the glossary and prompts are available for reference.

By the end of week six, your team knows what to do and what not to do. They understand why it matters. You have it documented. Your exposure has dropped. And you have a reference system they can use going forward.

The Price

$997. One-time. Permanent license.

All 11 deliverables. All white-label where applicable. All yours to keep forever. No renewal. No per-seat fees. No questions about whether you're using it enough to justify the cost.

You buy it once. You have it.

At 50 employees, that's about $19 per employee. At 10 employees, it's $95 per employee. At 75 employees, it's $12.70 per person. The value increases as you scale, but the kit is designed to work and pay for itself at any size under 75.

[CTA Button: Buy the Kit — $997]