Contents
How It Works
— DHH, Co-founder of Basecamp & HEY"The subscription model has been a bonanza for software companies and a raw deal for customers. We think there's a better way."
When to Use This Framework
Best Conditions for the One-Time Payment Alternative
| Dimension | Ideal conditions |
|---|---|
| Founder profile | Product-focused builders who can ship polished software with a small team. You need strong technical execution but not breakthrough R&D. Ideal for indie developers, small studios, or bootstrapped teams who don't need to optimize for ARR metrics that impress VCs. |
| Stage | Ideation through early growth. The framework is strongest when choosing what to build and how to price it. Less useful for companies already locked into subscription billing with existing customers. |
| Market conditions | Best when a dominant incumbent has recently forced a subscription migration that users vocally resent. Look for Reddit threads, Twitter complaints, and app store reviews with phrases like "used to be a one-time purchase" or "not worth the monthly fee." Adobe's 2013 shift to Creative Cloud is the canonical trigger event. |
| Product category | Desktop-heavy or offline-capable software where the core value doesn't depend on cloud infrastructure, real-time collaboration, or network effects. Think: design tools, text editors, note-taking apps, video editors, PDF tools, email clients. Avoid: CRMs, project management tools with team collaboration, or anything where the cloud IS the product. |
| Competitive environment | Ideal when the incumbent is large enough that they cannot credibly revert to one-time pricing without destroying their valuation. Adobe cannot offer a $300 perpetual Photoshop license without Wall Street punishing them. This structural constraint is your moat. |
| Inputs needed | Feature audit of the incumbent product, user sentiment analysis (Reddit, G2, Capterra reviews), pricing sensitivity research, competitive landscape scan, and a realistic cost model for sustaining development without recurring revenue. |
When It Misleads
Failure Modes & Blind Spots
| Blind spot | What goes wrong |
|---|---|
| Revenue sustainability trap | One-time purchases create a lumpy, front-loaded revenue curve. You get paid once per customer, then need to find new customers forever. Without a strategy for paid upgrades, add-ons, or new product lines, you hit a revenue ceiling that makes ongoing development economically unviable. |
| Feature treadmill exhaustion | The incumbent ships updates monthly, funded by recurring revenue. You ship updates funded by... what? If users expect continuous feature development but you've already collected their one-time payment, you're subsidizing development from a shrinking pool. Affinity addresses this with paid major version upgrades; others haven't figured it out. |
| Cloud-dependent categories | You try to build a one-time purchase alternative to Figma, Notion, or Slack — products where the cloud infrastructure, real-time sync, and collaboration features ARE the product. The ongoing server costs make one-time pricing structurally impossible without degrading the core experience. |
| Ecosystem lock-in underestimation | Users may hate Adobe's pricing but they're embedded in the Adobe ecosystem — file formats, plugins, team workflows, training. Switching costs are higher than the pricing frustration. You win the argument on price but lose the sale on inertia. |
| VC incompatibility | Venture capital rewards recurring revenue. A one-time purchase model generates lower LTV, less predictable revenue, and worse unit economics by VC metrics. If you raise venture money for this model, you'll face constant pressure to add subscriptions — which defeats the entire positioning. |
| The "good enough" ceiling | You build 80% of the incumbent's features and attract price-sensitive users. But the remaining 20% — the features that power users and enterprises depend on — is precisely what justifies the subscription. You end up serving the least valuable segment of the market. |
Step-by-Step Process
Find subscription products with vocal pricing resentment
Map the feature gap between essential and nice-to-have
Model the economics of one-time pricing
Ship a focused MVP that wins on the core workflow
Make the pricing model your primary marketing message
Questions to Ask Yourself
Company Examples

Adjacent Frameworks
Analyst's Take
Opportunity Checklist
One-Time Payment Alternative Scorecard
Top Resources
Why this matters next
Affinity applied the Network Effects mental model
Affinity applied the Inertia mental model
Affinity applied the Narrative mental model
Affinity applied the Scale mental model
Affinity applied the Environment mental model
Affinity applied the Feedback mental model
Continue exploring
Framework
Recent funding rounds
Analyze companies that have recently secured significant investment, identifying
Framework
Unbundling
Breaking down a bundled product or service into separate, standalone offerings,
Framework
Industry timing arbitrage
Apply newly developed technology from one industry to another that hasn't yet ad
Framework
Acqui-Deaths
Identify opportunities created when large companies acquire startups, potentiall
Framework
Three-Star reviews
Find business opportunities by analyzing moderately satisfied customers' feedbac
Framework
Niche down
Focus on a highly specific market segment or customer base, becoming a specialis
More like this, in your inbox
I send a newsletter every week — free, no spam, unsubscribe anytime.