We built our website in a week. I didn’t write a line of code.

A week ago, our new Zenro website was an idea. Today, it has pages explaining our solutions, enquiry forms and a pricing calculator that lets visitors explore their options.

I didn’t write a line of HTML or CSS. I described what I wanted to ChatGPT Sites in plain English, reviewed what it produced and kept asking for changes. Sometimes a lot of changes.

I know what looks right. Designing it is another matter.

Zenro works across construction, wholesale, manufacturing and professional services. I know our clients, the language they use and what the website needs to explain. But if you left the colours and layout entirely to me, you might end up with something from an 80s music video.

Sites let me close that gap. I could bring the business knowledge, see a design take shape and say, “This feels crowded,” or “That heading doesn’t sound like us.” I didn’t always know how to fix a page. I knew when it needed fixing.

What we built in seven days

This is more than a brochure site. It explains our solutions and business areas, introduces our team and includes a calculator based on our pricing information.

The calculator was the biggest achievement. Visitors can explore setup, widgets, subscriptions, integrations and support to understand the costs. I supplied the figures and explained the choices; Sites turned them into an interactive tool far more quickly than I could have built one myself.

But the AI didn’t know our business. I had to provide the content, the data and the judgement to tell whether the result made sense for our clients.

It was fast. It was also frustrating.

Sites sometimes told me a change was complete when the problem was still there. Fonts, colours and spacing drifted between pages. The calculator could get the figures right while its checkboxes were difficult to use.

I took screenshots, marked up problems and tested again. When a design still wasn’t working after several attempts, I occasionally asked Claude for a fresh perspective. That helped me explain what I wanted more clearly.

The lesson was simple: AI can build quickly, but someone still has to check the work. That matters most when visitors are entering details or making pricing decisions.

Did AI build our website?

I’d say we built it, using a new process. I supplied the knowledge, made the decisions and tested the experience. Instead of expressing those decisions in code, I expressed them in plain English.

That’s what excites me. People who understand their businesses can now play a much more direct role in creating the tools they need. Designers and developers can use the same technology to deliver more for their clients.

Our website took a week, and it took plenty of attention during that week. AI gave us speed. Our knowledge, data and judgement made that speed useful.