Back to Free AI consulting course
Course glossary
Terms from the public introduction and module 1. Sign in from a locked lesson to read the rest of the course glossary.
- AI (artificial intelligence)
- Software that reads, writes and makes judgements from information, rather than only following fixed steps.
- Example: Used two ways: to build the app, and inside the app to do real work.
- AI inside the app
- AI that does part of the job for the people using the app, not just help write the code.
- Example: The app reads each fault report and suggests which part to bring.
- AI workspace
- The tool where you talk to the AI and it works on your project.
- Example: Chosen during EAI Setup. The course uses Claude Code.
- Authentication (sign-in)
- Proving who someone is before they get in, usually with a login.
- Example: Technicians sign in on their phones. Someone who isn't signed in is sent to the sign-in screen.
- Claude Code
- An AI coding tool from Anthropic. EAI runs inside it.
- Example: The tool used on screen throughout the course.
- Client first
- EAI starts by understanding the client and the problem, then builds. The usual way is to ask for a feature straight away.
- Example: "Help me understand the problem before we build anything."
- Coding tool
- The software where you build. EAI runs inside several, with the same steps.
- Example: Supported: Claude Code, Codex, GitHub Copilot, Gemini CLI and VS Code.
- Context
- Everything the AI knows about your situation: the client, the problem, the goal. Better context gets a better build.
- Example: Who Coastal Snacks is, the second-visit problem, and what good looks like.
- EAI
- The AI tool the course teaches. It starts with the client and the problem, asks questions, plans, then builds.
- Example: Used in every lesson to consult, size, design and build.
- EAI Setup
- The one-off installer that creates your project and connects EAI to your AI workspace.
- Example: About 10 minutes, done once.
- First-time fix
- Fixing a machine on the first visit. Coastal Snacks' goal, and the number the app is built to move.
- Example: One in three call-outs needs a second trip.
- Four ways AI pays
- Every good opportunity does at least one of these: cuts cost, grows revenue, lifts customer satisfaction, or handles more volume with the same team.
- Example: The second-visit problem hits all four.
- Go live (deploy)
- Putting the app online so real people can use it, usually with a link and a login.
- Example: EAI puts the app live and hands back a link to open on a phone.
- Hunch
- A likely explanation or idea you haven't checked yet. Treat it as a guess until it's tested.
- Example: Technicians turn up without the right part because fault reports are vague.
- Personal productivity
- Using AI to save one person time on their own tasks, like emails and meeting notes. Step one, and the smallest win.
- Example: "The 80%."
- Plan (from EAI)
- EAI's description of what it will build, before it builds. Your chance to catch a misunderstanding cheaply.
- Example: The restock alerts plan came back in four pieces.
- Plan, build, check
- EAI's working order: it sets out a plan and checks it with you, builds, then runs the app and fixes what breaks.
- Example: The first version of the technician app.
- Project
- The folder that holds your app and everything EAI needs.
- Example: Named and saved during EAI Setup.
- Prompt
- The message you type to the AI. In the course, an opening prompt sets up a whole conversation.
- Example: The opening prompt for the opportunity hunt, under the 3.3 video.
- Template
- A generic starting design that isn't built around a specific client's problem.
- Example: What EAI avoids by asking about the client first.
- The 80 and the 20
- About 80% of businesses stop at personal productivity. The 20% put AI into how the business runs, which is where the money is.
- Example: Faster emails are the 80%. Restocking a fridge before it runs empty is the 20%.