The Claude AI Money Bible

Chapter 1: Choose Your Plan and Model Without Wasting Money

Overview

The right subscription can cost nothing or a hundred dollars a month, and the gap between an impressive result and a useless one often comes down to a choice that looks trivial. Picking badly wastes both money and time, yet nothing on the sign-up page says which option is right.

Free, Pro or Max

Free gives limited daily messages on a mid-strength model, enough for the first two or three days. Pro, about $20 a month, is this book's working plan; free accounts stall at Book 4's Claude Code and Cowork tools. Max, about $100 a month, suits heavy daily use, not beginners. Stay free through chapters 1 to 6, upgrading to Pro at Book 2's product module or Book 4. Avoid Max on day one, staying free past Book 3 and blaming the tool, or using an unread email. Test: send a message and confirm the model name appears. Pay monthly first, yearly after two months of daily use; keep the receipt, deductible.

Which Model to Pick

The dropdown holds four.

• Haiku, the intern: tiny jobs like shortening text or fixing spelling
• Sonnet, the everyday worker: normal daily tasks
• Opus, the senior: complex thinking, long documents
• Fable, the star: anything that matters, client work, writing, planning

Rule: use the strongest model your plan offers for anything that matters, lighter ones for throwaway tasks. Beginners hoard the good model, get average results, and decide AI is overrated. Avoid the fastest model for important writing, switching models mid-conversation, or assuming new names obsolete the basics. Test: ask the lightest and strongest models for a customer apology about a late delivery. If an answer feels shallow, check the model first.

Three Things Claude Can't Do

Claude has three limits.

• Confidently wrong: false facts in a calm tone; check numbers, prices, dates, laws, 'studies show' claims
• Knowledge cutoff: without web search, recent news or today's prices may return outdated and confident
• Knows only what you tell it: hence chapter 3, the most valuable in Book 1

A new employee shares these limits; you would still hire them. It costs $20 a month and works at 3am. Don't publish unverified statistics or ask current-events questions without web search. Test: ask today's date and this week's top news with web search off and watch how it handles not knowing. Verify facts that would embarrass you if wrong.

Key Takeaways

• Start on the free plan through Book 3, upgrade to Pro before the product module or Claude Code/Cowork tools, and skip Max entirely your first few weeks.
• Choose the strongest model your plan gives you for any task that matters, and use the lighter models only for throwaway jobs, or you will get average output and unfairly blame the tool.
• Treat any confident-sounding number, price, date, or "studies show" claim as unverified until you check it, because Claude can be wrong calmly, knows nothing after its cutoff without web search, and learns only what you tell it.
• Run a quick sanity check whenever output feels shallow: confirm the model name in the dropdown, then compare the lightest and strongest models on the same prompt before trusting either.
• After roughly two months of daily use, switch from monthly to yearly billing and hang onto the receipt for tax purposes.

Chapter 2: Install Claude on Your Phone and Your Computer

Overview

A tool you must think about reaching for is one you will not use. Getting it onto both your phone and your computer, with a single coherent identity, runs into more obstacles than it should.

Installing the Phone App

Claude reaches the pocket in about three minutes. Search "Claude" in the App Store on iPhone or Play Store on Android, install the app by Anthropic (dark icon, orange starburst), and sign in with the same email used on the computer. Existing chats appear immediately, with no manual syncing. Verify by sending a message from the phone and finding it at claude.ai. Two mistakes cause real trouble: downloading a similarly named copycat app, and signing in with a different email, which silently splits the account in two. Keep the app on the home screen next to frequent apps; that placement decides between daily use and being forgotten.

Installing the Desktop App

The browser version of claude.ai covers the fundamentals, but the desktop app opens in one click and reads files from the computer more directly. Download it from claude.ai, pick Mac or Windows, follow the installer, sign in. On a work computer, check IT rules before installing; otherwise bookmark claude.ai in the browser, which handles most of the book. The installed app becomes necessary for Claude Code and parts of the Cowork features; a personal machine, or a phone plus a friend's laptop for one evening, covers it. Test by opening the desktop app, sending "hello", and finding it on the phone. Learn the keyboard shortcut: when asking Claude beats opening Google, you ask it everything.

