Built my site with AI in an hour — should I pay an agency to audit it or start from scratch?

The biggest vulnerability in AI-generated static files is the form endpoint. If you don't stick a spam filter and input sanitization layer in front of the server, your server will turn into a spam relay within weeks. When paying for a review, have them scrutinize the form handler on the PHP or Node.js side specifically.

We tried something similar in Jeddah. Pushed the AI code straight to production, and within a week the form was getting 150 bot messages while the Arabic fonts completely broke on mobile. Paid a local consultant 2,500 SAR; he cleaned up the stylesheets and secured the form in 3 days. Definitely no need to blow 14,000 SAR on this.

The agency asking for 14,000 SAR and claiming "AI code is garbage" is just pulling a classic agency move. Of course they want to sell you their full custom build package. For a 5-page static brochure site, even messy code won't generate enough traffic or complexity to bring down a server.

Before uploading the site to hosting, run it through free Google PageSpeed and security testing tools. Forward the red warnings from the report to the agency that quoted 3.500 SAR, and get written confirmation asking, 'Will you fix all the errors in this report?'

Are product prices listed on the site with real-time ordering or is it just a downloadable PDF catalog and a WhatsApp button? If there's no dynamic cart, a custom development quote from scratch is completely overkill for that budget.

14k riyals for a five-page static showcase is a total waste. hand the code over to the agency charging 3.500 sar let them fix the meta tags and secure the form, that's plenty.

edit: fixed a few typos.

Pursuant to Saudi Arabia's Personal Data Protection Law (PDPL), name, phone, and email data collected via contact forms must be stored and processed on secure servers. It is your corporate responsibility to ensure that this data storage security is included in the agency's review specifications.

The discussion got scattered, let me summarize. Code without setup documentation isn't yours, even if you have it.

If scope grows, either time or budget must grow. There is no third option.

the opposite happened to me, thats why Im writing... most time waaste accumulates in tasks waiting for approval.

any unwritten clause becomes a point of disagreement later, as both sides remember it differently. just leaaving this note it might be useful.

I'll try it.

I've been down this road, let me tell you. When making a decision, first look at what data you have on hand.

Proven by experience.

I feel the same way. The harder it is to reverse a decision, the slower you should make it.

Of course, it varies if your situation is different.

We need to take it step by step. When making decisions, write down the worst-case scenario too, not just the best.

If you have questions write them; Ill answer as best I can.

theres a commmon mistake people make when doing this. honestly everyone rushing into website design with artificial intelligence gets stuck at the same point.

that's all, sorry if I went on too long.

Let me summarize the topic, since several different answers were given. The system lives on after delivery; maintenance is a separate line item.

If you have questions, write them; I'll answer as best I can.

You're right, I've been down that road too. When you try to change everything at once, nothing settles.

If I were you, I'd go this route.

saved.

Thanks for posting.