Stop “Working on the Business." Get Back to the Architecture.
If you own or run an architecture firm, you've heard the advice a hundred times: "Work on the business, not in the business." It comes from Michael Gerber's E-Myth, and it's been lifted into every leadership deck, coaching program, and LinkedIn post aimed at professional services owners.
For you, it's mostly wrong.
Somewhere along the way, "work on the business" got translated into "spend your day on admin, HR paperwork, invoicing, insurance renewals, and project management dashboards." You're drifting further and further from the one thing your firm was built around: your architecture.
Here's the reframe.
1. You are the product
Your clients didn't hire your firm for its project management software or its timesheet system. They hired it for your judgment — the way you read a site, push back on a program, or know when a detail is going to cause problems two years into operations.
That judgment is your firm's highest-margin output. It's also the hardest thing to replace, train for, or systematize. Every hour you spend away from the work is an hour your main asset sits idle.
2. Admin is the most expensive work you can assign yourself
If your effective value to the firm is $400–$600 an hour — across billable design, BD, mentorship, and the judgment calls no one else can make — then putting yourself on tasks a $30/hour coordinator could handle is a genuinely irrational economic decision. You wouldn't hire a senior architect to sort mail. You're doing the same thing when you approve expense reports.
The hidden cost isn't just the admin hour. It's the design hour you didn't get to, the client conversation that didn't happen, and the drawing you're reviewing at 10pm because you spent the day in QuickBooks.
3. "Work on the business" was written for businesses that scale without the owner
Gerber was writing about franchises — businesses engineered to run without the founder present. Architecture doesn't work that way. The best firms are built around the taste and judgment of specific people, and clients know it. A firm that successfully removes its principal from the work has usually removed the reason clients chose it in the first place.
Working on your business, as an architect, doesn't mean stepping away from production. It means building the systems, teams, and protections that let you keep showing up in the work.
4. Paperwork is a delegation failure, not a leadership task
Most of the admin you're buried in — timesheet approvals, invoice reviews, insurance forms, HR questions, contract routing, software renewals — is structurally delegable. It stays on your desk because the firm hasn't built the operational layer to handle it. No ops lead. No clear SOPs. No empowered project managers. No outside bookkeeper. No fractional CFO.
Fixing that is the real work on your business. Not doing the paperwork — eliminating it from your plate entirely.
5. Protect your production time the way you'd protect the firm's IP
If your design hours are the firm's most valuable output, they deserve the same protection you'd put around any other critical asset. That means blocking calendar time for architecture that nothing short of an emergency can move. It means routing client calls and admin requests through a gatekeeper. It means saying no to internal meetings that don't actually require you in the room.
A firm that routinely lets admin bleed into its principal's design time is telling its people — and its clients — what it really values.
The bottom line
The accepted wisdom says a good principal is one who has successfully stepped back from the work. The math, the market, and your clients say the opposite. You're your firm's highest-leverage architect and its most expensive admin at the same time — and every week, you're choosing which one you want to be.
Stop pulling yourself out of the architecture. Build the firm around keeping yourself in it.