Film, media, and entrepreneurship
Studied Film and Media Production at Arizona State University, supported by entrepreneurship grants that connected creative work to building ventures.
About the Founder
Litbox OS grew from the same experience many founders know well: the business is moving, the opportunities are real, and too much still depends on one person remembering what happened, deciding what comes next, and keeping everyone aligned.
I built Litbox because I needed a better way to turn what lived in my head into a system other people could understand, use, and improve.
The founder pattern
Customers learn to call the person who always knows. Team members learn to wait for that person’s answer. Important exceptions, preferences, and decisions accumulate in one person’s memory.
Then the business grows. More projects create more handoffs. More customers create more communication. The founder who once made the business move faster gradually becomes the place where work slows down.
That is not a personal failure. The business has outgrown an operating system built around one person’s attention.
The lived experience
My path has moved through film production, entrepreneurship, contracting, marketing, business development, and AI systems.
Across those environments, talented people were rarely the problem. The problem appeared in the space between them. Information did not always reach the person who needed it. Decisions were not consistently preserved. Lessons remained inside individual experience.
Founders often become the person who notices every gap and carries the missing context across it.
Career timeline
The path to Litbox was not a straight line. Each stage exposed another part of the same question: how does complicated work keep moving when knowledge, judgment, and coordination are distributed across people?
Studied Film and Media Production at Arizona State University, supported by entrepreneurship grants that connected creative work to building ventures.
Worked across television, post-production, and entertainment environments, including TNT and TBS, MTI Film, CBS, and Showtime projects.
Built ventures, developed brands, produced media, and learned what changes when sales, delivery, relationships, and risk all return to the founder.
Produced Vinnie Plays Vegas through production, premiere, distribution, and public release. The work made coordination, persistence, and institutional memory impossible to treat as abstractions.
Appeared as a guest on Chris Voss’s television show, That’s Right, where he interviewed me on camera.
Built and operated inside contractor-led work, where estimates, schedules, crews, clients, inspections, and field decisions exposed the cost of missing context.
The lessons converged into one product: an AI-native operating system for founder-led businesses that need knowledge to move beyond the founder.
Experience behind the method
Each environment reinforced the same lesson: good work becomes repeatable when its knowledge stops disappearing between people, projects, and conversations.
Creative work depends on practical coordination across people, schedules, locations, equipment, approvals, budgets, and deadlines.
Information moves through job-site conversations, estimates, texts, office updates, and decisions made under real pressure.
The promise made during sales has to survive the handoff into delivery, communication, and customer experience.
Useful AI needs trusted context, clear rules, visible processes, and organizational memory before it can support good judgment.
Credibility with context
My background includes documentary and independent film production, television and entertainment environments, contractor operations, marketing, outbound sales, and AI workflow architecture.
My documentary work has moved through development, production, distribution, and public release. I also appeared as a guest on Chris Voss’s television show, That’s Right, where he interviewed me.
The relevance is not proximity. It is the repeated experience of working where judgment, timing, persuasion, and coordination determine whether good intentions become a successful result.
Good work becomes repeatable when the knowledge behind it stops disappearing.
AI cannot organize a business that has never made its own knowledge visible.The turning point behind Litbox OS
Together, we build the system
Litbox begins with the business that already exists. Together, we find where work depends on memory, where information breaks between people, and where the same decision repeatedly returns to the owner.
Then that knowledge becomes practical operating infrastructure.
The system should sound like your business, reflect how your team actually works, and become more useful as the business learns.
Building in public
Their judgment should shape the system. Their experience should become business memory. Their repeated explanations should become guidance the team can use.
Litbox is making that transition internally while developing the method through real founder-led work, including a live engagement with a general contractor.
Follow the work in the Litbox PapersYour business already knows more than it can currently use
The operating system already exists in the way you estimate work, prepare projects, answer customer questions, evaluate quality, solve exceptions, train team members, and recognize problems before anyone else sees them.
You do not need to document everything at once. You do not need to replace your judgment with AI. You need to identify where your attention has become operational infrastructure and begin transferring that burden into a system your team can share.
The first step
Take the five-minute assessment and identify where founder knowledge should become organizational capability.
Take the assessment