Personal Guide — April 2026

Getting Started with Claude

A hands-on guide built for Mike Scherp — Sr. CPA, stock trader, fantasy football champion, future AI power user.

From your first prompt to building dashboards, websites, and automated workflows.

Built with care by your brother (and Claude) — April 2026

Use the tabs above (or click the section overviews below) to explore each section. Start with Overview

Ch 1 — Overview

What Claude is and why it matters for a CPA who trades and loves sports

Ch 2 — Get Started

Subscribe, download the phone app, and start using Claude in 5 minutes

Ch 3 — First Prompts

Copy-paste prompts tailored to your world

Ch 4 — Projects to Build

Landing page, dashboards, portfolio tracker & more

Ch 5 — IDE & Code

VS Code, Cursor, Claude Code, GitHub basics, and folder structure

Ch 6 — Advanced

APIs, MCPs, webhooks — connect betting, stocks & clone GitHub repos

Ch 7 — Workflows

Daily routines: market briefs, email drafts, game prep & more

🔥 Scott's Hot Tips

Tap to expand

Hard-won lessons from daily use. Internalize these and you'll get 10x more out of Claude from day one. See the full page →

See all 10 tips →

Week 1 Checklist

Tap to expand

Do these in order. By next weekend, you'll wonder how you lived without this. Open full checklist →

Progress0 of 10 complete
  • Redeem Claude Pro (use the gift link in Ch 2!)
  • Download the Claude app on your phone
  • Turn on Web Search, Code Execution, and Artifacts in Settings
  • Set your User Preferences (tell Claude who you are)
  • Set up Projects: Trading, Sports, and Client Work
  • Send your first 5 prompts — try the examples from Ch 3
  • Upload a CSV (trades, expenses, anything) and ask Claude to analyze it
  • Ask for a morning market brief and a betting lines dashboard
  • Get a personal laptop when you're ready for desktop power tools
  • Tell your brother how it went so he can add more ideas to your guide
Chapter 1
Overview — What is Claude & Why You Should Care

Claude is an AI assistant built by Anthropic. Think of it as an incredibly smart teammate who can write, analyze data, build websites, automate tasks, and explain complex topics — available 24/7.

Data Analysis on Demand

Drop a CSV of stock trades or client data and get instant summaries, charts, and insights — no Excel formulas needed.

Sports & Betting Intel

Pull live betting lines, build comparison dashboards, analyze fantasy matchups — Claude is your research analyst.

Build Things Without Code

Describe what you want in plain English and Claude writes the code. Websites, tools, dashboards — all from conversation.

Automate Your Routines

Morning market briefings, calendar management, client memo drafts, expense categorization — automate the boring stuff.

Think of it this way:

Claude isn't just a chatbot. It's a Swiss Army knife — a research analyst, web developer, copywriter, and data scientist rolled into one. The key skill you're learning isn't "coding." It's how to describe what you want clearly.

🌐 Where Claude Lives — And What Each One Can Do

Tap to explore

Claude isn't one app — it's available in four places, and each one unlocks different capabilities. Think of it like a car: the phone is a remote start, the browser is the rental car, the desktop app is your fully loaded daily driver, and the terminal is a race car.

PlatformBest ForLevelStart?
📱 PhoneChat on the go, dictate prompts, dispatch tasks to desktop, quick research, review & approve workBeginnerCompanion
🌐 BrowserFull chat, artifacts, file upload, web search — works on any computerBeginnerBackup
💻 DesktopEverything above + Cowork, computer use, Chrome control, local files, scheduled tasks, extensionsBeginner★ Start
⬛ TerminalFull app building, code projects, GitHub, scripts, API integrations, automation pipelinesIntermediatePhase 2

📱💻 Deep Dive: Phone vs Desktop — What Can Each Actually Do?

Tap to explore

Same brain, different bodies. Here's what each platform can and can't do:

📱 Phone — Your Command Center

Can do:

→ Full chat (same AI brain)

→ Web search, file uploads, artifacts

→ Voice dictation (up to 10 min)

Remote Control — send tasks to desktop

Dispatch to Cowork — assign a job from bed, it runs on your PC

Can't do:

→ No local file access

