CapitalOS Raises $21.9M Series A for Embedded Finance

A plumbing repair belongs to a property long before it belongs to a month-end spreadsheet. CapitalOS helps software providers keep that connection intact when their customers spend money, bringing financial operations into the platforms already organizing the work.

The Bay Area fintech announced a $21.9M Series A on October 21, 2026, led by LGVP with WEX Venture Capital, Group11, Great North Ventures and Night Capital participating alongside existing investors. Cofounders Nir Dremer, CEO, and Matan Goldschmiedt, CTO, are expanding infrastructure that lets B2B platforms offer financial products while handing much of the operational work to a specialist.

For a software company, that purchase reaches into its relationship with the customer. A financial feature can turn a familiar application into the place where a business pays for the work it manages, with a new supplier carrying responsibilities that continue well beyond integration day.

CapitalOS puts the financial service behind the software brand

CapitalOS offers cards, bill payment, wallets and receivables through financial infrastructure embedded into other companies' products. Its product overview describes integration options ranging from a managed suite on a customer's subdomain to embedded applications and more customized API components. That range matters because software businesses arrive with different engineering capacity and different ambitions for how much of the experience they want to design.

Choosing an integration is also a choice about continuing work. A card program brings questions about eligibility, available capital, suspicious activity and customer support. CapitalOS's platform description places specialized agents across those functions, offering its customers an operating arrangement as well as a technical interface. A platform team can spend its attention on the industry it serves while buying financial capabilities from a supplier organized around them.

The attraction is particularly clear for vertical software. A property-management application already organizes properties, owners and expenses; a field-service product organizes jobs and the people completing them. Carrying that context into a financial transaction gives the application another practical use inside the customer's day. The commercial opportunity rests on how well those connections work, including the ordinary moments when somebody needs an answer about a payment.

DevCuration's coverage of Mural's financial infrastructure and ScribeUp's embedded bill management shows adjacent ways financial services enter existing software relationships. CapitalOS approaches that distribution opportunity through the operating needs of B2B platforms and their business customers.

Guesty shows where a card becomes an accounting decision

In CapitalOS's Guesty customer account, property managers need purchases assigned to the right property and its books. The described integration connects card spending with property-level ledgers, receipt collection and memos. This makes the allocation part of the transaction workflow rather than a separate effort to reconstruct the purchase later.

That is a useful explanation of what an embedded product can change for a buyer. The spending decision and its accounting destination become easier to keep together. A cleaner or contractor making a necessary purchase should leave a record the office can understand, without turning the person closing the books into a detective. Guesty's case study offers a specific workflow illustration; its reported results remain customer and vendor claims rather than a guaranteed outcome for another platform.

CapitalOS's integration with Layer addresses the next part of that journey. Card transactions and bill payments feed embedded accounting, carrying spending information into the financial records businesses use. The value depends on preserving the meaning of the transaction as it travels across products. A payment can complete successfully and still create work if the books cannot explain where it belongs.

For software founders, this expands the supplier evaluation. The financial feature needs to fit both the moment of purchase and the later administrative work. The accounting connection becomes part of the product's usefulness, especially for customers whose financial staff is small or whose owner still does the reconciliation.

The founders have already worked through the infrastructure handoffs

CapitalOS was founded in 2022, according to its company profile, and its about page describes a distributed team across the United States. Nir Dremer and Matan Goldschmiedt have built the company around selling financial capabilities through the software platforms businesses already use. That model requires CapitalOS to make its own infrastructure choices before it can simplify them for a customer.

An Increase customer interview identifies Matan Goldschmiedt as cofounder and CTO and describes the difficulty of coordinating separate issuing and banking providers. The account explains CapitalOS's use of integrated funds flows, authorization controls and a delegated compliance arrangement. These details help explain the work underneath a seemingly straightforward embedded card: transactions must pass through a set of financial and technical relationships before the platform can present a coherent service.

The financing history also needs careful accounting. November 2023 reporting described $39M combining debt and equity, without a breakdown. The new $21.9M Series A is a separate announced financing; the older mixed figure cannot establish a current total-equity number. The latest company announcement does not disclose a valuation or individual investor allocations, leaving the scale of the round clearer than its complete capital structure.

Scaling the service includes the people around the agents

CapitalOS says volume through its infrastructure grew more than 20x over 18 months and that the Series A will help scale what it has built. The disclosed measure is transaction volume, with no accompanying public revenue or profitability figure in the announcement. The financing therefore supports a company reporting substantial activity growth while giving readers a narrower view of the economics beneath it.

The operating model has a human perimeter. A current customer-operations role includes escalating situations where existing agent rules lack a clear path and human judgment is needed. CapitalOS’s current careers page lists GTM and customer-operations openings. These openings describe the organization around the infrastructure, where launches, exceptions and customer communication still require someone to take responsibility.

For LGVP and the participating investors, the financing backs a supplier trying to make financial operations easier for software platforms to add and maintain. The business opportunity is tied to the platform's existing industry knowledge and customer relationship. CapitalOS's role is to make the financial side dependable enough to fit inside that relationship, including the calls and cases that resist automation.

The property manager eventually needs that repair in the right books. Between the card purchase and the owner statement, CapitalOS and its platform customer have several chances to make the working day easier, and several handoffs they now share responsibility for getting right.