On the face value, what was the goal that y'all wanted to see by identifying best management practices within the world of trails?

Yeah, it's a really good question, as you mentioned, something we baked in early on.

And there, there are a whole bunch of reasons behind it.

I mean, I could start at the top, which is that there are a lot of resources out there that are good how-to resources.

IMBA's published several volumes of sort of guidance on, you know, multipurpose and non-bike trail construction, which are very extremely useful tools.

They don't boil down to the sort of thou shall or thou should sort of the bullet list, the things we can take to, not just to, I would say we'll talk in a minute about that because the sort of role a document like this can play, but literally like a checklist or an assessment thing we can, we can cascade out to our chapters or use like, are these trails adherent, sort of compliant, consistent with our current best management practices? If not, where not, and giving more directive, kind of be able to...

Using as a tool, I'll put it that way.

This happened for sure in, like, East Burke, which is looking at the existing trail system and rating it as, like, how much of this is actually adaptive friendly now that we just didn't, like, know, we just really needed to evaluate.

But how do you figure out who else at an event should be considered a marketing qualified lead?

I think it depends what your lead scoring model looks like too, because what is an MQL? I don't want to say I've talked about it a lot, but is MQL the wrong thing to be looking at? Should you be looking at from an account level like, hey, these are the accounts that are showing intent.

It doesn't matter as much who the individual contacts are, but how do we show the accounts and surface that intent level so that we're following up with the right people and the ICP around that? But I also don't agree that any, like, you know, say we get an attendee list from an event, like should all those people be MQLs? Probably not because they just registered for an event.

I think hand raisers should.

I think people that see a demo should.

I think people that take multiple steps at an event should.

But I don't think everyone that you scan at a booth or everyone that you talk to should be considered an M2L.

You can track tons of data, but what actually matters?

So Nick, what's your background like? Is your story similar to Daniel's? Uh, is it something that you've been into for a long time, or been around for a long time, or did you come to it later on in life?

Well, unfortunately for me, I don't have the lineage and heritage of D- Daniel's history in, in, uh, in watches.

Uh, I've been a certified watch geek for a very long time, but I haven't worked in the industry for quite the same amount of time.

So I was working in a completely different industry, uh, when the pandemic started, and then Watch Collecting started up.

It was actually the sister platform of Collecting Cars, w- which you mentioned at the top of the show, which was already in existence.

And the, the owner of Collecting Cars decided, "Hey, we could apply this same logic to watches and start a watch platform." So I was already following Collecting Cars at the time 'cause I was also a car nerd.

I saw an advertisement for a job, and I thought, "You know what? I'm gonna give this a shot." Anyway, they asked me to write about a 5513 Submariner, and I was the only person who picked up that it was a service dial.

What do you do when, when you encounter a watch for the first time? Do you do everything in-house, or do you send some stuff to external parties to, uh, authenticate it for you?