Why This Exists
Software pricing has drifted away from usefulness and toward leverage.
Simple tools — clipboard managers, file converters, focus timers — charge subscription fees that bear no relation to their cost of maintenance. This isn't because software is expensive to build. It's because the market is structured to let a few options charge whatever they want.
AI changes that equation. Not in theory — right now. A small team with modern tools can build, maintain, and improve a growing suite of apps for a price that makes the old model look absurd.
This suite is an attempt to demonstrate that. Instead of charging for access, it charges for continuation. Instead of fragmenting tools, it lets them accumulate. Instead of optimizing for retention, it assumes trust.
If that sounds familiar, you're probably the kind of person this was built for.
Principles
1. Use Comes First
Software should be usable before it is monetized. People should be able to experience value before being asked to support it. Payment is a response to usefulness, not a prerequisite for it.
2. Payment Sustains, It Doesn't Unlock
Payment is not permission. A subscription sustains continued development and gives access to everything as it grows. It is not framed as an “upgrade” in dignity.
3. Tools Accumulate
Value should compound, not fragment. Instead of charging separately for small, overlapping functions, tools are allowed to accumulate within a shared suite — one relationship, growing usefulness over time.
4. Requests Flow Upward
Users influence what gets built next. Not through tokens, votes, or engagement metrics — but by expressing real needs. Roadmaps are shaped by use, not by extraction.
5. Exit Is Cheap
Leaving should be easy and unpunished. No dark patterns. No hostage data. No shame language. If the software stops being useful, the relationship ends cleanly.
6. Infrastructure Is Shared
New tools reuse what already exists. Authentication, design systems, sync, and patterns are reused so that new software doesn't require new cognitive or financial overhead from users.
7. Growth Is Not the Goal
Sustainability is. The aim is to build software that can be maintained with care — not to maximize users, revenue, or attention. Growth is allowed, but never required.
8. This Is Not a Platform
There are no lock-ins disguised as ecosystems. Data belongs to users. Tools should interoperate. Nothing is designed to make departure costly.
9. This Is a Lineage, Not a Brand
These principles aren't owned. They can be adopted, adapted, or ignored. There is no certification, no enforcement, and no central authority. Recognition is social, not contractual.
10. Software Can Have Manners
Software shapes behavior. These principles exist to encourage tools that are calm, legible, and respectful of attention — especially in parts of life that are already fragile or overloaded.
This software is built in the shareware tradition: useful first, supported if it lasts.
For Developers
What This Is
This is not a framework, license, foundation, or platform. It's a shared orientation toward how software is built, priced, and related to — especially when a single developer or small team can now build far more than before. If this matches how you already work, you're already part of it.
What Adopting These Principles Means
You don't need permission, approval, or certification. Adoption can be as simple as:
- Writing your own “Why this exists” in similar terms
- Letting users use before they're asked to pay
- Pricing for continuation rather than access
- Treating exit as a normal outcome, not a failure
- Reusing infrastructure so new tools feel additive, not extractive
What This Is Not
- Not a growth strategy
- Not anti-commercial
- Not a rejection of subscriptions outright
- Not a demand for pay-what-you-want pricing
- Not a purity test
You can charge money. You can earn a living. You can say no to requests. The only constraint is how power is exercised, not whether it exists.
On Discovery
If you adopt these principles, you're encouraged — but not required — to:
- Link to this page
- Add a short line like: “Built in the shareware tradition.”
There is no registry. No central list. No authority. Discovery is meant to be organic, not administrated.
On Forking the Idea
You are free to adapt this. Rewrite the principles. Narrow them. Extend them. Apply them to a specific domain. If the idea spreads, it should do so because it's useful, not because it's defended.