Operations Systems Architect
AI · Automation · Software · Data · Digital Infrastructure
I came to systems architecture through repeatedly asking how businesses actually work — and how technology can make the work easier.
My background spans operations, marketing, media, web development, digital strategy, UX, analytics, automation, AI and software. Those disciplines look different on a résumé. Inside a business, they are constantly connected.
A customer-facing page affects the people answering inquiries. A reporting decision depends on how data enters the system. A useful automation depends on understanding the task it is supposed to support.
That range helps me see a problem beyond the boundary of a single department or tool.
I work where a business problem involving operations and technology needs a connected approach.
Turn the business problem into a coherent system design.
Make the idea tangible enough to examine and improve.
Develop the parts of the system that make the solution work.
Connect the tools, information and workflows involved.
Reduce repetition where a clear process supports it.
Help specialized implementation fit the larger architecture.
Make the decisions and operating model understandable.
Keep the path from idea to implementation connected to the goal.
I want to understand the people doing the work, the decisions they make, the information they depend on and the exceptions they have learned to manage.
Then I can define what needs to change, how the system should behave and which technology makes sense.
The goal is to choose the right tools and make them work together.
Active work across platform architecture, restaurant systems and hospitality operations.
A business intelligence platform being designed for contractor businesses.
A connected restaurant experience across menus, reservations, catering, events and ordering.
A hospitality workflow prototype built around the people doing the work.
You don’t need a technical brief to start a conversation.