→ No computer use (can't control your screen)

→ No Cowork or Claude Code

→ No scheduled automations

💻 Desktop — Your War Room

Everything above, plus:

Cowork — reads, edits, creates files on your machine

Computer Use — controls your screen, opens apps, clicks, fills forms

Claude in Chrome — browses the web for you, scrapes data

Local file access — reads your actual folders and docs

Scheduled tasks — "pull a report every Friday"

Claude Code built in

Quick summon — Ctrl+Alt+Space

🌐 Browser & ⬛ Terminal

Browser — same as desktop chat minus the power tools. Use on someone else's machine.

Terminal (Claude Code) — the developer power tool. Writes files, runs commands, manages Git. Where serious automation happens.

🎲 Real Example: Betting Line Reports on Each Platform

Tap to explore

Same goal — "get me daily betting line reports" — very different capabilities on each platform:

📱 Phone: Manual but Fast — ★★★☆☆

Ask Claude each morning for lines. Web search only, one-time report. Clean and useful but manual every time.

🌐 Browser: Same as Phone, Bigger Screen — ★★★☆☆

Identical data, just easier to read on a full monitor. Still manual, no API access, no scheduling.

💻 Desktop: Semi-Automated — ★★★★☆

Claude in Chrome navigates actual sportsbook websites. Computer Use reads your screen. Cowork saves to CSV. Schedule it to run at 6:30 AM automatically — wake up to a finished report. No typing after setup.

⬛ Terminal + APIs: Fully Automated — ★★★★★

Python script calls The Odds API → structured data from 15+ sportsbooks → calculates implied probability → flags arbitrage → tracks line movement → texts you when lines shift → runs 365 days, hands-free. This is what the sharps use.

The progression:

Phone/desktop manual prompts (this week) → Desktop Cowork + Chrome automation (week 2–3) → Full API pipeline with Claude Code (month 2). Each level builds on the last.

Mike's path:

Desktop App for 2–4 weeks → learn prompting → build your consulting landing page → explore Claude Code + APIs → graduate to VS Code / Cursor when you're ready for bigger projects.

Can your phone dispatch the desktop tools?

Yes — and this is the killer combo. Once you set up a Cowork task or Claude Code session on your desktop, you can dispatch it from your phone. So you're lying in bed Sunday morning, tap your phone, tell Claude "run my betting lines report," and it executes on your PC using all the desktop power tools. You get the results on your phone a few minutes later. The phone is the remote control. The desktop is the engine.

Chapter 2
Get Started Right Now

You don't need a new computer to start — but you'll want one soon. Here's the full setup.

🖥️ Get Your Own Machine

Tap to explore

The phone app is powerful on its own, but the desktop unlocks the next level — Cowork, scheduled tasks, computer use, local file access, and Claude Code. For that you need a personal Windows machine (not your work laptop).

🎯 Top Pick: Dell XPS 14 (2026) — $2,199

32GB RAM / 1TB SSD / Intel Core Ultra X7 / 2.8K OLED display

The consensus best Windows laptop right now. Premium build, fast processor, gorgeous OLED, 12+ hours battery.

32GB RAM — Claude Desktop, VS Code, terminal, 15 browser tabs, Python scripts — all at once.

1TB SSD — plenty for projects, data, and repos.

3× Thunderbolt 4 — plug into your monitor, future-proof for docks.

2.8K OLED — dashboards and code look incredible.

12+ hour battery — couch, coffee shop, flight.

Also Great: Lenovo ThinkPad X1 Carbon — ~$1,800

Best keyboard in the industry (CPAs who type all day love ThinkPads), 32GB RAM, HDMI built in, legendary durability.

Monitor setup & accessories

Monitor:

You already have one — the XPS 14 connects via USB-C/Thunderbolt or a USB-C to HDMI adapter (~$15). The ThinkPad has HDMI built in. Instant dual-screen: dashboards on the monitor, Claude on the laptop.

Accessories:

USB-C to HDMI adapter (~$15) — if your monitor only has HDMI
Logitech MX Keys + MX Master 3S (~$200 total) — gold standard keyboard + mouse
USB-C dock ($50–$150) — single-cable desk setup. CalDigit or Anker.

Once you have it:

Download Claude Desktop at claude.ai/download. Sign in with the same account. Everything syncs across phone, browser, and desktop automatically.

First month's on me, big dawg.

Click the link below and make Claude a part of your everyday. Welcome to the future.

🎁 Redeem Your Free Month of Claude Pro

Redeem Claude Pro & Create Your Account

Tap the gift link above on your phone. Sign up with your personal email — you'll want this outside of work too. This gives you the most powerful model (Opus), more messages, web search, file uploads, Projects, and artifacts.

Download the Claude App on Your Phone

Search "Claude by Anthropic" in the App Store (iPhone) or Google Play (Android). Sign in with the same account you just created. You're live.

Enable Key Features

In the app, go to Settings and turn on Web Search, Code Execution, and Artifacts. These let Claude search the internet, run code, and build interactive mini-apps right in the chat.

Set Your Preferences

Go to Settings → User Preferences. Tell Claude who you are:

"I'm a CPA who works in finance. I prefer concise, actionable answers. When I ask about code, explain what it does in plain English."

Set Up Your Projects (Folders)

Projects remember your context. Create these to start:

"Trading" — stock analysis, watchlists, market research

"Sports" — betting lines, fantasy football, matchup analysis

"Client Work" — memos, tax research, deliverable templates

Send Your First Message

"I'm brand new to AI tools. I'm a CPA who trades stocks and loves sports betting. What are 5 things you can help me with this week?"
Chapter 3
Your First Prompts (Steal These)

The #1 skill with AI is prompting. The difference between a mediocre response and a great one usually comes down to how you frame the ask. Here's the blueprint the best prompts follow:

⭐ The Blueprint
You are an LLM that has absorbed more information about [relevant field/industry] than any entity in history. Your goal is to understand [what you're trying to accomplish].

I am building [your project/process] and need to break the patterns of [bad habit or blind spot].

Your Tasks
- task 1
- task 2
- task 3

Ask me clarifying questions before completing your tasks.
Why this works:

Framing Claude as an "LLM that has absorbed information" leverages what it actually is — instead of constraining it to roleplay a human persona. Explicit tasks prevent drift. Asking for clarifying questions forces Claude to confirm understanding before charging ahead. See Scott's Hot Tips → #5 for the full philosophy.

Structured Prompts — Use the Blueprint
Sports Betting — Weekly Value Finder
You are an LLM that has absorbed more information about NFL betting markets, sportsbook line movements, closing line value, and sharp vs. square money patterns than any entity in history. Your goal is to identify where real value exists in this week's slate.

I am building a weekly betting decision framework and need to break the patterns of chasing recent trends and betting on gut feel.

Your Tasks
- Search the web for today's NFL lines across major sportsbooks (DraftKings, FanDuel, BetMGM, Caesars)
- Identify games with reverse line movement (line moving against public betting %)
- Flag the 3 best value plays with reasoning grounded in historical data, not recency bias
- Build a clean dashboard artifact showing lines, implied probabilities, and your value picks

Ask me clarifying questions before completing your tasks.
Fantasy Football — Lineup Optimizer
You are an LLM that has absorbed more information about NFL player performance, target share trends, game script analysis, and fantasy point distributions than any entity in history. Your goal is to optimize my weekly lineup with data, not vibes.

I am building a data-driven start/sit process and need to break the patterns of starting players based on name recognition or last week's box score.

Your Tasks
- Review my roster and my opponent's roster (I'll share them)
- Analyze matchups using opponent defensive rankings, pace of play, and recent target/touch trends
- Identify "trap" players I'm tempted to start but shouldn't (and sleepers I'm overlooking)
- Give me a recommended starting lineup with a confidence score for each decision

Ask me clarifying questions before completing your tasks.
Stock Trading — Behavior Audit
You are an LLM that has absorbed more information about equity market structure, technical analysis, earnings reaction patterns, and behavioral finance biases than any entity in history. Your goal is to understand my trading patterns and identify blind spots I can't see myself.

I am building a disciplined trading review process and need to break the patterns of confirmation bias and anchoring to my cost basis.

Your Tasks
- Review the CSV of my trades from the last 6 months (I'm uploading it)
- Calculate my realized P&L, win rate, and performance by sector
- Identify patterns between my holding period and returns
- Flag trades where my behavior contradicted my stated thesis
- Suggest rule changes grounded in risk management, not recent performance

Ask me clarifying questions before completing your tasks.
Client Memo — 1031 Exchange Analysis
You are an LLM that has absorbed more information about US tax code, 1031 exchanges, rental property depreciation recapture, and professional client communication than any entity in history. Your goal is to help me draft a memo that's accurate, clear, and protects my client's interests.

I am building a repeatable memo template for real estate tax consultations and need to break the pattern of burying recommendations in jargon.

Your Tasks
- Draft a memo using these details: purchase $450K in 2018, current value ~$680K, ~$95K depreciation claimed, considering a 1031 exchange
- Compare straight sale vs. 1031 with estimated tax liability for each
- Recommend next steps in plain English
- Keep it under 2 pages

Ask me clarifying questions before completing your tasks.
Quick Prompts — For Casual Everyday Use

Not every prompt needs the full blueprint. For smaller asks, just be specific and give context:

Quick: Portfolio Snapshot
I'm uploading a CSV of my stock trades from the last 6 months. Give me my total realized P&L, win rate, best and worst sectors, and a chart of cumulative returns over time. Flag any patterns you notice.
Quick: Draft Rankings
Search the web for the latest 2026 NFL consensus rankings (PPR format). Create an interactive artifact showing the top 50 players by ADP, color-coded by position, with a column for value picks. Let me filter and sort.
Quick: Today's MLB Lines
Search the web for today's MLB betting lines from major sportsbooks. Build a clean dashboard showing each game's moneyline, spread, and over/under, with implied probabilities. Highlight any lines that differ significantly between books.
Prompting pattern:

For serious work, use the blueprint above — it leverages what Claude actually is (an LLM) and forces clarity before execution. For quick asks, just be specific about what you want and what format. And always iterate: "that's close, but change X" beats starting over.

Chapter 4
Fun Projects to Build

Real things you can build inside Claude Desktop — most in a single conversation.

Scott's Hot Tips
Power User Playbook

Hard-won lessons from real daily use. Internalize these and you'll get 10x more out of Claude from day one.

Chapter 5
The Next Level: IDEs, Code & GitHub

Once you've built a few things in Claude Desktop, you'll want a proper workspace. Don't memorize this — just know it exists.

What's an IDE?

IDE = Integrated Development Environment. It's like Microsoft Word, but for code. The AI does most of the writing — you're the project manager telling it what to build.

VS Code

Microsoft's free code editor. Industry standard. Pair with GitHub Copilot or Claude extensions for AI-assisted coding.

Cursor

VS Code rebuilt with AI at the core. Claude built right in. Highlight code, describe what to change. Easiest path from "I don't code" to "I'm building things."

Claude Code

Claude in your terminal. Describe what you want and it writes files, runs commands, tests code — like pair-programming with a developer.

  What's GitHub?

Tap to expand

Think of GitHub as Google Drive for code. Stores project files in the cloud, tracks every change, lets you collaborate.

Repository

A project folder. Each site/app gets its own "repo."

Commit

A saved checkpoint with a note about what changed.

Push

Upload your changes to GitHub.

Branch

An experimental copy without breaking the main project.

  Code Languages Cheat Sheet

Tap to expand

You don't need to learn these — Claude writes the code. But knowing what they are helps:

LanguageWhat It DoesYou'll See It When...
HTMLSkeleton of web pages — structure and contentBuilding your consulting landing page
CSSStyling — colors, fonts, layout, animationsMaking your site look good
JavaScriptLogic — buttons, data updates, interactivityDashboards, calculators, interactive tools
PythonSwiss Army knife — data analysis, automation, APIsAnalyzing CSVs, pulling stock data
ReactJavaScript framework for building interactive UIsComplex dashboards and web apps

📁 Folder Structure 101

Tap to expand
Project Filesmy-consulting-site/
├── index.html     ← Your main webpage
├── style.css      ← How it looks
├── script.js      ← How it behaves
├── images/        ← Your photos & logos
│   ├── headshot.jpg
│   └── logo.png
└── README.md     ← Project description
Don't panic.

You don't need to learn to code. Claude writes the code. Your job is to describe what you want, review what it builds, and ask it to fix things. You're the architect — Claude is the construction crew.

Chapter 6
Advanced: APIs, MCPs, Webhooks & GitHub Repos

This is where Claude goes from "helpful chatbot" to "automated system that works while you sleep." Don't let the jargon scare you — the concepts are simpler than they sound, and Claude does the hard part.

🔌 What's an API?

Tap to explore

API = Application Programming Interface. It's a way for two apps to talk to each other. When you check a stock price in your brokerage app, that app is calling an API behind the scenes to get the latest price from a data provider. APIs are the plumbing of the internet.

Think of it like this:

You're at a restaurant. You (the app) don't go into the kitchen yourself. You give your order to the waiter (the API), who brings back exactly what you asked for from the kitchen (the data source). APIs work the same way — you send a request, you get data back.

APIs That Matter for You

How to get an API key:

Most APIs require a free "API key" — it's like a password that identifies you. You sign up on their website, they give you a key (a long string of letters and numbers), and you paste it into your script. Claude will walk you through the entire process. Most have free tiers that are more than enough for personal use.

🔗 What's an MCP?

Tap to explore

MCP = Model Context Protocol. This is a newer concept and it's a game-changer. MCPs let Claude directly connect to external services — your Google Calendar, Gmail, Slack, databases, APIs — so Claude can read and act on real data without you copy-pasting anything.

API vs MCP — What's the Difference?

ConceptHow It WorksExample
APIYou (or a script Claude writes) call an external service and get data back. Runs outside of Claude.A Python script pulls betting lines every morning and saves a CSV.
MCPClaude connects directly to a service and can read/write to it mid-conversation. Runs inside Claude.You say "check my Google Calendar for this week" and Claude reads it live, right in the chat.

MCPs You Can Set Up in Claude Desktop

These are already available or easy to configure. Claude Desktop supports MCP servers — you enable them in Settings or via a config file.

Google Calendar

Claude reads your schedule, creates events, checks conflicts. "What's my week look like?" just works.

Gmail

Claude searches your inbox, drafts replies, summarizes threads. "Find the email from my client about Q3 taxes."

Google Drive

Claude reads your docs and spreadsheets directly. Upload nothing — just tell it which file to look at.

Slack

Claude reads channels, summarizes conversations, drafts messages. Great for catching up after PTO.

The vision:

Imagine saying: "Check my Google Calendar for this week, pull the latest NFL lines from The Odds API, cross-reference with my fantasy roster in Sleeper, and give me a game plan for Sunday — then draft a reminder email to my fantasy league group chat." MCPs + APIs make this a single conversation.

🔔 What's a Webhook?

Tap to explore

If an API is "you asking for data," a webhook is "data coming to you automatically." It's a notification system — when something happens (a stock hits a price, a line moves, a new email arrives), the service sends a message to your app instantly.

Real Examples for You

Betting lines move: A webhook fires when a line shifts by more than 1.5 points → triggers a script that sends you a text alert with the new odds.

Stock hits target price: Your Alpaca webhook detects NVDA crossing $180 → sends you a Slack message with your pre-written trade thesis so you can decide fast.

Client email arrives: Gmail webhook detects an email from a specific client → triggers a Claude workflow that drafts a response and adds a follow-up to your calendar.

How They Connect Together

The Stack ┌─────────────────────────────────────────────────────┐
  TRIGGER    Line moves, stock alert, new email, cron job 
             (webhook or scheduled script)              
                                                
  FETCH DATA  Call APIs (odds, prices, calendar, email)   
                                                
  PROCESS    Claude or a script analyzes the data       
                                                
  ACT        Send alert, update dashboard, draft email  
└─────────────────────────────────────────────────────┘

📦 Building Off Others' Work: GitHub Repos

Tap to explore

Here's a secret: you don't have to build everything from scratch. GitHub has millions of open-source projects that you can download, customize, and make your own. Someone has already built a sports betting tracker, a stock screener, a fantasy football analyzer — you just find it, clone it, and tell Claude to modify it for your needs.

How to Clone a Repo (Step by Step)

Find a Repo

Go to github.com and search for what you want — "sports betting odds tracker", "stock portfolio dashboard python", "fantasy football analyzer." Star it if you like it (like bookmarking).

Clone It to Your Computer

Click the green "Code" button → copy the URL. Open your terminal and type:
git clone https://github.com/username/repo-name.git
This downloads the entire project to your computer.

Open It in Your IDE

Open VS Code or Cursor → File → Open Folder → select the cloned folder. You now have the full project with all its files.

Ask Claude to Explain It

Point Claude Code at the folder or paste key files into Claude Desktop:
"Explain what this project does, how the files are organized, and how I can customize it for my needs."

Customize It

Tell Claude what to change: "Swap this API for The Odds API", "Add a column for implied probability", "Change the UI to dark mode", "Make it send me a text when a line moves." Claude modifies the code, you test it.

Repos Worth Bookmarking

Pro tip: README first.

Every good repo has a README.md file — it's the instruction manual. Read it (or paste it into Claude and ask for a summary). It tells you what the project does, how to install it, and what API keys you need. If a repo has no README or hasn't been updated in 2+ years, skip it and find a better one.

Putting It All Together: Your Automation Stack

Tap to explore

Here's what a fully automated week could look like once you've built up to it. You don't need to do all of this — pick one and grow from there.

Morning (Automated Daily Brief)

6:30 AM — A scheduled Python script runs:

→ Calls Alpha Vantage API for your watchlist pre-market data

→ Calls The Odds API for today's betting lines

→ Checks your Google Calendar via MCP for meeting conflicts

→ Formats everything into a clean daily brief and emails it to you

You wake up, check your phone, and have a personalized market + sports + calendar briefing waiting.

During the Day (Real-Time Alerts)

Webhooks running in the background:

→ Line movement alert: a betting line shifts 2+ points → text notification

→ Stock watchlist: NVDA drops below your buy target → Slack alert with your trade thesis

→ Client email: key client sends a message → auto-draft a response for your review

Sunday (Game Day Workflow)

One Claude conversation:

→ Pull your Sleeper fantasy roster + opponent via API

→ Cross-reference with latest injury reports (web search)

→ Pull consensus projections and betting lines

→ Generate start/sit recommendations with confidence levels

→ Output a shareable game card you can send to your league group chat

Getting there:

You won't build all of this in week one. Start by asking Claude to write a single API script — like pulling today's odds. Run it. See the data. Then add the next piece. Each step builds on the last. Within a month, you'll have a system that saves you hours every week.

What to ask Claude right now:

"I want to build an automated daily briefing that pulls NFL betting lines and my stock watchlist every morning. Walk me through the full setup — what APIs to sign up for, what tools I need installed, and write me the first script."

Chapter 7
Daily Workflows & Ideas to Steal

Real workflows you can set up today. Start with one or two and build from there.

Morning Market Brief

Every morning, open Claude and ask:

"Search the web and give me a morning brief: S&P futures, top pre-market movers, macro events today, VIX level."

Email Drafting

Paste any email you need to reply to and tell Claude the tone and key points. It drafts the response in seconds.

Expense Categorization

Upload a CSV, have Claude categorize by tax category, flag items over a threshold, and total by category.

Sunday Game Prep

Pull the week's fantasy projections, compare your roster vs opponent, flag injury updates, suggest lineup moves.

Meeting Prep Briefs

Give Claude the meeting context and get a one-page prep doc with talking points and next steps.

Weekly Review

Every Friday: "Help me review my week. Ask what went well, what didn't, priorities for next week."

Research Anything

Search the web, summarize articles, compare products, explain tax law changes, research competitors.

Quick Data Viz

Upload any spreadsheet and ask for charts: "Show me revenue by quarter" or "Plot my win/loss record."

Pro tip: Use Projects

Claude has a "Projects" feature where you save instructions and files that persist across conversations. Create a project called "Trading" — Claude remembers your context every time.

Week 1
Your Week 1 Checklist

Do these in order. By next weekend, you'll wonder how you lived without this. Tap to check off each item.

Progress0 of 10 complete
Remember:

There's no wrong way to use this. If something doesn't work, tell Claude "that's not what I wanted" and describe the change. The best prompt is the one you actually send.