Subsilo

3 months ago, I started building Subsilo with a simple goal: stop losing money to silent subscription renewals. I thought using AI tools like Claude Code and Cursor would speed everything up. Instead, it turned into the familiar struggle every AI-assisted coder knows too well. Code that appears to be correct but breaks during execution. Files rewritten in ways you didn’t ask for. Refactors that solve one bug and quietly create three more. Constant context drift. Hours spent debugging problems you never would’ve made yourself. At some point, you’re no longer “accelerating development.” You’re cleaning up after a machine that writes confidently and incorrectly. Subsilo only became real when I stopped trusting the AI layer and rebuilt every screen, every flow, every edge case by hand. That’s when the product stabilized. That’s when it started feeling like software, not guesswork. Today, Subsilo is exactly what it needed to be: a focused tool that prevents accidental renewals and exposes where money is quietly leaking. It’s the result of using AI where it helps, overriding it where it harms, and finishing the job like a real engineer.