About
I like making things simpler.
I’m Seth Sager: an entrepreneur, builder, and systems thinker. I build products, rethink systems, and explore ideas that make technology more useful and life a little more human.
My background is in manufacturing, supply chain, and operations. That work trains you to ask a plain question over and over: what is actually happening here, and what is the smallest change that would help? I still start there, whether the thing in front of me is a production line or a piece of software.
I build because it is the fastest way to find out if an idea is any good. Ideas are easy and everyone has them. Making one real, getting it in front of people, and learning from what happens is the interesting part.
What I care about
- BuildingEntrepreneurship, products, software, experimentation, open technology.
- ThinkingSystems, manufacturing, leadership, AI, economics, and society.
- ConnectingHuman relationships, communication, communities, education, and podcasting.
How I try to work
Keep it simple. Prefer open technology and tools that leave people in control of their own information. Use AI where it helps, and keep a person at the point of decision. Stay curious, stay grateful, and talk to interesting people.
Beyond the code
Built on experience.
I’ve spent over 20 years in manufacturing, supply chain, and operations, working to understand how things work, where they break down, and how to make them better. Four parts of that work show up in nearly everything I build.
Manufacturing & Operations
A plant is a system you can walk through. You can see where work waits, where it gets done twice, and where one small fix saves the next shift a lot of trouble.
Continuous improvement turned that noticing into a habit: try something small, check whether it worked, and keep what you learned.
Supply Chain & Procurement
Nothing is made alone. Every product depends on parts, suppliers, timing, and trust, and a small gap upstream shows up as a large problem downstream.
It taught me to look at the whole chain instead of one step, and to be wary of any plan that only works if everything goes right.
Leadership & People
Processes are carried out by people, and the people closest to the work usually know where the problems are.
Changes stick when those people help shape them. Leading, to me, is mostly making the next step clear and listening for what’s getting in the way.
Systems & Technology
Tools should fit the work, not the other way around. Whether it’s a process on paper or software on a screen, I ask the same questions: what is this for, who is using it, and what would make it simpler?
I wrote about this in The Same Principles, Different Products.
How it shapes what I build
I start with a real problem and try to understand it before I build anything. Then I make the simplest version that could work, put it in front of real use, and let what happens decide what comes next. That habit comes from the plant floor, and it carries into products that have nothing to do with a factory.
LoopSignal is the most direct example: software that keeps problems, evidence, countermeasures, verification, and learning connected on a manufacturing floor. The rest of what I make comes from the same curiosity pointed somewhere new.
The projects are on the work page, the podcast is Connection, and what has my attention right now is on the now page. If you want to talk, start here.