Article5 Minute Read

How to Vet an Offshore Development Team Before You Sign

Portfolios and sales calls do not show how a team works. A step-by-step way to vet an offshore development team, ending with a paid trial sprint.

Author

Michael Getu

Last Update

How to Vet an Offshore Development Team Before You Sign

Every development company looks good in a sales meeting. The portfolio is polished, the team is friendly, and the proposal says everything you hoped it would. None of that tells you what you most need to know: how this team writes code, how it communicates when something goes wrong, and whether the people in the meeting are the people who will do the work.

The good news is that those things can be tested before you sign. Here is the process we would follow if we were choosing a development partner ourselves.

Step 1: Check the portfolio properly

Do not just look at screenshots. For each project that resembles yours:

  • Visit the live product. Is it fast? Does it work properly on a phone? Do forms and key journeys actually work?
  • Ask what the team built. Design, front end, back end, the whole thing, or one feature? Agencies sometimes show projects where they played a small part.
  • Ask what went wrong. Every real project has a story of a missed deadline or a hard technical problem. A team that cannot name one is either inexperienced or not being straight with you.

Step 2: Talk to references who are not hand-picked

Ask for two references from clients whose projects resemble yours, and ideally one from a client who no longer works with them. Ask each:

  • Did the project finish on time and on budget? If not, how was it handled?
  • How did the team communicate bad news?
  • Who did you deal with day to day, and were they the same people throughout?
  • Would you hire them again for the same work?

The last question, asked plainly and followed by silence, usually tells you more than the rest combined.

Step 3: Meet the people who will do the work

Many providers send senior people to sell and junior people to deliver. Ask to meet the actual developers, tech lead and project manager proposed for your project, and to see their profiles. Then make sure the contract says what happens if any of them are replaced.

In that meeting, ask the tech lead to walk you through a technical decision on a past project: what the options were, why they chose one, and what they would do differently. You are listening for clear reasoning and honesty about trade-offs, not for buzzwords.

Step 4: Review real code

If you have a technical person, or can borrow one for a few hours, ask the provider for a code sample from a comparable project, with client permission, or an open-source repository they maintain. Look for:

  • Readable, consistent code with sensible naming and structure
  • Tests, and whether they look meaningful or merely present
  • Version control habits: small, clearly described commits and code review on pull requests
  • Documentation: a README that explains how to run the project
  • Security basics: no passwords or keys in the code, sensible handling of user input

If you are not technical, ask the provider to explain their code review process, testing approach and deployment pipeline. Clear, specific answers are a good sign. Vague ones are not.

Step 5: Examine the process

Ask how a typical week looks once the project starts:

  • How is work planned and prioritized, and how often?
  • What will you see each week: demos, written updates, access to the task board?
  • How are estimates made, and how accurate have they been recently?
  • How are bugs reported, prioritized and fixed?
  • How is work tested before you see it?
  • How are changes to scope handled and priced?

The contract model affects all of this; fixed price vs time and materials vs dedicated team explains how.

Step 6: Confirm ownership and security

Before signing, agree in writing that:

  • You own all code, designs and content produced for you
  • Code lives in a repository under your account from day one
  • Hosting, domains and third-party services are registered to you
  • Access is individual, protected with two-factor authentication, and removed when people leave the project
  • Credentials are stored in a password manager or secrets vault, never in documents or chat

A team that resists any of these points is telling you something important.

Step 7: Run a paid trial

The most reliable test is real work. Before committing to a large project, run a short paid engagement, typically one or two weeks:

  • A small but real feature from your backlog
  • A technical discovery phase that produces an architecture and estimate
  • A design sprint for one key page or flow

Judge the trial on more than the output. Did they ask good questions before starting? Did they flag problems early? Was the work delivered when promised, and did it come with a clear explanation? How did they respond to your feedback?

A trial costs a little money and saves a lot. It is also the only step in this process that shows you the team working rather than describing how it works.

Red flags

  • A quote far below every other quote, with no explanation
  • Unwillingness to let you meet the developers
  • No questions about your business before proposing a solution
  • Insistence that code stays in their repository until final payment
  • "Yes" to every request, with no trade-offs discussed

What we offer

When you add developers through our hire by tech stack service, you interview the top three to five finalists yourself, with resumes, video introductions and skill summaries in hand. For projects, a short discovery phase before the main build is a sensible first step with any provider, including us, because it lets you judge real work before committing to more. If you are still defining the project, start with how to write a website brief.