Roadrunner

What it is

Roadrunner is a CPQ built around agents instead of forms. Its shorthand is PQA, “Prompt, Quote, Approve”: a rep describes the deal in plain language, the Quote agent builds or edits the quote and shows the adjustments and discounts behind each line’s final price, and the approval engine routes it to the right reviewers in the right order, with a Slack notification and an AI-generated quote summary for each approver. A second agent faces the admin. Admin Agent, launched on October 7, 2026, changes catalog entries and pricing rules from natural language (“apply a 15% discount on AI Units when the quantity reaches 1,000”), checks the new rule against existing ones for conflicts, and tests the change on generated quotes before it ships. The same configuration capabilities are exposed to Claude, ChatGPT and other clients through an Admin MCP.

The company was incubated inside Kleiner Perkins, its first incubation in five years, and founded in 2025 by Joubin Mirzadegan (a Kleiner partner who built and ran sales organizations), Ajay Natarajan and Eugene Shao, who previously co-founded Athena. It announced general availability on May 12, 2026 together with $27 million in funding: a seed led by Kleiner Perkins and a $22 million Series A led by Founders Fund. Customer logos on its site include Asana, ZoomInfo, 6sense, Klaviyo, Chainguard, Watershed and Metaview, which tells you the target: software companies with enterprise deal desks.

Why it shows up in RevOps stacks

• Salesforce CPQ is end-of-sale. Salesforce stopped selling CPQ to new customers on March 27, 2025, and every team still running it now has a migration decision on the calendar. Roadrunner sells straight into that decision and runs on top of Salesforce rather than asking you to leave it.
• The rules are the product, and agents maintain them. The expensive part of a legacy CPQ is the admin who understands why rule 214 exists. Admin Agent’s conflict check and pre-release test runs target exactly that maintenance cost.
• Usage and subscription pricing on one quote. The product page lists usage, outcome, subscription and one-time charges together, with ramps, credits, commitments, minimum commits with pay-as-you-go, and overage. Upgrades, downgrades, swaps, cancellations and renewals can live in a single quote, with entitlements tracked over time.

Pricing reality

There is no pricing page; roadrunner.ai/pricing returns a 404 and every call to action is “Get in touch.” No seat price, tier or minimum has been published anywhere. The one public money signal is from Kleiner’s Mamoon Hamid, who told Fortune the company closed its first seven-figure deal within three months. That is a total contract figure, not a list price, but it places Roadrunner in enterprise procurement, not in a credit-card purchase.

Budget against the published comparables. Salesforce Revenue Cloud lists at $150 to $200 per user per month, so 50 Advanced seats cost $120,000 a year at list. Vendr puts the median annual contract at $44,297 for DealHub and $67,167 for Nue. A mid-market deal desk should expect a Roadrunner quote in that $45,000 to $120,000 band, an enterprise multi-product rollout above it, and should treat any number as a first offer from a startup that needs reference logos.

Best for

RevOps and deal desk leaders at Salesforce-run software companies with complex, mixed usage-plus-subscription deals, who are leaving Salesforce CPQ and want reps quoting in plain language and admins changing rules without a consultant. It fits best when your catalog changes monthly and approval cycle time is the complaint you hear most.

Do not buy it if you are on HubSpot or Dynamics: Salesforce is the only CRM the site names. Do not buy it for billing either, since Roadrunner hands off to “downstream finance and billing systems” rather than invoicing itself. And for one or two SKUs at list price, a CRM quote template does the job without a CPQ.

Versus the alternatives

Salesforce Revenue Cloud (Agentforce Revenue Management) is the default path off Salesforce CPQ and the incumbent by installed base. Pick it when staying inside one vendor’s data model and support boundary outweighs speed, and budget the 3-6 month migration Salesforce itself quotes. Pick Roadrunner when the old CPQ’s rule sprawl is the reason you are shopping.

Conga CPQ is the other large incumbent, heavier since it absorbed the PROS B2B business in February 2026. Pick it when price optimization, rebates or channel pricing are the requirement, or when you are on Dynamics or HubSpot.

DealHub wins when you want the whole chain from one vendor: CPQ, buyer-facing DealRoom, CLM and, since its Subskribe acquisition, billing.

Nue is the fast-growing Salesforce-native alternative and the closest architectural match. Pick Nue when billing and revenue recognition must be in the same product as quoting; pick Roadrunner when the agentic quoting and admin experience is the deciding factor and billing stays where it is.

If none fit, fix the price book first. An agent that enforces pricing policy cannot enforce a policy nobody has written down; the deal desk pricing skill shows the policy layer that has to exist before any CPQ.

Watch-outs

• Very short production record. Roadrunner went GA in May 2026, and the only quantified customer result is Chainguard’s sales operations director saying they went live “in twelve weeks.” Guard: ask for two reference customers on a deal shape like yours (ramps, usage, amendments), and write go-live milestones and an exit clause into the order form.
• Integration surface is thin on paper. The site names Salesforce, Slack and MCP. It names no e-signature, ERP or billing connector, no public REST API and no security certification. Guard: list every system the quote must reach (DocuSign, NetSuite, Stripe, tax) and get each integration demonstrated in your sandbox, plus a SOC 2 report, before security review signs off.
• Agent-written rules can still be wrong rules. Admin Agent checks conflicts and runs tests, but the tests are generated from your configuration. Guard: keep a human approval on every rule change, maintain your own set of golden quotes with known correct totals, and re-run them after each Admin Agent edit.
• Admin Agent has documented limits. It can answer questions about users and roles but cannot edit them, and the in-app agent does not yet accept attachments, so you cannot hand it a pricing spreadsheet. Guard: plan role administration and bulk catalog loads as manual or implementation-team work.