Matching Device to Task

Use both devices on purpose, each for its own job.

• The phone captures: ideas on the move, photos of documents and signs, voice notes that become plans, quick replies, and long answers read on the sofa.
• The computer produces: file work, long outputs, and anything a customer will see.

Phone-only use reaches about a third of Claude's capability; computer-only use misses ideas that arrive away from a desk. Don't attempt a website from the phone, and don't wait until you're at the desk to capture an idea; the moment passes. Test the handover by starting a request on the phone and continuing it on the computer. Keep one Project named Inbox for random captures and sort them at the computer on Sunday.

Key Takeaways

• Install Claude only from the official App Store or Play Store listing with Anthropic’s dark icon and orange starburst, and sign in with the same email you use on your computer; the two silent failure modes are lookalike apps and a split account.
• Put the phone app on your home screen next to apps you open daily, since that placement is the difference between a tool you actually use and one you forget.
• Install the desktop app on a personal computer so you get one-click file access and the doorway to Claude Code and Cowork, but when a work computer’s IT policy forbids it, a bookmarked claude.ai handles most of this book.
• Match the device to the moment: capture ideas, photos, voice notes, and quick replies on the phone, and produce files, long outputs, and customer-facing work on the computer, none of which works well on the other device.
• Keep a single project named Inbox for every random capture and sort it on your computer at the end of the week, so an idea taken on the move reliably turns into something usable.

Chapter 3: Set Up Projects So You Never Repeat Yourself Again

Overview

Starting fresh in a chat means re-explaining your situation every single time, and that repetition eventually becomes the reason people give up. The useful work gets buried under the same setup questions, asked and answered again. How do you make context persist without rebuilding it by hand?

Talk Instead of Typing

Tap the microphone icon near any phone chat's message box and speak; Claude turns your speech into the message. Typing is slow on phones, so requests come out short and vague, and the answers match. Talking lets you ramble for two minutes about a problem, then type "turn this into a clear plan" and get one. Messy speech is handled fine; check names and unusual words before sending. The best use: ten minutes of talking through a problem while walking, then "summarize this into three decisions" when you get home.

What a Project Is and When to Make One

A Project is a saved workspace that remembers your situation. Record your background once, and every conversation opened inside it already has that context: who you are and how you like things written. Without one, every chat starts from zero, and that constant re-explaining is why most people give up on AI tools. Create one from the left menu, name it, and fill the instructions box; that box is the whole feature. Make Projects for anything you will return to more than twice; use normal chats for one-off questions. Avoid one giant "Work" Project mixing conflicting businesses, and name Projects by what they produce: "Salon posts" beats "Salon."

The 5 Sentences to Put in Your Project Instructions

In the instructions box, write:

1. Who you are: "I am Rosa, owner of Rosa's Kitchen, a family Italian restaurant in Bristol."
2. Your customers: local families and couples aged 30 to 60, mainly for Sunday lunch.
3. Your voice: warm and family-run, proud but never posh.
4. Never: mention prices, use exclamation marks, or say "delicious."
5. Always: end with a reason to book by phone.

The fourth line carries the most weight in the book: banning three concrete items removes most of the telltale machine tone at once. The five lines work anywhere. Keep them in a phone note; next Project setup drops from fifteen minutes to three.

Adding Files So Claude Knows Your Business Properly

Upload documents to the knowledge area; every conversation in the Project can use them permanently. Add these in order of value:

• Price list or menu
• Services list
• Best past work
• Customer FAQ
• Any document you keep explaining repeatedly

No passwords, banking details, card numbers, or anyone else's private data, ever. With the menu uploaded, a request about a lunch offer returns real dish names and prices; without files, the AI invents. Keep to the ten files that matter, replace outdated files rather than adding second versions, since conflicting files produce confidently wrong answers.

One Project Per What? Real Examples

