I will begin. Only our internal team is working on the product, but we are already considering why we should not outsource testing. So, I believe we will actively work with outsourcing in the future.
@oleg_eltsov I like that approach. We've entertained outsourcing testing but are uncertain where or what to start with and how much of our product we should expose!
For one of my clients (I work as a freelancer myself): the entire team is mainly outsourced through Upwork. I don't think it's a bad idea but they gave everyone a part-time contract, so the work is going pretty slow, especially for the devs.
For the startup I co-founded: we're a team of 3 and most things have been done in-house. We hired a dev via Upwork and had a very positive experience. He proposed a clear timeline based on our requirements and budget, and it all worked out pretty well.
Nope, following the publication of articles about the project in the media, many volunteers reached out to us with requests, and despite that, all of us remained committed within the team. It is very dangerous to compromise on quality.
Personally, in-house development is far better than outsourcing.
Because with in-house development, we can ensure that everything goes as it should and it is easier to scale efficiently, and most importantly, we can make sure that our employee share the same vision and passion for building what the company aspires to achieve.
FirstHR