4 ms·

You obviously didn't read the article. He never said to outsource customer development. You made that up. In one of the actual examples, he had the VA simply

You obviously didn't read the article. He never said to outsource customer development. You made that up. In one of the actual examples, he had the VA simply form a list of 100 potential people he could reach out to for market research. Then he did the research himself. This is exactly the opposite of what you think he said. The other example was doing simple data-entry with a back-end ordering system because it was easier (at first) than automating it.

charleso 16y ago
Yes, I did read the article. Then I re-read it before commenting since I found the advice in that section to be so surprisingly bad. I did not make up my quoted comments. I pulled them right from the posted article and used them in context. Right under "Point #2: After Your Product Launch", the author states: "Customers make it necessary to put processes in place for marketing, sales, support, and back-end admin tasks. Any ongoing work that can be described in a written process can be outsourced to a VA and save incredible amounts of time for the founders. "If you do not outsource these tasks, they will get in the way of work that's truly productive for your business." The author is stating that a startup should outsource their support and I still think that outsourcing customer support for a new product is an extremely bad idea, no matter how easily that support process can be documented. Feedback from customer support is one of the best ways for a business to identify where a product can be improved. Yes, you can easily describe support in a written process, but you cannot possibly anticipate what customers will tell you during those support calls. The information shared during those early support calls is absolute gold.