• Job plus side hustle: "Day job," "Side hustle," and "Personal admin."
• One business: "Marketing," "Customer replies," and "Admin and numbers."
• Client work: one Project per client, always, because client A's voice leaking into client B's posts loses both.
• Studying: one per subject, with course materials uploaded.

Everyone should have an "Inbox" Project for random captures from the phone. Five to eight Projects is the sweet spot; fewer is too broad, more is forgettable. Prune every couple of months.

Key Takeaways

• Use the phone's dictation button to ramble through a problem aloud, then ask for the ramble to be compressed into a plan or decisions when you are done.
• Create a Project for anything you will return to more than twice, and fill its instructions with who you are, who your customers are, your voice, three banned phrases, and one required ending.
• Upload your menu, price list, or other reference documents to the Project's knowledge area so answers use your real details instead of invented ones; keep the set under ten files and replace outdated files rather than adding second versions.
• Match Project size to what you produce: one per client or per subject, plus an Inbox for random captures, and keep the total around five to eight so none becomes forgettable.
• Keep the five instruction lines as a reusable phone note, and every future Project setup drops from fifteen minutes to three.

Chapter 4: Get Answers From Your Bills, Contracts and Photos

Overview

Every important paper in your life is written by someone who wants something from you, yet we read them like outsiders, squinting and guessing at what matters. We pay for expertise we can’t judge and decide based on documents we’ve never understood. There has to be a better way to face the stack.

Upload a Bill or Contract

Claude reads uploaded PDFs, Word documents, spreadsheets, photos, and screenshots. Describing from memory is like imitating engine noise to a mechanic, so upload instead. In a twenty-page Bangkok apartment lease, Claude was asked to list every money cost, flag anything one-sided, and verify personal details. It caught a misspelled name threatening the deposit refund, a clause letting the landlord cut electricity after late payment, and one-sided cancellation terms. Worth uploading:

• phone or internet contracts
• insurance policies
• rental or employment agreements
• medical letters
• invoices

Avoid blurry photos, vague questions, and uncovered bank or card numbers. Verify on one known detail. For legal matters, prepare with Claude, then consult a professional.

The Three Questions

Three questions work on any paperwork.

1. Explain this simply, as if I'm smart but not an expert in this field.
2. What could cost me money now or later: fees, automatic renewals, deadlines, penalties?
3. Is anything unusual, unfair, or worth questioning versus how such documents normally look?

One is the translator, two the money detector, three the second opinion that licenses pushback. Follow-ups: what to ask before signing, and the three worst clauses rewritten as you would want them, for concrete negotiating language. Ask one at a time; check claims that a clause is illegal. Run question two on any subscription; a forgotten auto-renewal or fee surfaces. Do it before signing.

Photos of Anything

The phone camera as input is the book's fastest move. Claude reads printed text, handwriting, screenshots, charts, labels, signs, and forms from photos. Uses:

• bills you don't want to type
• forms you're stuck on
• per-unit comparisons
• foreign menus
• error messages
• whiteboard scribbles turned into an action list

Photograph the fridge and ask what to cook. Shoot one page at a time, straight on, well lit; don't expect perfect transcription of terrible handwriting, and check names and numbers. Test on a printed page: ask for an exact transcription and compare. When handed a document in person, photograph it and run question two from section 4.2 before leaving the room.

Key Takeaways

• Feed Claude the actual document, not what you remember of it, and treat the answer as preparation: for anything legally binding, carry it to a professional before you act.
• Run the three questions as a fixed routine before you commit to any document: a plain translation, a hunt for every cost that could come due later, and a comparison with the standard shape of such paperwork. The third pass tells you which clauses are genuinely worth fighting over.
• Ask for the contract's three harshest clauses rewritten the way you would prefer, so you walk into the negotiation with concrete wording instead of a vague objection.
• Point the money question at subscriptions you already pay for and at any paper document handed to you in person; forgotten renewals and hidden charges surface there while you can still act on them.
• Keep each photo to a single page, taken head-on and with good light, and verify every name and figure yourself, since a blurry capture is precisely the input failure that turns a careful reading into a guess.