AI Fluency for Small Businesses: teaching notes
Side-by-side notes for 11-praxis-ai-fluency-for-small-businesses.html (12 slides). This is the 4D framework (Delegation, Description, Discernment, Diligence) reapplied to the small business owner: capabilities and limits, market research, customer data, operations, and a team AI policy. It is the sibling of course 05 (Framework & Foundations); where 05 teaches the framework cold, this one runs it through one person's whole business. Reuse the 05 examples as the seed; the difference here is that the learner is usually the owner, so every slide ties back to their business, not a department. Written from the deck and 11-ai-fluency-for-small-businesses-lessons.txt, against the Praxis teaching library. Method: teaching-notes-method.md.
How to use these notes
- Guidance, not a script. Teach the person, not the slides.
- Every teaching slide has a Pause, then ask block. Put the question, then stop. Don't fill the silence. If they freeze: "Take your time, type anything when you're ready, including 'I don't know'." Then wait again.
- By background gives a line per archetype (
tutor/scenarios.md). Reach for the one that matches whoever's in front of you; the rest are a palette, not a checklist. For this course the strong fits are Outreach, Exec, Knowledge worker and Content, but a small business owner is usually all of these at once, so don't over-sort. Treat the tag as "which hat are they wearing for this task". - The throughline of this whole course is one line from the deck: efficiency is not the point, it's the means. Every hour AI saves should buy back time for the human side of the business, better service, real relationships. Return to that. It's also the answer to the job-loss fear.
- Hold the voice (
train-the-trainer.mdPart 4): no "great question", no emoji, one term: Claude Code. Underclaim. Cost is "about twenty dollars a month" and stop.
Four moves that make AI actually work for your business
Set the frame: not tips and tricks, four habits that outlast the tools. Nine ideas, one screen each, ending in a policy the owner and their team can stand behind. The watching is the lesson, so take the silences.
"Tips and tricks date fast; the tools change every few months. This is the thing underneath that doesn't: four moves that make AI actually work for your business. Learn them once and they keep working whatever the tool does next. And the point isn't to do everything faster, it's to buy back time for the part of the business only a human can do."
The thing eating their week. "By the end we'll have run your real task through all four moves, and you'll have a one-page policy you could hand your team tomorrow."
The whole course on one screen
Learn the framework, understand the tool, run its two loops, put it to work, ending in a team policy. Orient, don't teach.
"Here's the shape. We learn the framework, look at how the tool actually works, run its two loops, then put it to work on something real, and we finish with a one-page AI policy. If you lose the thread, this is the map back."
Twenty seconds. The 4D framework on slide 4 is the heart; everything else points at it.
Write your business down once
Most owners retype their context into every chat. Build it once, in a back-and-forth interview with AI, into a reusable briefing sheet: mission, role, customers, constraints, where AI could help. Then every conversation starts already informed. This is the small-business version of "the folder is the memory" before the folder exists.
Pair the project-memory framing with the briefing-sheet move: "You find yourself re-explaining your business to AI every single time, who you are, what you sell, what you'd never compromise on. Do it once. Sit down and let it interview you about your business, then have it write that up as one document you paste in from then on. Every chat after that starts already knowing your business." (framings.md: the folder is the memory, the previewed version; 01-claude-101 slide 7, projects as a workspace that remembers.) Read the caption out loud: AI fluency is using AI efficiently, effectively, ethically and safely, and the efficiency exists to buy back time for the human work.
- "What do you re-explain to AI, or to every new hire, every single time?"
- "Finish this sentence honestly: if AI could help me _____, I'd spend more time _____."
(wait: the second blank is the whole course's promise; let them name it.)
- Investigator
- the house report rules, screening standards, what you never infer.
- Analyst
- the standard column set, the "no data" rule, your reporting basis.
- Designer
- brand tokens, the retailers you ship to, the specs that bite.
- Knowledge worker
- the suppliers you deal with and their quirks, the schema you need.
- Reporter
- the five-section format and who's on the team.
- Content
- the house voice, the back catalogue, the audience you write for.
- Form-filler
- the template, the categories, the filing cycle.
- Outreach
- what you sell, who buys it, the relationship history that shapes the ask.
- Exec
- mission, the KPIs you watch, the constraints you operate under.
Owners share too much in the interview, real customer names, exact figures. Name it now, lightly: "be mindful what you paste, we'll cover privacy properly two slides on." Don't derail; just flag it. (Lesson 1 exercise says the same, gently.)
The 4D Framework, two loops
Four competencies in two loops. The outer loop frames every job: Delegation (decide what to hand off) and Diligence (own what comes back). The inner loop does the work between them: Description (say what good looks like) and Discernment (judge what came back), run over and over, sharper each pass. Delegation sets the stage; Diligence closes it.
"Four habits, two loops. The outer loop is the bookends: Delegation, decide what's even worth handing over, and Diligence, own the final result with your name on it. The inner loop runs between them: Description, say what you want and how, and
, judge what came back. You run that inner loop again and again, and it gets sharper each pass. That's the whole framework, and the rest of the course is these four." (05-... slide 5 is the same idea; this deck draws it as two nested loops, which is the only real difference, so point at the picture.)
- "Of those four, which are you already weakest at? Most people know."
- "Take the task eating your week. What would delegation even mean for it, before you typed a word?"
(wait)
- Investigator
- delegate the extraction; describe "cite every source, never infer"; discern the citations hold; stand behind the filing.
- Analyst
- delegate the table; describe columns and basis; discern the "no data" cells are honest; own the comparison.
- Designer
- delegate the variants; describe the brand rules; discern they're on-brand; sign off the campaign.
- Knowledge worker
- delegate the extraction; describe the schema; discern the flagged rows; trust the CSV.
- Reporter
- delegate the consolidation; describe the five sections; discern nothing's misattributed; send the briefing.
- Content
- delegate the draft; describe the house voice; discern it's on-voice; publish under your name.
- Form-filler
- delegate the allocation; describe the categories; discern the totals reconcile; submit it.
- Outreach
- delegate the per-customer drafts; describe the format; discern no invented numbers; send it.
- Exec
- delegate the synthesis; describe "facts, not editorial"; discern risks are stated straight; present it.
"Describe what good looks like, once" is writing the rules down, the skill file they'll meet in the Claude Code courses. Plant the seed here; don't dwell. (framings.md: skill file as institutional memory.)
What it does well, where it slips
Knowing how the model is trained tells you what to trust it with. Strengths: versatile across tasks, natural conversation, connects to your tools. Limits: a knowledge cutoff (stale facts), hallucinations (confident and wrong), context limits, multi-step reasoning that can slip. The limits aren't bugs to wait out, they're why you pair its speed with your oversight and verify anything that costs money to get wrong.
"It's strong exactly where most of us are short on time, speed, breadth, tireless drafting. And it's bounded in ways that matter for a business: it has a knowledge cutoff, so recent or local facts can be stale. It can be confidently wrong. The best work pairs its speed and scale with your judgment, and you verify anything that would cost you money to get wrong." (05-... slide 7, strong-where-you're-weak.) Read the in-diagram line: it predicts plausible text, it does not look facts up.
- "What's the judgement you bring to your business that it structurally can't?"
- "Where in your business would 'plausible but wrong' actually cost you money?"
(wait)
- Investigator
- a hallucinated fact bites hardest → your verification is the value.
- Analyst
- an invented figure → your basis-checking is the value.
- Designer
- it lacks your taste → you curate, it supplies volume.
- Knowledge worker
- it'll guess a blank → your "leave it empty" rule holds the line.
- Reporter
- it can't read the room → you decide what people need to hear.
- Content
- it doesn't know your audience → you own voice and judgement.
- Form-filler
- rules change past its cutoff → you check this year's thresholds.
- Outreach
- it doesn't know the relationship → you bring the angle.
- Exec
- it can't carry accountability → you own what you act on.
The knowledge-cutoff limit is sharper for a small business than for most: local rules, tax thresholds, this year's pricing. The lesson exercise is explicitly "ask it something local and time-sensitive, then check". Use that as the live demo of the limit.
Under the hood: it guesses the next word
Same trick as your phone's keyboard, scaled up. From what's been said so far it ranks likely next words, picks one, adds it back, and repeats. It's prediction, not lookup, which is exactly why it can sound certain and still be wrong. The idea is a century old (Markov, 1906); transformers in 2017 made it fluent.
Pick the route by audience (framings.md: deterministic vs probabilistic). For most small-business owners, the phone-keyboard route the deck draws: "It's the predictive text on your phone, scaled up. From what's been typed so far it guesses the most likely next word, picks one, adds it, and guesses again. That's all. Brilliant for drafting and summarising. But it's guessing what's plausible, not looking up what's true, so it can be completely certain and completely wrong." For analysts and regulated owners, the "cat sat on the mat" version. For technical peers, one sentence and move on.
- "If it's guessing a plausible answer rather than looking up a true one, what does that change about when you'd trust it?"
- "Where in your business would 'plausible' simply not be good enough?"
(wait)
- Investigator
- it predicts a plausible date, it doesn't know one, demand sources.
- Analyst
- it generates a plausible figure, not a true one, cite it or mark "no data".
- Designer
- generating a plausible look is its gift, ideate freely, you curate.
- Knowledge worker
- it can plausibly fill a blank, which is exactly why you forbid it.
- Reporter
- it'll smooth a gap with something plausible, attribute everything.
- Content
- plausible prose is its strength, lean in, then check the facts.
- Form-filler
- a plausible category isn't a correct one, give it the definitions.
- Outreach
- it'll invent a plausible stat, forbid numbers not in the file.
- Exec
- a plausible projection isn't a real one, numbers as-is, no extrapolation.
This is the conceptual "aha" that makes cost, safety and reliability click later. Don't skip it for time. There's a hands-on widget in the source lesson (the "Text Your Friend Markov" page), if the owner is curious, that interactive is the cleanest way to feel it; mention it as homework, don't try to run it live.
Describe well, then never skip the check
The inner loop, made concrete on research, the highest-stakes thing a small business asks AI for (regulations, competitors, pricing). Good context in (Describe), then discernment on the way out (Discern): is it real and current? relevant to a business my size? what's missing? Two outlets, use it, or verify at the source. AI accelerates research; it does not replace your expertise.
"The inner loop in practice, and the place it matters most for you is research. Two halves. Going in, you describe: who you are, what your business does, the exact thing you need. Coming back, you never skip the check, is this real and current, is it right for a business my size, what's it missing? The big trap with research is that it'll happily invent a competitor or quote a stale number with total confidence. So anything that decides money, regulations, a competitor's price, a deadline, you verify at the source." Read the caption: the gap between what AI sees and what you know is where your judgment is irreplaceable.
- "What's a piece of digging you do that means opening twenty tabs and pulling it together?"
- "Walk me through one round: it gives you a competitor list, what's the first thing you'd check before you trusted it?"
(wait)
- Investigator
- background research on a subject; verify every cited source exists.
- Analyst
- market-rate benchmarking; verify the numbers against the original source.
- Designer
- a competitor-campaign scan before a pitch; check the brands still trade.
- Knowledge worker
- supplier due-diligence; confirm terms haven't changed.
- Reporter
- a landscape read to frame the narrative; attribute every claim.
- Content
- source-gathering for a piece; check each citation is real and current.
- Form-filler
- this year's thresholds or allowances; verify against the official site.
- Outreach
- a prospect brief before the proposal; confirm the company facts.
- Exec
- a competitor or market brief; verify the headline figures before acting.
"What if it just makes things up?" lives here. Answer straight: ask for sources, then check at least one. The lesson exercise builds exactly this habit, ask it to name a trade body or supplier, then verify it exists. (objections.md: hallucinate / make stuff up.)
Strip it before you share it, own it after
The outer loop on the owner's own business data. Delegation here is a data decision: match the tool to the sensitivity, and strip what isn't needed, names, contacts, exact figures, before you share. Diligence is owning what comes back: accurate to my records? useful, keep/edit/cut? would I put my name on it? Some tools train on your inputs; if something goes wrong, act fast, delete the chat and request data deletion.
"Same outer loop, now on your own business data, sales, feedback, customer lists. Two gates. Going in, you delegate deliberately: strip names, contacts, exact figures the AI doesn't actually need, and match the tool to how sensitive the data is, some tools train on what you type. Coming back, you own it: is this accurate to my records, is it useful, would I put my name on it? And the reassurance that matters, you connect what you trust, and a tool sees only what you can see; connecting your inbox doesn't expose anyone else's." (01-claude-101 slide 10, connectors; objections.md: IT/compliance/privacy.) Read the in-diagram line about acting fast if something goes wrong.
- "Which piece of your business data feels most sensitive, and what's your plan to protect it?"
- "Before you'd put your name on something AI produced from your data, what's the bar?"
(wait)
- Investigator
- the privacy of the file; disclosure where required; you vouch for the filing.
- Analyst
- where the data may go; transparency to stakeholders; you sign the comparison.
- Designer
- rights and brand safety; credit AI where the client expects; you ship it.
- Knowledge worker
- how the data is handled; a note the CSV was AI-assisted; you trust the numbers.
- Reporter
- who sees the raw updates; the briefing is yours to stand behind.
- Content
- your publication's disclosure norms; your name goes on it.
- Form-filler
- the privacy of the receipts; you submit and you're accountable.
- Outreach
- customer-data handling; you vouch for every claim in the proposal.
- Exec
- confidentiality of the inputs; you own what you act on, AI-assisted or not.
This is the data-safety gate for almost every small business owner. Slow down. Give the floor (Claude on the web, no install) and the ceiling (a local model, nothing leaves your network). The caption's second half also matters, AI helps even if you're "not a numbers person": formulas, plain-language read-outs of your figures. Use that to defuse the "I'm not technical" fear here. (objections.md: IT/compliance; not technical.)
Ask "should AI do this?", not "can it?"
All four Ds at once, the operations slide. Before automating, sort the work into three lanes: AI can handle (documented, standardised, FAQs, hours, return policy), AI assists and a human decides (drafts a reply, you send it), human only (complaints, contracts, judgement). The question is never capability, it's appropriateness. Then describe the system three ways, Product (what it makes), Process (the steps), Performance (tone, limits, what it must never do), and apply diligence before a single output reaches a customer.
"Now operations, and this is all four Ds working together. Before you automate anything, sort the work. Don't ask 'can AI do this', ask 'should it?'. Three lanes: the stuff AI can just handle, your hours, your return policy, the documented FAQs; the stuff where AI drafts and you press send; and the stuff that stays human, complaints, contracts, anything needing judgement. Then for whatever you automate, describe it three ways, what it makes, the steps it follows, and how it must behave, including what it must never do. And test it on real cases before it ever touches a customer." (05-... slide 10 covers the three Description layers; this slide adds the sorting and the test-before-ship discipline.)
- "Think of last week. What's the most repetitive task you'd put in the 'AI can handle' lane?"
- "What in your business goes in 'human only', no matter how good the AI gets, and why?"
(wait: the second answer is the heart of the human premium; let them feel it.)
- Investigator
- AI drafts the standard sections; the judgement call on significance stays yours.
- Analyst
- AI builds the recurring table; deciding what's comparable stays yours.
- Designer
- AI batches the variants; the creative direction stays yours.
- Knowledge worker
- AI processes the routine files; the awkward exceptions stay yours.
- Reporter
- AI consolidates the updates; deciding the narrative stays yours.
- Content
- AI drafts to the pattern; voice and the final argument stay yours.
- Form-filler
- AI allocates the clear receipts; the edge cases stay yours.
- Outreach
- AI drafts one per customer; the relationship and the ask stay yours.
- Exec
- AI answers the standard customer FAQs; the complaint, the negotiation stay yours.
People over-delegate the judgement and under-delegate the grunt work, the opposite of the win. And the diligence half of this slide is non-negotiable for anything customer-facing: review outputs first, be honest about AI's role, always keep a path to a human. Spend time there for any owner automating customer comms. (objections.md: permission/auto.)
Write the policy your team can stand behind
Scale your judgement by writing it down. One page, three honest sections: what we use AI for (approved tasks and tools), what stays human (the work AI doesn't touch, and why), how we stay accountable (oversight, transparency, what happens when something goes wrong). Being "the human in the loop" is more than oversight, you decide what problems AI should solve. Avoid dependency through understanding, not avoidance: if you can explain what the AI is doing, that's a good sign.
"The last move is to write your judgement down so your whole team works from it, not from whatever they each invent. One page, three sections, and the trick is to be honest in all three: what we use AI for, what stays human and why, and how we stay accountable when something goes wrong. This is the same idea as everything else today, the rules in your head, written down, so the work comes out your way every time, whoever's doing it. And the worry people raise, dependency, the answer is understanding: if you can explain what the AI is doing, you're fine. The time it buys back should free your team for more of the human work, not less." (framings.md: skill file as institutional memory, adapted from one expert's head to the team's shared page.)
- "If a customer asked you straight, 'do you use AI in your business?', what would you want to be able to say?"
- "What's the work in your business you'd never let AI touch, and could you say why in one sentence?"
(wait)
- Investigator
- the accountability section, who verifies, and what's never inferred.
- Analyst
- the transparency section, where the data goes, what's disclosed.
- Designer
- the "what stays human" section, taste, brand sign-off, client credit.
- Knowledge worker
- the "what we use AI for" section, the named, approved tasks.
- Reporter
- the accountability section, who stands behind the briefing.
- Content
- the transparency section, disclosure norms, whose name goes on it.
- Form-filler
- the accountability section, the review step before filing.
- Outreach
- the "what stays human" section, the relationship, the real signature.
- Exec
- all three, this is the document they'll actually own and circulate.
This is where the human teacher beats the video, and the natural home for the job-loss and dependency fears. Name them and answer honestly: a human with AI beats either alone, and that gap doesn't close; we're future-proofing the role, and the policy is how you say so in writing. (05-... slide 7 watch-for; train-the-trainer.md: name the fear.) For a Praxis student, this policy is the artefact, point out that the one-page policy and a skill file are the same instinct, judgement written down once.
Pick one real task this week
Fluency is a habit, not a certificate. Choose one real task already waiting for you and run the full loop, Delegate, Describe, Discern, Diligence, then go round again. It's a loop, not a line. Keep a running doc of the prompts and workflows that work, so you're not starting cold each time and anyone on the team can pick them up.
"You don't get fluent by finishing a course, same as you don't get fluent in a language that way. You get there by doing it, badly at first, then better. So pick one real thing waiting for you this week, and run all four moves on it: decide what to hand off, describe it well, judge what comes back, own the result. Then do it again, it's a loop, not a line. And keep a running doc of what works, so next time you start warm." (05-... slide 15, fluency is built by practice. framings.md: the system improves through use.)
- "Of everything today, what's the one task you'll point this at this week, one concrete thing, not a category?"
- "What would 'a bit more fluent' look like for you a month from now?"
(wait: their first answer is the use case you build the rest of the relationship around.)
- Investigator
- turn one case file into a structured background report.
- Analyst
- one comparison you run every quarter.
- Designer
- one campaign's full asset list.
- Knowledge worker
- one month's invoices into a clean CSV.
- Reporter
- this week's briefing from the team's updates.
- Content
- one post drafted in house voice from the back catalogue.
- Form-filler
- one filing period's receipts allocated to the template.
- Outreach
- one segment's proposals, personalised.
- Exec
- one board prep, or one set of customer FAQs, turned into a repeatable output.
Resist adding features. The win is one task done, not ten shown. The deck points onward to the blueprints at claude.com/resources/use-cases and to the deeper AI Fluency: Framework & Foundations course (course 05), name them as the next step, then close the loop on their task. For a Praxis student, the durable version of this, the folder, the skill file, the script, is the next session in Claude Code. (patterns.md: set the next concrete step.)
Decide what to hand off. Describe it well. Judge it. Own it.
The whole course in one line: four competencies, two loops, run on real work until the gains buy back time for the human side of the business. The framework outlasts the tools.
"Four moves, two loops, one practice. If the tools change next year, and they will, this still holds. Decide what to hand off, describe it well, judge what comes back, own the result. Run that on real work until it's saving you real time, and spend that time on the part of your business only you can do."
Their task from slide 11 and the next concrete step. End with the session-improvement habit: "at the end of any session, tell it to look back at what you did badly and save how you fixed it, so next time it's better." For Praxis students, point forward: 4D is the why; the skill file and Claude Code are the how that makes "describe what good looks like, once" permanent. (framings.md: the system improves through use.)