Peter Browning · Field Note 02 1 / 13
From daily practice, not theory

Working With AI:
A Beginner's Field Guide

How to actually get started — the providers, the models, the tools, and what to do first. I use this stuff every day to ship real things. This is what I'd tell you over coffee.

Navigate with , the arrows below, or the dots. Every page is linkable.

Before we start

Who this is for

Unless you've been living under a rock, you already know roughly what AI and large language models are. We're skipping that. This guide is about getting started: maybe you're a product owner who wants to learn to vibe code, or you're just curious whether AI can take a few routine chores off your plate. Providers, models, tools, first steps — covered.

Fair warning: this is my experience, not a certification. I'm not a pro — I'm a product guy who started using AI daily and ended up shipping real software with it. I'm writing down what I learned because the answer to "where do I start?" shouldn't take months to find. It took me months.
What's ahead

The map

Eleven short topics, ending with a real worked example. Four of them open doors to deeper dives — published separately as this series grows.

  • 01 What can you even do with AI?
  • 02 What I've personally used it for
  • 03 Providers & their apps
  • 04 Models come in tiers
  • 05 Tokens are the gasoline
  • 06 What it costs to play
  • 07 The app, or the toolbox (IDE)
  • 08 What you need to start
  • 09 Context is the whole game deep dive
  • 10 The operator matters more deep dive ×2
  • 11 Vibe coding — with a real example deep dive
The obvious first question

"What can I even do with AI?"

Build your own app or website

From a simple page to genuinely complex software — without waiting on anyone.

Create agents with skills

Teach AI your rules and let it run specific, complex tasks on its own.

Analysis and decks

Detailed analysis, drafted documents, and presentation decks with precision.

Automate the routine

The small recurring stuff you do every week is exactly what it eats first.

The possibilities really are endless. All you need is an idea and some curiosity, and you can get good at this faster than you'd expect.

Receipts

What I've personally used it for

At work

  • Working, near-production-grade prototypes in days — instead of waiting months for engineering capacity just to get real user feedback
  • Live experiments on complex use cases in user-facing apps
  • Automated software release notes straight from Jira tickets
  • An agent that writes Jira stories off a prototype
  • An estimator agent that sizes new work against similar completed work
  • Interactive presentations and training guides you can attach to an email
  • Reverse-engineering legacy logic and calculations — saving real development time

At home

  • Built FlowIt, a personal product-ops app that keeps me focused on what actually matters
  • Built and shipped Exile Forge, a live game-economy advisor with real market data
  • This guide you're reading — built with the same AI it teaches

None of that required me to be an engineer. And honestly? It's easy to get started. That's the part people don't believe until they try.

The players

Two core providers, plus a chasing pack

Anthropic
app: Claude

One of the two core players. Their models power everything I've built this year.

OpenAI
app: ChatGPT

The other core player, and the household name most people meet first.

+ THE FIELD

The second bucket

Google Gemini xAI Grok

Capable and improving fast — just not where I'd point a beginner today.

The competition from China is real, too: Moonshot's open-weights Kimi K3 debuted at #3 on the leaderboards this summer, right behind the two US frontier models. Worth knowing; not where you start.

Both camps have fans who will lobby you hard. Both are highly capable, with their own pros and cons. My recommendation: just pick one. If you get into it, try the other. Maybe you keep both, maybe one wins you over. Either way they update constantly, so a little curiosity about what's new goes a long way. This guide focuses on these two.

Not all models are equal

Models come in tiers

Every provider ships a lineup, and it helps to know the shape of it. Oversimplifying on purpose: there's a frontier model (the premier brain), a mid-tier, and efficient models for everyday work. Different tools for different jobs — the smaller ones are still highly capable.

TierAnthropicOpenAI
Frontier Fable 5Mythos 5 is its restricted-access sibling — same underlying model, available only to approved organizations GPT-5.6 Sol
Mid-tierOpusGPT-5.6 Terra
Everyday / fastSonnet · HaikuGPT-5.6 Luna

Accurate as of August 2026. The names on this table will age; the tier idea won't.

Why the tiers matter

Tokens are the gasoline

Think of it like gas in a car: more horsepower usually burns more fuel. Same deal with AI. Bigger models need more compute, which means more energy, which means more cost. The unit you're burning is called a token, and you spend them every time you use AI. Frontier models chew through your plan's limits much faster than the everyday ones.

Everyday model
Sips tokens. Great daily driver.
Mid-tier
More muscle, moderate burn.
Frontier
The V8. Save it for hard problems.

Knowing how much horsepower the job actually needs is how you get things done efficiently. That's genuinely all you need to know for now — the rest comes with use.

The money question

What it costs to play

Both providers run subscriptions. There's a free tier, but if you want to do anything meaningful, the real starting line is the $20/month plan. Plans scale up to around $200 for max tiers — that's for heavy, daily users. For 90% of people, $20 is all you need.

Claude (Anthropic)
ProStart here — the everyday plan$20/mo
MaxHeavy, daily users only$100–200/mo
ChatGPT (OpenAI)
PlusStart here — the everyday plan$20/mo
ProHeavy, daily users only$200/mo

Prices verified August 2026 — both providers also have free tiers worth trying first. Check their current pricing pages before subscribing.

Twenty bucks for a tireless assistant that can code, analyze, and draft. I've spent more on worse.

