30 years in production,
not in an office.
I've spent my career as the conduit between the customer, production, IT, and the Executive team — which means I show up already speaking your operation's language.
I started in production, not in a strategy meeting — running production before I ever sat across the table proposing how to fix it. That's shaped everything since. I don't walk into an operation reading a process map for the first time; I've worked in the Adobe suite, staffed the help desk, and been the one explaining to sales why a job ran late. I know where the friction actually lives, not just where it shows up on a spreadsheet.
Over three decades I've led process improvement, systems integration, and prepress automation for print, packaging and corrugate operations ranging from single-plant turnarounds to global manufacturing networks spanning dozens of facilities — work that's added up to $100M+ in documented savings and consistent double-digit efficiency gains. Not from theory, but from standardizing what works and automating what's repeatable.
More recently, I've been applying that same discipline to AI and the various new tools — finding the handful of places in a production workflow where they genuinely reduce manual effort, without adding risk or noise to a process that already works.
Lone Star Prepress is how I bring that experience to operations that don't need a full-time hire — just someone who's already solved the problem.
I Don't Compromise On Principles
Start on the Floor
I audit the actual workflow — not the org chart — before proposing anything. Most bottlenecks aren't where the process document says they are. I ask 'why' alot!
Standardize Before you Automate
Automating a broken process just breaks it faster. We fix the process first, then automate what's actually worth automating.
No Engagement Without a Measurable Outcome
Every project ends with a number attached, not just a deck. If I can't define what "better" looks like, I won't take the engagement.
Right-Sized, not a Retainer
Most engagements are scoped and finite. I'm not in the business of selling ongoing dependency — I hand off something your team can run.
Let's talk about your workflow.
If it sounds like I've solved a version of your problem before — I probably have.