While I do see your experience and opinion as valuable, I simply cannot agree to your conclusion for the following reasons:
(2) It is “way” more cheaper than native: You write one code base in HTML/CSS/JS, and you deploy on “ALL’ 2 major platforms (again from experience). You also mentioned your hybrid team consisted of 4 devs compared to your native team of 1? That tells me you most defnitely hired some inexperienced developers i.e junior developers or people who weren’t as familiar with building hybrid apps. You then proceeded to compare them to what i can only assume is an experienced Android developer (since you only needed 1, otherwise, the work hours do not add up at all). This is most definitely not a valid comparison in any standard.
(3) In some cases, you experience less app updates “directly to the store” than with native — which means you get more patches/hotfixes to your users faster, and avoid app store friction. Please take a look at ionic deploy. I have used ionic deploy before and it works beautifully.
(4) One code base to support web/mobile — I have also built hybrid apps that i’ve hosted on a web server — I’m doing it now. In your scenario, if you had a web app version of your native app, you’d still need a web developer, and would still pay him for his work. That is never the case for me — in fact, my Hybrid project compiles to a “www” folder with HTML/CSS/JS, so I can deploy and host it fro ma webserver with no issues whatsoever.
What I’m trying to show you here is that your approach to Hybrid development is everything, and you chose an approach that was neither cost effective, not efficient.
Do more research into Hybrid and you’ll immediately see the benefits over native.