I'm responsible for our e-commerce technology, including development, servers, domains, SEO, UI/UX, databases, and business analytics. Our current site is dynamic and relies on a database, while a friend of my nontechnical boss built a simple informational site with a contact form using free static hosting and now promotes it as faster, easier, AI-powered, and free.
My boss is convinced we should move our e-commerce site to the same setup so he can edit everything directly, and he sees our cloud-hosting bill as unnecessary. He is also experimenting with AI-generated code without really understanding the architecture or the risks. I'm struggling to explain that a static informational site is fundamentally different from an e-commerce system that needs product data, customer information, orders, authentication, forms, and secure server-side processing.
How can I present the differences clearly and professionally? Should I build a small proof of concept, document the risks, or simply follow his instructions and let the limitations become obvious? I'm also worried about being blamed if the experiment fails, and I'm considering looking for another job.
4 Answers
Document every warning by email, then follow the agreed direction as safely as possible. Keep backups, preserve the working version, use source control, and avoid replacing production until the new system passes a written test plan. If someone is generating code with an AI tool, it still needs code review, security checks, testing, and a rollback plan.
If the site has already been damaged by an unreviewed AI change, that is strong evidence that the process—not just the hosting choice—needs controls. Start updating your resume and looking around quietly as well. A manager who ignores documented technical and business risks may eventually blame the person who raised them.
Put the comparison in writing and keep it factual. A static site can serve HTML, CSS, JavaScript, images, and perhaps connect to separate services, but it does not replace a secure application backend or database. Your e-commerce system needs somewhere to store products, variations, inventory, customers, orders, and form submissions. It may also need authentication, permissions, payments, backups, monitoring, and protection for sensitive data.
Explain that “free hosting” does not mean the whole system is free. The costs may simply move to other services or to additional engineering and maintenance time. Also check the host’s commercial-use, traffic, and availability limits before making it part of the business infrastructure.
There may be a legitimate request underneath the bad proposal: your boss wants routine content changes to be simple and does not want every edit to require a developer. You could address that separately with a CMS, an admin panel, or a managed content service while keeping the transactional e-commerce backend intact.
Static pages can be excellent for marketing content, but they are not automatically a replacement for dynamic features. Treat the static site as one possible frontend or marketing layer, not as proof that the entire business application can run without a backend.
Don’t frame this as a personal argument about who understands technology better. Create a short options document with the current architecture, the proposed static setup, what features would stop working, expected traffic, security implications, ongoing maintenance, recovery time, and estimated costs. A small test deployment could demonstrate the limitations without risking the production site.
Ask your boss to approve the choice in writing, including which features can be sacrificed and who accepts the risks. If he still wants the simpler architecture, you can implement it within a defined scope rather than silently being held responsible for an unrealistic design.
Be especially clear that removing the database does not make the data disappear; it either has to live in another service or be exposed as files and code. That can create privacy, security, and update problems.
The important question is not whether the site has 55 products today. It is what information and workflows the business needs: inventory, variations, orders, customers, payments, reporting, and future growth. Even modest traffic can require proper security and backups.