How are folks handling ‘proof of concept’ requests? My hypothesis is that what Clay can do is so new that people want to see it works for their use case, which is fait. So they want to see a POC. But, I usually can’t build a POC that get’s great results (i.e. Results that make them say “wow this really works”, without investing quite some hours into the POC, which is kinda the whole project. Would absolutely love to get a convo going on this and hear what others have to say!
Having similar challenges Andreas W.. As a potential solution from our work with Asana as Solution Partners, we have demo projects and recorded workflows for high request items that can be shared when these requests come up. It was an investment of effort to get them built, and there a little generic in the sense it’s not exactly the prospects workflow, but it’s enough for them to “see and touch it” before committing to a paid engagement seeking to accomplish the next level of validation.
thanks for taking the time to respond Alex J., yep that’s where my mind is going. Ran someone through a comparable use case just the other day love on a meeting and it went well, we’re gonna work together. I’m building quite a bit but don’t feel yet that I have that library of use cases, but I think this is the way to go

