I’m not sure I would actually build Clay all that differently in full transparency, as I think that each step we’ve taken as defined who we are now, and I think each of those successes, mistakes, and periods of Clay are part of that development.
Additionally, I think adoption of MCPs depends on the types of companies in your customer base. Larger enterprises may struggle to adopt MCPs as quickly as small to medium size teams that are focused on the cutting edge. So, I think it’s important to maintain both ways of using Clay. We want to adapt to your use-cases.
In terms of how to use AI and Clay together, the biggest thing that I can say is that as Clay becomes your source of truth for your operational data, and we orchestrate your workflows, Claude can then use all of the data we have to make better decisions for the pieces of your business we don’t know about
