Big Idea

The argument in one line.

Claude Code plus Astro, GitHub and free Cloudflare hosting lets one person build, launch and maintain dozens of client websites without WordPress, cutting a morning of edits from hours to about 30 minutes.

Who This Is For

Read if. Skip if.

READ IF YOU ARE…

A freelancer or small agency owner still managing client sites in WordPress and page builders who wants a faster, cheaper way to build and maintain them.
A non-developer who has never touched GitHub or Cloudflare and wants the exact order of steps to get an AI-built site live on a real domain.
An agency owner buried in daily client change requests who wants to batch updates across many sites with parallel AI sessions.

SKIP IF…

You need a CMS with a visual editor your clients log into themselves, since this workflow has the owner making every change through Claude.
You want a deep Astro or code-level tutorial. The video stays at the process level and leaves the details to Claude.

TL;DR

The full version, fast.

The creator built over 70 websites in 2026 by replacing WordPress with Claude Code. Sites are written in Astro for clean, fast HTML, kept in one project folder per client with incoming and outgoing folders for assets, and built page by page from reference screenshots with Claude's preview browser. Context carries between sessions through handoff notes. Finished work is pushed to GitHub, which Cloudflare Workers watches and deploys within a minute or two on a free plan. Client change requests are batched into parallel sessions, one per site, and a morning that took three to five hours now takes about 30 minutes.

Free for members

Chat with this breakdown — free.

Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.

Create a free account →

Chapters

Where the time goes.

00:00 – 01:09

01 · 70+ websites this year

The claim, the scope of the video and why Claude Code.

01:09 – 04:32

02 · Migrating WordPress sites to Astro

Tell Claude to migrate, keep or enhance the design, and finish a site in two to three hours.

04:32 – 05:38

03 · Why Astro

Clean HTML, fast pages, and why AI builders that default to React single-page apps are a mess.

05:38 – 07:53

04 · Client project folders and incoming/outgoing

One folder per client with incoming and outgoing subfolders as the working space.

07:53 – 10:22

05 · Building pages from references and previews

One folder per page, references from other sites, and Claude's preview browser.

10:22 – 13:43

06 · Context and session handoffs

Sessions in the sidebar and picking up work in a fresh session.

13:43 – 14:29

07 · Optimizing before launch

Lighthouse, schema and cleanup before going live.

14:29 – 16:32

08 · GitHub setup

Why GitHub sits between your computer and Cloudflare, and how to connect an account.

16:32 – 18:46

09 · Cloudflare hosting and Workers deploy

Free hosting, domains and DNS, and the Workers flow replacing Pages.

18:46 – 19:22

10 · Custom domain and www redirect

Attach the domain in settings and redirect www to the root.

19:22 – 24:38

11 · Managing client websites

Batch updates with parallel sessions, commit vs push, and the 30-minute morning.

Atomic Insights

Lines worth screenshotting.

Telling an AI tool to build in Astro gives you clean, fast HTML, while Vite and React builders produce single-page apps you have to hack to get real pages.
Existing WordPress sites can be migrated into Astro in roughly two to three hours per site, with content pulled over without logging into WordPress.
One folder per client, with a session list under it, keeps every project's context separate and lets you resume any site later.
Incoming and outgoing folders give the AI a predictable place to find client assets and drop finished work.
A commit alone does not put anything live. Cloudflare only deploys changes that reach the main branch, so always tell Claude to push to main.
Asking Claude to write session notes before you stop lets a brand new session pick up exactly where the last one ended.
Cloudflare Pages is being folded into Workers, and telling Claude to look into it fixes the confusion from its older training data.
Hosting on Cloudflare costs nothing for this setup, so the only recurring costs per site are the domain at roughly $10 a year.
Running one Claude session per client at the same time turns ten client change requests into a half-hour job instead of a half-day one.
You can ask Claude to run Lighthouse and handle schema before launch, which is how the creator keeps every site scoring in the 90s on desktop and mobile.

