IT outsourcing experiments fail in 20 to 25 per cent of cases during the first two years of cooperation with a tech agency. The IT outsourcing market is huge and is predicted to grow by 409 billion dollars in 2022. With a growing demand for IT outsourcing, along with high-performing tech agencies, many development companies offering poor quality work have appeared as well.
You might have given them a try, failed and decided to try again, with the belief that next time they will choose a better web development partner. You don’t want to fail again though, right? So how can you choose a tech partner to develop your product wisely?
In this article, we will cover the most important aspects to consider when shortlisting tech vendors.
In addition to our own experience, we have asked Janna from ProdPad and Mirko from Intermate to share their experience and tips on choosing the right web development company.
A small disclaimer: we don’t represent any particular software development agency – in this article we are sharing our experiences of working with many software agencies in the past and observing the mistakes they have made with their clients.
Let’s start with defining where outsourcing pitfalls appear most frequently.
Communication with a remote team of developers
This isn’t an issue that’s commonly considered during the process of selecting a web development agency. Most clients focus on choosing a tech stack to use with your team, assessing developers’ tech skills, calculating budgets, agreeing on a cooperation framework and project deadlines. You don’t know what the communication with your team will look like before you start working with the supplier.
However, communication can quickly become an issue when your customers complain about a new bug in your product. You will probably try to contact your team, but they won’t respond – as it is probably night time in their time zone. The bug, if not fixed in time, will give some of your clients a nightmare.
These are the moments when you understand the importance of having direct access to your developers.
How can you be sure your tech agency will communicate well, before you start working with them?
The agency should develop a communication plan. A good sign is when they start talking about communication without you bringing it up first.
If they suggest a toolstack (using Slack or instant communicators like Telegram), discuss the regularity of your meetings and updates on progress This will underline the importance of regular communications .
Don’t work with a vendor that doesn’t give you direct access to their developers – middlemen prolong the process of reporting and solving issues.
Consider using these tools for frictionless communication:
- Google docs
Jana from ProdPad shared her experience on choosing a tech agency and establishing transparent and regular communication with a remote tech team:
Time zone differences and remote work practices
Choosing nearshoring, which means working with a software development agency located just a few flight hours from you, is much easier in comparison to offshoring when, for example, your company is located in Texas and your tech team in Poland.
You have to be aware of the impact that h time differences bring and equip yourself with remote work tools which help make work seamless.
First of all, choose a team with whom you will have at least several hours of overlap – e.g. 9-11 am in Austin and 4-6 pm in Warsaw. During these overlap hours you can conduct daily meetings (standups) to discuss the work to be done during the next 24 hours, problems, blockers, progress, and send feedback.
You can also consider sharing Google calendars with your team to be able to check on each other’s availability. In addition, consider asynchronous work, a form of communication that doesn’t happen in real time, but intermittently. Consider tools such as Twist.
Transparency and trust
Transparency is key to establishing trust with your remote team. Like communication, transparency is hard to measure before you start working with your developers.
How can you be sure that a tech agency will be transparent? Take a look at how they work! Are they using time tracking tools such as Harvest or Clockify and supplying clients with regular reports? Are they using Jira to track tasks and do they allow you direct access to check on progress?
The team of developers you choose to work with should be measuring their work productivity by recording performed tasks together with the time spent on each of them. You should be given access to the tool where this is recorded so that you can check on progress at any time.
Due diligence on track record
You can avoid many outsourcing pitfalls by taking a bit more time to verify your vendor – doing your own due diligence. With services like Clutch.co you are now able to read verified reviews submitted by the agency’s past clients. These reviews are gathered during a call with Clutch analysts who verify if the feedback submitted is authentic using a defined procedure.
Client reviews are a good source of information on how a tech vendor handles project management, communication and code quality. Go through the reviews carefully and look for details on the aspects you want to check. Does the team usually deliver on time? Can they get up and running quickly? How flexible are they in terms of scaling the team or substituting developers? Do they stick to the budgets or are their estimations rarely accurate?
In addition, you can also ask your agency to provide you with client referrals and then reach out to those clients to confirm them.
Previous experience in your industry
Case studies can tell you a lot about the type of clients the tech agency has worked with before, the calibre of projects they have managed and the tech stacks they are proficient at. All of this will help you to understand if their team will be a good fit to work with. Often companies publish case studies on their websites – go and check them out. Filter them by industry, project size and technology used.
An agency that has previously worked with a project similar to yours – in terms of the tech stack, complexity, industry etc. should already have some knowledge about the market and the specifics of your product, so it will be easier for them to understand your product and cater to your market.
A business focus over technocracy
Excellent code quality no longer defines an excellent software development agency. It has become a must. Apart from checking the tech skills of your chosen team, check how well they understand your business and customers. You should be looking beyond the code because even the highest quality code cannot guarantee the success of your product on the market. The key to successful product development is understanding the needs of your end users.
Consider a strong product focus as a big “plus” for the agency, especially if you are a first-time founder with limited previous experience in developing products.
Software development agencies working in the Scrum methodology will sometimes support you with a product owner (PO) proxy – a person within the development team acting as an intermediary between the person making decisions (you) and the team of developers – the people developing the product.
A PO proxy will perform the activities a product owner would normally do – gathering customer feedback, defining and managing the product backlog, planning with the team, deciding on product increment releases. However, it should be you – the actual product owner, who defines the product vision and overall strategy, have the last say on the backlog, make final decisions and control the budget.
To sum up, before engaging an outsourcing web development agency, check if they try to understand your product first before jumping into discussing budgets and timeframes. Assess how helpful they can be when it comes to suggestions, feedback or even full support in the product design cycle.
Ammar Akhtar from Finalrentals.com claims that communication and leadership are the two main challenges of working with remote teams of developers:
Coming from Western Europe, Asia or the United States and starting work with a team of developers from Eastern Europe, you will certainly notice cultural differences. For example, developers from Eastern Europe usually say things as they see them, often choosing a blunt response over diplomacy.
They don’t like admitting failure, trying to crunch on a problem without mentioning it which may later result in delays. They can also be shy at first.
Even if cultural differences exist, don’t exaggerate their complexity. You can certainly mitigate these issues! First, when your developers claim that they are right about something, don’t get mad and take it personally – discuss the issue with them. To avoid hiding problems under the carpet, communicate that problems are not to be ashamed of and encourage them to report them ASAP. To establish trust with your developers, try to loosen up relationships and remember that it can take some time, so don’t give up.
The best trick is to regularly visit your team in person, do activities together and get to know each other outside of work, but also share in-depth business insights. This will help you to read each other in between the lines, and make sense of any cultural differences.
There is much more to say regarding the challenges of outsourcing and their solutions – to research the topic in depth, download the Complete Outsourcing Guide.
I hope that the aspects discussed in this article together with the comments from experts help you define the selection criteria for your outsourcing partner better.
To get recommendations of the best web development companies in Europe, drop me a line at firstname.lastname@example.org.