I work as the main IT person for an e-commerce business, handling development, servers, domains, SEO, UI/UX, databases, and analytics. Our current site is dynamic and relies on a database, while a colleague's much simpler informational site is a static parallax page hosted on GitHub Pages with only a contact form.
That colleague keeps telling my boss that his site is faster, free, AI-driven, and easy to edit directly. My boss now wants our e-commerce site rebuilt using the same approach and believes our cloud hosting is an unnecessary expense. He does not seem to understand that an informational site and an e-commerce platform have very different requirements.
The site currently has around 55 products including variations, with plans to expand significantly, and traffic may range from hundreds to thousands of visits per day. We need to manage product and customer data, forms, authentication, orders, and potentially sensitive information. My boss is also using AI coding tools to build parts of the site without fully understanding the consequences, and a previous attempt already caused code and months of work to disappear.
How can I explain the practical differences between a static site and a dynamic, database-backed e-commerce system? Should I document my concerns and implement what he requests, or start looking for another job?
4 Answers
Put your technical concerns in writing before making changes. Describe the risks plainly: loss of database functionality, exposure of customer information, traffic and usage limits, lack of backups, difficult rollbacks, search-engine disruption, and the extra work required for updates. Ask your boss to approve the trade-offs in writing, then follow the agreed direction rather than silently owning the consequences.
Create backups and use version control before touching anything generated by an AI tool. If code has already been lost once, that is a process problem, not just a coding problem.
Stop arguing in general terms and translate the disagreement into specific requirements. A static site can serve pages and images very cheaply, but it cannot by itself manage products, inventory, customers, orders, permissions, or sensitive data. Those features require a backend or external services, which means the supposed free solution still has infrastructure, security, maintenance, and integration costs.
Make a simple comparison showing what the business needs, where each piece of data lives, who can edit it, what happens if it fails, and the expected traffic. Also explain that removing hosting costs can simply replace them with more developer time and operational risk.
The important point is that static hosting is not automatically wrong; it is just only one layer. The business can use static pages for some content, but the transactional parts still need a properly secured backend.
You may not be able to change his mind. State your recommendation once, document the risks, and avoid making yourself responsible for an architecture you were not allowed to choose. Keep your résumé current and look for another position quietly, especially since he is already bypassing you and experimenting with production code.
Do not issue an ultimatum unless you are genuinely prepared to leave. A clear written record and a sensible backup plan are safer than waiting for the next outage to prove the point.
Give your boss a small, measurable demonstration instead of trying to win a debate. Build a simple static product page, then show what happens when you need inventory, customer accounts, checkout, order history, access control, or a product update across many items. Compare the monthly hosting cost with the labor and risk involved in manually maintaining static files.
AI can help explain the architecture or generate prototypes, but it does not remove the need for testing, security review, backups, and someone accountable for production failures.
An earlier AI-built change already removed much of the project after a bad repository and ignore-file setup. That is why I am especially worried about letting this continue without safeguards.