Nue.io

Inside a conference room at OpenAI, Keith Jones watches a sales rep configure a deal. The subscription includes usage-based API pricing, tiered seats, and a custom enterprise discount. Eight months ago, this would have meant spreadsheets, Slack threads, and someone in finance manually checking the math. Today, the rep clicks twice. The quote generates. The billing rules cascade automatically. Jones, OpenAI's Head of GTM Systems, calls it "one of the smoothest deployments of my career."

The Problem Nobody Wanted to Fix

Revenue operations is where software dreams go to die. It sits at the intersection of sales, finance, and product - a Bermuda Triangle of spreadsheets, manual approvals, and pricing models that stopped making sense three business pivots ago.

By 2019, enterprise software had solved nearly everything except the mundane horror of getting from quote to cash. Companies used one system to configure prices, another to manage subscriptions, a third to handle billing, and a fourth to reconcile it all. Data moved between them through integrations that broke on Tuesdays and exports that someone forgot to run.

The problem wasn't lack of tools. Salesforce CPQ existed. Zuora handled subscriptions. NetSuite managed invoices. Each solved its slice of the puzzle competently. But when a customer wanted to add three seats mid-contract, convert from monthly to annual billing, and apply a promotional credit - all in the same transaction - the systems started arguing with each other in languages none of them fully understood.

The founders of Nue knew this particular hell intimately. Tina Kung had spent two decades building the tools that created it - leading engineering at Salesforce CPQ, Zuora, and Oracle CPQ. She understood exactly why the patchwork existed, and why it would never work properly. The architecture was the problem, not the features.

The Founders' Bet

Before writing a single line of code, Kung and her co-founders Kate McCullough and Cheng Zou did something unusual. They interviewed 70 CFOs and revenue leaders. Not to validate their product idea - they didn't have one yet. They wanted to understand why the problem persisted despite billions spent on solutions.

McCullough brought the go-to-market perspective. She'd been part of the early team at Anaplan, scaling from Series A through Series D. She'd watched companies spend millions implementing revenue systems that still required spreadsheets to bridge the gaps. Zou contributed deep technical expertise in building scalable SaaS platforms.

The answer was architectural. Every existing tool solved one piece of the revenue puzzle, creating data that had to be translated for the next system. A quote in CPQ became an order in subscription management became an invoice in billing. Each translation introduced latency, errors, and the need for someone to check the numbers. Revenue teams spent more time reconciling systems than actually analyzing revenue.

Nue's bet: build everything on a single data model. When a rep creates a quote, the billing rules already exist. No handoffs. No translations. No downstream work. The same data structure that holds the pricing logic carries through to the invoice. One source of truth from opportunity to cash.

The Founding Team

The Product

Nue is a quote-to-revenue platform built natively on Salesforce. It handles the entire revenue lifecycle - from the moment a rep configures a price to the invoice landing in accounts receivable. The platform supports subscription billing, usage-based pricing, one-time charges, credits, and hybrid models that combine all of the above.

The Salesforce-native architecture matters. Companies already live in Salesforce for CRM. When the CPQ and billing system exists in the same environment, there's no integration to maintain, no data sync to debug, no middleware layer adding latency and complexity. Sales reps don't need to learn a new interface or switch between applications mid-deal.

What sets Nue apart is the channel flexibility. The same pricing logic that powers a rep-assisted enterprise deal also powers self-service checkouts on the company website and partner-sold transactions through reseller portals. Most companies cobble together different systems for each channel. Nue treats them as configurations of the same underlying engine.

The Journey So Far

The Proof

OpenAI's implementation tells the story best. The company was managing ChatGPT Enterprise pricing through spreadsheets - a setup that worked at startup scale but collapsed under hypergrowth. They needed a system that could handle seat-based subscriptions for enterprise clients and consumption-based API billing for developers, ideally without requiring a team of analysts to reconcile everything.

