My Take on What Roadrunner Is Doing

I'm a longtime friend of Frank Sohn's CPQ Podcast (Novus CPQ). I have sat in that guest chair myself, so I know the format: Frank asks the questions the rest of the industry is too polite to ask, and the guest gets room to make their case. His recent episode with Tiffany, Roadrunner's head of solution architecture, was one of the more provocative conversations he has run in a while. So I did what any friend of the show does after a good episode: I kept arguing with it in my head for days.

And here is the quiet irony I can't resist pointing out. One real drawback of going on a specialized podcast is that it hands your competitors a front-row seat into exactly what you are building. So to Roadrunner: thank you for the generous product briefing. I took notes.

Here is my take, cleaned up. I graded what I heard the way I would grade any bold new entrant: two stars for what genuinely lands, one wish for what still needs to grow up. Three sections, six stars, three wishes. And a tip of the hat to Frank for getting it all on tape.

First, what Roadrunner CPQ actually claimed on the show

For readers who missed the episode: Roadrunner is an AI-native quote-to-cash company pitching a new category it calls PQA (Prompt, Quote, Approve) as the successor to CPQ. Tiffany described a platform that lets you prompt a quote into existence, spin up several pricing scenarios in seconds, bulk-edit lines through an agent, and push approvals into Slack in real time. She was candid about the backing too: Roadrunner was incubated by Kleiner Perkins, cofounded in 2025, and has raised $27M (seed led by Kleiner Perkins, Series A led by Founders Fund). It runs standalone but ships with a Salesforce managed package and connectors for the usual suspects like NetSuite, Zuora, Ironclad, and Docusign.

That is a lot of confidence for one episode. Some of it is earned. Some of it I would gently return to sender.

Section 1: The product Tiffany demoed in words

Star. The interaction model she described is a real leap. Prompting a quote into existence and generating pricing scenarios side by side is not a reskin of a click-through wizard. Anyone who has watched a rep wrestle a legacy configurator for twenty minutes heard that segment and felt something. Credit where it is due.

Star. The performance story is more than marketing. Recalculating everything on every change, with no batching, no "click to calculate," and no ceiling on quote lines, goes straight at one of legacy CPQ's most notorious weaknesses. That is a real engineering bet, and Frank was right to press on it, because it is testable rather than vague. This is not true for all legacy CPQs - but still a valid point.

Wish. I wish the "built for any industry" claim came with receipts. Tiffany was honest that every real Roadrunner customer today is a SaaS or usage-based tech company on a modern stack, which is the easiest CPQ problem there is. The manufacturing and telecom support she mentioned lives in internal "would this work for..." design conversations, not shipped deployments. I spend my days in the hard corners of configuration and I will believe the slogan when I see the difficult deployment.

Section 2: The "CPQ is dead" category play

Star. Roadrunner has named the pain correctly. Legacy CPQ frustration is real, adoption failures are real, and Salesforce moving its long-dominant CPQ to end-of-sale created a genuine vacuum. Walking into an unsettled market with a fresh answer is good instinct, and Frank's audience knows that frustration first-hand.

Star. Reimagining the workflow, not just the form, is the right ambition. Folding approvals into chat so they happen in real time, and treating the agent and the UI as interchangeable, is the kind of thinking this category has needed for a decade.

Wish. I wish they would retire the funeral. "CPQ is dead, meet PQA" makes a great podcast soundbite, but a rename is not a reinvention. Strip away "prompt, quote, approve" and you still have configure, price, quote. The hard problems have not vanished: product rules and constraints, discount governance, amendments and renewals, dirty data migration, clean CRM and ERP integration. AI changes how you touch those problems. It does not make them disappear. Call it evolution. It is a strong story without the graveside theatrics.

Section 3: The delivery model, which hit closest to home

This is the part of the episode that made me sit up, because it is aimed squarely at people like me.

Star. Owning the outcome is a bold, welcome bet. Bundling implementation into the license and putting Roadrunner's own team next to the customer aligns incentives in a way the old "pay the vendor, then pay the integrator by the hour" model never did. I can respect that even when the target is my own corner of the industry.

Star. Pointing AI at delivery itself is genuinely clever. Using models to read a customer's existing configuration and Roadrunner's own codebase to auto-generate setup is real leverage that a product company has and a traditional integrator does not. If the quality holds up, it matters.

Wish. I wish the confidence came with more humility about the last mile. "The SI model is dead" lands a little rich next to "half the time," "shipped in 48 hours," and "scenarios in six seconds." Those are wonderful demo lines and unfalsifiable promises. CPQ value has never lived on the happy path. It lives in the amendment logic, the renewal co-terming, the ten years of messy assets, and the approval matrix that reflects how a business actually says no. Add early-stage reality (small team, first customers, roadmaps standing in for features) and the "integrators are obsolete" verdict feels premature. That last mile is exactly where I have watched projects be won and lost.

My closing take

Promising, genuinely so. Tiffany made a strong case, and the technology behind it is real. But a podcast is a place to make the boldest version of your argument, and the boldest version writes checks the roadmap has not cashed yet. If you are shopping for a Salesforce CPQ alternative and you look like a modern SaaS company, Roadrunner belongs on your shortlist. If you live in complex, industrial, or regulated quoting, treat it as one to watch and pressure-test hard.

Mostly, though, this is why I keep coming back to Frank's show. Episodes like this are how our industry argues in public and gets sharper for it. My advice: reward the architecture, ignore the obituary, and grade every AI-native entrant on the unglamorous problems that decide whether a CPQ project lives or dies. Thanks, Frank. Save me a seat. And thanks, Roadrunner, for the front-row view.

Roadrunner CPQ FAQ

What is Roadrunner CPQ?
Roadrunner is an AI-native quote-to-cash platform that pitches a new category called PQA (Prompt, Quote, Approve) as a successor to CPQ. It runs standalone and integrates with Salesforce via a managed package.

Is Roadrunner a Salesforce CPQ alternative?
It can act as an AI-native quoting layer for Salesforce customers rather than a full CRM replacement. Whether it replaces your CPQ depends on the complexity of your configuration and approval needs.

Who funds Roadrunner?
Roadrunner was incubated by Kleiner Perkins and has raised $27M, with a seed led by Kleiner Perkins and a Series A led by Founders Fund. It was cofounded in 2025.

Where can I hear the full conversation?
On the CPQ Podcast hosted by Frank Sohn of Novus CPQ. The post above is my personal reflection on that episode, not a transcript.