Start of testing in a startup

We all know what a startup is: quick to make, quick to release, don't care about processes, and quick to hotfix. We don't have to talk about quality. But sooner or later the team comes to the point where they need a first tester. Who, they do not understand, but understand that he can help them in some way. 

But what about the tester himself? Where to start? How to identify what the project needs? How to deal with the consequences of such quick starts? How do you structure your processes and set up agreements? How not to get bogged down in the routine of manual testing and bring order and predictability? And why is it logical for a tester to do all this? All of this will be discussed in the talk.