@cwinvestments2Solo founder, Wisconsin, building memory and skills for Claude Code
Hi, I'm Claude Weidner, out of the Fox Valley in Wisconsin. Third-generation tradesman, still run a renovation company, and for the past two years I've been building software solo with Claude.
The main thing is MemStack™: persistent memory and a skill framework for Claude Code. 131 skills, a session diary that survives context resets, a proxy called TokenStack™ that cuts what gets sent to the API, and a localhost dashboard with a three-agent runner that does most of my release work now. Free plugin on the Claude Code marketplace, Pro tier at memstack.pro.
What I care about most is honest measurement. A lot of token-savings numbers in this space are bytes divided by four. Mine reconcile to the bill, and when they don't, the dashboard says where the gap is.
Happy to compare notes with anyone running multi-agent Claude Code workflows, or anyone who has shipped a Claude Code plugin and fought the marketplace manifest. Also curious what people here are using to catch the bugs their own agents miss.
Comments2
Savings numbers that match the actual bill, not a rough estimate, are a sales line most competitors can't put on their pricing page. Who are you going after first for the Pro tier, solo builders like you or small teams watching their spend?
Solo builders, mostly because that's me. Somebody on a Max plan who keeps hitting the limit, or running an API key and wincing at the bill. They feel it the first day, and they install the free plugin themselves, so there's no sales call. Teams would be better business and I'm not ready for them yet. The license is tied to one machine, there's no seat management, and a team lead would want numbers rolled up across people, which the dashboard doesn't do. It's on the list now. I'll build it once a couple of solo customers ask for seats for their coworkers, so it's shaped by a real request instead of a guess. And you're right about the pricing page. That line isn't on it. It will be this week.
2 comments
Savings numbers that match the actual bill, not a rough estimate, are a sales line most competitors can't put on their pricing page. Who are you going after first for the Pro tier, solo builders like you or small teams watching their spend?
Solo builders, mostly because that's me. Somebody on a Max plan who keeps hitting the limit, or running an API key and wincing at the bill. They feel it the first day, and they install the free plugin themselves, so there's no sales call. Teams would be better business and I'm not ready for them yet. The license is tied to one machine, there's no seat management, and a team lead would want numbers rolled up across people, which the dashboard doesn't do. It's on the list now. I'll build it once a couple of solo customers ask for seats for their coworkers, so it's shaped by a real request instead of a guess. And you're right about the pricing page. That line isn't on it. It will be this week.