"One-man army" sounds heroic until you do the arithmetic. Here's a real week, not an aspirational one.

The actual hours

• 27 hrs building — split across long-running client work and my own products.
• 6 hrs client calls and the email around them.
• 4 hrs writing — these posts, docs, the occasional proposal.
• 3 hrs fixing yesterday. There is always a yesterday.

That's a full 40 billable hours a week — not including the standard overhead (inbox triage, scheduling, invoicing, the admin every freelancer carries) that rides on top. The trick isn't working fewer hours; it's making sure the forty that get billed are the forty that matter.

How it stays standing

One deep-work block a day that nothing is allowed to interrupt. Ruthless defaults: no standing meetings, async unless it's genuinely faster live, and a hard stop most evenings. Two products stay alive not because I work more hours but because I protect the few that count.

The honest caveat

This works because it's one person who owns the whole stack and answers his own email. It does not scale by adding hours — only by saying no. The day the no's stop is the day the army loses.