CloudPay joins a $10 million round for a startup that rents out payroll engines

If the $10 million were split evenly among the five named investors, each would be in for $2 million, and the angels in the round make every named check smaller than that ^[1][2][18]. A stake that size buys information and an option without committing CloudPay's own customers' payroll to someone else's engine.

Intermezzo says it can take a typical 20-day payroll cycle down to about 24 hours and hold accuracy above 99 percent ^[8][9]. Twenty days is 480 hours, so the claim is a twentieth of the elapsed time, a 95 percent cut ^[19]. The company describes long processing cycles, high error rates and compliance risk when rules change as the problems it is selling against, along with institutional knowledge that lives in spreadsheets and email ^[11].

The smaller claim is the one that changes what a platform can sell: runs on demand instead of a fixed calendar ^[10]. Pay frequency becomes something the platform sets in software. Underneath it, AI agents read source material and turn it into structured, machine-readable rules ^[6]. Those rules feed an engine that handles gross-to-net calculation, statutory filings, payslip generation and ERP synchronization ^[7].

CloudPay chief executive Roland Folz said Intermezzo's emphasis on automation, artificial intelligence and reducing complexity aligns with how CloudPay itself approaches product development. He framed the stake as support for technology that can improve outcomes for customers across the payroll ecosystem ^[12]. Ed Park of UKG Ventures said payroll is no longer a back-office chore but core business infrastructure, and that UKG has seen firsthand how difficult multi-country pay can be ^[13].

UKG Ventures is the stronger evidence that platforms now expect to rent an engine, because UKG sells workforce software and its venture arm is funding the layer that would sit under it ^[2][13]. CloudPay's position cuts both ways. It already operates in global payroll and payments, and Intermezzo is selling to the same class of platforms and service providers that sit around enterprise payroll ^[14][15]. One outcome hands CloudPay country coverage it does not have to build; another equips the platforms it competes with to keep payroll in-house, and CloudPay owns equity in both.

By the source's own framing, a working API model gives established processors a way to expand country coverage without rebuilding local engines from scratch. A failed one leaves the fragmented vendor model as the default ^[16]. The founders argue the market is ready for a programmable payroll layer comparable to modern payments infrastructure, with one integration, many jurisdictions, and rules that update as regulations change ^[17]. The record so far is a funding round and a set of vendor performance figures. The size of CloudPay's stake is not disclosed, and the figures arrive without a named customer or a baseline error rate behind the 99 percent ^[20]. On that evidence the round is an option on a model, priced too small to say that CloudPay's own coverage strategy has changed.