We Didn't Start with Software. We Started with Chaos.
This didn’t start as a product idea. It started as a shared frustration between two post supervisors trying to keep shows on track with disconnected tools and way too many “final” cut folders. We weren’t trying to reinvent the wheel. We were just building internal fixes that actually made post easier. Eventually, those fixes became a system. Then the system became a framework. And that framework became SAMEpg. Here’s how it all happened.
Before there was a name, a website, or even a plan—there were just a lot of shows, a lot of moving parts, and a lot of us wondering: Why does post still feel like this?
We didn’t set out to build a product. We were just trying to survive the daily chaos of unscripted TV post-production.
We were both working on fast-paced shows with tight schedules, scattered assets, overlapping teams, and no shortage of “Can you just check this one thing real quick?” messages. The tools were there—Google Sheets, Slack, Box, Airtable—but they weren’t built to work together. And they definitely weren’t built for post.
So we started building little fixes. Not code—just systems. Smarter spreadsheets. Cleaner file structures. Simple automations. Things to reduce friction and buy back time.
And they worked. Suddenly, version tracking wasn’t a daily fire. Cut delivery wasn’t a scavenger hunt. People were spending less time double-checking and more time actually doing their jobs.
That’s when we realized something: we weren’t just building band-aids. We were building a framework.
Over time, those internal systems evolved into what SAMEpg is today:
A customizable, post-specific workflow layer
Built by people who’ve lived the pain
Designed to integrate with the tools teams already use
And tested in the same production chaos we deal with every day
SAMEpg didn’t come from theory. It came from years of trial, error, and iteration in real unscripted pipelines. We didn’t guess what teams needed—we lived what teams needed.
We didn’t start with a software idea. We started with a problem we couldn’t ignore anymore.
SAMEpg is our answer to that problem—and we’re still building it with the same mindset:
Don’t disrupt. Just fix what’s broken.
See the SAMEpg Difference
If you’re running a post pipeline that works—but barely—we’ve been there. Let’s talk about how we can help streamline it, without disrupting what’s already working.
Craig Thorogood
Post Supervisor & Co-Founder, SAMEpg