One person "teams" but reviewing and approving each others' work and then switching every six months or so, works well.
From what I have seen single person can deliver more and quicker than 2-5 people and having to seek approval from their peers keeps quality in check too.
In that case you don't have a one person team. You have a distributed team with effective communication and well designed systems that a single individual execute with minimal coordination. Which is the ideal but calling them one person teams is a misnomer.
A lot of the inefficiencies of bigger companies come from the redundant people needed to fill out the bus factor. Having a DBA on hand for emergencies might be overkill for a startup, but when you have revenue of 100 million per day depending on the database always being up it is much cheaper to have a spare person sitting around (even if they're not doing much most of the time).