Replying to @jamiepowell168 Should you build your own AI tools when consulting or becoming an AI specialist? My advice is no, at least to start. #rachelwoods #chatgpt #aiops #aiforwork #promptengineering #gpt #openai

If you're just getting started with AI and specifically AI operations, here's my advice on whether you should build solutions for clients or buy them. And I'm going to talk specifically about chatbots because I think they're a really good example of this. If you have no coding experience, and even if you do, you can build MVPs extremely easily with out-of-the-box tools like chatbase. But the minute you start implementing these chatbots inside an organization, you're going to run into things that you wish this out-of-the-box tool had. That doesn't mean you need to jump straight into coding the whole thing. Even though we code, we've built a lot of ours in Bubble, which is a popular no-code tool. And while there's definitely a learning curve to figure out how to build your own versions of these, I think the upside when it comes to learning, control, and customizability is well worth it. So I would buy for the MVP and then build once you're ready to really implement. And we have a lot of resources on how to do this in the AI Exchange, and I've been thinking about rolling out something to help you go from zero to one with more guidance. If of interest, comment below.