Module 6

Graduation

Look at what happened here. A few hours ago — maybe a few days, if you spread it out — the phrase "I'll just build a tool for that" was not something you could say. Now it is. Let's close the loop properly: a recap, a glossary you can come back to, and a launchpad for what's next.

What you built

1. A break-even calculator. In your very first working session, you described a financial tool in plain English and Claude built it as an interactive artifact — then you improved it twice by simply asking. The lesson: software starts as a clear description of what you want.

2. A customer intake website. Real HTML, CSS, and JavaScript files on your own computer, built by Claude Code under your direction, styled and reworded until it matched your business — and published to the live internet with a drag and a drop. The lesson: the describe-review-refine loop works on real projects, and you are the reviewer.

3. A QuickBooks A/R aging dashboard. A Node.js app that proves itself to Intuit with OAuth, asks the QuickBooks API for open invoices, and turns them into aging buckets, totals, and a chart — with secrets handled properly in a .env file, read-only from start to finish. The lesson: your tools can talk to your business systems, safely, on your terms.

Just as important is what you learned around the edges: your AI account is configured privately, you know the four things never to paste into any AI tool, and you know that error messages are things you hand to Claude, not things that stop you.

Glossary: every term from this course

Bookmark this. Each definition is one plain-English sentence — the same explanations you met along the way, gathered in one place.

• API — a formal, safe way for one piece of software to request things from another, like a waiter carrying orders between your table and the kitchen.
• API key — a secret code that lets software access an account; treat it like a key to your office and never paste it into websites or chats.
• A/R (accounts receivable) — money customers owe you; an aging report groups it by how overdue it is.
• Artifact — an interactive thing (like your calculator) that Claude builds in a panel beside your chat, ready to use immediately.
• Claude — the AI assistant from Anthropic that you've been working with; you talk to it in plain English.
• Claude Code — Claude in your terminal, able to create files, build whole projects, and run programs — always with your permission.
• Client ID and Client Secret — the username-and-password pair that identifies your app to a service like Intuit; the ID is shareable, the Secret never is.
• Commit — a saved snapshot of your code in git, like a dated version you can always return to.
• CSS — the styling layer of a web page: colors, fonts, spacing, and how it adapts to a phone screen.
• .env file — a small text file that holds secret keys separately from your code, so code can be shared without sharing secrets.
• Git — the tool developers use to save snapshots (commits) of a project's files over time.
• .gitignore — a list telling git which files to always leave out of snapshots; your .env file always goes on it.
• Hosting — putting a website on a server so the whole internet can reach it, like Netlify did for your intake page.
• HTML — the content and structure of a web page: the headings, text, forms, and buttons.
• JavaScript — the behavior of a web page (what happens when someone clicks or types), and the language Node.js runs.
• Localhost — the web address that means "this computer": an app at localhost runs privately on your machine, not on the internet.
• LTS — "Long Term Support": the stable, recommended version of software like Node.js, as opposed to the experimental one.
• Node.js — a free program that lets your computer run JavaScript outside a web browser; your dashboard runs on it.
• OAuth — the standard way one app gets your permission to access your account on another service, via that "allow access?" screen you clicked through with Intuit.
• Prompt — the message you type to an AI; being specific, giving context, and iterating are what make prompts work.
• Sandbox — a free practice copy of a system, filled with fake data, where nothing you do can affect the real world.
• Terminal — a way of operating your computer by typing commands instead of clicking icons; Claude Code lives here.

Where to go next

The pattern you now own — describe it, build it with Claude, review and refine — applies to almost any repetitive or number-crunching corner of your business. Some ideas that owners in different industries have found worth building, roughly in order of ambition:

• A quote builder — type in job details, get a formatted, printable estimate with your standard pricing and terms built in.
• A price-increase letter generator — paste a customer name and their current rate; get a warm, personalized letter in your voice.
• A scheduling helper — paste your week's jobs and crew list; get a suggested schedule that respects drive times and skills.
• A review responder — paste an online review (glowing or rough); get three response drafts matching your tone.
• More QuickBooks dashboards — the same read-only pattern from Module 5 works for sales by customer, expense trends, or a morning cash-position summary.
• An internal FAQ tool — feed Claude your policies and procedures, and let new hires ask it questions instead of interrupting you.

Start small, keep secrets in .env files, stay read-only with real data until read-only feels boring, and remember the Module 1 rules about what never gets pasted. Beyond that: if you can describe it clearly, you can probably build it.

One last click

Marking this module complete finishes the course and unlocks your certificate — suitable for printing, framing, or casually leaving visible during video calls.