How to extend a UK squad without the culture tax

The failure mode of “team extension” is not the CV. It is the culture tax: extra process, a shadow manager, and engineers who wait to be told what to pick up. UK squads that have been burned by body leasing assume the next vendor will do the same. Fair.

A Lisbon extension only works if the people sit in your rituals, on your clock, and own slices of the system rather than a ticket queue.

What we mean by “in the team”

• Same stand-up, same tracker, same repo permissions as the London engineers.
• A tech lead on your side who actually has time to review work — we cannot replace that.
• Code that ships through your pipeline, not a parallel “vendor branch”.
• The right to say no to a candidate. The 2–4 week calendar is worthless if you are forced to take whoever is on the bench.

What it is not: a named “offshore lead” who translates between you and a room you never meet. If you need that layer, the model is already wrong.

English, not theatre

Portugal ranks 6th globally for English on EF EPI 2025, in the very high proficiency band. That is a market fact from the Portugal ICT Study 2026–2030 (German Outsourcing Association with 99x, AHK Portugal and ICT Markets) — not a 99x score. It is why a UK squad can run refinement without a language tax.

It does not mean every engineer is a conference speaker. Interview for the domain. A quiet senior who writes clearly in PRs is often more useful than a fluent account manager.

Ownership vs. the ticket hose

Give the Lisbon people a service, a surface, or a problem — not a stream of “please fix this Jira”. The first two weeks should look like any other senior joining: access, architecture walkthrough, a first production change with a reviewer who cares.

If after a month they still cannot ship without a written spec from London, either the brief was a factory, or we sent you the wrong people. Both are fixable. Pretending is not.

Tools and security, without a side quest

UK clients in regulated spaces (gaming, finance, health-adjacent) will ask about laptops, SSO, and where the code lives. The honest answer: your tools, your cloud, your policies. We are not asking you to adopt a 99x stack. GDPR and EU contracts are the default, not an add-on, because the company doing the work is in Lisbon.

If your security questionnaire assumes a 2,000-person Indian campus, say so early. We will answer it; we will not pretend to be that campus.

A working agreement in five lines

1. You interview every engineer.
2. They join your squad chat on day one.
3. You have a counterpart in London who can unblock them.
4. We replace people who are not landing, without a theatre of “performance plans” that last a quarter.
5. You can stop. This is not a hostage contract.

If that is the shape you want, start a conversation. If you need a black-box project with a weekly PDF, we are the wrong vendor — and we would rather say that in the first twenty minutes.