Rutter

A single endpoint, somewhere behind your favorite fintech

Open the spend-management app your finance team lives in. Connect it to your accounting software. The handshake takes ten seconds and feels like nothing. That nothing is the product. Somewhere underneath, a request travels to Rutter, which translates the chaos of QuickBooks or NetSuite or Xero into one clean shape and hands it back. You never see it. That is exactly the point.

Rutter sells plumbing. Not the kind people photograph, but the kind that breaks loudly when it is missing. The company has built one data model that sits between B2B software and 60-plus accounting, commerce, payments, and ads platforms. Ramp uses it. Airwallex uses it. Payoneer uses it. Roughly a hundred more companies you have probably touched this week use it without telling you, because telling you would defeat the purpose.

Fig 1. The scoreboard for an invisible company. Note that "platforms connected" is the only number Rutter's customers actually feel.

Business financial data is a swamp. Everyone wades in alone.

Here is the unglamorous truth the founders noticed: the data that runs a business - invoices, orders, payouts, balances - lives in dozens of systems that were never designed to talk to each other. QuickBooks does not speak NetSuite. Shopify does not speak Amazon. Each one has its own format, its own quirks, its own special way of being slightly wrong on a Tuesday.

So every fintech that wanted to build a lending product, an expense tool, or an AP automation workflow faced the same tax. Before writing a single line of the thing customers would pay for, they had to build and maintain integrations to all those platforms. Weeks per connection. Months of upkeep. An engineering team quietly drowning in other companies' API edge cases.

It is a deeply boring problem. It is also worth a great deal of money, which is the most reliable signal that a problem is real. The companies that solved it for one platform still had fifty-nine to go. Rutter looked at that math and decided the integration should be a commodity - bought once, never built again.

Two Yale grads bet on one model to rule them all

Peter Zhou and Eric Yu met in school, the way a surprising number of infrastructure companies begin. Zhou, a Yale computer scientist who had been an engineer at Atrium, took the CEO seat. Yu took CTO. In 2021 they made a bet that sounds obvious in hindsight and was anything but at the time: that the messy diversity of business platforms could be collapsed into a single unified data model, and that companies would happily pay to never think about it again.

The reference point was deliberate. Plaid had done this for consumer banking - one API to connect a person's bank account to any app. Rutter's framing was "Plaid for commerce," the same trick aimed at the business data underneath every B2B transaction. The phrase was almost too neat. So neat, in fact, that Plaid's own CEO, Zachary Perret, wrote a check.

That number was $27 million. In March 2022, Andreessen Horowitz led Rutter's Series A, with a16z's Kristina Shen joining the board. The round pulled in Comma Capital, Basis Set Ventures, Haystack, founders from Modern Treasury and Airwallex, and - because every good origin story needs an odd detail - The Chainsmokers' venture fund. Total funding climbed to roughly $28.5 million.

The cap table reads like a fintech dinner party where someone also invited a Grammy-winning DJ duo. Everyone is, somehow, talking about API integrations.

One API, many doors

Rutter is not a single feature. It is a family of APIs that share one model, so a developer learns the shape once and reuses it everywhere. Read, write, update, remove - across systems that would otherwise demand a separate dialect each.

What can you actually do with it? Build a lending product that underwrites on live commerce data. Automate accounts payable without a human re-keying invoices. Run expense management that reconciles itself. Spin up bank feeds. And, increasingly, hand the keys to an AI agent that needs to read product data and place orders on a merchant's behalf - the same single integration, now serving software that did not exist when Rutter started.

The names that don't usually share a stage

Infrastructure companies are judged by their customers, because they rarely have a face of their own. Rutter's roster does the talking: Ramp, Airwallex, Payoneer, Mercury, NorthOne, Parafin, Bench, Meow, Nitra, Orb, Pluto. These are not pilots. They are companies that put Rutter on the critical path of how money moves - the highest compliment one piece of software can pay another.

Fig 2. The shortest bar is the whole business model. Everything Rutter sells is the distance between the long bars and the short one.

The funding backs the story. $28.5 million raised, a Series A led by the most-watched firm in the category, and a board seat held by an a16z partner who bet early on enterprise software. Money is not proof of a good company. But a16z, Plaid's CEO, and a hundred paying fintechs arriving at the same conclusion is a fairly loud coincidence.

Connecting the world's business data

Rutter describes its purpose plainly: connect the world's business data. Strip the slogan and what remains is a genuine conviction - that financial data should not be trapped in the system that happens to hold it, and that the cost of moving it should approach zero. The company is, in its own framing, remote-first with hubs in New York and San Francisco, built around treating customers as partners rather than tickets.

There is a small irony in a company named after a navigator's logbook. A rutter, in the age of sail, was the book of routes - the hard-won directions a captain followed to cross water that all looked the same. Rutter the company is doing the modern version: charting the routes between systems so nobody else has to rediscover them. The name was either a very good pun or a very lucky one. Either way, it fits.

The agents are coming, and they need an interpreter

Here is the bet for the next decade. AI agents are starting to act on behalf of businesses - placing orders, reconciling books, moving money. By some estimates, agents will influence over $200 billion in e-commerce within a few years. Those agents cannot each learn sixty platform APIs any more than a human team could. They need one interpreter that speaks every system. Rutter spent four years building exactly that, before the customer it was built for had fully arrived.

That is the quiet advantage of infrastructure. The work that looked boring in 2021 - normalizing financial data into one model - is the work an autonomous agent now depends on. Rutter did not pivot to AI. The world pivoted toward the thing Rutter already was.

So return to that ten-second handshake. The finance manager connecting two systems, watching them snap together, moving on without a thought. They will never know Rutter's name. They will never need to. But the reason it felt like nothing - the reason an integration that once cost a quarter now costs an afternoon - is that a small company in New York decided the plumbing was worth getting right. The best infrastructure disappears. Rutter is betting its whole future on being forgotten in exactly the right way.