-A simulation software for electrical engineers would get an update every 6 months. Keep in mind there was a robust pipeline and most projects or new key features would take 12-24 months to develop, as it involved some combination of new (to us) physics and optimization of the engine with hardware. Most users wouldn't even install the updates because they didn't want their simulation to break.
-A consumer health would update every couple of months, with beta tests organized for every new feature every sprint (2 weeks). This was basically a secure CRM with video feed and fluff and the side. We had a team of 8 devs.
So I would compare myself to others in my boat, i.e. level of product complexity, team size, and the target market.
Also get to the root... Why can't these people ship? Is it lack of experience leading to an underestimation of the work required? Is it perfectionism? Are they just not good? Do they not know when to say "this is done"? The solution here is to go spend 5-10 years learning all this at an established, profitable company