Takeaway

Build once in code, publish through GitHub

WHAT TO LEARN

A clean folder structure, plain-HTML sites and a free GitHub-to-Cloudflare pipeline let one person run dozens of sites without a page builder.

Tell your AI tool the stack up front, Astro, then GitHub, then Cloudflare, so it builds clean, fast HTML instead of a heavy JavaScript app.
Give every client one project folder with incoming and outgoing subfolders so assets and finished work always have a known home.
Build page by page from references and use the preview browser, then let Claude carry the design language across the rest of the site.
End each session by having Claude write notes, so a new session starts with full context instead of from scratch.
Ask Claude to run Lighthouse and handle schema before launch rather than treating speed and SEO as a separate cleanup project.
A site goes live only when the change reaches the main branch on GitHub, so ask Claude to push to main and confirm the deploy.
Host on Cloudflare Workers connected to GitHub and expect updates to go live within one to two minutes.
Batch client changes by running one session per site at once, reviewing previews, then pushing and drafting the reply email for each.

Glossary

Terms worth knowing.

Astro: A free web framework that outputs plain, fast HTML. AI tools often default to it for content-style websites.
Cloudflare Workers: Cloudflare's hosting and compute product, which is replacing Cloudflare Pages. It deploys a site from a connected GitHub repository.
Commit vs push: A commit saves changes locally. A push sends them to GitHub. Neither makes the site live unless the change lands on the main branch Cloudflare watches.
Main branch: The primary line of a project's code in GitHub. Cloudflare deploys from it, so work left on another branch never goes live.
Apex domain: The bare domain without www, such as example.com. The creator redirects www traffic to it with a Cloudflare rule.
Session handoff: A note Claude writes at the end of a work session so a new session can continue with the same context.

Resources

Things they pointed at.

04:32toolAstro

14:29toolGitHub ↗

16:32toolCloudflare ↗

24:50productConvology+ Community ↗

Quotables

Lines you could clip.

00:00

“I built over 70 websites this year.”

tight claim that sets up the whole video→ TikTok hook↗ Tweet quote

19:50

“Claude's working on ten websites at a time running all of their updates.”

vivid before and after of agency work→ IG reel cold open↗ Tweet quote

22:00

“A commit alone is not a push live.”

clears up the most confusing part for beginners→ newsletter pull-quote↗ Tweet quote

The Script

Word for word.

Read-along

Don't just watch it. Burn it in.

See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.

I built over 70 websites this year. And as I move now into 2027, I have an entire process, an entire system, basically now an entire business where I can build websites for my clients in a matter of days in ways in which I was completely incapable of doing historically for the last 10 years as I've been using WordPress and WordPress plugins and managing all my websites in WordPress.

Well, all of that changed this year when I transitioned to using Cloud, generally speaking AI, to build my websites, to manage my websites, to create applications and custom functionality and basically anything I want for myself, for my business, and for my clients. So in this video, I want to walk you through my process, how I build websites, how I approach website projects now, how I manage and maintain websites for clients.

for my own companies, and how I can do all of that as a very, very small team or a solopreneur even, and how none of it is overwhelming anymore, and how I've been able to quite possibly more than 100x my productivity. My AI of choice is Claude. I use Claude, particularly Claude Code, for all of my website work.

You can use ChatGPT Codex, probably one of the Gemini models. There are other tools. I use Claude Code.

I have found it gets me the best results and Claude Code fits within my workflow. So like I mentioned, I built over 70 websites this year. Well, how did I do that?

Well, first off, if the website already existed as a WordPress website, let's say there was a design and let's say my client liked it, but I wanted to take it out of WordPress so that it was easier to manage. To do that, all I had to do was go to Claude, say to Claude, hey Claude, I need to migrate this WordPress website.

Now, I've done a video all about migrating WordPress websites using Cloud and AI into Astro, which is the framework that I use for building websites now, or that Cloud uses for me, with me, to do websites. Now, that video is still 100 % applicable.

