AI consultant for companies & founders

An AI consultant is someone you hire to work out where AI belongs in your business and then put it there. Not a course and not another subscription: a person who looks at how you actually work, decides what should stop being done by hand, and builds the system that does it instead.

In my case, 8 steps in order: install and audit your week, then build the 7 layers of your AI OS. Context, data, tools, memory, skills, automations, apps. Each layer needs the one below it, so the order is the job.

You can do it yourself, and the full method is free. People hire me when they have read it, agree with it, and would rather not spend the next 3 months being the one who builds it.

Yes. I teach the same audit, build and handover I use with my clients in the Certified AI OS Consultant program, an 8-week live cohort that certifies you on a real build.

An agency usually runs the work for you on their stack. I build the system inside your business and hand it over, so what you end up with is yours and keeps working after the engagement ends.

A course hands you the knowledge and leaves the building to you. Here the outcome is a system that runs, not a folder of lessons you meant to get to.

A developer builds you software. I build the layer underneath the software you already pay for, so your existing tools start working together instead of being replaced.

No. Usually the audit ends with fewer tools, not more. Most of the work is connecting what you already pay for and writing your business down once.

Because the tools were starting from zero every time you opened them. Once your context, your data and your corrections live in one folder every agent reads, each session is better than the last instead of the same as the first.

Yes, and most of them are. Nothing in the build needs you to write code. It needs you to know your business, which you already do.

Navid Moazzez is a leading AI business strategist, the founder of AI OS Lab, and the host of the AI Creator Summit, watched by 100,000+ creators in 110+ countries. He helps creators and founders master AI and build their own AI Operating System (AI OS) to automate their business and life.

He has spent 12+ years building online businesses and 5+ of them building with AI, before it was a category. His work has been featured in Forbes, Entrepreneur, HuffPost, Inc and Business Insider.

He runs his own business on the same AI OS he builds with you, which is why he can show you the thing working instead of describing it.

I build AI operating systems for a living and I run my own business on one every day. The context, the connectors, the skills and the automations behind this site are the same ones I would set up for you.

I have spent 12+ years building online businesses and 5+ of them building with AI, before anyone called it a category. My work has been featured in Forbes, Entrepreneur, HuffPost, Inc and Business Insider.

I have also replaced most of the software I used to pay for. My CRM, my checkout, my CMS and my email automations are apps I built. So when I help you build your AI OS, I am not learning on your business.

An AI OS is the layer underneath your AI tools. It holds your context, your voice, your offers, your customers and your workflows in one structured place that every AI you use can read. In practice it is a folder of plain text files.

No. ChatGPT is one tool. An AI OS is the folder that tool reads, so the same context works in whichever agent you open tomorrow.

A prompt library is text you paste in. An AI OS is read automatically at the start of every session, before you type a word, and it carries your data and your connectors as well as your words.

A second brain is written for you to read. An AI OS is written for an agent to act on, and it is connected to the tools where the work actually happens.

Because nothing it learned was written anywhere it reads next time. Memory is one of the 7 layers, and it exists exactly so a correction you gave in March still holds in June.

Context knows you. Data holds your business in one place. Tools reach your apps. Memory keeps what it learns. Skills do the work. Automations run without you. Apps show you the answer.

Any of them. The folder is plain files, so Claude Code, Codex, Cursor and Gemini CLI all read the same rules. That is the point of building it as a folder rather than inside one product. How it connects to each agent.

You own it. It is a folder of plain files plus connectors to your own accounts. There is nothing of mine you have to stay subscribed to.

On your machine and in your own accounts, with a private repo as your backup if you want one. We connect to your tools rather than copying your business somewhere new.

AI OS Lab is where the whole method lives, free. Every layer, every step and the prompts, written up in full at AI OS Lab.

It is not a lead magnet with the good part removed. It is the same system I build in a paid engagement, documented well enough that you can build it yourself if you have the time.

The AI OS Starter Kit is the folder itself, open source and free. One command installs it, and you open it in whichever agent you already use.

It arrives with the 12 skills, the context files, the rules file and a brand-guardian agent that checks drafts against your voice. `/onboard` fills in your context in about 15 minutes. Get it at AI OS Lab.

With the audit. A 60 minute call where I go through your setup live and you leave with a roadmap. If you then want me to build it, the audit has already told us both what the build is.

Day one gets you a session that already knows who you are and how you write. Week one gets you a morning brief. A full system that runs without you takes 2 to 3 months, depending on how much of your stack needs connecting.

Both, and you pick which. The audit is advice you go and build yourself. Consulting is me in the work with you every week. The buildout is me building it hands on and handing it over running. Every format, with prices.

Time on the calls, access to the tools you want connected, and honest answers about how you actually work. Not a brief, and not a tidy version of your business.

No. We connect what you already use. Switching tools is a separate project and it is usually the wrong one to run at the same time.

Then I say so on the audit call. If the work does not repeat, or the business is not running yet, an AI OS is the wrong thing to build and there is no version of this I would sell you.

Each layer has one number. Times you had to re-explain something it should know, heading to 0. Repeat tasks now running from one skill, going up. Work done while you were away, going up every week.

There are 4 levels, listed above with their current prices. The audit is a single call, consulting runs 3 months minimum, and the buildout and the enterprise rollout are one-time engagements. Those are the same prices the checkout charges.

If you want it done fast and done right, start with the audit. If your business is bigger than one person, the buildout or the enterprise rollout is the one. If you are not sure, send me what your week looks like and I will tell you. You can also book any of them directly at navid.consulting.

Yes, and most people do. The audit stands on its own, and what you learn in it carries into the build if you decide to go further.

Yes. The full method is free, and so is the AI OS Starter Kit. Paying me buys speed and the fact that someone else does the building, not access to the method.

The audit is the try-before-you-commit step on purpose: one call, a fixed price, and you keep the roadmap whatever you decide next.

Founders and creators running their own business, teams inside growing companies, and enterprises rolling it out across departments. The common thread is not size. It is that the work repeats and it is still waiting on one person to sit down and do it.

For a company, that often starts as training rather than consulting. Workshops and AI‑native training for your team are on the AI training page.

Both. Most of the work runs over video, which is how the weekly sessions go and what most clients prefer, and I have lived in 16 countries and worked across time zones the whole time, so a scheduling gap is normal rather than a problem. In person is available too, anywhere, and it suits a buildout or a company rollout where a few days in the same room moves faster than a month of calls.

Yes, and for anything beyond one person it should be. The enterprise rollout exists for that: the same system across a company, with the access, the review and the training so your team can run it.

You keep everything, because it was built in your folder and your accounts from day 1. You also get the build order for what to add next, so it keeps growing without me.

Yes. Send me what your week looks like and what you are stuck on. I will tell you which of the 4 fits, or that none of them do.

Travel and accommodation sit on top of the engagement, at cost, and we agree them before anything is booked. Nothing gets added after the fact. If the numbers do not make sense for the size of the engagement, I will say so and we run it over video instead.

Yes, and for a company that is often the right first step. A workshop gets a whole team to the same place at once, where consulting puts one system in one business.

It runs in person or virtually. The formats and what each one covers are on the AI training page.