Claude Code for Non-Engineers

“Raise your hand if you have ever waited more than a month for a tool or report that IT was supposed to build.” Hands go up. “Keep your hand up if the tool you eventually got was not quite what you asked for.” Most hands stay up.

“That gap — between what you need and what engineering has time to build — is the reason this module exists. Claude Code does not replace your engineering team. It fills the gap between ‘I need a tool’ and ‘engineering will get to it in Q3.’”

“I am going to build three working tools in front of you in the next thirty minutes. None of them require you to understand code. All of them solve problems you probably have right now.”

Open a terminal. Type claude to launch Claude Code. The audience sees a command-line interface with a text prompt, not a chat window. This visual difference is intentional — it signals that this is a different kind of tool.

Type: “Build a Python script that reads quarterly-sales-messy.csv, cleans up the column headers (remove spaces, lowercase everything), fills in missing region values by looking at the previous row, and outputs a clean CSV called quarterly-sales-clean.csv.”

Narrate what the audience sees: “Claude Code is reading the file. It is writing a Python script. It is running the script to test it. It found an edge case — some rows have ‘N/A’ instead of blanks — and it is fixing the script. Now it is running it again. Clean file created.”

Open both files side by side. Show the messy input and the clean output.

“Five minutes. This is the task someone on your team does manually every week with find-and-replace and conditional formatting. The script is reusable. Run it next week with a new file, same result.”

“This one is more ambitious. I am going to ask Claude Code to build a tool that a sales rep can use to prepare for customer visits.”

Type: “Build an HTML page with a form where a sales rep enters: customer name, visit date, visit objectives, and key contacts. When they click Generate, the page should create three things: a formatted visit brief, a draft calendar invite text, and a pre-visit checklist. Use clean, professional styling. No external dependencies — everything in one HTML file.”

Narrate the build process. Claude Code will create the HTML file, test it, and iterate on the design. Open the finished page in a browser. Fill out the form. Click Generate. Show the three outputs appearing on the page.

“Fifteen minutes. This is the kind of tool that sits on an IT backlog for six months because it is useful but not urgent enough to prioritize. Claude Code builds it in a quarter-hour. The sales rep uses it tomorrow.”

“Last one. Three CSV files: sales data, expense data, headcount data. I want a single dashboard that shows key metrics from all three, with charts, updated by running one command.”

Type: “Build a dashboard that reads sales.csv, expenses.csv, and headcount.csv. Calculate: total revenue, total expenses, revenue per employee, expense ratio, and month-over-month changes. Create an HTML dashboard with charts for each metric. Use Chart.js from a CDN for the charts. Save as dashboard.html.”

Show the finished dashboard in a browser. Click through the charts. “One command. Updated dashboard. This replaces the Friday afternoon ritual of copying numbers from three spreadsheets into a PowerPoint.”

“I will give you a task. You tell me which interface. Ready?”

“Task: You need to rewrite a client email to sound more professional.” Answer: Chat. It is a quick, one-off text transformation.

“Task: You need to build a script that reformats your CRM export every week.” Answer: Claude Code. It is a reusable tool.

“Task: You need to analyze three contracts for inconsistent terms.” Answer: Cowork. It is multi-file analysis that produces a document.

“Task: You want every support ticket automatically categorized and routed to the right team.” Answer: API. It runs at scale without a human.

“Task: Your marketing team needs ongoing access to brand guidelines and competitive research when chatting with Claude.” Answer: Projects. It is persistent background context.

Do six to eight scenarios. Let tables discuss before revealing the answer. The wrong answers are as instructive as the right ones — they reveal where the boundaries feel ambiguous.

“Claude Code builds things fast. Speed is not the hard problem. The hard problem is knowing what to build with Claude Code and what should go through your engineering team.”

“Here is the line: internal tools, personal automations, prototypes, data pipelines, one-off scripts — Claude Code territory. Production systems, customer-facing features, anything touching sensitive data at scale, security-critical code — engineering territory.”

“The highest-value use of this module is giving you the ability to prototype what you need and show it to your engineering team. Instead of writing a requirements document that gets misinterpreted, you hand them a working prototype and say: ‘Make this production-ready.’ The conversation changes completely.”