I have worked on QA teams with as few as three testers and as large as 150. Three years ago, I elected to start over and was the first QA staff member hired at CAQH (small non-profit health care company) and was brought on board with a mandate to “fix product quality”. I found the organization had taken delivery on several poor-quality software releases of our flagship product from our development partner, and the ongoing application development and testing was in disarray. As employee #2 on the newly formed Technical Team, this is the story of how we built a Quality Assurance presence from scratch and turned our team into an automated testing powerhouse. Along the way, we had to overcome doubts from management, eliminate redundant processes, educate our colleagues who had never worked in a software development shop on the value of testing, teach non-technical users how to review test cases and correctly engage in user acceptance testing, sell our colleagues and our development partner on the concept of automation, train our support and implementation team on how to run the underutilized more technical components of our application, and finally, prove our methodology was working. I will cover that tipping point that every organization goes through when trying to transition from a manual testing shop to an automated one and how we handled rejection, doubts, fears, and ultimately succeeded.