Answer up front

Build-Operate-Transfer is priced as an annual engagement for a standing team that delivers before you have a company in the country, not as a per-seat rate. Our own Build-Operate-Transfer engagements start at €400k a year on a 12-month minimum. Published third-party figures run far lower, because almost all of them price offshore service seats rather than senior product engineering in Europe.

That gap is the reason this breakdown exists. There's no shortage of content explaining what Build-Operate-Transfer (BOT) means. There's very little that says what you pay, phase by phase, and almost none that says what the transfer itself costs. Below is the anatomy of the price: what's in the build phase, what's in the operate phase, what changes hands at transfer, and which line items sit outside every quote you'll receive.

We build and run Tech Hubs in Porto on this model, so we have a commercial interest in one of the answers here. Every external figure is linked to its source, and where a number is ours, it's the one published on our own site.

What does Build-Operate-Transfer cost?

Build-Operate-Transfer is priced as an annual engagement with a minimum term, covering a working team and enough structure around it that the team can deliver with no local operations in place. Our engagements start at €400k a year on a 12-month minimum. That covers the squad, temporary office space, Employer of Record services if you need them, and access to the local partners who handle entity setup, accounting, tax, legal, HR and relocation.

Three things about that shape matter more than the number.

It's a floor, not a quote. Price moves with team size, scope and seniority mix. A squad of four senior engineers and a Product Owner prices differently from a ten-person team carrying design and product alongside engineering.

The build phase is discounted, not surcharged. In our contract the build phase is the pilot phase, and it runs at a minimum of 30% below standard rates. That inverts the usual shape, where setup carries a premium and the client pays most heavily before anything ships.

It isn't an all-in number, and no Build-Operate-Transfer price is. The partners who incorporate your company and run your accounting are contracted by you, not by us, and they invoice you directly. What the engagement price buys is a team delivering while that work happens, rather than instead of it.

Why published Build-Operate-Transfer costs disagree so much

Published Build-Operate-Transfer costs disagree because they're pricing different things. Most sources that quote a number are pricing a 50-seat offshore service center in India or Southeast Asia. A few give percentage savings with no figures at all. One says the transfer happens at no cost. None of them are pricing a senior product engineering team in Western Europe.

Here's what's actually published:

Two distortions follow, and both push the published numbers down.

Headcount. A 50-seat operation amortizes entity setup, office and management across five times the people a product squad has. Per-person setup cost falls as headcount rises, so a figure built on 50 seats can't be read across to a team of ten.

Salary base. Workforce cost is roughly 85% of total cost per full-time employee in those India benchmarks, which means the salary market does almost all the work in the totals. Portuguese senior engineering salaries sit well above that base, and Western European ones above that again. A model built on one salary market tells you nothing about another.

The honest read: the published Build-Operate-Transfer price range is real, and it belongs to a different service in a different market. For European rate context, our nearshore software development rates breakdown works through what the underlying numbers are and why the sources conflict.

What do you pay in the build phase?

The build phase pays for a working team and, if you're doing it yourself, for everything underneath it: recruiting, a legal entity, payroll, accounting and office. Build-Operate-Transfer doesn't make those costs disappear. It takes them off the critical path, because the pilot squad delivers with no local operations required and you open the entity once you've decided the country is where you're staying.

What the market publishes for each of those items in Europe:

Portugal isn't in the Taleva cost-per-hire dataset. The nearest comparable market it does cover is Spain, at €3,100.

Two notes on reading that table. Recruiter fees and cost per hire overlap rather than stack: agency fees are one of the external cost categories inside the cost-per-hire formula, so adding both double counts. And every figure there is per hire or per month, which means the build phase costs what it costs per person, every time you add one.

The cost that doesn't appear in any of those rows is time. Filling a senior engineering role takes a median of 79 days in the US, 95 in Germany, 88 in the Netherlands and 92 in the Nordics, according to SquadXP's 2026 benchmarks built on 2,400 placements. Hire six people sequentially and you're a year in. Hire them in parallel and you're running six processes at once with no delivery team yet to interview them.

For the full line-by-line cost of doing this yourself in Portugal, including salaries, the 30.5% statutory loading and office, see how much it costs to set up a Tech Hub in Portugal. This breakdown doesn't repeat that math.

What do you pay in the operate phase?

The operate phase is the running cost of a team that's already delivering: salaries and statutory employer costs, delivery management, HR, accounting, office, equipment and the partner's margin. On a Build-Operate-Transfer engagement it's a single recurring price. Run in-house, it's payroll plus roughly a third again in statutory costs, plus everything payroll doesn't cover.

In Portugal that loading is 23.75% for Social Security alone, and about 30.5% once work-accident insurance, the meal allowance, the mandatory health and safety plan and health insurance are counted. That's the part of the operate phase nobody forgets twice.

Three things distinguish an operate-phase price from a rate card, and they're worth asking about explicitly:

• Who carries a replacement. When someone leaves mid-quarter, either the partner replaces them from their own team or you go back to hiring. On a standing-team model it's the first. That difference is worth more than a few percent on the rate.

• What the price does when the work slows. An hourly contract earns a partner more when the work takes longer. A fixed monthly squad price earns the same either way, which puts the incentive on velocity rather than volume.

