Well, I don't agree that it's misleading, because we take the Access app, and implement it in the cloud. That's what we do. The app is in the cloud. The data is in the cloud. You get a login and password and bob's your uncle. You have 25 users, then you get 25 logins.
I guess it does gloss something over - the fact that the front end is in the cloud too. And we always migrate data to SQL Server, which all our customers require (we don't retain data backends in Access). We send the database and the new app version back to you for continued development (unless we do the app build ourselves, which for NFPs is usually free).
But I did try to make clear that we manage the front end if it's a client build, and work with the client as though we were the Release Manager on the team. We check all releases, and spurious changes are the subject of alerts which we feed back to the client for approval. For example, the CR comes to us with the new FE - if we find that the FE changes don't match the CR we alert the client. This can happen when a developer encounters a bug during testing, fixes it to enable the test to complete, and forgets to alert the team leader that another object has been changed. In which case, the CR comes to us, and that's when we find a change in an unrelated object. (In fact, we always alert the client to the result of our check, with a report that says "Your CR said [blah blah], and your changes are [blah blah to objects blah blah], and they do (or do not) correspond with CR requirements").
So, yes, we do take care of our customers, thanks for that. And RDP is underneath our partners any-device thin client connection apps. I think what I said was Ok, if a little brief.
Jack