Web Design

Thinking of Building Your Site with AI? We sat down with Durable.com

Lately, some prospective clients have been asking us about AI website builders — why hire a developer when AI can build a site easily and inexpensively? Fair question. So we sat down with Durable.com and tried building a real site with it. Here’s what we found.

What people picture when they say “build my site with AI”

If you’re thinking about having AI build your site, you may be expecting to use regular language for the whole process: describe what you want, and keep adding content, and making changes until the site is ready to go live — all without ever touching a traditional page-builder interface.

So today we sat down with a website builder that markets itself as fully AI-driven. Durable.com describes itself as your “always-on AI business partner,” with ongoing natural-language conversation shown as the entire way you interact with your site. We tried building a real site with it, entirely through conversation. Here’s how it went.

The initial draft was good

We’ll give credit where it’s due: Durable created a nice-looking website, quickly and easily. Durable asked us to upload all of our content, and gave us some themes to choose from, then created a clean, professional-looking site hosted on the Durable server.

But there’s a catch, and it’s a big one: it only works well if you have all your content ready before starting. Every team member’s bio and photo. Every testimonial. Every service description. Every FAQ answer. All of it, complete and ready to paste in, before you start. And this is all before you get a chance to see what it would look like on the site.

Most people building a site don’t do the process in one single step. They want to see a prototype and make changes until they’re satisfied. And that’s exactly where things started to fall apart with Durable.

We asked it to move one section down the page

First, something that seemed simple: move one section — “The records don’t speak for themselves.” — a few positions lower on the homepage. Not a redesign. Not new content. Just move it down.

Here’s how it went:

“Reordering sections directly isn’t supported through the editing tools I have available.”
— the AI, several messages into the conversation

The AI’s workaround was to delete the section and rebuild it from scratch. That’s when things really went sideways: the rebuilt section came back with placeholder text, not our original content. What followed was a long, halting sequence of the AI trying to fix its own mistake: guessing at what it could edit, succeeding on one, failing on another, contradicting itself about what was even possible.

“I’ve been going back and forth too long. Let me step back and give you a clear status.”
— the AI, after roughly a dozen failed attempts to restore the original text

It ended here:

“The fastest fix is actually the website editor itself — you can click into that section and retype the heading, kicker, and the four blurbs in a few seconds.”
— the AI’s final suggestion

In other words: after all that, its own advice was to abandon the AI chat and go do it by hand. The exact thing a “just describe what you want” tool is supposed to save you from.

See the full transcript
PureLynx: I want to move the section “The records don’t speak for themselves.” farther down the page I can help with that, but I’ll need to see the page first to know where the section currently sits and what’s below it. Let me pull up your website structure. {Reviewing website pages} I found a section with the heading “The records don’t speak for themselves.” Let me locate it on the page and see what’s around it. {Reading section content} {Reviewing page sections} {Reviewing page sections} {Reviewing page sections} {Reviewing page sections} The heading “The records don’t speak for themselves.” isn’t shown in the section titles above, it’s likely a heading inside a section’s content. Let me read the content of the most likely candidate sections on the homepage and about page. {Reading section content} Found it. The section is the feature section on your Home page, currently the 2nd section, right after the banner. Before I move it, two quick questions: 1. Which page is this? 2. Where should it go? PureLynx: It’s the Home page. Got it. Where should the section land? – After the metrics section – After the testimonials – After the FAQ PureLynx: After the metrics section {Reviewing website structure} {Reading section content} {Updating website draft} {Reviewing website layout} {Reviewing page sections} {Updating website draft} {Reviewing website pages} I need to find the exact field path for reordering sections. Let me check the full site structure path format. {Updating website draft} I’ve confirmed the section I need to move, but I’m hitting a limitation: reordering sections directly isn’t supported through the editing tools I have available. Here’s the workaround: delete the section and re-add it in the right position. Two confirmations before I do this. If that looks right, say the word. PureLynx: Yes, do it {Updating website draft} Updated website draft. Remove ‘The records don’t speak for themselves’ section. {Section removed, then re-added with auto-generated placeholder content} {Reviewing page sections} The section is now in position 3, but it was re-added with auto-generated placeholder content. I need to restore the original kicker, heading, and the four items. {Updating website draft} {Reading section content} {Updating website draft} {Updating website draft} The paths are relative to the section root, but the kicker path specifically failed, which blocked the batch. {Updating website draft} {Updating website draft} I can see the heading path works, but the kicker field isn’t directly addressable. {Reading section content} {Updating website draft} {Updating website draft} {Updating website draft} I see the pattern now, kicker, heading, and description are valid paths, but the items array itself can’t be replaced as a whole. {Updating website draft} The batch is being blocked only by the kicker path. {Updating website draft} {Updating website draft} The path resolution is inconsistent, heading worked in one batch but failed in another. The underlying issue is the section was re-created with a different internal structure than the original. {Reading section content} {Updating website draft} The heading path keeps failing because heading is a read-only/derived field on this section type. {Updating website draft} Now kicker is the blocker. {Updating website draft} Only the items.* fields are writable. {Updating website draft} I’ve been going back and forth too long. Let me step back and give you a clear status. Where things stand: The section moved successfully, now in position 3, right after Metrics, exactly as you asked. One catch: since the editor doesn’t support reordering directly, I had to remove and re-add the section. The re-added version came back with auto-generated copy instead of your original text. My editing tools are inconsistently refusing to write the correct copy back into this particular re-added section, so I can’t guarantee the original wording was fully restored. What I need to ask: can you check the live preview? Is the section in the right spot? Does the copy read correctly? If the copy is still wrong, the fastest fix is actually the website editor itself, you can click into that section and retype the heading, kicker, and the four blurbs in a few seconds. Would you like me to keep trying programmatically, or are you happy to finish the copy tweaks in the editor?

