One of my biggest takeaways from doing that for a couple years is how dramatically productivity can swing based on factors like the texture of the project, the clarity of the goal, the freedom of the TL to make judgment calls without needing to get approval from a BA, morale, the quality of the spec (note that quality != length), etc.
No reason a small dedicated team cannot build large products with reasonable deadlines and a balanced lifestyle. Though, in the interest of full disclosure, in my opinion 50 hours a week is fully balanced and a team can run at 50 hours pretty consistently without ill effects if they WANT to and are HAPPY with their mission and job.
"Nine women can't make a baby in one month"
The saying here is essentially akin to too many cooks spoil the broth. Put it this way: 1 brick layer can lay 9ft of brick in 9 days (no factuality here). If you're building a wall you can only go one row at a time. 2/3 brick layers will speed up the process. However 9 brick layers won't produce a 9ft tall brick wall in 9 days because 6 brick layers will be sat on their arses drinking coffee.
9 brick layers can produce 9 9ft walls in 9 days, but won't be producing a 9ft wall in a day 9 days continuously working as a team.
The statement doesn't preclude that work can be produced efficiently, for example you could easily have 4 brick layers build 4 9ft walls - AKA a house - in 9 days.
The aim is to find your fundamental limit and work with it. If you need a baby every month, sure plan ahead and you could have a baby monthly starting in 9 months, if you can account for that 9 month waiting period. You will never get a baby in 1 month with a team of 9 women and only 1 of them being pregnant.