I'll probably do a revised version for 2027 as I'm nearing the point in which I've migrated all of my client websites that I manage. But let me give you the basics of this process and then you're welcome to go watch that video. And if you'd like to join Kimbology Plus, which is my community, I make a skill totally available to you as part of your membership where you can just give it to your cloud and it knows exactly how to do all of this.

But here's the gist of it. I go to cloud and I say, hey, I have this website over here. I want you to migrate this website into Astro.

I want you to bring over all the content. And if I want to keep the design, I tell it. Let's keep the design, but maybe elevate and enhance a little bit of it.

Maybe something we were doing wasn't possible because a plugin didn't work the way we wanted it to, or our page builder maybe couldn't do some sort of visual thing that I really wanted to do or the client really wanted to do. All I would have to do is tell Claude, do that thing. And that's going to be the foundation for pretty much all of this.

All you have to do is be able to describe to Claude what you want to achieve. and it will make it happen or it will walk you through the options for making it happen. So let's say we liked our design, but we wanted to enhance it a little bit.

We'd say that to Claude. Claude then gets to work. Using the skill that I created, and honestly, you can walk Claude through this probably on your own with a little bit of back and forth, but it's able to bring over all of the content, strip out all the WordPress stuff.

Even if you're using some complex page builder that doesn't create clean code, Claude is able to go in and pull all of that data out of WordPress without having to log in. without having to do anything other than just access the website in its own particular way. So it sucks all of that content, pulls all of the pages over, recreates all of them.

The way that I like to do it is I typically like to start with the homepage and I'll say, okay, great, let's make some tweaks. Let's set up kind of like a design language. If we make a change on one page that we want on other pages, I let Claude know.

And in a matter of maybe two to three hours for your average website, it has been completely rebuilt and completely launched. brand new. That is the gist of the migration process.

I go into more details in another video that I'll put in the description down below. But now let's talk about building websites from scratch or even taking an existing website and basically just completely redoing it. Like I said, I use the Astro framework.

It's completely free. You don't need to download anything. You don't even really need to know anything about it.

You just can say to your AI tool, I want to use Astro. And in most cases, the AI is going to default to recommending Astro anyway.

It's pretty much the best option out there. Most of the AI tools out there, the ones like Lovable and there's a bunch of them, they'll build everything in Vite, React, all these JavaScript things. You get these like single page applications that you kind of have to hack around in order for them to make multiple pages or to render clean HTML.

Then you've got server side rendering, client side rendering. All of that's a mess. Just have it build an Astro, and it always makes clean HTML, always blazing fast.

All of my websites are scoring 90s and above on desktop and mobile for page speed. Cloud can literally optimize this prior to launch automatically. Okay, so we've got our framework.

We know we're building an Astro. You just tell it that. Now, where do we work on our computer?

Well, Cloud Code works on your computer, at least the way that I use it. Yes, I'm sure there's cloud solutions you can use, etc. I work locally on my computer.

So I use that as like a form of a backup because eventually our files are going to be sent to GitHub and then to Cloudflare. That's the way that I manage my website builds. So we've got our computer here.

We've got a folder on our computer. I call this folder client projects. Inside of client projects, I have client A, client B, client C, client D, et cetera.

Each of those clients has their own folder. Inside of those folders, That's where Cloud Code is going to work to build the websites for each of these clients or projects or businesses.

I don't worry about micromanaging any of the file structure. Cloud takes care of all of that. You don't need any complex prompts.

You don't need any kind of operating system logic folder mumbo jumbo. I see some of the videos out there about like creating a AIOS and all these like AI structures. All that stuff does.

is force Claude to work your way and it works less efficient and it eats up tokens and you burn through your credits much faster. Let Claude cook. Let it do its own thing.

Give it a folder. It works in there. The next thing I like to do inside that client folder.

So let's go into client folder A. Let Claude do whatever it wants. It's going to create all its various folders for Astro, its source folders, its public, whatever.