The complexity was genuine. OpenAI sells to individual developers paying for API tokens, small teams buying ChatGPT Plus, enterprises negotiating custom contracts, and partners embedding the technology into their own products. Each segment has different pricing mechanics, different approval workflows, different billing cycles. Traditional approaches would require separate systems for each, with an army of analysts reconciling the differences.

Nue deployed in eight weeks. Not eight months. Weeks. OpenAI's sales team, accustomed to dreading new software, was "relieved at how straightforward" it was. Keith Jones, their Head of GTM Systems, called it "one of the smoothest deployments" he'd experienced - and he'd implemented plenty of revenue systems in his career.

Notable Customers

The Culture Factor

Nue earned Great Place to Work certification with numbers that would make most HR departments suspicious. 97% of employees call it a great workplace. 100% say they're given significant responsibility. 100% report they can count on colleague cooperation. These aren't self-reported vanity metrics - third-party certification backs them up.

The company philosophy distills to "Brilliantly Nue" - big thinking without ego, innovation through supportive teamwork. At 120 people across eight countries, they've maintained the culture that usually dies around employee fifty. The distributed nature of the team hasn't diluted the cohesion; if anything, it's forced clearer communication and more intentional collaboration.

Mark Walker, who joined as CEO after selling his previous company Strongpoint to Netwrix, brings two decades of experience scaling SaaS operations. His leadership style emphasizes customer empathy - understanding the pain points before proposing solutions. The executive team reads like an all-star roster of revenue operations veterans, with alumni from Zuora, Salesforce, Talkdesk, and Fivetran.

Why It Matters

B2B pricing got complicated. Usage-based billing, consumption credits, hybrid models, product-led growth alongside enterprise sales - these weren't edge cases anymore. They were the standard playbook for any SaaS company trying to meet customers where they are. A company might charge by seat for their core product, by API call for their developer platform, and by outcome for their enterprise tier - all to the same customer.

The old tools couldn't keep up because they were built for a simpler world. Nue was built for this one. The unified data model means that pricing complexity doesn't create operational complexity. Sales teams can experiment with new pricing structures without waiting months for finance systems to catch up.

In October 2025, they launched Nue AI - an agentic system that can handle mid-term changes through natural language prompts. OpenAI and Anthropic served as design partners, which says something about the technical credibility of the platform. The AI doesn't just answer questions about revenue; it executes transactions with full audit trails. A finance manager can ask it to "apply a 15% discount to all renewals closing this quarter" and watch it generate the appropriate amendments across hundreds of contracts.

The implications extend beyond efficiency. When revenue operations becomes intelligent and automated, companies can offer pricing flexibility that was previously too expensive to support. Custom deals, complex amendments, usage-based components - these become features rather than operational burdens.

Back to That Conference Room

OpenAI's revenue operations used to require reconciliation spreadsheets and weekly alignment meetings between sales and finance. The complexity was understandable - they were scaling one of the fastest-growing products in technology history while managing both consumer subscriptions and enterprise contracts. Different pricing models. Different billing cycles. Different approval chains. All needing to reconcile into coherent financial statements.

Today, when a rep configures a deal in Nue, the billing rules propagate automatically. Finance sees the same data sales sees. The invoice generates from the quote. No translation layer. No manual checks. No Tuesday integrations to debug. The sales rep who configures that complex multi-product, multi-pricing deal doesn't need to think about what happens downstream. The system already knows.

This is what the founders saw when they interviewed those 70 CFOs. Not a feature gap, but an architectural flaw in how the industry approached revenue. Every company was building bridges between islands when what they needed was a single continent. Fix the foundation, and the problems built on top of it disappear.

Keith Jones still sits in that conference room, watching deals configure in seconds. The spreadsheets are gone. The reconciliation meetings are shorter. The sales team stopped dreading software implementations. OpenAI's revenue operations now match the pace of their product innovation.

Nue fixed the foundation. Everything else followed.