/ 01 - PRESENT TENSEWhat RecVue is, right now.
A control layer the C-suite forgot to draw on the org chart
On a Tuesday morning somewhere in San Mateo, a cold-storage logistics company invoices a customer for a shipment of frozen blueberries. The customer ships another pallet on Wednesday. By Thursday, a billing event fires. By Friday, revenue is recognized, the partner gets their cut, and the accountants do not have to file anything by hand. That sequence runs on RecVue.
RecVue calls the product RevOS - the Revenue Operating System. The name is bigger than the buzzword cycle usually allows, but RecVue is not selling a feature. It is selling the seam between the CRM that signs the deal and the ERP that closes the books. That seam is where revenue lives. It is also, traditionally, where revenue goes to die.
The company is roughly 180 people. Most of them work on the bit of the stack you do not see and do not particularly want to think about: how dollars travel from a signed contract to a recognized line on an income statement. RecVue's pitch is that this journey, which finance teams patch together with spreadsheets and middleware and the occasional fervent prayer, can be done by software. Specifically, by software with an AI sitting on top.
/ 02 - THE PROBLEMThe middle of the stack has been broken for twenty years.
It was easier to ignore. Then everything went subscription, usage, and partner-share.
For most of the 2000s, software companies sold licenses. You paid a number, you got a thing. Revenue recognition was a paragraph in an accounting textbook. Then SaaS happened. Then usage-based pricing happened. Then partner ecosystems, marketplaces, and AI-token metering happened. Then ASC 606 happened, which made the FASB the most-cited rulebook in board meetings since Robert.
The result: a contract for a modern enterprise customer might involve a base subscription, a usage tier with a credit pool, a partner-share clause, mid-cycle adjustments, and three different currencies. The CRM does not handle this. The ERP does not handle this. The seven Excel files between them used to. Until they didn't.
This is the problem RecVue was built to solve. Not a feature gap - a category gap. The empty middle where the bills get sent, the revenue gets booked, and the partners get paid.
/ 03 - THE BETOne founder. Twenty years of quote-to-cash. A single thesis.
Nishant Nair had been here before. He came back with a plan.
Nishant Nair spent more than two decades building order-to-cash and subscription billing systems before he started RecVue in 2015. The biography is not glamorous. The thesis is.
Nair's bet was that the seam between CRM and ERP needed its own platform - not another bolt-on, not another middleware. A revenue operating system, capitalized like it meant it. He raised seed money from Cota Capital and EPIC Ventures in 2018. Then, in January 2021, he closed a $13 million Series A from Cota Capital, EPIC Ventures, and Long Light Capital. Total raised since: just over $20 million.
For a company that now puts $100 billion of annual revenue through its platform, $20 million in venture funding is, to put it mildly, capital-efficient. It is the kind of ratio that does not get framed posters in a16z's lobby. It does, however, get customers.
/ 04 - THE PRODUCTRevOS, and the contract that reads itself.
Announced August 20, 2025. Less of a launch, more of a category claim.
RevOS is RecVue's name for the whole thing - the platform that orchestrates billing, revenue recognition, partner settlements, contract management, pricing, and analytics. The unsexy term for what RevOS does is "revenue lifecycle automation." The honest term is: it watches the contracts so people don't have to.
The headline feature is the Autonomous Contract Orchestrator. It uses what RecVue calls human-centered AI to parse contracts in real time, detect changes that move revenue, and trigger the downstream consequences automatically - billing adjustments, revenue waterfall updates, compliance flags. If a customer renegotiates a usage tier on a Tuesday, the books reflect it on Tuesday. Not at quarter-end.
Around the orchestrator sit the more conventional modules - billing automation for subscriptions, usage, and hybrids; revenue recognition compliant with ASC 606 and IFRS 15; a dynamic pricing engine; partner compensation management. Each one is a product in its own right. Together they are something more useful: one place where revenue rules live, instead of seven.
A short, honest timeline
- 2015Nishant Nair founds RecVue in Palo Alto. The pitch: a revenue platform that sits between CRM and ERP.
- 2018Seed round of $5M from Cota Capital and EPIC Ventures.
- 2021Closes $13M Series A led by Cota Capital. Long Light Capital joins.
- 2024Crosses $5B+ in recurring revenue managed for customers. Adds AI infrastructure customers.
- 2025Launches RevOS - AI Revenue Operating System with Autonomous Contract Orchestrator.
- 2025CIO Review names RecVue a top AI-powered multi-model monetization platform.
/ 05 - THE PROOFThe numbers, and who is putting them in.
Hertz, ACI Worldwide, Textainer, General Assembly. The names tell you the use case.
RecVue's customer list reads like a tour of industries that bill in ways that would make a SaaS startup faint. Hertz rents cars by the minute and the month. ACI Worldwide moves payments at planetary scale. Textainer leases shipping containers around the world. General Assembly teaches code in a dozen formats. None of these are tidy. All of them are billable.
Below, the platform's load - not what RecVue earns, but what it processes for customers. The unit of work is interesting because most enterprise software is sold on seat counts. RecVue is sold against scale.
What flows through RecVue
RecVue's own revenue is small relative to what it manages - in the single-to-low double-digit millions, depending on whose dataset you trust. That is the trade enterprise infrastructure makes: long sales cycles, multi-year contracts, and a customer who never wants to swap you out. Sticky in the good way.
/ 06 - THE MISSIONRevenue as a system.
The phrase is small. The implication is not.
"Revenue should be a system, not a silo." Nair has said this in interviews until the phrase is more or less a stamp on the company. It sounds like a slogan. It is closer to a worldview.
A silo is what most enterprises have today: billing in one place, recognition in another, partner share in a spreadsheet, contracts in a folder, pricing in a deck. A system is what RecVue wants them to have: one platform where the rules live, one place where the AI can reason across them, one source of truth for finance teams that have been told for a decade that they would have one any minute now.
/ 07 - WHY IT MATTERSThe AI economy bills weirdly.
Tokens, calls, credits, GPU-hours. Someone has to invoice for all of it.
The AI boom has produced a billing problem nobody talks about. Every model provider, every agent platform, every infrastructure layer is metering something - tokens, calls, credits, GPU-hours - and trying to settle revenue across partners who all want a cut. The 2010s SaaS playbook does not scale to this. The 2000s ERP playbook absolutely does not.
RecVue's pitch lands here. The company has already added AI infrastructure customers. RevOS is built for monetization models that change weekly. The competitive advantage is not feature parity with Zuora or Stripe Billing. It is the orchestration layer: contracts, settlements, recognition, and partner share running together.
Back to the cold-storage warehouse in San Mateo. Frozen blueberries shipped on a Wednesday. By Friday, revenue recognized, partner settled, books closed. That used to take a week of human labor. Now it takes a platform nobody on the customer side has to think about. Which, if you ask Nair, is exactly the point. The best revenue system is the one you never have to talk about.
RecVue is not loud. It is just very, very busy.