I recently finished a website for a custom knife maker. Complete, live, and ready to showcase his work. By the end of the afternoon, his site was on Cloudflare Pages, his gallery was loaded with photos of hand-forged blades, and his contact form was funnelling enquiries straight to his inbox. When I told him how quickly it came together, his first reaction was scepticism. His second was relief. He'd expected weeks of back and forth, design revisions, and a bill that hurt. Instead, he got exactly what he needed, exactly when he needed it.
Here's what "built in an afternoon" actually means. It doesn't mean rushed. It doesn't mean templates. It doesn't mean a compromise on quality or functionality. What it means is that the tools available to a web designer in 2026 are so efficient that the technical execution of a small business website has compressed dramatically. But the strategic thinking, the understanding of what the business actually needs, and the care in implementation? That part takes exactly as long as it always did.
The conversation comes first
Every project starts the same way. I message back and forth with the client, usually over email or text, so they can reply in their own time without any pressure. What's your business? Who's actually coming to your site? Are they looking to buy right now, or are they researching? What's broken about your current setup? Maybe you're using a platform that charges a monthly fee and feels clunky. Maybe you don't have a site at all and people are having to message you on Instagram to ask basic questions. Maybe your old site doesn't work on phones and you're losing customers because of it.
I spend time understanding what success looks like. For the knife maker, it was clear. He needed to show off his craftsmanship, display the types of blades he makes, give people a way to get in touch about custom orders, and let the work speak for itself. That's not complicated, but it's specific. Getting those specifics right matters far more than having seventeen extra features that nobody will use.
I also think about what the business stands for. This is someone who spends hours at the forge creating something by hand. The site needs to reflect that. Raw, tactile, considered. The tone of voice, the colours, the way the images are presented: these decisions shape how people perceive the business. That's not something AI generates automatically. That's something I decide based on what I've learned from the conversation.
Then the building actually starts
Once I know what we're building, I use AI to generate the foundation. Clean HTML, responsive CSS, proper semantic markup. The AI handles the technical scaffolding quickly. It generates a navigation bar, a hero section, a gallery, a contact form, a footer. All of it follows current best practices. All of it is production-ready.
But it's not personalised yet. So I start customising. I change the colour palette to suit the brand. Dark tones, warm steel greys, a layout that puts the photography front and centre. I write custom copy that sounds like the maker, not a generic template. I integrate the tools that matter: a contact form that feeds to the right email, an image gallery that loads fast and looks sharp on every screen size.
Then I test. I open it on three different phones. I check it on a tablet. I test on Safari and Chrome. I make sure the form actually works. I verify the links all go to the right place. I check that the page loads in under two seconds. I test the contact form five times to make sure enquiries actually arrive. This bit takes time because it's important. A fast build means nothing if the site doesn't work.
By afternoon, it's live
Once I'm confident it's right, I deploy to Cloudflare Pages. No faffing about with hosting companies or FTP clients. The site goes live immediately, gets a global CDN for free, and runs on infrastructure that handles traffic spikes without breaking a sweat. The client gets a message with a link. They can see their site exactly as customers will see it. They can send through tweaks if something feels off.
Usually, there are one or two small things. The heading might feel a bit off. The button colour could be slightly different. These changes take minutes. I adjust them, deploy again, and send another link. By the end of the day, we're done.
The reason this is possible isn't laziness. It's leverage. I'm not spending hours writing code from scratch. I'm not reinventing the wheel. I'm using tools that handle the repetitive, technical part of the job so I can focus on the part that actually requires thinking. The creative decisions, the strategic direction, the quality control. That's what I do. The code generation is just infrastructure.
What matters is what actually works
After launch, the knife maker messaged me to say he'd already had enquiries through the site. People were finding his work through Google, browsing the gallery, and reaching out about custom orders. His site loads instantly, looks sharp on every device, and he's not paying a cent for hosting or security updates.
That's what "built in an afternoon" means in 2026. It means that a small business no longer has to choose between doing without a proper website or spending thousands of dollars and waiting weeks. It means that good, functional, beautiful sites are now accessible to people who actually need them. It means that a designer can focus on strategy and quality instead of getting bogged down in technical minutiae.
If you've been thinking about getting a website but worried about cost or timeline, you don't need to worry anymore. The tools have gotten good enough that fast doesn't mean cheap or low quality. It just means efficient. It means you get what you actually need, without paying for what you don't.