
Welcome to the design jungle.
AI doesn't fail on the model. What fails is the system underneath, which was never designed.
Ray Butler · Big Freight Life
The system underneath.
I spent my career inside complex enterprise systems, improving how work actually moves — not the interface, but the machinery beneath it: the workflows, decisions, handoffs, and approvals that decide whether a product succeeds or fails.
It led to a simple observation. Most AI failures aren't model failures — they're systems failures. Organizations invest heavily in models while overlooking the layer that decides whether those models create value: fragmented workflows, unclear ownership, disconnected data, decisions trapped in tribal knowledge. AI doesn't solve those problems. It exposes them.
That's what Big Freight Life was built to design. I structure the systems around AI so models operate clearly, predictably, and within real-world conditions — mapping how work moves, designing decision paths, defining ownership, and building the architecture that lets people and AI work together.
The result isn't just working AI. It's working operations.
The architect, not the factory.
I design the architecture. Your team builds it.
Before anyone designs a screen, I model the system as objects — the real things your users think in: what each one knows, what it can do, and how they connect. That map mirrors how people actually reason about the work, and it doubles as the structure your AI reasons over. Get the objects right and the screens design themselves.
My role is to understand how work moves through the organization, identify where AI belongs, pressure-test assumptions through working prototypes, and create a foundation your engineering teams can confidently ship from.
No large consulting teams, no layers of project management, no dependency on a single builder — just clear architecture, direct collaboration, and systems designed to hold under real-world conditions.
Big Freight Life remains intentionally small, so every engagement gets direct attention from the person designing the architecture — not a committee managing the project.
This isn't theory. See the work →
Nope.
No RFP work.
Procurement-scoped engagements move too slowly to fit the work I do.
No enablement decks.
Slides aren’t a deliverable. The architecture is.
No implementations without authority.
If I can’t make calls on the system, I can’t be accountable for it.
No multi-year retainers.
Engagements are finite, scoped, and named. I’m not a permanent line item.
From web pages to AI systems.
I started out designing web pages, then moved into telecommunications, designing physical systems. Along the way I started a few small businesses of my own. It all converged in enterprise experience design (UX) — the foundation for what I do now.
My AI journey began in 2022. I kept learning as the work pulled further upstream. I now help organizations like yours understand how teams decide, how systems coordinate, and where trust holds or breaks between humans and software.
You're moving fast. Your system isn't keeping up.
I design the foundation that makes everything else possible.
Without it, nothing holds.
Let's talkAddress
Big Freight Life LLC
1351 N Buckner Blvd #180397
Dallas, TX 75218
Business Hours
Monday – Friday, 9am – 6pm CT