Intelligence Heavy Work Automates Before Judgement Heavy Work
Claim
AI autopilots will win first in domains where most of the work is rule-bound intelligence, while judgment-heavy domains remain human-led for longer.
Raised by
- 2026-03-05-sequoia-services-the-new-software - julien-bek / sequoia-capital uses the intelligence-versus-judgment distinction to explain why coding moved first and to rank services opportunities.
Supporting evidence
- 2026-03-05-sequoia-services-the-new-software - points to software engineering as the first high-adoption category, then maps services verticals by intelligence intensity versus judgment intensity.
Counter-evidence
- (unknown - needs source) Some judgment-heavy work may be decomposed into narrow intelligence tasks faster than expected, while apparently rule-bound work may hide hard exceptions, liability, or data-access problems.
Implications
- Vertical selection should score workflows by rules density, exception frequency, verifiability, and liability.
- The first agent should attack repeatable task execution before trying to own strategic judgment.
- Human-in-the-loop design should be explicit: humans keep judgment and sign-off where the system has not earned autonomy.
Ideas this favors
- human-in-the-loop-accountability - because high-judgment seams need approval even when intelligence work is automated.
- full-stack-ai-vertical-services - if the service can split AI execution from licensed human judgment.
- agent-native-go-to-market - because coding-agent adoption is the proof point for high-intelligence work moving first.
Ideas this weakens
- First wedges that require nuanced executive judgment, negotiation taste, culture fit, or strategy from day one.
- Broad “autonomous consultant” ideas before the intelligence subcomponents are isolated.
Confidence
Medium. The framework is useful, but each vertical needs operator validation because the line between intelligence and judgment is often hidden in edge cases.
What would change our mind
- AI systems prove reliable in judgment-heavy workflows before rule-bound services verticals show adoption.
- Buyers care more about trust, brand, and accountability than intelligence ratio when choosing providers.
- Data-access and exception handling dominate automation difficulty more than the intelligence-versus-judgment split.