For most of my career, I’ve worked in operations.
Customer experience. Travel operations. Escalations. Large teams. Processes. Systems.
The kind of work where things look clean in PowerPoint until real life gets involved.
Over the last several months, I’ve been building out systems for my own business, The Knight Emporium — and honestly, it’s changed the way I think about AI completely.
What started as “let’s organize inventory better” turned into:
- Redesigning workflows
- Rebuilding reporting structures
- Separating operational truth from file storage
- Cleaning up years of process clutter
- Rethinking how systems should actually talk to each other
One thing I’ve realized very quickly: AI is not magic.
If your operations are disorganized, AI will scale the chaos just as fast as it scales productivity.
That part doesn’t get talked about enough.
The real value comes from forcing yourself to answer questions most businesses avoid:
- What is the actual source of truth?
- Which system owns what?
- What should be automated?
- What absolutely should not?
- Where does operational debt exist?
- What processes only exist because the system design is bad?
Over the last week alone, I’ve been restructuring our operational architecture around Postgres instead of scattered spreadsheets, folders, and disconnected tools.
Not because it’s trendy. Because operational clarity matters.
I’m not approaching AI as an influencer or an engineer.
I’m approaching it as someone who has spent years in operations and is now watching AI fundamentally change how businesses can be built, managed, and scaled.
This is where I’ll share that journey:
- The wins
- The mistakes
- The architecture decisions
- The operational lessons
- The reality of applying AI inside an actual business environment
Not theory. Not hype. Actual implementation.