I don't even know what those are. I don't care. I put a folder.

I call it incoming. And I make another folder and I call it outgoing. Outgoing is where Claude would put things that I need to give to my client or something that I'm going to take and go with.

Incoming is where I put things that I want Claude to do something with. So for example, I might have a client that says, hey, add these photos to my website. Incoming folder becomes the dumping ground for anything a client gives me.

I dump everything into the incoming folder and I say, hey, Claude, I've added some new images to the incoming folder. The client wants them to be added to this page. And Claude will just then go in and do it.

And I check the folder. The folder is empty. Claude has taken those images, optimized them, made them better for web, put them on the website.

We're done. So as I'm building a new website, I'll go into my incoming folder. I might make, for the sake of simplicity, additional folders like home page, about page, contact page, service page A, B, C.

I'll put inside of those folders any content, any images. I try to make it honestly more organized for my sake than it is for Claude. I could probably just dump all of this into the incoming folder and just say, Claude, have at it, figure it out.

And it would. But for my own sake, I'm a little bit of, I like a little organization and this does not hurt Claude's efficiency. I just like to put the stuff in there and Claude just gets to work because it knows where to get things.

So great. I go to Claude and I say, all right, in the incoming folder, I've put all the things for the different pages. You're going to find copy.

You're going to find content. You're going to find everything that you need in order to build these individual pages. And then from here, all we have to do is talk back and forth about what I want for a website.

I might find three or four websites and say, I like this thing from this website and this thing from this one. I like the way in which this website did their hero section on this subpage. I like the form on this page.

I'll find various pieces that I like and I can give those websites to Claude or I can take screenshots, put them in the incoming folder, in a folder called reference materials or examples I like, dump my screenshots in there and then just tell Claude, I like the form on this website and then name the file so Claude knows what it's looking for.

That's kind of my... back and forth process with Claude so that it knows what it's looking for and where to find it. Now, inside of Claude, Claude has this preview browser.

It's in the upper right -hand corner. It looks like a tiny little globe. I like to click on that because that's where Claude's going to open up what it calls the local host.

The local host is on your computer. It's like a virtual rendering of the website. It renders things on your computer.

It's like magic. So instead of it being a website somebody could reach live, You get to see what it looks like without it having to go anywhere or be on a staging link.

Think of it like free staging on your computer. So I open up that panel, shrink the other columns as much as possible, and I get to see the website as Claude builds it. While it's working, I may interrupt it and say, hey, I see that you're doing this.

I don't love the way that that looks. Can you make that bigger and that smaller? Can you change that color?

You're going in a little bit of a wrong direction. So I might micromanage some of it, or I might let it cook the whole way and then just come back and say, yeah, it looks good, or make this change, and it will go do that.

Now, an important part of building your website with Cloud is knowing when to stop. Inside of Cloud Code, This changes with various updates, but you're going to find some kind of usage meter.

Sometimes it's near the chat bar. It's like a little circle that looks sort of kind of filled in. Sometimes it's on the right -hand column if you don't have the preview browser open.

Somehow find your usage because you're looking for something called context. And context is basically how long your conversation is going before you reach the limit of what Claude can hold and what it can process. I typically...

like to, when I'm building a website, go about 50 % of my content usage, or a better metric would be we finished the homepage. We finished something big. I like to say to Claude, all right, I'm going to stop for this session.

And I use the word session because Claude used it with me one day and it stuck. I want to pick up with you in another session. So make any notes we need for this project.

Make sure nothing's in your scratch pad. Make sure it's all been documented, noted, so that when I come back in a new session, We can pick up exactly where we left off, and you'll know exactly what to do.

It thinks for 30 seconds, makes some notes, and it says, okay, session handoff is good to go. See you next time. Then right away, I can open up literally another session.

Here's what's cool. In the left -hand sidebar of Cloud Code, the left -hand sidebar has folders. So as soon as you start working in a folder, remember, we're working in client projects, and within client projects are those subfolders for each of our websites that we manage.

