ROB SULZMAN / TECHNOLOGY LEADER & BUILDER

Complex problems.
Clear direction.
Working solutions.

I connect business needs, people, and technology—then work across the details to make the solution real.

STRATEGY ↔ EXECUTIONTexas · Working across disciplines
A FEW WAYS I SEE THE WORK01 / 04

ALIGN THE PEOPLE. CONNECT THE WORK.

See the whole picture.
Own the next step.

From distributed teams to business systems, good technology leadership connects the decisions to the people doing the work.

Explore the work behind this perspective
EXPERIENCE ACROSS
Multi-site operationsManufacturingSoftware & infrastructureApplied AI

01 / SELECTED WORK

The interesting part is
making it work.

A few examples of connecting technical depth to a real operating need.

02 / APPLIED AI, WITH INTENTION

Bring AI to the work.
Know where the data goes.

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?
ILLUSTRATIVE DATA FLOWLOCAL MODEL
YOUR CONTROLLED ENVIRONMENT
Your informationApproved sources
Access & retrievalOnly what’s permitted
Local modelInside this boundary
A useful answer, linked to its sources HUMAN REVIEW

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

Spend inference
where judgment matters.

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

Efficient Intelligence

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.

IN PRACTICE

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 workflow

AN OPERATIONS BRIEFING FROM CHANGING SERVICE RECORDS

Same goal.
Only the reasoning it needs.

“What changed this week,
what needs attention, and why?”

EXAMPLE INPUT

A service record has a new status and timestamp. The reporting rules already define how to classify the change.

  1. CODE + TOOLS

    Gather the changes

    Read allowed records. Validate IDs and timestamps.

  2. CURRENT MEMORY

    Check the context

    Reuse relevant knowledge. Refresh stale facts.

  3. KNOWN RULES

    Let code handle it

    Queries and calculations assemble the routine content.

  4. CODE + REVIEW

    Validate and reuse

    Check sources and calculations. Retain only reviewed learning.

No inference needed for this step.

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

Curious about what’s next.
Grounded in what works.

I’m interested in the space between a promising idea and something people can actually use.

01

Understand the real problem.

Listen to the people doing the work. Find the constraints, the friction, and what a better outcome would look like.

02

Connect the whole system.

People, process, data, software, and infrastructure influence each other. The solution has to account for that.

03

Build. Test. Make it useful.

Turn the idea into something concrete, verify the behavior, and refine it against the operating need.

04 / THE PERSON BEHIND THE WORK

A builder’s curiosity.
A leader’s perspective.

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.

Let’s find some common ground

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

What could we
figure out together?

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.

A good place to start.

CONVERSATION BRIEF
I’d like to talk about

A high-level description is plenty. Please leave out confidential information.

Review your brief before sending. Your details are used to respond to your message.

SELECTED WORK

Talk about a similar challenge
READY TO REVIEW

A starting point for
our conversation.

Check the details, then send your message.

You can also keep a copy of your brief.