I notice operational problems the way some people notice typos. It's not something I decided to do — it's just how I see things.

My first job out of college was at a fitness studio where the manager held onto everything — decisions, tasks, information — in a way that made the whole operation dependent on her being there. I started a basic tracking system for the closing staff so mornings ran more smoothly. Nobody asked me to. I just noticed it would help.

My second job brought me inside a more complex version of the same problem. A small professional services firm, over two decades old, where one person had quietly become the institutional memory of the entire organization. It worked — until she left. When the first major deliverable came in after her departure, the gaps became immediately visible. What should have been straightforward required reconstructing information from across a fragmented system. The business hadn't failed, but it was far more dependent on one person than anyone had realized.

I've been working on rebuilding that foundation ever since. That experience is a big part of why I started Arclane Systems.

I have a master's degree in business analytics and an undergraduate background in philosophy. Analytics gave me fluency with data, systems, and structured problem solving. Philosophy gave me something harder to name — a deep discomfort with vagueness, a need to find the logic underneath messy things, and a habit of asking what something actually means before accepting that it makes sense.

That combination shapes how I approach operational problems. I'm not asking what's disorganized on the surface. I'm asking what the underlying structure actually is, what logic it was built on, and whether that logic still holds. That kind of thinking tends to surface problems that aren't obvious — and solutions that are more durable.

It also shapes how I think about tools. Most businesses try to solve operational problems by buying software — a new CRM, a project management platform, a better spreadsheet. Sometimes it helps. More often the same problems follow them into the new system. AI integration, automation, and other tools are only as good as the structure underneath them. If the underlying logic is broken, the tool inherits the problem.

That's the work I focus on. Getting the structure right first.

I started Arclane Systems because this kind of work genuinely interests me. Not just the fixing — the figuring out. There's something I loved about studying philosophy that shows up here too: the best questions aren't about what something looks like on the surface, they're about what's actually true underneath it. What's the real structure here? What logic is this built on? Does that logic still hold? Operations and systems ask the same kinds of questions. I find that interesting in a way that makes the work feel less like consulting and more like solving something worth solving.

If any of this sounds familiar — if your business runs more on memory and informal knowledge than you'd like to admit — I'd be glad to talk.