--admin dashboards, --deployment, installation, configuration, upgrading technology and process -- SAML & SSO -- role based access control -- enterprise dashboard and reports
on site support, training
might require a different SLA since some things you'd need to be on site for more
tooling around debugging and troubleshooting for support. Easier in the cloud when you have access to the logs. On-prem you need a mechanism for the customer to package that stuff up and get it to you in a sane and secure manner
Depending on the size and complexity of deployment you might want to consider the cost of parking a resource there for extended periods of time. I would also push to get SSH / Console access to the hardware (where your software would be installed) even if its On-Prem ( that way it would look the same as any other hosting facility for you to support), we have done that in the past and it makes a huge difference. You want your SLA to be dependent on you getting access to customers IT as you would need them for troubleshooting network / system issue beyond your software. Most importantly I would think about how long it would take to do the initial implementation and 3X the time to set customer expectations
We currently have a deployment where we have deployed on customers AWS for instance. It’s pretty sweet as it looks pretty much the same for us to support, we don’t pay for hosting and our sponsor (at the customer) has been able to check on-prem box. Just an idea