EAS AI Training / One-on-One / Google Meet

Become a web developer. No code skill required.

Two to four hours, one-on-one, your project on the screen. Not a course, not a webinar — a working session over Google Meet where you learn AI by doing the actual work, on your actual stuff. Booked straight off our Google Calendar: pick a slot, the Meet link shows up, we work. AI builds it. An engineer signs off. You keep the money.

This is notA course, a webinar, or a video you watch alone.
This isYou, an engineer, a shared screen, and your real project.
You leave withThe skill — plus whatever we built while you learned it.
How it runs / booking to done

Book it like a haircut. Work it like a job.

Sessions book through our Google Calendar — the same Google Business setup we run the shop on. Pick an open slot, tell us in one line what you're working on, and the Google Meet link arrives with the invite. That's the whole paperwork.

When the call starts, screens get shared — yours or ours. You drive when you can, we drive when you're stuck, and either way you're watching real work get done in real time, with the reasoning out loud. No slides. No syllabus written for somebody else.

Booked on Google CalendarPick a slot from live availability — no back-and-forth email chain.
Meet link in the inviteOne click at session time. Nothing to install.
Beginners welcome, literally"I've never opened ChatGPT" is a valid starting point.
Book → Meet → Work2–4 hrs
01
Pick a timeGoogle Calendar — the invite carries your Meet link
02
Tell us the targetOne line: "my site," "learn GPT," "read this code"
03
Screens shared, work startsYour project on the screen from minute one
04
Done or the clock's outYou leave with the skill and the artifacts

Straight talk: two hours is a skill. Four hours is a transformation. Pick the size that matches the goal — the rate doesn't change.

The bench / twenty-five years in

Our AI is better than your AI. Here's why.

We've been developing for twenty-five years. Back when a prototype took six months — six months of work just to put something in front of somebody and talk about what might work, before anything real ever got built. Now we talk to machines and task ten different things to do ten different things at once. You could never task a team of humans like that. It never worked that way.

But here's where people get confused: the humans still review everything. Nothing leaves this company without at least two sets of human eyes on it — at least twice. We don't offer a service we haven't looked over, and we're not going to rely on something we're still training. Neither should you.

You've had AI since 2022. We've been training ours since 2000. Same tools on the shelf — a different bench behind them. That's what a session actually buys you: the bench.

And it's not a slogan — we're one of the top firms in the country using AI correctly, and we can prove it. OpenAI ranks us in the top 1% of GPT users in the United States, measured on what we build. Public GPT didn't exist until late 2022 — we were in the invited pool that had it years before that. Roughly half a million accounts got that invite; if you weren't one, you know. Want to ask how we had GPT two years before you did? Please do — call us.

Then → Now25 yrs
01
2001: six months for a prototypeHalf a year just to have something worth talking about
02
Now: ten tasks at onceTell ten things to do ten things — the agents run in parallel
03
Still: two sets of human eyesEvery build, every review pass, every session — checked twice before it ships
04
The difference is the benchSame AI everyone can rent — trained by people who were building before it existed

Straight talk: the tools are the same for everyone. Twenty-five years of judgment about what to ask them for is not.

Level 01 · Beginner
ChatGPT / the foundations

GPT for real work — done right the first time.

For the basic GPT user: you have the account, you've asked it things, now let's make it useful. Four solid blocks — design, copyright, your website, and clean HTML — taught on your own material, not canned examples.

And here's the part most people won't tell you: we stop at HTML5 with ChatGPT. Past that line it writes code that looks right and runs wrong, and that's how people get in trouble — a half-built thing nobody can fix. When you hit that wall, you're ready for Level Two.

Design with GPTLayouts, palettes, mockup language — what it drafts well, where it lies, how to push back on a bad draft.
Copyright, straightWhat you can use, what you can sell, what's actually yours when the AI drew it. The rules, not internet folklore.
Website tune-upTitles, descriptions, the words Google reads — the quiet stuff that's costing you visitors right now.
HTML5 tune-upClean markup, tags that mean what they say — and the honest ceiling on where ChatGPT's code stops being safe.
Beginner track~2 hrs
01
DesignBriefs, drafts, taste — you keep the judgment
02
CopyrightUse, ownership, and what gets you a letter
03
Website tune-upWhat Google reads vs. what visitors see
04
HTML5 — and the wallWhere GPT's code stops being trustworthy

Why the wall matters: past HTML5, ChatGPT produces confident, broken code. Learning where the line is saves you the rescue bill later.

Level 02 · Intermediate
Claude & Codex / real code, real structure

Tools that write code — and you, still in charge.

For people past the basics. Claude and Codex don't draft paragraphs — they build software. That means the skill changes: less "ask it a question," more modular code, reading what it wrote, and knowing which language does what.

This is the level where it clicks: what a module is, when you need Java versus SQL versus something else entirely — what they do and what they mean, so "use the right tool" becomes a decision you make, not a slogan you heard.

