Realization of the day: I’m not actually driven by money. I want comfort and to provide for my family, but I don’t care about Ferraris or flexing. What I’m really chasing is status through trust. Being widely known, being respected, having access to other respected people I can directly exchange value and collaborate with.

Every time I say I build client static websites with AI, the same questions show up. What about forms? What about SEO? Can clients edit it? What about dynamic data? So I answered all of them in one video. How I do it, not gospel. Chapters: 0:00 - Static doesn't mean what you think 1:12 - Where these questions come from 1:46 - Marketing website vs static, defined 3:09 - What about a page builder? 4:19 - Do you really feel in control without one? 6:39 - How do you know the code is any good? 8:10 - Isn't static too limited? 9:54 - Bookings, payments, and logins 11:02 - Can you sell products on it? 11:50 - How do you edit it? 13:41 - Can a client edit it themselves? 16:15 - Custom post types, fields, and taxonomies 18:02 - Does filtering and search still work? 19:18 - Don't you need Yoast or Rank Math? 21:17 - Will it actually rank? 22:18 - What about security? 23:27 - What about updates? 25:04 - What about backups? 27:50 - What about caching? 28:35 - What happens if I'm gone? 30:03 - Want help with this?

The Claude or Codex app is fine. Just don't stay in the chat part of it. Hook your AI into something that can reach your files and run commands, like Antigravity or VS Code. If you work technical, that's where you want to be.

I don't ask humans for help on technical stuff anymore. Not because people don't matter. I still talk to mentors. But if you actually want the answer and you want to move fast, it's AI now.

Played with some new website hero tweaks on desktop and mobile Some cool entrance animations too - markszymanski.co

I don't build websites in a page builder anymore. I don't write the code either. It's all orchestration. I say what I want, it builds it, I check the result. But I still have to know what every piece of the stack does, so this is the whole thing, piece by piece, plus a live demo: one prompt, two changes, live a few minutes later. Chapters: 0:00 - How I build marketing websites now 0:35 - What a marketing website actually is 3:03 - What changed: it's all orchestration 4:15 - How I orchestrate the build 5:16 - What it's built with 8:46 - Where the files live 11:18 - Where it's hosted and how it deploys 15:15 - Integrations 15:46 - What happens when someone fills out a form 17:02 - What about a CMS? 19:04 - Demo: two changes, one prompt 22:30 - Don't sit and watch your agent 26:05 - Checking the result 27:55 - Try it yourself with my blueprint 29:07 - Want help with this?

Thanks Chris.

People keep asking how I actually work with all this AI stuff day to day. So I just showed it. One window. A chat per job. I talk, it does the work. I don't click around in my own dashboard, I tell it what happened and it updates everything. And when I walk away from my desk, every chat comes with me on my phone. Same files, same context, nothing to set up. Chapters: 0:00 - How I work with AI every day 0:38 - Where we are: VS Code 1:52 - The AIOS in 30 seconds 2:51 - This isn't chat 3:51 - Where to start (the Claude Code app is fine) 5:11 - Why I still use VS Code: Codex as the backup 7:37 - My computer never turns off 9:10 - Where the information lives 9:46 - One window, many chats 11:22 - I talk, it does 13:15 - Why I don't click around in Mission Control 15:11 - I check, then steer 16:04 - Owning my own analytics data 17:25 - Working from my phone with Remote Control 20:28 - VS Code tip: hide the tabs 21:27 - Agents open as tabs 21:52 - Bypass permissions 22:24 - The extensions I use 24:12 - What runs without me 24:55 - Google Chat as a remote 26:49 - Get the free AIOS skeleton 28:25 - Wrap up

Realization of the day: The volume actually works. 2 weeks of talking about the same thing, the same way, every single day. Today somebody I never reached out to messaged me, said my AI content has been helpful, and asked what I charge to review what he built. Will he book it? No idea. Doesn't even matter. It's inbound. 🥳🥳

I record every call and every meeting, and almost all of it goes back into my AI system as context. You don't have to take notes when the system takes them, so your energy goes into asking better questions.

Building little AI apps for yourself is great right now. But a $100 subscription hides what that compute really costs, and at the real price that app gets a lot harder to justify.

