Billing more than one client? The hard part is not the work, it is keeping the hours straight.
A day spent jumping between three projects produces hours that blur into one pile, and at invoice time you are guessing which client each chunk belonged to. Memory rounds down, so you undercharge. The fix is not working more. It is one project per client and a timer that knows which clock it is on, so every hour lands on the right invoice.
A team of 8 has 28 possible communication paths. A team of 16 has 120. That is n(n-1)/2, geometry, not management.
In six years inside corporate dev teams, the calendar-time ratio of solo versus team for the same feature ran 20x to 60x. Not because the people were slow, but because the system extracts a tax that scales with its size. The day you go solo, you stop paying it.
Agencies routinely underbill around 10% of their hours. Not fraud, just leakage: the 12-minute Slack triage, the 'quick' call, the context switch nobody logs because it felt too small to write down.
The fix is not working more. It is making the small stuff visible. You cannot bill what you never recorded, and you cannot scope the next project when last project's hours are a guess. Track the tiny interruptions for a week and the gap between worked and billed stops being invisible.
The real change AI brought solo founders was not speed.
It is that AI-generated design gave backend-first developers a starting point we never had. For years the blocker was not 'can I build it', it was 'I open a blank frontend and freeze'. That one barrier falling is why solo founders went from 23.7% of new startups in 2019 to 36.3% in 2025. The window did not open because we got faster. It opened because the thing that used to stop us at step one stopped stopping us.
The default 2026 solo freelancer stack: Toggl Track for hours (~$10/mo), Bonsai for invoices (~$25/mo). About $420 a year on paper.
The real cost is the Friday reconciliation: moving hours into invoice lines, chasing mistagged entries, roughly 45 minutes a week. At a $75/hr effective rate that's ~$2,900 a year of unbilled labor. The two-tool stack survives because nobody invoices themselves for reconciliation.
A team of 8 has 28 possible communication paths. A team of 16 has 120. n(n-1)/2, geometry not management.
In six years inside corporate dev teams, the calendar-time ratio of solo vs team for the same feature ran 20x to 60x. Not because the people were slow. Because the system charges a coordination tax that scales with its size, and the day you go solo you simply stop paying it. That, not raw talent, is why one person can now move so fast.