I’m interested in what holds things together…

People. Businesses. Families. Systems. Identities. Especially the structures we build when something has to work before we have the time, money, language, safety, or perspective to build it well. Those structures can be remarkably effective. They can keep a person functioning for years. They can keep a business running long past the point where the infrastructure should have collapsed. They can make you capable, useful, productive, impressive, resilient. And eventually, they can become the exact thing limiting what comes next. That is the work I care about. Not optimizing everything into oblivion. Not handing you another blueprint somebody else decided you should follow. I want to know:

What did you build?
What problem was it solving?
Does that problem still exist?
And does the structure still deserve to stay?

Because “it works” and “it works well” are not the same thing. And neither are survival and sovereignty.

I know some things are about survival architechture.

I spent years becoming very, very good at functioning. I learned how to read a room. Anticipate what people needed. Make myself useful. Hold a ridiculous amount at once. Keep moving. Adapt quickly. Build around whatever circumstances demanded and make the result look intentional. Some of those abilities protected me. Some of them became genuine strengths. And some of them stayed long after the circumstances that created them were gone. That distinction took me the better part of two decades to understand. Because rebuilding was never as simple as rejecting everything survival created.

It required better questions:

What protected me once? What is protecting me now? What is actually mine? What am I carrying simply because I never realized I was allowed to put it down? What deserves to stay?

That process changed the way I understand people. It also changed the way I understand almost everything else.

I learned business in places that didn’t call it business.

For five years, I booked and promoted DIY shows in my local music scene. Which turns out to be a very good education in entrepreneurship if you are willing to learn between soundchecks and benders.

You learn how to build an audience without much of a marketing budget. How to sell something people can technically live without and make it matter. How to coordinate venues, talent, schedules, money, promotion, personalities, emergencies, and twelve moving parts that all seem determined to go sideways at once. How to create demand through identity, community, scarcity, word of mouth, and belonging before you know anybody calls those things “growth strategy.” You learn to make a lot happen with almost no infrastructure. To improvise. To negotiate. To read people. To make the room work. And, in my particular case, how to do all of that while partying like a fucking animal. It was messy. Deeply un-corporate. Occasionally unhinged. Life-is-a-movie type shit.

And it taught me something a lot of polished business education misses:

You build the thing with what you have. You figure out what people care about. You create culture. You earn trust. You solve problems in real time. And if something breaks, you fix it before doors open.

That instinct never left.

simultaneously…I spent a decade inside systems where the details mattered.

Mortgage & finance, sales and operations gave that instinct structure. In a regulated environment, one “small” change can break something three steps downstream. A field changes. A disclosure pulls the wrong information. A handoff fails. A compliance problem appears somewhere nobody was looking. You learn very quickly that a system is not a collection of isolated parts. It is a network of dependencies that can quickly cost tens-if not hundreds-of thousands of dollars. So I learned to trace the flow.

Where does this information come from? Where does it go next? Who depends on it? Why does this step require a person? Where is the same work being repeated? What breaks if we change this? What should happen automatically? Where is the system quietly relying on somebody’s memory to keep functioning?

I got very good at finding the thing underneath the thing.

Eventually, I realized I was always doing the same work

Give me a messy business and I immediately want to know what is underneath the mess. Why does this process exist? Why are three tools doing the job of one? Why does every decision come back to the founder? Why are customers getting stuck here? Why is somebody copying information from one system into another? Why did this workaround exist in the first place? And — maybe most importantly — is the original problem even still here?

Businesses develop survival architecture too.

You launch before the infrastructure exists. You do things manually because you need revenue now. You bolt on another tool. You keep the process in your head. You become the connective tissue between systems that were never designed to work together. And because it works, you keep going.

Until the business grows. Then the architecture that helped you survive the beginning starts choking the thing you built.

That is where I come in.

That’s The Hot Mess Collective.

THMC is a strategic systems and operations studio for businesses whose ambition has outgrown the infrastructure holding everything together. I work across systems, operations, automation, digital experience, client flow, CRM, information architecture, and the ugly little gaps between platforms where work has a tendency to disappear.

The methodology is simple: See what is actually there. Understand why it exists. Keep what works. Remove what doesn’t. Rebuild deliberately.

Not because everything needs to be rebuilt. Because nothing should keep its job simply because nobody has questioned it yet.

I’m NOT here to make your business depend on me.

I am not interested in creating founders who need me to keep making decisions for them. And I am definitely not interested in building systems that require me to keep them alive.

The goal is sovereignty ✨

A business you can see clearly. Infrastructure that holds without consuming you. Systems that make good decisions easier instead of making simple decisions more complicated. Technology that earns its place. Processes that survive outside the founder’s head. And enough operational clarity that growth does not automatically mean more chaos. You should understand what you are standing on well enough that your next decision is actually a decision.

Not a reaction.

Not another workaround.

Not another subscription.

Not another thing you are now responsible for holding together.

I don’t believe complexity = sophistication

Some of the best systems are almost boring. Information goes where it is supposed to go. People know what happens next. Customers do not have to chase you. The founder does not have to remember twelve invisible rules. One change does not mysteriously break five unrelated things. Nobody celebrates them because nobody notices them. That is usually the point. Good infrastructure gets quieter as the business gets stronger.

The work is not to destroy the thing that got you here.

Some of it deserves to stay. Some of the ugly workaround is actually brilliant. Some of the manual process exists for a very good reason. Some of the system just needs reinforcement. Some of it needs to be ripped out immediately. And occasionally, you discover the entire thing was built around a constraint that no longer exists. The job is not to impose a prettier blueprint. The job is to understand the architecture well enough to choose deliberately.

Keep what holds. Dismantle what doesn’t. Build what comes next.

That applies to businesses. It also happens to be how I learned to rebuild myself.

May your darkness be the lantern that lights your way.

xoxo,
Sam 💖