AI can produce a persuasive website image in an evening. That is a useful draft, but it does not prove the site works for the business. A screen does not reveal whether the form works, what happens on a phone, who owns the code or what breaks after an update.
“Why pay a designer if AI has already made the site?” is a fair question. The answer is not that generation is useless. It is the difference between demonstrating an idea and launching a product that can be used, measured and maintained.
What the mockup does not show
Before visuals, you need to understand the audience, key journeys and content. Then come page hierarchy, copy, contrast, keyboard navigation, forms and error states. Development adds performance, responsive behavior, security, analytics, SEO, backups and release processes.
Not every project needs months of research or complex infrastructure. Every project does need a deliberate decision about which checks matter and who owns them. Otherwise the apparent saving becomes a bill for fixes after launch.
When repair is sensible
Repair is reasonable when you own the source and rights, the architecture is understandable, core journeys work and issues are localized: a few mobile sections, copy, metadata or component accessibility. Then you can list defects, estimate hours and fix by priority.
Start with a compact audit of real devices, speed, form validation, indexing, rights to images and code, and the ability to update content. The home-page screenshot is not enough.
When a rebuild is cheaper
A rebuild is often more honest when source code is missing, key journeys fail, the same defects repeat across templates, content cannot be maintained or each fix breaks something else. A stack of patches can become a new build without a coherent system.
Compare two routes: repair cost including risk, and rebuild cost while preserving useful content. Without that comparison, “cheap AI site” is just a debate about taste.
Agree on the next step
Ask for a quote separated into audit, design, development, launch and support. Each stage needs a deliverable and acceptance criterion. Extra work then becomes visible scope rather than a mysterious surcharge.
Keep the AI mockup as a mood reference if it helps. Do not automatically treat it as a specification: first check which choices help users and which merely look good in one image.
Takeaway
Compare the cost of two paths to a reliable launch, not the price of an image with the price of a website.