Two ways in

The app, or the toolbox

The chat apps — Claude and ChatGPT — are one way in, and where most people should start. But here's where it gets a little techy. Developers live in something called an IDE — an integrated development environment. If you passed a pickup truck with a toolbox on the back, you'd guess there's a hammer, a drill, and a level inside. An IDE is that toolbox for building software: one app that gathers the tools, including direct connections to AI models from every provider. The most common one is VS Code.

A faithful mock-up, not a marketing shot: your files on the left, your code in the middle, and the AI working alongside — all in one app.

Native apps (Claude, ChatGPT)
  • Easiest possible start — sign up and go
  • Chat, coding, and cowork features in one place
  • Most polished experience
  • Less control over how things connect
IDE route (e.g. VS Code + models)
  • Often the sanctioned path inside big companies where native apps are blocked
  • Pick and switch models from any provider
  • Grows with you as projects get serious
  • More setup, steeper learning curve

Learning from home? Start with the native app. Sitting inside a Fortune 500 with security restrictions? The IDE route may be your only option. Learning both paths pays off over time.

The whole barrier to entry

What you need to start

  1. A computerAny modern desktop or laptop with decent RAM and an SSD. Nothing high-end — the models do their work in the cloud, not on your machine.
  2. A $20 subscriptionClaude or ChatGPT. Flip a coin if you have to; you can switch later.
  3. The appThe provider's own app to start. An IDE later, if and when you get techy.
  4. An ideaThe only genuinely required hardware. A real, small annoyance in your week works better than a grand vision.
The skill itself

Context is the whole game

Feed the model a lazy prompt and it will do its best to guess what you meant. People are surprised by how good the guessing is. They're a lot more surprised when the guessing stops — and that's what context does. Think of context as an arrow: you want it pointed straight at the target. The more relevant context you give, the more accurate the shot.

Asking cold
Youmake my resume better
AITen generic resume tips that apply to every human alive. Polite, fluent, useless.
The model isn't bad — it's guessing, because you made it guess.
Pointing the arrow
YouHere's my resume [pasted] and the job posting [pasted]. 12 years in product. Rewrite my summary and top 3 bullets to match what this role asks for. Keep only numbers I can defend. Cut every buzzword.
AIA focused rewrite in your own vocabulary, mapped to that posting's actual requirements.
Same model. The context did the work — and fewer do-overs means fewer tokens, which means it's cheaper too.
One warning: you can overdo it. Dumping everything you've ever written on the model muddies the aim. Enough context to point the arrow — not the whole quiver.
The part nobody tells beginners

The operator matters more than the model

The models are great. The person operating them matters more. Two people with the same $20 subscription get wildly different results, and the gap is operator skill: knowing what to hand the model, when to trust the output, and when to check it. That skill compounds — and it goes further than prompts. Eventually you can teach the AI your rules and your domain: standing instructions called skills, and agents that run whole jobs with them. That's how the model goes from guessing at your world to working in it.

Deep dive · next in this series

Agents & Skills

Teaching AI your rules, then letting it run whole jobs — with real examples from my own setup.

Coming next →
Deep dive · in progress

The Operator Ladder

The levels of working with AI, from prompt-and-wait to running a fleet — and how to climb.

Coming soon →
The term you keep hearing

Vibe coding — what is it?

Vibe coding is using natural language — plain English — to get AI to produce software, analysis, or some other finished output. No syntax, no programming background. You describe what you want; the AI builds it; you react and refine. You can vibe code an app, a slide deck, a dashboard, or an agent that reads your email once a day and sends you a recap.

Everything you've read in this guide feeds it: pick the right model tier for the job, hand over real context, and iterate like an operator. Vibe coding is just those habits pointed at building something.

So now that you know what it is — let's put all of this into practice, for real, on the next page.

Put it all to practice

A real vibe-coded example, start to finish

Step 1 — the ask (one well-aimed prompt)
YouHere's a spreadsheet of my last 12 months of spending [attached: sample-spend.csv]. Analyze the spend patterns — totals by category, month-to-month trends, anything unusual. Then build a one-page dashboard with the top metrics, two simple charts, and 3–4 insights written in plain English. Keep it readable on my phone.
Notice what's in there: the data itself, the specific analysis wanted, the exact deliverable, and a constraint. The arrow is pointed.

Step 2 — the AI works. It reads the file, computes totals and trends, finds the stories in the numbers, and writes a working web page. No code from you at any point. A few minutes, start to finish.

Step 3 — the output. This is the actual result, live, built from that exact prompt and spreadsheet — scroll it, hover the charts:

Open the dashboard full size ↗  ·  It found the story on its own: subscriptions quietly crept up 58% in a year. That's vibe coding.

Full disclosure: this is the exact example a peer showed me six months ago — the demo that got me started, the one I wrote about in my first Field Note. If it does for you what it did for me, this guide paid for itself.
That's it. Go.

Start this week

A computer you already own, twenty dollars, an app, and one real idea. Pick a small, genuine annoyance in your week and point the AI at it. You'll learn more in one honest attempt than in a month of reading about it — this guide included.

More in this series as it grows: Agents & Skills, The Operator Ladder, and how I built an AI product that has to show its receipts. All at petebrowning.com — and I'm always up for comparing notes on LinkedIn.