1. Easy calls to C with CFFI. No Clojure->Java->JNI->C, just straght CL->C.
2. Useful, optional, type system (which can also catch mistakes at compile time with SBCL and other compilers)
3. Very fast startup times.
and many more features like for example an object system that is massively above what Clojure and Java bring to the table, better exception handling, very explícit errors and nice stack traces, it can also compile to JVM if you want, etc.
If you like Lisp, try it. You already learned a Lisp so the jump is easy.
Why? Are the rumours of porting the language to Chez Scheme true?
2. Spec does solve the problem for me, but I don't really like static typing anyways.
3. I keep Clojure REPLs open for days. I restart if I need a new dependency and for other minor reasons, but startup time is almost a non issue for development. For scripting, you can try Planck, although yeah you lose the Java interop. I love Clojure, but I just don't use it for scripting.
Not trying to tell you you're wrong, just offering some insight into how Clojure could address (or not address) your points.
My own related exaggeration is that type declarations without performance gains are useless. Get them out of my dynamic langs unless you can deliver the performance goods. (Like Common Lisp can. It can also tell you you're stupid locally trying to make an invalid call, at compile time, since COMPILE is built-in.)
We get around the startup time by keeping our work either in the REPL, or just having large enough tasks that the loading is dwarfed by the time it takes to get started. Webdev might be a little crappy if you're used to the turn-around cycle of either node or PHP.
(ClojureScript has very good live reload support as well)
Can't imagine that would be too hard to wrap.
For me the C/C++ was a minor issue since if you're going to the trouble to do it on the JVM you may as well build that part in Java.
Show examples of large companies using Scala in production (Twitter, LinkedIn, Walmart etc)
Gradual low risk introduction of Scala using Gatling load test and ScalaCheck
Production ready frameworks like Play and Akka
Demonstrate that Scala can be introduced at various levels from "Java without semi colons" to "You need to learn category theory to understand this" and what we would do to make sure everyone on the team would be up to speed.
Build a prototype
What counted against Clojure and Common Lisp was the immediate reaction of people with no exposure to lisp languages was "those brackets" and the lack of a large stable framework one can pick up and use as a gateway to using the language.
Simply put there can be a gradual adoption of Scala in a company that's really not possible with Clojure.
1. No C/C++ FFI.
2. Lack of a strong type system (clojure.spec almost solves this problem now, but when I quit this didn't exist yet).
3. Horrific startup times: although clojure itself is fast, its startup time isn't. This makes scripting in clojure unsatisfying. And you don't feel like a ninja when it takes 30 seconds to start a REPL. You can use clojurescript to target node to get around this, but then you cut yourself off to most of the powerhouse clojure libraries.
I now use Haskell (with C/C++ FFI). I do miss the homoiconicity (and slightly more concise syntax) of clojure. In my opinion Haskell and clojure are the two sexiest mainstream languages that you can get stuff done in.