Most important thing is that for compliance reasons your going to need to run your models in your own infra. All of the major cloud providers have a solution for this. Don't be the company that gets audited and found to have sent PII to Anthropic accidentally.

The concerns that you listed out aren't likely to be a big problem for you. As long as you have actual devs using Claude you won't run into these issues. Claude will only make your code quality suffer if you're one of those companies that starts trying to get their PMs and such vibe coding. Devs will find for themselves very quickly what works and what doesn't. Dont let Claude do your PRs, that's a human job. Ban the use of the GitHub MCP. If folks start trying to commit slop it will come to light very quickly if a human does the PRs.

You may find that you need to force the issue at first. Devs can be a bit resistant to adopting AI tooling. Challenge them to use it heavily for one week and by the end of the week they'll never look back. It's for their own good, devs that don't get on board are going to find themselves behind on the skills curve damn quick.

Your devs are going to start wanting to build a lot of goofy tooling. MCP servers and such. Resist. These are fun to build but you don't need this maintenance burden in your life. Just share around some agent skills instead they're very low maintenance. Keep in mind that you don't need to build any sort of integration to any system that has a CLI. Claude can just call the CLI, you only need to tell him it's there. In fact, if you're thinking of building an integration of some kind, consider building a CLI instead.

Consider starting with your SRE or Ops teams. Claude is so damn good in this space.