The Alice Problem: How Software Startups Navigate Patent Eligibility Under 35 U.S.C. § 101

In June 2014, the Supreme Court issued Alice Corp. v. CLS Bank International, a decision that sent shockwaves through Silicon Valley, fintech, and any startup whose competitive moat depended on software patents. The case established a two-step framework for analyzing whether software-implemented inventions are eligible for patent protection under 35 U.S.C. § 101.

The Legal Background: Section 101 and Judicial Exceptions

35 U.S.C. § 101 states that "whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent." But the Supreme Court has long recognized three judicially created exceptions: laws of nature, natural phenomena, and abstract ideas are not patent-eligible, no matter how they are claimed. Software is, at some level, executing mathematical operations — abstract by nature. If taken to its logical extreme, the abstract idea exception would swallow virtually all software patents.

The Mayo/Alice Two-Step Framework

Building on Mayo Collaborative Services v. Prometheus Laboratories (2012), the Alice Court established a two-step test now embedded in MPEP § 2106:

Step 1: Is the claim directed to a patent-ineligible concept — a law of nature, natural phenomenon, or abstract idea?

Step 2: If yes, do the additional elements transform the claim into a patent-eligible application? They must amount to "significantly more" than the ineligible concept — generic computer implementation is not enough.

Alice's patents covered a computerized trading platform using a third-party intermediary to reduce settlement risk. The Court found intermediated settlement was an abstract idea, and implementing it on a generic computer didn't add "significantly more." The patents were invalid.

Claim Drafting Strategies After Alice

Claim the technical improvement, not the result. Claims directed to improving computer functionality itself — faster processing, reduced memory, improved network efficiency — tend to survive Alice better. The Federal Circuit's Enfish v. Microsoft (2016) held that claims directed to a specific technical improvement in how a computer operates can satisfy step 1 of Alice without even reaching step 2.

Include meaningful hardware limitations. Claims tied to specific hardware configurations are harder to characterize as purely abstract.

Use the specification to tell the technical story. Examiners look to the specification to understand what the invention actually does. A specification explaining the technical problem solved, why conventional approaches failed, and how the claimed invention solves it differently creates a stronger § 101 record.

The USPTO's 2019 Guidance

The USPTO issued revised § 101 guidance in January 2019, incorporated into MPEP § 2106, breaking the analysis into step 2A (prong 1: is it directed to a judicial exception? prong 2: does it integrate into a practical application?) and step 2B (does it add significantly more?). This is what examiners now follow and what the patent bar exam tests. Software patents are not dead, but the strategy for obtaining them requires careful attention to the technical story the claims tell.