as a marketer, you know, like what is the actual, like, what is it actually like translating something that technical into something like a buyer just understands and then trusts?

Yeah, really it's collaboration with other departments is really where you need to begin and talking to customers.

Something, the approach I like to take is that I really ingrained myself with product and engineering teams because I don't, as a marketer, I don't want to be brought in at the finish line, right? I don't want to be brought in when someone says, Hey, we have this new feature, read about it.

It's already in beta.

We're ready to go to GA.

To me, that's far too late.

I want to be in the room when we're researching, coming up with ideas, starting to plan out the roadmap, because that helps me understand from the beginning, what is the pain point we're trying to solve? Who cares about it? How can I start figuring out and translating that as it's being built and not after the fact? So there's definitely a time component to it of the earlier you can start to understand the technical nuance, the better, especially for marketers who may not have as much technical expertise or experience in the past.

Is there ever a risk of like, do you ever worry about that where you have to, the technical depth isn't really there in the messaging?