Modular codeWhat a module is, how files talk to each other, how to read a codebase instead of staring at it.
Which language whenJava, SQL, JavaScript, Python — what each one actually does, and when each is the wrong tool.
Working with a coding agentPrompts that produce whole files, review habits that catch confident mistakes, when to take the keyboard back.
Reading the outputDiffs, errors, tests — telling good output from confident output.
Intermediate track~3 hrs
01
Modules & structureWhat the pieces are and why they're separate
02
The language mapJava vs. SQL vs. JS vs. Python — jobs, not jargon
03
Agent workflowClaude & Codex doing the typing, you doing the steering
04
Review & verifyHow to check what it built before you trust it

Reality check: you don't need to write the code — you need to be able to read it well enough to say no.

Level 03 · Web Developer
The whole desk / zero to shipping

Come in with no code skill. Leave a web developer.

That's the product. Not "exposure to coding," not "a feel for it" — the working ability to take a site from a blank folder to a live page, with AI doing the typing and you doing the thinking, the checking, and the shipping.

The long sessions live here: your real project, start to finish, with an engineer beside you the whole way. Structure, files, deployment, the mistakes that only show up in the wild. People pay bootcamps five figures for a worse version of this — stretched over months, taught on toy apps. This is one afternoon at a time, on the thing you actually want to build.

Blank folder to live pageStructure, markup, styling, getting it on the internet — the whole walk.
Your project is the classroomBring the site you want. We build it while you learn to build it.
The judgment layerWhat to build, what to skip, what to never trust the AI with — the part that makes it a skill, not a trick.
Developer track~4 hrs
01
Scope the buildWhat the site needs, in what order, and why
02
Agent-built structureClaude/Codex produce the files — you direct and review
03
Fix & polishThe debugging loop: read, test, correct, repeat
04
Ship itDeploy to a real URL — it's live before the session ends

Straight talk: one 4-hour session won't make you senior. It will make you dangerous enough to keep going — and that's the whole point.

The honest math / where the money goes

If your engineer is mad, dump him.

You can use ChatGPT and Codex to build a website. You can use them to build an application. That's not hype — we do it every day, and after Level Three so can you. What you won't get without Claude or Devin is sound — the structure that holds when real users lean on it. And yes, a real engineer still takes the last pass. We say that upfront because it's true.

But here's the part that changes the economics: by the time your project reaches that engineer, your cost should be so low the invoice reads like a review fee — not a build. If the engineer you hand it to is angry, understand why: he's mad because he can't milk you anymore. Dump him.

The smart ones — and we like to think we're in that pile — run through what you built and say "you did a great job." Then we help you sell it. We don't have huge egos here. We like to make money — and there's more of it in finishing a hundred smart builds than in pretending AI can't do the first ninety percent.

Mad vs. smartPick a side
✗
The mad oneCalls your work garbage, rebuilds from scratch, invoices like nothing happened — the meter was the product
✓
The smart oneReads what you built, charges for the pass it actually needs — then helps you sell it
$
The tellAnger at AI-assisted work isn't judgment — it's a business model watching its margin walk out the door
→
Our side of the tableFinish it, ship it, sell it — open a case when your build needs the last ten percent

Straight talk: the first ninety percent belongs to you and the AI now. The last ten percent is a fee, not a ransom — from us, or from anyone honest.

Booking / pick your size

Same hour, three sizes.

Flat per-hour rate — $75 an hour, same on every level. The only decision is how deep you want to go today. Level and length both get set when you book — tell us where you're starting and where you want to land.

2 hours
$150 session

One skill, tight. Pick one block off a level and work it end to end — a tune-up, a copyright walk-through, one module explained until it's yours.

3 hours · most picked
$225 session

A level, done right. The natural fit — cover a level's ground with room left over for your project's own questions.

4 hours
$300 session

The deep dive. Level material plus hands-on work on your actual site or codebase. Bring the messy one.

How to book: sessions run through our Google Calendar — pick an open slot and the Meet link arrives with the invite. Prefer to talk first? Call 209-672-0033 or email the desk.

Fine print / what you actually get

You leave with more than notes.

  • ✓Everything we built stays yours. Files, drafts, markup, notes — created on your accounts, saved to your drive.
  • ✓A written recap. What we did, in the order we did it, so you can repeat it without us.
  • ✓The honest ceiling. You'll know exactly where each tool stops being useful — including the HTML5 wall on Level One.
  • ✓A next step that isn't us. The goal is you not needing the session anymore. We'll say when you're there.
Who this is for

Three people book this.

The owner.

You pay for every little website change and you're tired of it. Level One alone pays for itself the first time you don't have to call somebody.

The voluntold.

Your job decided "the AI stuff" is yours now. Come in behind, leave ahead of the assignment.

The career mover.

No code background, real ambition. Level Three is built for you — web developer is a skill, and skills can be installed.

Pick a slot. Bring the project.

Beginner, intermediate, or the full web-developer track — two to four hours, one-on-one, over Google Meet, on whatever you're actually trying to build. Based in Oakdale, California — but it's a video call, so "local" is anywhere with a browser.

Sessions book through our Google Calendar. If you'd rather ask a question first, the phone and the inbox are right there. And when your build is ready for the last ten percent — the finish, the polish, the sale — that's a case, not a session. We'll review it and help you sell it.