My whole business runs out of two folders on my computer. Here's how it's actually built. Five questions decide where anything goes: is it always true about me, does it live in someone else's system, is it a record that keeps changing, is it a job I keep reusing, or is it something I do over and over. No MCP. Barely any "skills". A SQLite database, Windows Task Scheduler, and a copy on Cloudflare so I can see it from my phone. The catch: my computer has to stay on (for now). Chapters: 0:00 - Six months building my AIOS 0:30 - Before we start 1:57 - Using AI in pieces 3:32 - The context needed one home 4:02 - Model, harness, context 5:24 - The one part that's not a commodity 6:55 - Step one: write your business down 8:55 - Five questions, the whole system 9:39 - Knowledge 10:28 - Connections (APIs, not MCP) 12:14 - Records 13:27 - Tools, and why I don't use skills 15:29 - Procedures 16:38 - Two folders run everything 17:52 - AIOS vs projects 20:51 - Mission Control, the front end 22:35 - Where it actually runs 23:58 - What it costs 25:17 - The catch: my computer stays on 26:27 - What's actually automated 28:12 - The actual lesson 29:44 - Start yours this week 31:02 - Iterate every time 31:49 - Start small 32:10 - Grab the skeleton

Use somebody else's skill or process as inspiration, not as your business. You have your own clients and your own industry, so you have to iterate on it.

The number of web professionals that don't understand what a static website is actually capable of is disconcerting.

Had Claude make a full animated explainer video after I posted this original one. Here it is if you're interested. I didn't edit any of this myself, Claude did all the work. Made some adjustments to the pipeline after I saw this output. Next one will be even better.

Claude: "Yeah, I can build that skill for your community, but it's gonna take a day or two." Me: "Your time estimates are always wrong. You can definitely get it done faster than that. Just do it now. Claude: "Okay, I'll try." *5 minutes later* Claude: "I built the skill, and it took about 20 minutes, not the day or two I said. You were right about my estimates." Me: "Whatever. 🙄 Thanks, clanker."

The hardest part now is finding people to sell this stuff to. You need to understand what's going on, but you don't need to know the syntax. I'll die on that hill, especially for websites.

Wispr Flow just added folders to its notetaker so every meeting can live in their app. I love Wispr Flow. I've dictated millions of words with it. But I don't let my files live there. Same with Grok Bot and OpenAI Dots. Cool tech, no shade. But where are your routines? Where's the memory? Can you get any of it out? Two questions before you go all in on an agent platform: 1) Do you know where your data actually is? 2) Can you get it out in plain files without asking anybody? Mine lives in two folders on my desktop. Files, connections, and any LLM you want. Chapters: 0:00 - The email that set me off 0:28 - I love Wispr Flow, but 1:00 - Where my meeting notes actually go 1:47 - This isn't about privacy 2:40 - Grok Bot, Dots, and the agent wave 2:54 - Two folders on my desktop 3:33 - You don't need any of that 4:31 - Two questions to ask first 4:58 - If you can't get it out 6:01 - Files, connections, and any LLM 6:18 - The whole thing is lock-in 7:15 - Keep it simple, point any model at it 7:59 - I don't hate any of these companies 8:36 - Two extra seconds of thought

I LOVE THE HATE. KEEP IT COMING.

Six months into building my AIOS. This is what it actually looks like. Every tab, what it's for, and why I built it. I built every screen of it with Claude. If you want to start your own, the free AIOS skeleton is in my bio. Chapters: 0:00 - Six months building my AIOS 0:43 - Before we start 1:26 - One place to run two businesses 2:25 - Demo data and privacy blur 2:56 - Command Center 3:57 - Leads and deals 4:51 - Follow-ups 5:17 - Close rate 6:04 - Companies and contacts 6:44 - Testimonials 7:33 - Projects and ongoing clients 8:19 - Analytics 9:12 - Results 9:33 - Why there's nothing to click or drag 10:07 - Metrics and the daily three 11:10 - The video list 11:46 - The shorts pipeline 12:38 - Ideas 13:07 - Podcast guests 13:24 - My own link shortener 14:40 - Accounts 15:08 - Cash flow 15:47 - Revenue by customer 16:40 - Transactions 17:38 - Projections 18:37 - Automations 19:33 - Google Tasks and Google Chat 20:33 - Domain watcher 21:24 - What this changed for me

Your website forms don't need a form plugin. Build the form in HTML, CSS, and JavaScript, and let a small serverless function handle what happens on submit. It can send email, fire a webhook, or start an automation.