Edward Kandel

100%.

We are fully team Anthropic at Cofor.

No, no.

Sorry to all the opening ISEs out there.

Oh, a world of pain has caused that thought process when you try and go, who are the people we should accept to our events?

And then you have a list of 30 job titles, right?

So yeah, the catch-all term we use within the community is solutioners.

And that's obviously a made-up word, but the idea is it is meant to encapsulate the workflows that people are doing from, as you say, pre-sales, scoping, demos, etc., to the delivery part of like

either implementation support or actually that delivery work on-site, the more forward-deployed engineer side.

The reason why it was very intentional having a space with both together is because one, you see some teams where, for example, the MOLLE team who are in the community, one of the focal customers, they do pre-sales and delivery in one team.

So it wouldn't make sense to exclude half of that.

The second reason why is both teams are intrinsically connected.

How good delivery is able to perform is very inextricably linked to what the pre-sales function or part of the process is doing and vice versa.

So that is why, as a space, it felt right to really focus on those two.

And for example, we never have any AEs, salespeople, leaders who are not in the solution space.

But yes, we have solution as a catch-all.

And then our terms, we use at least our pre-sales and delivery to go pre-signature and post-signature just as a catch-all.

I think, one, I love the term, you know, because, hey, Clay uses what go-to-market engineer as well to mean a salute.

Anyway, the job titles, it's so frustrating.

Everyone, let's just agree on something.