Fetching from the wire…
Public story · 2026-08-04 · high
The gap between building CPQ rules and going live is bad product catalog data, not the discount logic itself.
Why now: SaaStr posted the demo recap as part of its August 4 AI Day coverage.
An AI agent built a working guided-selling ruleset from plain English in about two minutes at SaaStr AI Day, per SaaStr.
For quote-to-cash buyers, that's the real number: configuration speed and implementation speed have split apart. Full CPQ implementation still averages 90 days, per SaaStr, sometimes a year.
Nue's agent backed the claim with two live tests. It correctly routed a 35% discount to approvals and refused a 150-unit order against a 75-unit tier cap.
The agent didn't just generate rules from a prompt. It wrote its instructions to a markdown file, then validated them against the live product catalog, per SaaStr.
That validation step is where the 90 days comes from. The reasoning, per SaaStr: good in, good out, and broken data produces a broken CPQ.
Nue's demo shows the AI layer that builds CPQ rules is basically solved. The real competitive edge is who can shrink that 90-day data-cleanup window, not who has the fastest rule builder. Watch whether CPQ vendors start selling data-migration speed as hard as they sell two-minute demos.
SaaStr posted the demo recap as part of its August 4 AI Day coverage.
Each link below shares sources, entities, or timing with this story.
SaaStr released Qbee / Shared entity: SaaStr / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (SaaStr released Qbee); both cover SaaStr; reported by the same outlet (saastr.com).
SaaStr uses Claude / Shared entity: SaaStr / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Claude); both cover SaaStr; reported by the same outlet (saastr.com).
Jason Lemkin works at SaaStr / Shared entity: SaaStr / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Jason Lemkin works at SaaStr); both cover SaaStr; reported by the same outlet (saastr.com).
SaaStr criticizes Marketo / Shared entity: SaaStr / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr criticizes Marketo); both cover SaaStr; reported by the same outlet (saastr.com).
SaaStr uses Claude / Shared entity: SaaStr / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Claude); both cover SaaStr; reported by the same outlet (saastr.com).
SaaStr uses Replit / Shared entity: SaaStr / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Replit); both cover SaaStr; reported by the same outlet (saastr.com).
SaaStr uses Artisan / Shared entity: SaaStr / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (SaaStr uses Artisan); both cover SaaStr; reported by the same outlet (saastr.com).
SaaStr uses Claude / Shared entity: SaaStr / Same source domain / Earlier coverage / Tension
Linked by a graph relationship (SaaStr uses Claude); both cover SaaStr; reported by the same outlet (saastr.com).