Hi Mishti 👋 Thank you for taking the time to answer our questions; it's greatly appreciated! Clay has written about the best GTMEs being "hybrids," commercially thinkers who build vs just being tool specialists. For someone with no portfolio, what's 1 concrete example of a project you've seen that proves this, not just claims it on a resume? Context, I'm new to pretty much everything and learning as I go. I want to ensure I'm spending my time forming good habits and learning key skills early on before I spread myself thin exploring ancillary ones. I don't know enough to know what is a "need to have" vs. a "nice to have" so any guidance you can provide would be warmly received 🙏
Totally hear you! It's hard to figure out how to learn things described as abstractly as "systems thinking in practice." One great start, I think, would be to reach out to a business, learn what they're struggling with in their go-to-market motion (it could even be someone super local, like a coffee shop or a laundromat), and build them out a workflow that would help them. I think Clay and a lot of GTM engineering tools are best learned by having specific projects in mind versus in the abstract. There are definitely a lot of boot camps that do a good job at teaching fundamental skills! But the reason I suggest something like this is that it'll immediately get you into the belly of a business: understanding what they're struggling with, coming up with a solution, and then implementing it, which is the core skill I think.
I know some of our employee bootcamp projects really range from sourcing pizzerias in New York to crawling lists of journalists that are good to pitch for various topics. It's often not even related to a specific customer problem or something but people learn these tools by just thinking about some research and outreach tasks they're curious about and then trying it out

