This static site project didn't cost much for my client. I wrote the entire engine over a span of close to 2 years using my personal time over the weekends, try

This static site project didn't cost much for my client. I wrote the entire engine over a span of close to 2 years using my personal time over the weekends, trying to re-write it in different languages, frameworks, etc.I did a re-write in all possible methods out there - Including Jekyll, Middleman, Hugo, etc. In the end, I settled with Elixir / Phoenix. Money, if you factor in my personal time valued at $X00 USD/hr, then yeah, multiply that with 8 hours a weekend for 2 years, that was probably the cost. For my clients? Just about a month. The clients didn't lose any opportunity because of this move. They were still on Wordpress as this was being tailored for them. These OTS static site generators are fine for small sites, but at the scale of our clients who have more than 30k posts and counting, none of these would be able to handle it. When I say handle it, I also am referring the time taken to generate 30,000 posts in the shortest possible time. In a custom solution, you're able to optimize this heavily. I brought it down to 30 minutes from 1.5 hours for 30k posts. Why not simply add a caching layer infront of a Wordpress instance? For starters, this is a media company, so they would like to have instantly updated posts on certain parts of their site. For that, you need to disable caching. Which means tens of thousands of requests are hitting your instance every minute. So, that means you need a high performance server + SQL instance (Expensive). It worked out to $3000USD per month just for servers alone. The static site generator use just $100/month instance, for comparison. Of course, there is also the development cost for the client for this solution, but I can comfortably share that their ROI would be less than a year if you factor just server costs alone. There are many other bonuses with a custom static solution - Your whole theme can be broken down into an MVC paradigm which makes future integrations super clean and easy. Codebase maintainability also has improved drastically - partly because of the language itself (Elixir) and partly because of the MVC architecture.