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.
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.
Eleven short topics, ending with a real worked example. Four of them open doors to deeper dives — published separately as this series grows.
From a simple page to genuinely complex software — without waiting on anyone.
Teach AI your rules and let it run specific, complex tasks on its own.
Detailed analysis, drafted documents, and presentation decks with precision.
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.
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.
One of the two core players. Their models power everything I've built this year.
The other core player, and the household name most people meet first.
Capable and improving fast — just not where I'd point a beginner today.
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.
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.
| Tier | Anthropic | OpenAI |
|---|---|---|
| Frontier | Fable 5Mythos 5 is its restricted-access sibling — same underlying model, available only to approved organizations | GPT-5.6 Sol |
| Mid-tier | Opus | GPT-5.6 Terra |
| Everyday / fast | Sonnet · Haiku | GPT-5.6 Luna |
Accurate as of August 2026. The names on this table will age; the tier idea won't.
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.
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.
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.
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.
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.
1// settings page — dark mode
2const toggle = document.querySelector('#dark-toggle');
3toggle.addEventListener('change', () => {
4 document.body.classList.toggle('dark');
5 localStorage.setItem('theme',
6 toggle.checked ? 'dark' : 'light');
7});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.
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.
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.
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.
Teaching AI your rules, then letting it run whole jobs — with real examples from my own setup.
Coming next →The levels of working with AI, from prompt-and-wait to running a fleet — and how to climb.
Coming soon →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.
So now that you know what it is — let's put all of this into practice, for real, on the next page.
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.
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.