Security Assessment of Our Own Proprietary C++ Binary (ARM32)

Nuven is a commercial audio software company. We are commissioning an independent security assessment of our own proprietary C++ agent, which runs on ARM hardware at customer sites. We applied the build with obfuscation, and we want an outside read on how well it holds up before a production release. The question: what can a competent adversary learn from this binary, and how long does it take them? Black-box, static analysis on a non-production build with test endpoints. Deliverables are a findings report, a recovered string table with call-site cross-references, and your annotated Ghidra or IDA database, not bulk decompiler output. Looking for demonstrated experience with obfuscated ARM32 targets specifically, not only x86-64, and familiarity with LLVM-based obfuscation passes. Mutual NDA and proof of ownership before any files are shared. Please include your standard pricing for this type of work.