I use it in my day job and have done so on and off for a little over thirty years. I've used it in team settings, as well as solo. It's a large force multipler solo and on small teams, but it can also be productive for larger teams.

You want at least one experienced Lisper who can mentor the less experienced and build guard rails where needed. The good news is that it's unusually easy to build guard rails with Lisp because of that same "bendable" quality you mentioned.

Another thing that is unusually easy with Lisp is building code-analysis tools. The source code is made of standard Lisp data structures that you can operate on with standard Lisp functions, and you can do it all interaactively in the live environment. That makes it much easier to build linters and other analysis tools than it is in most other languages.

You need someone on the team who is experienced enough to know how to do these things, and team-oriented enough to want to do it.

You also need to be aware that you probably don't know what guard rails and analysis tools you need when you're starting out. You'll discover them along the way. So you need project management with enough foresight to invest in prevention up front in order to save on cures down the road.