• Whether the operating overhead is inside or outside. HR, legal, accounting and office are real costs whoever carries them.

One thing the operate phase does that a rate card never shows: once you commit to the country, you're paying twice for a while. The engagement keeps delivering while you stand up your own entity, payroll and hiring alongside it. That overlap is deliberate, it's where the delivery risk gets absorbed, and it belongs in the budget rather than in the surprise column.

If you're weighing this against buying capacity rather than a standing team, our comparison of Staff Augmentation, Managed Services and Build-Operate-Transfer sets the three side by side on who directs the work, who's accountable and what you keep at the end.

What does the transfer itself cost?

The transfer is the least standardized part of the model and the part worth reading first. Published Build-Operate-Transfer contracts price it anywhere from a five-figure exit fee to nothing at all, and the same word covers both. Ours carries no management fee after transfer, with transition windows planned after the first 12 months.

What the published contracts contain:

That last row is the one that changes the arithmetic. If transfer is an obligation with a date on it, you're buying a project with a deadline and pricing an exit you've already agreed to. If it's selective and optional, you're buying a working team now and keeping the right to take the parts of it you want later, which means the transfer cost only arrives if you decide it should.

Three questions get you the real number out of any Build-Operate-Transfer quote, ours included:

1. Is there a fee attached to transfer, and is it fixed or calculated? A percentage of annual salary behaves very differently from a flat figure as the team grows.

2. Who legally employs the team before and after, and what does changing that cost? Entity setup, contract migration and any Employer of Record arrangement all have a price, and they don't always sit with the same party.

3. What happens if you never transfer? If the answer is a penalty or a step change in rate, the option isn't really an option.

What sits outside the price?

Some costs sit outside every Build-Operate-Transfer quote, including ours. The biggest one is the partners: the firms that incorporate your company and handle accounting, tax, legal, HR and relocation are contracted by you, and they invoice you directly. What the engagement gives you is access to them, not a bill that absorbs them. Ours names its partner network: Fresh, beTaxed, RedBridge, AGPC and Porto City Council.

Outside the engagement price, on our contract and generally:

• Entity setup and the partner fees around it. Legal incorporation, tax registration, accounting and the specialist advice that goes with them are billed by the firms providing them, directly to you.

• Software licenses and tooling your stack requires, which follow your standards rather than ours.

• Travel and onsite time beyond what's agreed, in either direction.

• Anything you'd pay anyway as an employer once you take the team on, which is the point at which the cost model converts into the one in the Tech Hub breakdown linked above.

A quote that appears to include all of these is usually carrying them as an estimate rather than a commitment. Ask which line items are fixed and which are pass-through, because the pass-through ones move.

What makes a Build-Operate-Transfer price move?

Four variables move a Build-Operate-Transfer price, and only one of them is negotiable in the ordinary sense. Team size and seniority mix set most of it, scope sets the rest, and the operating structure underneath is largely fixed because it costs what it costs.

• Seniority mix. A team of senior engineers with a Technical Team Leader prices differently from one built around mid-level developers with a lead borrowed from elsewhere. This is the single biggest driver.

• Team size. Operational overhead spreads across the team, so per-person cost falls as the team grows. It falls fastest in the first few people and flattens quickly.

• Disciplines in scope. A squad carrying UX Design and product ownership alongside engineering costs more than engineers alone, and usually needs fewer people to ship the same roadmap.

• Where the team sits. Porto and Lisbon price differently, and both price well below London, Amsterdam and Berlin. The gap is large enough to change the answer, and small enough that it rarely decides it on its own.

Who is this price wrong for?

Build-Operate-Transfer is the wrong purchase at this price for most of the companies that ask about it. It's a standing team with an ownership option attached, and it only pays back if you want both. Three situations where the number won't make sense, and we'd say so on the call:

• A three-month project. The minimum term is 12 months. A defined piece of work with an end date is a project engagement, not a hub.

• One or two people. Below squad size the operational overhead dominates the price and you're paying for structure you don't need. Staff Augmentation is the cheaper and better answer.

• No intention of ever employing people locally. The option to own the team is most of what the price buys. If you'll never exercise it, you're paying for something you don't want.

That last one is the real qualifier. Build-Operate-Transfer costs more per seat than employing people directly, and it should: you're paying for a senior squad that ships from the first weeks, the structure that lets it do that before you have a company in the country, and the option to take the team on later.

What a Build-Operate-Transfer quote is actually telling you

A Build-Operate-Transfer quote is three prices wearing one number: what the team costs, what the structure around it costs, and what your exit costs. The published market reports the first, buries the second and rarely mentions the third, which is why the figures you'll find range from "15–35% savings" to a fully itemized $659,000 over three years and both are honest about something.

The comparison that matters isn't rate against salary. It's the total of team, structure and time against what you'd carry yourself, with the transfer terms attached to both ends. A model that costs more per person and reaches production in four to eight weeks can be the cheaper answer over three years than one that costs less per person and spends the first of those years hiring.

Ask what's inside the price, ask what the transfer costs, and ask what happens if you never take it. Whoever you're talking to, those three answers tell you more than the headline figure does.