We work in Cloud Code down at the very bottom where it says choose where to work. We work in client projects. And the reason we do that is so that let's say we liked something from another client project.

I could say in client B's website, we're going to do something very similar to client A. Can we bring something like that over? And then Cloud just goes and takes the code it already created and we use it again.

It's awesome if you work like that. So in that left sidebar, you're going to see. client projects, the name of the folder.

And then underneath that is going to be a list of all the sessions that you've had. So if you forget to do your handoff and say take notes for the next session, go back to your previous session and then tell it to work out of that or just see if it looks like Claude is at a natural stopping point already and then start a new session.

but you're going to see your list of sessions. And I like that because then you're able to see like a trail, almost like a log of all the work that you've done. So you personally have context, but Claude's context has not been filled up where it stops working well or starts working less efficient.

So now we completed our homepage. We're ready to go work on other subpages. Start a new session.

Here's what I say. Let's pick up working on client B and we were going to move on to the about page next. Or I'll say to it, let's continue working on client B.

I don't remember what we were working on. What does it say in our notes? Or where would be a good place to go next?

Or do you have any recommendations based on the migration process of where we should go? You can ask Claude. I would say for me, it's about 50 -50.

I either ask Claude what to do next, or I say, maybe I'm in the mood to build a contact page. Let's work on that. I just say something like that.

And then we pick right back up where we left off. and we can complete that project or that session, and we can then tell it we want to pick up on the next one. All right, now let's talk about what happens when we're done.

We like the way that our website looks. We're happy with everything. There's a couple things you can do from here.

You can say to it, optimize it so that everything's good to go, and it'll use something like Lighthouse, or you can say to it, hey, can you run this through Lighthouse, make sure everything's optimized, everything's clean, talk to it about schema, all those types of things. You can go through that process. I'm going to let Claude basically assist and help you.

And in my other video, I talk a little bit about this as well. But I want to walk through the process of how we take our websites and we put them live so that when it comes to the management section, this part's easy. So we want to work in GitHub.

And by the way, unless you like knock this website out in a day or two, throughout the process of creating your website, let's say you finished your homepage. Claude might bring up the fact that, hey, this isn't connected to any GitHub repo. Would you like me to make one?

And at any time, you could say to Claude, yes, make me a GitHub repo, make it private. Let's go ahead and commit and put this on GitHub. GitHub is where your code sits.

It's like the intermediate place between your computer and Cloudflare, where we're going to host our websites, where I host all of mine. There's other options out there. Cloudflare is completely free the way that I use it and the way that...

you're likely going to use it as well. So I use GitHub and Cloudflare. Anytime I'm done with a session, as long as I've created a GitHub, I just say to it as part of my process for being done for the session, go ahead and push everything to GitHub and then make notes about our session.

So you can tell it to make your repo. Now, how do you connect GitHub? That's really easy.

All you have to do, github .com, create a free account. None of this costs any money. Create a free account.

Claude will walk you through the steps to create a GitHub account. In fact, I'm going to put them up here somewhere on the screen for you to see the process of creating a GitHub account. Step one, and Claude, who's going to help me edit this video, is going to help me fill in the blanks here.

But step one, create your free GitHub account. Step two, tell Claude you want to connect. It's going to run something.

If you're on a Mac, it uses the terminal typically, and you'll just run a command, copy something, etc. Mac is super easy, by the way, compared to Windows. If you're on Windows, you're going to download the GitHub desktop app, and you're going to walk through the process of logging in, and then your system will do all the connections it needs in Cloud.

With Mac, super easy. Mac just takes care of everything. Cloud works in the terminal.

It'll tell you what to do. You make a connection. You authorize it, password or something like that.

You're done. You're good to go. Cloud will walk you through the whole process, and I'll have it up here on the screen visually for you to understand kind of how that works.

But from there, super easy. It just automatically makes the connection for you when you tell it to push it to the repo. Now let's talk about Cloudflare.

