We did not. Most of our contracts were integrating our stack into the customer's existing Unity project.

Plus we'd have to either re-train our Unity devs (more than half the software team) or find new developers.

The extravagant cost of a Unity seat meant we couldn't afford to give anyone except the Unity devs a license. The rest of the software team can no longer tweak the Unity project, and instead must file a ticket for one of the Unity devs to make the change and upload a build. For the same reason, we couldn't set up a build server in our CI system.

It was an absolute nightmare. At the end, I had to resort to ripping apart old copies of our android apps to inject new libraries into them. We couldn't afford Unity at all by that point, so it was the only option to get things working right now.

So glad that my new job has nothing to do with Unity or desktop software at all.