You don't need an AI class. You need am AI installed on the machines you actually work on.
Most businesses aren’t behind on AI because they lack tools. They’re behind because nobody has sat down with them and wired it into the work they already do — the quoting, the reporting, the follow-up, the admin.
We do that in the room, on your laptops, on your real work. You leave with it running.
La Jolla · 1–8 people · Your machines, not ours
We build practical AI workflows for reporting, quoting, follow-up, CRM, POS data, lead research, internal documentation, and client communication. The goal is not to impress you with tools. The goal is to make repeated work easier to run, review, and improve.
What's in your hands on Friday
Not notes. Not a prompt library you’ll forget. Working software, configured for your business, on your own machine.
Claude, installed and configured
Set up on your machine with your business context loaded — not a demo account, yours.
Your root instruction file
The one page that makes every future answer sound like your business instead of a generic one.
Your first Projects
Set up around work you actually do, not example data.
One workflow, running
Built live, on a real task, working before you pack up.
A written recap
What we built, why, and what it’s for.
Your prompts and practices guide
Ready the next morning.
A one-page AI stack summary
What you have and what to reach for first.
Your Morning Dashboard, packaged as a skill
You install it yourself. That’s on purpose — it’s the last rep of the training.
What actually happens in the room
Every session runs the same three phases. The first is identical for everyone. The second is only yours.
The install
Same order, every client, no improvisation: email, calendar, drive, the document tools, then the one system you actually run your business on. You watch where each piece lives, so you can do it again without us in the room.
The architecture
We map your real stack on the wall, then build your root instruction file together — who you are, who you serve, what you never do, what “good” means here. About thirty minutes, and usually the most useful half hour of the day. Teams routinely discover they’d each describe their own business differently. That gap is worth finding.
The clinic
Open floor. What broke, what’s confusing, what doesn’t fit. We fix live what can be fixed. What can’t gets written down in front of you as a ranked list with the business reason attached — and you get that list in writing whether or not you ever hire us to build any of it.
What a workshop unlocks
Three engagements, and what changed as a result.
Coastal Color Works
A commercial painter was writing every proposal by hand. Three to four hours per job. In one workshop, we helped structure Claude around his real bidding process. Two weeks later, he had connected Claude to his own proposal builder — something we did not even scope for him. Same proposal logic, now done in minutes. He also referred two other business owners after using it.
2 Businesses, 1 Voice
Charles had two businesses: an established contracting company and a coaching brand he was building from the ground up. One Claude account was producing generic output for both. We rebuilt the setup around his actual voice, principles, and business context, so each brand could sound distinct without starting from zero every time.
From Dabbling to a Real System
A consultant had used ChatGPT and Claude before, but every session still felt like starting over. The issue was structure. He was treating Claude like memory, when Claude works better as the processor. We helped him set up Notion as the memory layer and Claude as the thinking layer. Now he has a repeatable way to research, qualify, and organize leads.
Who runs the room
I’m Oz Riveros. I run every one of these myself.
I facilitate the way I’d run a table, not a lecture: your business is the world, your team are the players, and I set the scenes and ask the questions. It’s more fun than it sounds, and it gets far more honesty out of a room than a slide deck does.
AI drafts and sorts. A human approves and sends. Nothing goes to a client, a donor, or a bank without your eyes on it.
That’s the line I say out loud in every session, so you may as well hear it now. If someone is telling you otherwise, they’re selling you something.
And I’ll tell you when AI isn’t the answer. If your files are chaos or your process is broken, wiring AI into it just gets you a faster mess. Sometimes the honest deliverable is “fix this first” — and I’d rather say that in session one than take your money for three.
In person at the Lead Wolf studio
We do this in person because it depends on live discussion, screen sharing, your real business context, and hands-on setup. It is not a webinar and not a passive online class.
You bring your laptop. We bring the structure. Together we set up your workspace, build your root instruction file, choose one real workflow, and get it running in the room.
Bring: your laptop and your logins
Bring: one task you’d pay someone to never make you do again
Don’t bring: anything under a confidentiality obligation until we’ve talked about it
We start with diagnosis, then build only what the business can actually use.
Diagnose
We map how your business runs day to day: where work starts, where it slows down, who owns it, and what gets repeated.
What you get: the highest-leverage workflow to fix, in plain language, with the business reason attached.
Install
We set it up and build the first workflow live with you: your root instruction file, one project context file, and the first repeatable pattern for a real task.
What you get: a working AI workspace, your first workflow, and the pattern to repeat it.
Build
Scoped and priced before anything starts. Built around your real data and tools, tested before handoff, documented, and delivered with training.
What you get: a documented working system, plus a team that can operate it without us in the room.
Advise
Optional ongoing support once something is running. We tune workflows, surface new uses, improve adoption, and keep the system aligned as the business changes.
What you get: someone who already knows your business, month to month, cancel anytime.
Common questions
Do I need to be technical?
No. If you can use email and a web browser, you’re fine.
What do I bring?
Your laptop, your logins, and one task you’d pay someone to never make you do again. We work on that task.
Whose account is it?
Yours, in your name, on your card. We set it up with you and you own it. We don’t resell software, and there’s nothing to cancel if we stop working together.
Is my client data safe?
We only connect the tools you choose to connect, and we say out loud what should never go near an AI system — anything under a confidentiality obligation, and anything regulated. If you’re in healthcare or education, ask me directly. There are real limits and I’ll tell you what they are rather than guess.
What if my team doesn't stick with it?
That’s the actual risk, and it’s why the format is built this way: everyone builds something for their own job, on their own machine, and leaves with an owner and a date attached. We check in at 30 days.
What happens after?
You get a ranked build list in writing. Some of it you can do yourself, and we’ll tell you which. The rest you can hire us for, or not.
This is not for everyone.
This is not a shortcut for a broken business model.
It is not a generic ChatGPT or Claude class.
It is not a library of prompts you will forget in two weeks.
It is not a software subscription we resell.
This is for businesses with real work, real repetition, and enough operational pain to justify building a better system.