Cloudflare is your host. It's free. So if you're coming from WordPress world, you don't need web hosting anymore.

Why? Well, because Cloudflare is your host. Cloudflare is like the world's best CDN.

It's the fastest thing on the planet. It's basically where all the enterprise stuff is at, that and AWS. So inside of Cloudflare, probably your domain is there already.

And if not, It probably should be. Cloudflare is where I register all my domains at like as low a price as you can get, not counting the ridiculous discounts that some websites give you and then they like quadruple the price on you in year two or three.

Cloudflare is always super cheap, like $10 for a domain per year. So I get my domain in Cloudflare. Now Cloudflare manages all of my DNS.

Super awesome because that means it goes through their firewalls, it does bot protection, makes sure everything's fast, it's not going to be DDoSed. We're good to go. Connecting is super easy.

All you have to say to Claude is, I want this to go on Cloudflare. And by the way, you can say to your Claude in the very beginning, we're going to build it in Astro, it's going to go to GitHub, and then ultimately land on Cloudflare. Now Cloudflare...

Just a few months ago, maybe longer, but I became aware of this a few months ago, Cloudflare decided that Cloudflare pages would become more of a legacy thing as they migrate everything to Cloudflare workers. That might confuse Claude at first because it's so new, but just tell Claude to look into it and then he'll understand the fact that now we're using workers, which is a Cloudflare term, workers for everything.

Pretty simple. All you have to say is we're going to make this a Cloudflare worker, and then Claude can actually do quite a bit of it through the CLI. I think that's command line interface.

Or you, if you wish, could go do some manual work inside of Cloudflare. Go into Cloudflare, make sure your domain's set up. You can do the setup on the left -hand side.

Go to Compute. So not in your domain, just in your overview of your account. Go to Compute, and then create a new worker, give it a name, then...

Where do you want to connect it to? Choose GitHub. And then once you just click Yes, Authorize, it connects your accounts.

And then you just basically find the repo that Cloud Code made, select it, and then just follow Cloud Code's instructions. I believe this is just the default, so you probably don't need to change anything. Just hit Deploy or Save, and it takes care of everything.

But Cloud will walk you through it. At that point, your website is on Cloudflare's kind of like dev environment. It's there, but it is live.

It's just on a dev URL. So to connect it, you just go to settings, domains, and then you just set up to attach your website. For me, it's convology .com, and then I add www .convology .com, and then I just go to Cloudflare rules templates, and I add a redirect all www traffic to the root or the apex, I guess it's called, and you're done.

That's it. And now from now on, any updates you make are automatic. So that brings us to the...

How do we manage websites? How do we make updates to our websites now that we've built them and now that they're live on the internet? Well, this is the cool part because historically, every morning for the last five plus years, clients will just flood my inbox with changes on their websites.

I want this page added, take this down, do this, do that, et cetera. Historically, that meant that almost every morning for the last five years, I've spent three plus hours making updates to client websites because I'm going into WordPress.

I'm going to pages, finding the page, clicking edit in, you know, Thrive Architect, Elementor, whatever builder that happens to be used on that website, Astra, Spectra, whatever it might be. And I'm having to go through the slog of being like, okay, what did they want? Where do I edit it?

Here's the tweak. Great. They sent me a five megabyte file.

I have to now optimize this image. I was doing everything manually. is over.

Now, if I have 100 edits in my inbox this morning, all I do is say, hey, Claude, check my inbox, find all the requested client updates, go ahead and get started and take care of those. Or I might say to it, if it's a light morning, Claude, here's the changes that client A wants. I've put them in the incoming folder.

Or if it's like a simple sentence that just says, change this word, I'll just give that to Claude in a session and let it go to work. Now, remember our sidebar in Claude. We have client projects.

And then under the client projects, we have all of our sessions. Well, if we have changes for clients A, B, and C, I'll start a session with that little plus button in the sidebar next to our folder. Plus button starts a new session into the client websites folder automatically.

