I shouldn't be afraid to break my organization's HubSpot instance. But I am terrified!

Because I don't know what's going to happen when I do. And that, my friends, is slop.

Neat that someone can build really complex workflows that automate manual tasks for multiple departments.

Not so neat when no one understands the upstream and downstream automations that can completely mess up workflows for multiple departments.

Add add add

Imagine being the first person to purchase HubSpot for your business. The field is green. You get to build whatever you want.

You decide to build a simple Contact Sales flow:

Contact sales form submission → enrichment tool → qualified/unqualified → sales

Beautiful, simple. You understand what's happening. Now, imagine your organization grows and someone else takes on that workflow, and they want to get cute:

Contact sales form submission → enrichment tool → LLM enrichment → qualified/unqualified/support requests → sales OR support

Okayyyy, still manageable. Now imagine another person gets in there and gets even cuter:

Contact Sales form submission → enrichment tool → LLM enrichment → qualified/unqualified/support requests/partner requests → n8n → write 30 properties on contact record → update lifecycle stages → sales OR support OR partners

And because we're already here, let's add round robin functionality through n8n.

And if it's a sales request, let's push it into a custom tool.

Which, naturally, means adding another automation in another platform.

Okayyyyyyy, now imagine adding another person and saying: ok, new person, add in lead routing based on region. Should be easy right?

But where do I do that??? You'd think here: the sales custom tool?

BUT, you don't have access to that custom tool, and that tool has +20 other actions that you have to study and learn whenever you do get access.

So now, before you can add regional routing, you have to understand an entire automation that lives outside of HubSpot, figure out what all of those actions do, determine what depends on what, and hope you don't accidentally break something for sales, support, or partners.

It shouldn't be this hard.

This is where we're getting our systems wrong. We keep adding.

Until eventually, nobody wants to touch it because no one is really sure what's going to happen if they do.

You gotta rebuild it

At some point, you have to stop adding. If you can't answer: this is where I'd add this iteration

You gotta rebuild!

Instead of adding regional lead routing into the giant workflow your predecessor(s) created, build something better.

And challenge the systems. Do you really need that second enrichment tool? Do you really need to push data into n8n? Does that lifecycle stage actually need to exist?

There really isn't one magical way to structure your HubSpot instance. But, you should be able to change it whenever you need. And quickly.

Something as simple as adding lead routing based on region should be very simple to add/iterate.

If adding one new requirement means you have to understand five people's work, three platforms, 20+ automation steps, and a bunch of undocumented dependencies...

You've got slop.

And the answer isn't to add another layer on top of it.

Reason and build in public

I actually think it benefits you more than your organization to reason and build loudly.

Explain what you're doing. Document it. Show people how the thing works in public Slack channels.

I don't think it should feel like a win that you're the only person who knows how it all works. It's actually a huge liability.

Because eventually, you're going to move on. Someone else is going to own it. And they're going to open up your beautiful, complicated system and think:

What the heck is happening here?

If their first instinct is to leave it alone because they're scared to break something, you've made the next person's job harder.

Now they add another workflow. And another integration. And another exception. And the slop gets worse.

So, yes. Build the cool stuff. Automate the manual work. Use the LLM. Connect the tools.

But know what you built, why you built it, and make it easy for someone else to change.

Because if the answer to "where would I add this?" is, "Uhhhh. Let me find the person who built it."

You've got some slop to clean up.