mwarcholinski

I've worked before with my two startups with teams from India, and this was a disaster, but I think the reasons why were:

#1 Lack of my experience in dev area - how to work with dev teams (mainly external)

#2 Pricing - I was price sensitive, and in the long term, it caused that the code was not usable while scaling the business.

I hated it so much that after those two startups I've built my own software dev company focused on one technology and a quite small team of tech-savvy colleagues.

Below my checklist that I'm using to evaluate the outsourcing companies with who I would like to work -> http://bit.ly/2Hthv5A

Happy to hear that you advocate the same hiring tactic.

I highly recommend a podcast with Jonathan Siegel on how he used this approach on buying 29 companies and hiring people to run them -> https://okdork.com/buying-a-business-jonathan-siegel/

Of course, there is nothing more valuable than real experience, but there is a ton of useful resources over the internet to help to become a CTO. Let's create together an amazing list of resources (blog posts, books, presentations, videos etc.) to help others to become a CTO/Technical Leader in a startup/company.

Please add your resources in comments or directly in google sheet ---> https://docs.google.com/spreadsheets/d/17eBWH-n4-Ap8_S59gpTK...

Thanks for feedback guys. I agree that in various companies those terms might have a bit different definition.

I wrote this, because I couldn't find anything good enough describing this topic. We often got aks by our our customers or first-time-founders - What is the difference? And why and how they can do it?