Owers LLC
ProductionJune 15, 2024
My company — Owers LLC, at owers.llc. The successor to We Are 101 as a business entity. The website is very behind despite dozens of web apps being deployed since. A meditation on the erosion of projects without constant attention, why maintenance is where the money is, and the business model of vendor lock-in and retainers.
Purpose
Owers LLC is the business entity — the legal container for professional work, the EIN for contracts, the name on invoices. The website at owers.llc exists but has fallen behind as attention went to shipping other projects. It is the cobbler's children again: the company that builds web apps has a stale website.
Stack
What I Learned
- Projects erode without constant attention. Dependencies go out of date. SSL certificates expire. The design that looked current 18 months ago now looks dated. Content that was accurate becomes misleading. A deployed web app is not a painting you hang on the wall — it is a garden that grows weeds. Every site in this blog that is "production" is also silently decaying unless someone is actively maintaining it.
- Creation is amazing. There is genuine elation in building something new — the first deploy, the first user, the first time someone says "this is cool." Destruction has its own energy too — ripping out a bad architecture, deleting dead code, sunsetting a project that served its purpose. Both are emotionally charged and satisfying. But maintenance — keeping the thing running, updating dependencies, fixing the CSS that broke in a new browser version, renewing the domain — is where the money is. Maintenance is not glamorous. It is essential. And it is the phase most solo developers refuse to enter.
- The business model of agencies and freelancers who thrive is not project fees — it is retainers. A retainer is a recurring monthly payment for ongoing maintenance, updates, and support. Build the site for $5,000 (one-time). Maintain it for $500/month (recurring). The build is the loss leader. The retainer is the business. Over two years, the retainer revenue ($12,000) exceeds the build fee. The client gets a site that stays current. The developer gets predictable income.
- Vendor lock-in is the strategic advantage that makes retainers work. When you build a client's site on your stack, with your deployment pipeline, using your accounts (hosting, domain registrar, analytics, CMS) — the client depends on you to keep it running. This is not nefarious when done transparently: the client is paying for the convenience of not managing infrastructure. It becomes nefarious when the dependency is hidden or when migration is intentionally made difficult. The ethical version: document everything, give the client access to all accounts, and make your value about expertise, not hostage-taking.
- The difference between ethical vendor lock-in and hostage-taking: ethical lock-in means the client stays because switching would be inconvenient and your service is good. Hostage-taking means the client stays because you control their domain registrar login and they do not know the password. One builds a long-term relationship. The other builds a lawsuit.
Key Insights
- Creation, destruction, and maintenance map to the three emotional modes of building software. Creation is the startup energy — everything is possible, the codebase is clean, the vision is pure. Destruction is the refactoring energy — tearing out what does not work to make room for what does. Maintenance is the operations energy — the steady, unglamorous work of keeping systems alive. Most developers are drawn to creation, tolerant of destruction, and resistant to maintenance. The market pays the most for maintenance because the fewest people want to do it.
- The owers.llc website being behind is not a failure of the company — it is a prioritization signal. The time that would go into updating the company site went into building Potatuhs properties, deploying client projects, and writing code that generates revenue. The cobbler's children have no shoes because the cobbler is busy making shoes for paying customers. The fix is not more discipline — it is a retainer with yourself: schedule 2 hours per month for your own properties.
- For any developer considering freelancing or starting an agency: the retainer model is the path to sustainability. Project-based work creates income spikes followed by drought. Retainer-based work creates a baseline that covers expenses. Even a small retainer portfolio (5 clients at $300/month = $1,500/month baseline) transforms the financial psychology of independent work from scarcity to stability.
- The erosion of projects over time is the strongest argument for simple architecture. A static HTML site from 2018 still works. A React app from 2018 has 47 outdated dependencies and three abandoned packages. The simpler the stack, the slower the erosion. This is why the current brettowers.com uses static data files instead of Appwrite — fewer moving parts means fewer things to maintain.
This post was composed through a conversation between Brett Owers and Claude Code (Anthropic). The content reflects Brett's recollection of each project and the lessons drawn from it. Some details may be approximate or omitted — the purpose is to paint an honest picture of a software engineer's development over time, not to serve as a precise historical record.