Four Fluencies

A new framework for partner enablement in the era of AI

AI fluency demands partner fluency.

Enablement was built for an era when information was scarce, training was expensive, and partners had to be equipped before they could perform. That era is over. The infrastructure changed underneath us and the vocabulary hasn't caught up. This is an attempt to update it.

The four fluencies

Partner programs operate across four distinct dimensions. Each can be developed independently, but the strongest programs build fluency across all four at once.

KnowPortfolio Fluency
How well partners and their agents articulate your value, products, and competitive positioning in the moments that matter.
SellCo-Sell Fluency
How smoothly your joint go-to-market and attribution motions actually run.
DeliverDelivery Fluency
Whether partners can reliably produce customer outcomes, not just whether they can sell.
OperateProgram Fluency
How AI-native the partner program operations are themselves.

Place your program on the grid

Each fluency matures independently, through three stages. Pick the one that honestly describes your program today, not the one you are working toward. Nobody is fully Ambient on anything yet.

Portfolio
Co-Sell
Delivery
Program
Choose a stage in each row to see where your program sits.

The essays

Partners working with AI-native vendors will operate with continuous portfolio fluency, agent-mediated co-sell, instrumented delivery, and dynamic program ops. Partners working with traditional vendors will still be logging into portals to download last quarter's battlecard. The gap between fluent ecosystems and static ones will widen fast over the next eighteen months.

It's clear. AI fluency demands partner fluency.

An ongoing series. Delivery Fluency is up next.

Brian Quimby has led partner programs and enablement efforts across enterprises and startups for the last 15 years. The views expressed here are his own and do not necessarily reflect those of his current employer. Any information presented is drawn from publicly available resources, and all anecdotes and scenarios are hypothetical.