What a country of delivery actually confirms

A vendor profile carries two separate country fields: a headquarters location and one or more countries of delivery. The geography axis this guide covers is built from the delivery field. Headquarters is a separate fact about where the legal entity is registered. This page works through what each field confirms, how the fourteen values in the geography axis overlap with each other, and what a country of delivery leaves open once a shortlist stage ends.

Two country fields answer two different questions

The headquarters field records the country of a vendor's head office, and the city where a source confirms one. That fact bears on the contract side of an engagement: which entity a buyer is contracting with, and which jurisdiction it sits in before a governing-law clause settles the question in writing. The delivery field records where the team assigned to a project actually works. That fact answers a different, operational question: which country's public holidays and labor law apply to the project calendar. It also decides which time zone a daily standup has to reach. A profile that lists a headquarters in one country and a delivery country a continent away is describing two facts a buyer needs for two different purposes, and a vendor profile prints both fields separately for exactly that reason.

Fourteen values, and where they overlap

The geography axis holds fourteen values: twelve countries and two regions. The countries are the USA, Canada, the UK, Germany, Poland, Ukraine, Spain, Portugal, Romania, India, the Philippines, and Vietnam. Europe covers a delivery team located anywhere in Europe, including the EU, the EEA, the UK, and the Western Balkans. Latin America covers a delivery team located anywhere in Latin America.

Europe is defined on the axis as a list of member countries. Because of that, a country value and the Europe value overlap for any country that sits inside the list. A delivery team in Poland matches the Poland value and also matches the Europe value, and the same is true for a team in Germany, Spain, Portugal, or Romania. A country value narrows to one specific delivery location; the regional value narrows to a broader legal and time zone contour that includes several of the listed countries plus territory the axis has no separate country value for. Reading both values for a candidate serves two different purposes: how the team compares within its exact country, and how it compares across the wider contour a region draws around it.

Not every one of the fourteen values carries its own published ranking page: a value with too few confirmed profiles behind it does not clear the threshold for publication, though the value itself still exists on a profile even where no ranking page exists to browse it. The UK, India, and Europe each have one.

What time zone overlap actually buys

A time zone difference on its own is a number of hours. The number a buying team actually needs is how many of those hours fall inside a working day on both sides. A six-hour difference between a delivery country and a buyer's own office can still leave a comfortable four-hour window if both sides run a similar working day, while an eleven-hour difference can leave close to no live window at all, depending on how each side's day is scheduled. What a buyer is choosing when it picks a delivery country is that daily window: how many hours a defect can be discussed live or a requirement clarified in real time, instead of left to an asynchronous message that waits until the other side's morning. A candidate whose delivery country produces almost no daily overlap with the buyer's own hours can still deliver good work, but the coordination shifts toward written handoffs, and that shift is easier to plan for before signing than to renegotiate once the first sprint has started.

Where test data sits once a test environment holds real records

Some engagements run entirely on synthetic data invented for the test suite. Others run against a staging or test environment that has been seeded with a copy of real user records, because reproducing a specific production bug needs the data that triggered it. Once real records sit inside a test environment, the country of delivery is no longer the only location that matters: the country where that environment is hosted, and the country where the people accessing it are physically located, can each differ from the country named on the vendor's profile. A regulatory readiness field on a profile can confirm that a vendor is set up for a named regime, but it does not confirm where a specific test environment for a specific project will be hosted or which country's staff will access it. That question is worth resolving before a contract is signed, while the test environment is still being scoped.

The language of a defect report outranks the language of daily correspondence

A delivery country carries a working language, and two languages are actually in play once a project starts: the language of daily correspondence between a project lead and the buyer, and the language a written defect report gets filed in. The first is usually settled quickly, since a call or a chat channel makes a mismatch obvious within the first exchange. The second is easy to overlook at the selection stage, because a proposal and a sales call both happen in whichever language sells the engagement, and neither one is the artifact a developer will actually read months later. A defect report written in a second language, translated loosely or missing a precise technical term, can cost an engineering team more time resolving ambiguity than the original defect would have taken to fix. Asking directly which language defect reports and test case documentation are filed in, before assuming it matches the language used during the sales conversation, is a question worth putting to a candidate before a country of delivery is treated as a settled fact.

Public holidays and a working week move a delivery date without announcing it

Every country observes its own set of public holidays, and the number and placement of those holidays across a year differs by country. A delivery country with a holiday cluster in a specific month can lose several working days from a sprint that a buyer's own calendar shows as fully available, because the buyer's own country does not observe the same dates. The standard working week is worth confirming for the same reason, since it decides how many working days actually sit inside a two-week sprint counted from a signed contract. Neither fact is visible on a profile field by itself: a profile records a country of delivery, and reading its holiday calendar or its standard working week requires checking that country directly. Asking for the delivery team's holiday calendar and standard working week for the contract period is a direct question to put to a candidate once a country of delivery narrows a shortlist, because a sprint plan built on the buyer's own calendar alone silently loses days it never accounted for.

A delivery country agreed at signature does not need to stay fixed

A country of delivery named during a sales process describes the team assigned at that moment. It does not by itself commit the vendor to keeping that same team, or that same country, in place for the life of the contract. A vendor can restructure staffing internally, or subcontract part of the work to a third party operating from a different country, and neither move necessarily breaches anything unless the contract says otherwise. The clause that closes this gap is the one covering subcontracting and relocation of the assigned work: a requirement for written notice before work moves to a different country, and a requirement that any new location and any subcontractor meet the same data handling and access terms as the original team. Without that clause, a country of delivery checked carefully during the shortlist stage describes the team on the day the contract was signed, and nothing about the team months into it.

Reading a profile that names more than one country of delivery

A profile carries at least one country of delivery, and many carry several. A list of several countries states where a vendor holds delivery capacity, and it stops short of stating which of them will staff a particular engagement. A vendor with teams in three countries can assign any one of them, or split an assigned team across two, and the field carries no commitment either way. So the question to send is the one this guide opens with: which country does the team assigned to this specific project actually work from, independent of where the head office issuing the invoice sits. Ask for the answer in writing and have it named in the statement of work, so that the holiday calendar, the working week, and the daily overlap all checked during the shortlist stage describe the team that will actually run the tests.