Powstania Warszawskiego 15
31-539 Kraków
Most guides to nearshoring stop at "Poland has good developers and a convenient time zone". Both are true, and neither helps you sign a contract. This guide covers the practical side a CTO or founder runs into in the first month: how the agreement is structured, what Polish law requires for you to own the code, how the invoices work, and the calendar quirks that move release dates.
Hiring Flutter developers in Poland usually means signing with a Polish company rather than with individuals. The contract should transfer the economic rights to the code in writing and list the fields of exploitation, because Polish copyright law requires both. EU clients receive invoices without Polish VAT under the reverse charge; US clients receive invoices outside the scope of Polish VAT. A team in Cracow overlaps a full day with Europe and, with slightly later working hours, three to four hours with the US East Coast, and Poland has 14 public holidays worth planning releases around.
A company in the United States or Western Europe rarely employs Polish developers directly. Employment would mean a Polish payroll, Polish social security and a local entity. Instead, you sign a services agreement with a Polish company, usually a limited liability company, and that company provides the developers.
Inside the agency, senior developers are often not employees either. Many work as self employed contractors on so called B2B agreements, which is common and legal in the Polish market. For you this changes nothing day to day, but it matters for one question: whether the agency actually holds the rights to the code its contractors write, so that it can pass them to you.
The two common commercial shapes are a monthly team, where you pay per person per month, and a fixed price project against a written scope. How a monthly team runs in practice is covered in how a dedicated Flutter team works, and the fixed price side in fixed price app development.
This is the point most foreign clients do not know about, and the one worth checking before anything else. Under the Polish Copyright Act, a transfer of economic rights to a work, including software, must be made in writing, otherwise it is void. The agreement also covers only the fields of exploitation it names, such as copying, modifying, distributing and publishing the code.
For employees, Polish law gives the employer the economic rights to software written as part of the job. For contractors, there is no such automatic rule. The rights stay with the developer until a written agreement transfers them. That is why the chain matters: developer to agency in writing, then agency to you in writing, with the fields of exploitation listed at both steps.
This is general information, not legal advice. A short review by a lawyer familiar with Polish IP law is cheap compared with fixing a missing clause later.
Under Polish law, code written by a contractor belongs to the contractor until a written agreement says otherwise. Check the chain, not just your own contract.
Invoices from a Polish agency follow the general European rule for business services: VAT is settled where the client is based. In practice that gives two simple cases.
The invoice shows no Polish VAT and carries a reverse charge note. You account for VAT in your own country. The agency needs your valid EU VAT number, which it checks in the VIES register.
What you provideCompany details and an active EU VAT number.The service is outside the scope of Polish VAT, so the invoice has no VAT at all. Your finance team may ask for the standard IRS form in which a foreign company confirms its tax status.
What you provideCompany details and a billing address.Invoices can be issued in US dollars or euros, and payment is usually a bank transfer. Agree the currency before signing, because the exchange rate risk sits with whoever invoices in a currency they do not spend. Rates and price bands are on our pricing page.
Cracow runs on Central European Time. The shared working day looks like this for the cities most of our clients are in.
Zero or one hour of difference. The team works your calendar, and meetings can happen at any point in the day.
Six hours behind Cracow. Teams working with US clients usually start and finish a little later, so your morning meets their afternoon, which is where standups, reviews and decisions happen.
Nine hours behind. Overlap is short, so the setup works best with written updates and one fixed call early in your day.
One detail catches US teams every year. The United States moves its clocks on the second Sunday of March and the first Sunday of November, while Europe changes on the last Sunday of March and the last Sunday of October. For two to three weeks in spring and about one week in autumn, the gap to New York is five hours instead of six.
Recurring meetings set in one calendar will move by an hour in the other, so check them in those weeks.
How this works for American companies specifically is described on app development for NYC businesses, and for European ones on app development in Europe.
Since 2025, Poland has 14 statutory public holidays, after Christmas Eve was added to the list. Most do not overlap with US holidays, and several fall in clusters that take a Polish team offline for longer than a single day. Plan release dates and store submissions around them.
A good agency shares its holiday calendar at the start of the year and plans around it. Ask for it in the first week.
A Polish team works under the GDPR by default. When developers access production data that includes personal information, you need a data processing agreement that sets out what they can see and why. For European companies this is routine. For US companies it is often an advantage, because the setup that satisfies European customers is already in place.
In most projects developers do not need production personal data at all. Test data and a staging environment cover the daily work, and access to production is limited to the people who deploy and support it.
How we answer each of these, with our setup for US and European companies, is on our page about Flutter app developers in Poland. If you are comparing several agencies, see choosing a mobile app development company in Poland.
Directly employing them would require a Polish payroll and usually a local entity. Most US companies instead sign a services agreement with a Polish agency that provides the developers and handles employment or contracting on its side.
You do, if the contract transfers the economic rights in writing and lists the fields of exploitation, as Polish copyright law requires. Ask how the agency secures the rights from its own developers, since contractors keep their rights until a written agreement transfers them.
No. Invoices to EU businesses with a valid VAT number are issued without Polish VAT under the reverse charge, and the client accounts for VAT in its own country.
Usually six hours. With the Polish team working slightly later hours, as is common for US clients, that gives three to four shared working hours. For a few weeks in March and around the end of October it is five hours, because the US and Europe change their clocks on different dates.
Fourteen since 2025, when Christmas Eve became a public holiday. The ones that affect planning most are the first days of May, Corpus Christi, 15 August, 1 and 11 November and 24 to 26 December.
Most invoice foreign clients in US dollars or euros and are paid by bank transfer. Agree the currency before signing so exchange rate risk is clear.
Thomas sets the company's long term strategy and direction, identifies market opportunities, and owns business development and client acquisition. He builds strategic partnerships that last beyond a single project. He works with clients from the first strategy conversation, so their business goals, not just their feature list, drive every decision.
Tell us where your company is based and what you are building. You will get straight answers on the contract, code ownership, invoicing and the hours we would share with your team.
30 minutes, no preparation needed.