What the round buys
Athens-based Omilia raised 67 million dollars in a Series B led by Expedition Growth Capital. The company had taken 20 million dollars from Grafton Capital in 2020; since then it has grown its annual recurring revenue tenfold to 60 million dollars. The money is going to an office in the United States, a market that accounts for a significant chunk of its revenue, to bolstering the go-to-market team, and to hiring a chief revenue officer, a chief marketing officer and a VP of revenue operations. The company has around 500 employees now and expects to reach 600 by the end of the year.[1]
The list is worth reading for its omissions. Every disclosed item sits on the distribution side: an office, a go-to-market team, three sales and marketing executives. No item is announced for deployment, support engineering or client-side adaptation. That is a legitimate choice, and it also says where the company sees its constraint: the problem to solve is selling the technology rather than making it work.[1]
Where the work actually moved
Omilia's clients include Capital One, Discover, RBC, DWP and PSEG; the technology has been deployed across more than 1,000 Taco Bell outlets, and the company is in talks with two more quick-service restaurants in the United States. Chief executive Dimitris Vassos says a large proportion of incoming queries involve basic information such as account balances and there is little need to run large language models for them.[1]
The number that would show where the work went sits on the client side: contact-centre headcount, or the share of contacts handled by a person. Neither appears in the reporting. A tenfold increase in recurring revenue is a result measured on the vendor's side and on its own shows that no job disappeared. What I take from this is that the disclosed data is not enough to answer the distribution question. Another explanation is available: automating a balance lookup may be absorbing a queue that was never adequately staffed, shortening waiting times rather than displacing a worker.[1]
What happens without the system
Take the company's own description seriously. If most incoming contacts are balance lookups, the counterfactual for those contacts need not be a worker on a headset; it could equally be a voice menu or a web page. The displacement question then narrows to the contacts that genuinely need a person, and the real burden gathers on the exception path: whoever catches the error, reverses it and explains it to the customer. The failure TechCrunch reports, in which a customer was said to have ordered 18,000 cups of water last year, shows what that path looks like; Vassos maintains the incident never took place and did not appear in Omilia's logs, and TechCrunch has asked Taco Bell about it. The question the company should answer is who carries that exception path while the sales roster grows.[1]