I put all the stuff in the incoming folder for client A. Please make all these changes. I click the plus button.

I put all the stuff in the incoming folder for client B. Make these changes. Hit the plus button.

Now I go to client C and I say, client C is pretty simple. They just want to make these updates. Can you make these updates to their website, please?

Claude's working on three, four, five, six, ten websites at a time running all of their updates. So you don't have to connect your Gmail if you don't feel comfortable doing it. I have because I like using Claude's Duet Assistant, which I'll make a video about in the future, to help me manage and stay on top of everything.

But essentially, Claude Code can just work off those incoming folders if you want to triage the content yourself. And then what do you do? You check the preview to make sure everything looks good.

You say, looks good. Commit and push live. Draft me an email so that I can send it to client A.

Repeat that process for all the clients. All of your drafts, if it's connected to your Gmail, are sitting there waiting for you. If not, copy paste, put them in your Gmail.

Your updates are done. Here you go. And you've completed your morning in about 30 minutes or less compared to me, three to five hours of work sometimes.

So again, what does that process look like? It's fairly simple. It's literally, hey, Claude, we're going to work on this website.

And you're telling it that because you're starting in the client websites folder. You make all your changes, you commit. So some terminology here.

From what I understand, and again, this is the great part. You don't have to be an expert. A commit alone is not a push live.

So sometimes you can locally commit on your computer where Cloud basically commits the changes locally. You can commit and push to GitHub. And sometimes that is not pushing live.

This is where it gets a little confusing. You just have to learn the nuances. It will say things like, I created a branch.

I did not merge it with main, M -A -I -N. That just typically means it did not get pushed into the main branch of your code. And so Cloudflare did not pick it up because Cloudflare is only going to pick up changes to the main branch of your website's code.

This is a way of version control so that you can create things and have backups and version controls in case you need to roll back. Bottom line, if you want something done, just tell Cloud, push it to GitHub, make it live, push it to Cloudflare. It'll know what to do.

And you can always ask it, did this go live to Cloudflare? And sometimes it'll just tell you automatically, I'm waiting to see if it went live to Cloudflare and it just pulls and it waits and then it'll let you know when it's live. And by the way, these changes take about one to two minutes max to go from your computer to Cloudflare because they're going through GitHub and Cloudflare is sitting there waiting, listening to GitHub for when it's ready.

So that's my process. That is how I am making websites. Now that in 2026, I've built 70 plus websites and now going into 2027, I'm keeping this exact same process and I'm continually making it better.

Now from here, the sky's the limit. If you want to make a custom platform, if you want to create some kind of custom app, a custom portal, you can do all of that through Cloud Code. And in fact, I have an entire playlist that you can check out over here on the right -hand side, where I walk you through how to make some pretty awesome tech stack tools so that you can get rid of all the various tools inside your tech stack that you're paying for and build and manage your own.

And here's the cool thing. Now that you're building websites through Cloud, All of those tools can connect right into your website natively and work even better.

So check out that playlist. And if you're looking for more help, if you want some coaching and assistance in going deeper into building websites with AI, managing an agency, check out Convology Plus. It's my community where I can devote my time specifically to you and to help you and others at scale have office hours and additional AI resources and content and courses that you can access inside the community.

I'll put links down below in the description for that as well as some of these other videos that I mentioned. And if you have any questions, feel free to leave a comment down below.

The Hook

The bait, then the rug-pull.

One agency owner went from managing every client site by hand in WordPress to building 70-plus sites in a year with Claude Code. This is the whole process, from the first prompt to a live domain and the daily client edits after.

Frameworks

Named ideas worth stealing.

05:38model

Client-folder website workflow

Client project folder
Incoming and outgoing folders
Build in Astro
Preview in Claude
Push to GitHub
Deploy on Cloudflare

Each client gets one project folder where Claude works, with assets coming in and finished work going out, then GitHub and Cloudflare handle publishing.

Steal forany agency or freelancer managing many sites

CTA Breakdown