The euro changed the negotiation before anything else did
Bulgaria adopted the euro on 1 January 2026 at the fixed conversion rate of 1.95583 leva. For anyone buying software services out of Sofia, that single fact did more to the commercial conversation than any productivity trend.
Currency risk on Bulgarian contracts is gone for euro-denominated buyers. The lev was pegged to the euro for decades, so the economic exposure was always small, but the perception of exposure was real and it showed up in procurement risk registers and in the discount buyers demanded for it. That discount has evaporated. Bulgarian vendors know it, and the good ones repriced in the first quarter.
If you are renewing a Bulgarian contract this year and your supplier has not raised the euro conversion in the negotiation, they are either being generous or they have not thought about it. Neither is a great sign.
Related reading: Poland's Capability Centres in 2026: Hiring After the GBS Growth Slowdown Β· Lithuania's Fintech Talent Market in 2026: Hiring and Licensing in Vilnius Β· CEE Tech Salary Benchmarks for 2026.
How big the sector actually is
BASSCOM, the Bulgarian Association of Software Companies, has been running its Barometer survey for seventeen years, and it is the only sector dataset worth quoting. The headline figures: roughly 108,000 ICT professionals nationally, of whom about 70,000 work in software and IT services, across some 6,100 companies. Annual software sector revenue passed 3 billion leva. Growth ran at 11.5% in 2024 with a forecast around 9% for 2025.
The number that should shape your procurement thinking is different: 87% of sector revenue comes from exports. Bulgaria's software industry was built to sell outward, primarily into Germany, the UK, the Nordics and the US. That means the delivery culture, the English proficiency, the contracting norms and the working-hours expectations are all already calibrated to foreign clients. You are not teaching a domestic-market vendor how to work with you.
It also means the sector is exposed to demand cycles it does not control, which is why Bulgarian firms have been unusually willing to negotiate on commercial terms during slower quarters. There is more flexibility here than in Poland.
Sofia, Plovdiv, Varna: what the second cities are for
Sofia holds the large majority of software and fintech employment, the highest salary bands, and effectively all of the product and startup layer. Plovdiv and Varna have grown real capacity, mostly in delivery and support rather than product, at clearly lower cost and much lower attrition.
The pattern that works is a Sofia lead team with delivery capacity in a second city, which several vendors will offer you as a blended model. The pattern that fails is a pure second-city team for anything requiring frequent architectural judgement, because the senior architects are in Sofia and they are not moving.
Who is actually here
The named entities matter more than the aggregate figures when you are trying to judge whether a market can support your work.
Chaos, the company behind V-Ray, is Bulgarian and has been shipping rendering software used across global film and architecture for more than two decades. Payhawk, the spend-management platform, was founded in Sofia and became the country's first unicorn. Progress Software has run a large Bulgarian engineering base since acquiring Telerik in 2014, which is the acquisition that put Sofia on the map for a generation of engineers. SAP Labs Bulgaria has expanded its Sofia development centre with an AI incubation team, and its current hiring skews to senior engineers with Python and large language model experience rather than the junior intake of a decade ago.
That last detail is the useful signal. When a captive centre stops advertising junior roles and starts advertising senior LLM engineers, the local senior market has become deep enough to supply them. Five years ago it was not.
Rates, and what you should expect to pay
Planning numbers for 2026, in euros, for outsourced delivery through a Bulgarian vendor. These are blended commercial rates, not salaries, and they assume a dedicated team rather than time-and-materials staff augmentation.
| Role | Sofia, monthly rate | Second city | Notes |
|---|---|---|---|
| Mid-level backend engineer | 6,000 to 8,000 EUR | 5,000 to 6,800 EUR | Java, .NET and Python all well supplied |
| Senior engineer, 8+ years | 8,500 to 12,000 EUR | 7,500 to 10,000 EUR | Prices against remote Western European work |
| ML or data engineer | 10,000 to 14,000 EUR | Limited supply | Thin market, expect a long ramp |
| QA automation | 4,500 to 6,500 EUR | 4,000 to 5,500 EUR | Deepest pool in the country |
| Delivery lead or architect | 11,000 to 15,000 EUR | Rare outside Sofia | The genuine constraint on scaling |
Two caveats. Bulgarian ML and data engineering supply is thin relative to demand, and any vendor promising you six machine learning engineers inside eight weeks is either poaching from a client or padding the team with backend engineers who did a course. Ask to interview every one of them. Second, the architect and delivery-lead tier is the actual ceiling on how fast a Bulgarian team can scale, and it is where you should spend your due diligence, not on the mid-level bench.
Contracting: the clauses that matter here
Bulgarian vendors are, on the whole, straightforward to contract with. EU member state, EU data residency, standard European IP assignment norms, no exotic exchange controls. The friction points are specific and predictable.
- Name the people. Bulgarian delivery quality is strongly individual, and a contract that specifies a team profile rather than named individuals will get you a different team by month four. Insist on named leads with contractual notice on rotation.
- Get the euro conversion in writing on any contract that started in leva, including how any indexation clause now works. Some pre-2026 contracts have indexation language that no longer makes arithmetic sense.
- Set the AI usage terms explicitly. Bulgarian development shops adopted AI coding assistants fast, faster than most of their Western clients realise. Decide what you permit, what gets disclosed, and who carries the liability for generated code, then write it down.
- Ask about the Article 4 position if the work touches AI systems you will deploy. Your regulator will treat you as the deployer regardless of who wrote it.
The AI point deserves more attention than it usually gets. A senior engineer at a Sofia consultancy told me their team's throughput on a routine integration project roughly doubled once the tooling settled, and the client never asked, so the price never changed. That is not a Bulgarian problem. It is happening in every delivery market and Bulgaria is simply further ahead on adoption than most buyers assume.
Where Bulgaria beats the alternatives, and where it does not
Against Poland: cheaper by 15% to 25% at comparable seniority, smaller talent pool, less depth in enterprise finance and German-language capability, comparable or better in product engineering and graphics. If your work is product engineering, Bulgaria is underrated. If you need 300 people with SAP finance experience, go to Poland.
Against Romania: broadly similar cost, similar size, Romania stronger in automotive and embedded, Bulgaria stronger in product software and fintech. The euro adoption gives Bulgaria a real edge on contract simplicity that Romania will not match for some years.
Against Ukraine: Bulgaria costs more and carries no war risk, which for most European enterprise buyers has settled the question since 2022 regardless of the price difference.
Against India or the Philippines: Bulgaria is more expensive per head and cheaper per outcome for European work, because of time zone overlap, EU legal perimeter and lower coordination cost. That calculation flips as team size grows past a couple of hundred people, where the cost gap stops being absorbed by the coordination saving.
The training layer, and why it is thinner than it looks
BASSCOM's own reporting notes that essentially every Bulgarian development business has adopted AI practices in some form, and 451 new tech companies appeared in 2024 creating more than 2,500 jobs. Adoption is not the gap. Structured capability building is.
Bulgarian firms are excellent at absorbing tools and weak at formalising skills. Most vendors you evaluate will have no internal curriculum, no assessment, and no way of telling you what proportion of their engineers can do a given thing to a given standard. Training happens by osmosis on projects, which works while the seniors have time and stops working the moment you scale the team.
This creates a specific opening for EdTech companies and training providers selling into Bulgaria, and a specific due diligence question for buyers. For vendors: the market has money, growing revenue, and almost no established internal L&D function to compete with. For buyers: ask how a vendor brings a new joiner to productive on your stack, and how they measure it. The honest answer is often "they sit with a senior for a month", which is fine at ten people and falls apart at eighty.
The firms that have built something structured here (a few of the larger Sofia consultancies have) can ramp a team twice as fast, and it shows up in your delivery timeline rather than in their sales deck.
A last thought on how to evaluate a Sofia vendor
Skip the capability deck. Ask them to walk you through a project that went badly and what they changed afterwards. Bulgarian engineering culture is direct to the point of bluntness, and the firms worth working with will give you a real answer with specifics, dates and an admission of fault. The ones that give you a polished non-answer have learned to sell to procurement rather than to engineers, and that is usually visible in the delivery six months later.