Lisbon work divides fairly cleanly into three kinds, and they want different things from us.
The first is the shared service centre: back-office document work and multilingual support run from Lisbon for several European markets at once. The volume is real, the languages are plural, and the process is already documented because it had to be in order to be moved here — which makes it unusually good ground for automation. The relevant patterns are support automation and cross-platform workflows, and the hard part is rarely the model. It is agreeing what happens on the cases the system should not touch.
The second is tourism and hospitality, where the defining feature is that demand is not flat. A group that handles a certain volume of enquiries in February handles several times that in August, in more languages, with staff hired for the season. Fixed headcount is the wrong shape for that curve. A system whose cost falls close to zero out of season and absorbs the peak without recruiting is one of the few genuinely obvious cases for this technology, and one of the few where the business case survives contact with a finance director.
The third is product. Lisbon now has a serious concentration of engineering teams building software sold across Europe, and their problem is not compliance. It is whether an AI feature can be shipped at a cost per user that does not destroy the margin, and whether it can be evaluated well enough to change the model later without breaking. That is a different engagement shape and it is covered under in-product AI and, where the company is earlier, startups.
Energy and utilities appear too, usually with technical documentation and asset records rather than customer contact, and the work looks much like it does anywhere else in Iberia.