The 70/30 Method

The 70/30 Method is a simple rule for where effort should go.

Roughly 70% of the work in any business is repeatable — the same steps and the same decisions, run over and over. That work should be automated: handled by systems and AI agents that never get tired, never skip a step, and never have an off day.

The other 30% is where judgment lives — the calls that need taste, context, relationships, and someone accountable for the outcome. That stays with people.

It's the same principle behind how I build software, which I call 70/30 Engineering: AI agents handle the mechanical 70% — scaffolding, boilerplate, the first draft of nearly everything — while senior judgment owns the 30% that decides whether the result is any good. The Method just applies that split to the whole business.

The 70% is the work that follows a pattern. Once you start looking for it, it's everywhere:

• Chasing leads, sending follow-ups, and updating the CRM
• Reporting, reconciliation, and moving data between tools
• Scheduling, reminders, and routine customer questions
• First drafts — proposals, summaries, replies, content
• Onboarding steps that happen the same way every time

The point isn't to reinvent any of this. The 70% is built on proven tools and platforms, wired together and supervised by agents — not a pile of custom software you have to maintain forever. You automate the boring, repeatable majority so it runs reliably in the background.

The remaining 30% is the work machines shouldn't own — because getting it wrong is expensive and getting it right needs a human:

• Judgment — the architecture, pricing, and strategy calls you live with for years
• Relationships — the conversations that close deals and keep customers
• Edge cases — the weird, high-stakes situations a script can't anticipate
• Knowing what not to do — the most valuable decision there is

This is where your people should be spending their time. The Method exists to protect that 30%, not to shrink it.

There's a second 70/30 split hiding inside the first.

Most teams spend nearly all their energy just running the business — keeping the lights on, clearing the queue, answering the same questions. There's nothing left over to make next month easier than this one.

When the repeatable 70% is automated, that flips. Your team spends ~70% running and reserves ~30% to improve the system itself: tightening workflows, removing friction, teaching the agents to handle more. Those improvements compound. The business gets a little more capable every week instead of just staying afloat.

The 70/30 Method isn't about doing more with less. It's about pointing your best people at the work that actually moves the business.

• Speed — the repeatable work happens instantly, around the clock
• Lower cost — you don't hire headcount to do what a system can do
• Focus — your team spends its time on judgment, not busywork
• Compounding gains — every improvement to the 70% pays off forever

The 70/30 Method is the philosophy. An Agentic OS is how you deliver the 70% in practice — the connected layer of agents that actually runs the repeatable work.