Build in Claude Code without the surprise bill
Five small habits that keep your AI spend low, shown as the exact things you type. No code, no jargon.
Distilled from Anthropic's Claude Code documentation on managing cost.
The outcome
By the end you'll know the five moves that keep an AI build cheap: pick the right model, watch the meter, clear the desk between jobs, plan before you build, and hand off the heavy lifting.
- Claude Code open on a project (the app or the terminal)
- Ten minutes. Nothing to install.
Your AI bill is mostly avoidable waste, not the price of the work. You pay by how much the assistant has to read and think, so the savings come from a few small habits, not a spreadsheet. None of this is code. It is the same handful of things you type into Claude Code, and most of the saving comes from the first three.
1. Use the right model for the job
Claude Code lets you choose how clever the assistant is, and that choice drives the cost. It defaults to a strong all-rounder (Opus), which is the right pick for most real work. But if you're watching spend, routine jobs (small edits, drafting, renaming) run fine on Sonnet or Haiku, which cost less per use. Open the menu with /model, or leave Auto mode on and let it choose for you.
Type /model to open the menu. Sonnet and Haiku cost less for routine work. Claude Code❯ /model
Select a model
Default Opus 4.8 · best for everyday work ✓
Sonnet efficient for routine tasks · cheaper
Haiku fastest, cheapest
# Default is the strong all-rounder. Drop to Sonnet or Haiku to spend less on routine jobs.
2. See what you're using
You're never flying blind, but where you look depends on where you work. The desktop app shows a usage ring next to the model picker. In VS Code, typing /usage opens a usage panel. In the terminal, /usage prints the details. One thing that trips people up: on a monthly plan (Pro or Max) you see how much of your allowance you've used, not a dollar figure. Only pay-as-you-go billing shows actual dollars.
Type /usage to see where you stand. In the desktop app it's the ring beside the model picker; in VS Code it opens a panel. Claude Code❯ /usage
This week
Plan used 38%
Resets in 4 days
# On a monthly plan you watch your allowance. Pay-as-you-go billing shows real dollars instead.
3. Clear the desk between jobs
The assistant remembers the whole conversation, and you pay to carry that memory on every turn. When you finish one task and start another, wipe the slate with /clear so the next job starts light. Mid-job, /compact tidies the memory without losing the thread.
Finished a task? Run /clear before the next one. Claude Code❯ /clear
Started a fresh conversation.
# Old clutter gone. The next job starts light, and light is cheap.
4. Plan before you build
The most expensive mistake is building the wrong thing and redoing it. Plan mode lets the assistant lay out its approach before it touches anything, so you approve the direction first. Turn on plan mode (Shift+Tab twice in the terminal, or the plan-mode control in the app), and it proposes the steps before changing a thing.
Plan first, approve, then let it build. Claude Code# Turn on plan mode before a big change.
Plan mode on. I'll propose the steps before changing anything.
# Approve the plan, then it builds. You stop paying for wrong turns.
5. Hand off the heavy lifting
This is the one advanced move, and you can skip it until you need it. When a job needs a lot of reading (digging through files, scanning logs), let a helper do it in a side conversation and report back just the answer. The heavy reading happens elsewhere, so your main session stays small and cheap.
Send big lookups to a helper that works on the side. Claude Code❯ find the three slowest steps in this workflow
Sending that to a helper to dig through the files...
Helper read 40 files, reports back 3 lines.
# You only paid for the 3-line answer, not the 40 files of reading.
The takeaway
Right model, check your usage, clear the desk between jobs, plan before building, hand off the heavy reading. Five habits, most of the savings.
Prefer to learn by doing?
The interactive version of this playbook lives on melwyn Class, with animated terminal demos, Claude Code walkthroughs, and a library that saves your takeaways.