Usually, Studio license cost is not transferred to the client. It is bared by the company where he RPA developers are working in. So the development team owns the Studio and the development license. For the client, pass in the cost that are required to run the project. Production robots, orchestrator if needed etc…
Hmm, So for example,
I have a client get an orchestrator license - the studio license cannot be connected so I retain my license?
From what I think I know, a studio license is needed to edit a workflow, and as part of the sustain & improve concept, changes would have to be possible after implementation.
Does this mean to offer maintenance & support a studio license must be dedicated to an instance of orchestrator?
Starting with the latest release 19.10, you will be able to keep your Studio local license and only connect to Orchestrator (without consuming a Studio license from Orchestrator). We did this exactly because we have received feedback with cases like yours. Hope this helps!