I didn’t start out trying to build a product. I was just trying to get through the week.

As a post supervisor juggling multiple shows, I saw the same problems over and over: emails lost in the shuffle, approvals delayed, teams working from slightly different spreadsheets. It wasn’t about one broken tool—it was the entire workflow duct-taped together.

On one show, I spent three hours chasing down a single missing VO pull—across five tools and three time zones. Not because anyone dropped the ball. Just because the system didn’t catch it. That’s when it hit me: this isn’t a people problem. It’s a workflow problem.

At first, I built templates. Then checklists. Then systems that actually reduced the chaos. That eventually became SAMEpg.

But here’s the thing: I never wanted to create another app. Production teams don’t need another login. What they need is a system that thinks like they do—one that fits their tools, not fights them.

So I built a framework. One that adapts to the way your team already works, instead of forcing a reset. One that’s 80% ready to go—and tailored for the final 20%. It’s not software in the traditional sense. It’s a smarter structure, designed by people who’ve actually been in the trenches.

And it works. Because it was never about “building tech.” It was about building clarity into chaos.