Understand the real problem.
Listen to the people doing the work. Find the constraints, the friction, and what a better outcome would look like.
ROB SULZMAN / TECHNOLOGY LEADER & BUILDER
I connect business needs, people, and technology—then work across the details to make the solution real.
ALIGN THE PEOPLE. CONNECT THE WORK.
From distributed teams to business systems, good technology leadership connects the decisions to the people doing the work.
01 / SELECTED WORK
A few examples of connecting technical depth to a real operating need.
02 / APPLIED AI, WITH INTENTION
The useful question starts with the problem, the information involved, and who should be allowed to use it. Model choice comes after that.
Explore two possible approaches.
Have a problem like this?In this design, retrieval and model inference run inside the chosen environment. Logs, updates, backups, and network access also need controls to preserve that boundary.
Illustrative architecture · This diagram does not process your information.
HOW I THINK ABOUT APPLIED AI
Low power does not mean low intelligence—efficient intelligence.
My approach brings together time-aware memory, knowledge that improves through verified learning, and agents with clearly defined jobs. Code enforces the workflow. Tools connect the systems.
The aim: use the minimum necessary inference energy while preserving the quality of the result.
Select a part. Follow the connections.
THE SHARED PURPOSE
Use inference where it adds value. Bring current context, verified knowledge, and the right expertise together without asking a model to repeat work that code can already do.
Reuse what is known. Check what has changed. Think deeply where it counts.
A backlog total can come from a query. An unexplained change may need one carefully scoped question.
An illustrative architecture, grounded in how I approach the problem.
Explore an efficient workflowAN OPERATIONS BRIEFING FROM CHANGING SERVICE RECORDS
“What changed this week,
what needs attention, and why?”
A second agent appears only for a separate question.
A service record has a new status and timestamp. The reporting rules already define how to classify the change.
CODE + TOOLS
Read allowed records. Validate IDs and timestamps.
CURRENT MEMORY
Reuse relevant knowledge. Refresh stale facts.
KNOWN RULES
Queries and calculations assemble the routine content.
CODE + REVIEW
Check sources and calculations. Retain only reviewed learning.
Code and current knowledge can produce the routine content. Important interpretations still pass through human review.
Illustrative workflow · Synthetic service records · No model is running and no information is submitted.
03 / HOW I THINK
I’m interested in the space between a promising idea and something people can actually use.
Listen to the people doing the work. Find the constraints, the friction, and what a better outcome would look like.
People, process, data, software, and infrastructure influence each other. The solution has to account for that.
Turn the idea into something concrete, verify the behavior, and refine it against the operating need.
04 / THE PERSON BEHIND THE WORK
I’m Rob Sulzman. My work spans technology leadership, infrastructure, software, and business operations. I like problems that require more than one discipline—and people who want to explore a better way forward.
Today, that includes multi-site technology operations at Traders Village, a part-time CTO role in precision manufacturing, and hands-on work with applied AI.
There’s a life beyond the systems.
I also serve as President of the Animal Rescue Foundation of Texas.
A LITTLE MORE ABOUT HOW I WORK
Selected perspectives from my experience.
TRADERS VILLAGEDirector of Network Operations & Engineering
CS FABRICATIONChief Technology Officer · Part-time
05 / START A CONVERSATION
A technology leadership opportunity. An interesting professional connection. A complex problem that could use a fresh perspective.
Exploring a potential project? Tell me what’s getting in the way and what a useful outcome would look like.
rob@sulzman.com