Short answer: The rough first version of AgentShelf mattered because it turned years of Salesforce automation, flow design, and LLM experimentation into a working product direction.
I've never built software with others before LLMs gave me the ability to. I was always designing and automating in declarative tools like Flow but the sense of accomplishment afterwards made me feel great. I remember when flow builder introduced Record triggered flows, I was an associate admin at that time, and decided to take all the process builders we had in the org and migrate them. I wasn't asked to do this, I had no certifications at the time, I was just driven by pure interest and discovery. I was listening to Twenty one pilots a lot at the time so as I was looking at the logic that needed to be ported into flow, all I heard over and over was:
Sippin' on straight chlorine
Let the vibe slide over me
This beat is a chemical, beat is a chemical
When I leave, don't save my seat
I'll be back when it's all complete
The moment is medical, moment is medical
Sippin' on straight chlorine
The moment truly was medical in a sense that I had started to gain momentum as an associate admin. Prior to this, I had failed. I tried to take all the Case process builders and merge them into one process builder. I remember Gabe walking through the Process builder I had built - looking to troubleshoot it - maybe get it off the ground to not waste the effort. I really appreciated those sessions. It felt like editing a chapter, like reading something you wrote and then looking at the content to edit or adjust it-except it was declarative programming. Coming full circle and just like an intern training to become a resident, I found myself practicing with a new tool to accomplish the same goal as the previous endeavor-but this tool was more capable. Flow at the time of my associate admin career was starting to become the defacto go to for admins during the #clicksovercode era and it came at such a great time.
I found that the new structure I put in place, 4 different flows - Cases: When Created - before save, Cases: When created - after save, Cases: When Updated - before save and Cases: When Updated - after save - was a framework that was polished and had meaning. Just like a writer planning out a story, I took each part of the logic I wanted to port but put it instead into an excel sheet and then sliced and diced the narrative into proper sections. The result was a framework that was new and the best part is that I came up with it and it worked! That was my "when I leave, don't save my seat" moment cause I had left the literary world, the call center, and front facing customer world and entered into software. Which leads me back to developing Agentshelf on 1/5/2026.
Looking back at our first interface, it was rough but it had meaning. We wanted users who had never used LLMs before to do work, to understand the different parts of the platform we were creating. It was simple, but it was elegant. Just like the new solution I had created years ago as an associate admin - this solution was a young idea but a powerful one.
The interface though, was rough to look at. There was a lot everywhere, and I could see users getting overwhelmed. Our new design is more modern and sophisticated but its still not perfect. If I showed you a picture of the chat workspace today, you would hardly recognize it from the picture above. It's amazing to think that just like record triggered flows - with a new tool introduced - I've been able to take something like Claude Code, or Codex and run with it to design and build something that would typically take a team of software engineers.