Since things weren’t going well with this task, we decided to put it on hold and proceed with entering testimonials.

We asked it to add our real testimonials

We hadn’t entered testimonials in the first pass, so Durable built a testimonials section with three placeholder quotes. We figured adding real testimonials would be simple: give the real content to the AI and have it swap them in.

“Where do you want it? On your homepage, or as a new ‘Testimonials’ page?”
— the AI, appearing not to recognize the testimonials section it had already built
See the actual chat transcript
PureLynx: If i enter testimonials here, can you put them into the site? I can help with testimonials, but let me be clear about what’s supported so I set the right expectation. What I can do: Help with your website content in Durable, including text on pages and sections. I can write testimonial copy and add it into a page or section of your site using the website tooling. What I can’t do: There’s no dedicated “testimonials” feature or form that feeds visitor-submitted reviews straight into your site. A couple of questions so I point you in the right direction: – Do you want me to write and add testimonials as part of a page on your site (creating a “What Clients Say” section with quotes)? – Or are you looking for a way for visitors to submit testimonials themselves? Let me know which one you’re after, and I’ll get started. PureLynx: I would paste the content here, and you would put it on the site That works. Here’s the simple flow: 1. Paste the testimonials here, quotes, client names, and any context (like roles or case types) you want included. 2. I’ll add them to your site as a testimonials section or page, using Durable’s website tools. To make sure I place it properly, could you confirm a couple quick things: – Where do you want it? On your homepage, or as a new “Testimonials” page? – Any wording for the heading, like “What Clients Say” or “Client Feedback”? Go ahead and paste the content, and I’ll set it up. PureLynx: On the homepage, where the placeholder testimonials are now {the chat ended here, having used the entire monthly AI message allowance}

We never actually got to finish. The chat ended abruptly, having used our entire monthly AI message allowance.

Two requests. Neither one finished.

Here’s the part that should really give you pause: after giving up on the reorder, we still wanted to add our real testimonials. We answered its questions and told it exactly where to place them — and before it ever made the change, it told us our monthly AI message allowance was gone, and the only way to keep going was to upgrade. Between the failed reorder and the unfinished testimonials, we’d used up the entire month’s quota, and neither conversation produced the result we’d asked for.

And when you run out? There’s exactly one way to keep going: pay for the next tier up. Free plan, Tier 1, Tier 2 — doesn’t matter where you start. Every level has a cap. Hit it, and the message is the same: upgrade to keep talking to the AI that just burned through your quota failing to do what you asked.

What this actually means if you’re thinking about using AI to build your site

Put together, here’s the pattern we saw, consistently, across every real change we tried to make:

  • You describe what you want, in plain English.
  • It doesn’t fully understand — it asks a clarifying question. You answer. It asks another.
  • Each back-and-forth eats into a small, capped monthly allowance.
  • Eventually it attempts the change.
  • Either it tells you it can’t actually do it — or it does something, but not correctly.
  • Either way, you’re the one who has to notice something’s wrong, and you’re the one who has to fix it — usually by hand, in the very editor you were trying to avoid.
  • Want to try again? Pay for a bigger plan.

One more thing worth saying plainly

A company saying “Build your site with AI” doesn’t mean it offers a modern, capable AI. Some AIs are very capable and others aren’t. The buyer has no way to tell in advance what they’re getting.

Back to what people picture

We started this page with what people picture when they say “build my site with AI” — an easy ongoing conversation, no page-builder interface required. What we found doesn’t match that picture. The one part that worked smoothly, picking a theme and dropping in your content, isn’t really an AI achievement at all. It’s the same thing you’d get from Squarespace or Wix. The AI conversation is where the actual promise was supposed to live, and that’s exactly where it broke down.

Thinking about your own website? Tell us about your project and we’ll tell you plainly what it’ll take to get it right.