I'm confused by what you mean. I'd argue that onboarding new customers should be your core competency, the focus of your main product. What am I missing?
We make an application that makes use of folder on a network share. One of the developers here types up instructions each time we install a new site. If the customer has trouble or opts to have our help, they will connect remotely to create a folder and some sub folders. This takes anywhere from a few minutes to over an hour if they have trouble connecting remotely.
I mentioned in a developer meeting that we should create an install script for the network folders. It would save the company hundreds of hours or work.
One developed asked how I would do it. A generally competent developer, who has worked with files and folders for many years, asked how we could deliver a program to create folders.
I nearly walked out (and we still dont have a 4 line script to create the folders we need)
>> I'd argue that onboarding new customers should be your core competency, the focus of your main product.
I suppose that's true, in a way. We host open source stuff for stuff, we support people, we do lots of stuff, some of it is automated, and some of it isn't. I was just saying a larger part of getting the new customers in production would be good to have more automated and I've not yet found an easy way to do that.
I do like the idea of that being a core competency, though not quite a focus of the main product.
