It's Okay If They Don't Get the Harness

It took Brian Halligan 3 minutes as the new/old CEO to reposition HubSpot as a “Customer Relationship Harness”.

I felt a bit vindicated because just 20 minutes before that change, we’d been discussing some feedback from the LeadDev Berlin conference that people didn’t understand our positioning as a “reliability harness”. And we sell to engineering teams who use a code harness every single day. If our audience doesn’t understand a harness, then there’s zero chance anyone will understand HubSpot’s new positioning, right?

Maybe. But that’s okay.

HubSpot is desperate to move beyond its marketing automation / CRM roots. It has to, to stay ahead of all the innovation that’s happening because of agents + APIs + “headless” GTM.

And the same applies to us. We have to make sure engineering leaders know that we’re more than the best response platform with on-call that doesn’t feel archaic. We’ve evolved into a full reliability platform with agents that solve the hard part of reliability work for you, like investigating an incident and finding the likely cause.

Iterative positioning changes aren’t big enough given the clear step change of AI.

So it’s okay if not everyone immediately understands the “harness” context when they visit the HubSpot website or see incident.io at a conference. We want people to ask us “so what do you do?” because that’s the only way they are going to really understand how we’ve evolved.

And let’s face it, no matter what messaging you put on a conference booth, 90% of the audience is still going to ask “so what do you do” 🤣

I’m honestly not sure being a “reliability harness” is right for us, but I do know that it’s okay to use positioning to start a conversation and educate a market.

The next test will be at re:Invent in a couple of weeks…

p.s. here’s how I think about defining a harness: the system of tools, data context, permissions, and guardrails wrapped around an AI model or agent to make its work safe, repeatable, and connected to real-world business outcomes.

Originally posted on LinkedIn.