[nathana]

I'm glad to hear that companies such as yours that are doing this are not necessarily considering making it permanent. I read PG's original article, and although you make reference to it, I felt he was addressing a different sort of issue than it sounds like you are. In your case, you actually went out of your way to engineer internal systems that let you do things manually, and you probably could have spent the same time and engineering resources you used to do that to instead develop the automation you don't have yet.

I may be in the minority, but let me give you some perspective as a potential customer who has experienced this kind of hands-on "service" from other SaaS-y outfits: I WANT automation from your service. I have worked with 2 companies that made me jump through all kinds of hoops to get an account set up with them when I could have had a usable account provisioned and active in 5 minutes had they automated their processes. As a result, it took days, because (surprise) their employees have their hands full, and I also have better things to do (you know, actual work responsibilities and customers of my own to respond to) than to have my hands held jumping through all of your contrived and artificial hoops just to use your service. That's just a waste of my time and yours and something that only ends up causing unnecessary delays to service turn-up, and in both cases, it seriously soured my taste for the service and almost made me contemplate throwing in the towel and going with a different solution.

This isn't the feeling that you want to leave your new customers with who are trying very hard to give you their money. You mean every time we need to make a change to service parameters, I need to submit a spreadsheet with my change request to somebody that's going to plug it in on your side by hand? MAYBE 24 hours later, if I'm lucky? Forget that: I'll go with somebody that gives me an API or a web portal that I can use to make the changes myself in a matter of minutes.