Product & Packaging Moves — How B2B Software Companies Move

Product and packaging moves are where a vendor's roadmap becomes a sales conversation. Across the 98 companies tracked in this hub, the dominant motion is not a single flagship launch but a steady cadence of tiering, module launches, early-access programs and agentic add-ons that change what a rep can put in front of a buyer and what a buyer can justify internally. For sales leaders, this is the raw material of competitive positioning: every new tier, module or preview is a new objection to handle and a new wedge to exploit.

Why it matters right now is that packaging has become the primary vehicle for AI monetisation. Vendors are no longer shipping AI as a free feature; they are wrapping it in named modules, tiered portfolios and governance consoles that carry their own price and their own buying committee. Sales-enablement teams that treat these as product news rather than as deal-shaping events will find themselves outmanoeuvred by reps who can map a new tier to a customer's budget line before the competitor's rep does.

Pattern name: AI as a separately packaged module, not a free upgrade. Heimdal Security opened early access to an AI Control Module, WithSecure launched Elements AI Security, Barracuda shipped an AI Data Security solution aimed at MSPs and SMBs, and ESET added an AI Security Module while renaming its AI Advisor to ESET LiveAI. The pattern is deliberate: AI capability is being carved out as a named, sellable SKU rather than folded into existing licences. That signals vendors want AI to expand deal size and create a distinct buying conversation, often with a different stakeholder (security, data governance) than the original purchase. For reps, the module becomes a land-and-expand lever and a reason to re-open accounts that already bought the core product.

Pattern name: tiered portfolios and support plans as a segmentation tool. ESET relaunched its PROTECT portfolio with Core, Premium and Ultimate tiers, Barracuda introduced tiered support plans (Core, Plus, Pro), and Sophos packaged CISO Advantage for organisations that have no CISO. This is packaging doing the job of market segmentation: a three-tier ladder lets a vendor serve SMB, mid-market and enterprise from one product line while giving sales a natural upsell path and a defensible reason for price differences. The Sophos move is especially telling, because it packages a service around a role the buyer does not have, which turns a product into an outsourced capability and shifts the conversation from features to risk coverage.

Pattern name: agentic and workflow layers shipped as previews and betas. Navan rolled out agentic travel and expense management inside Slack, Ramp launched a Glass AI workspace for company knowledge, Payhawk shipped its Fall '26 edition with MCP, playbooks and new AI agents, and Pleo announced Pleo MCP with GenAI agents in beta. Shipping in preview or beta is itself a packaging decision: it creates urgency and a feedback loop with early adopters while limiting support exposure. It also signals that vendors see the agent layer as the next competitive surface, and that integration into the tools buyers already use (Slack, MCP-compatible assistants) is becoming part of the product promise rather than an add-on.

Pattern name: governance, control and spend visibility as a premium wrapper. Outreach released an AI Control Hub for agentic AI governance, Rippling launched an AI Spend Console to govern corporate token costs and track ROI, and Ramp released Token Spend Management for AI infrastructure costs. These moves package control rather than capability, which is a mature-market signal: once buyers have AI features, they need to govern, budget and audit them. For sales teams this creates a second buying centre (finance, IT governance) and a compelling narrative for accounts that are worried about uncontrolled AI spend rather than about missing features.

What this means for sales leaders and sales-enablement teams: Reps need a packaging map, not a feature list: for each competitor, know which capabilities sit in which tier, which are in preview, and which carry a separate module price, so they can reframe a competitor's headline launch as an upsell the buyer has not budgeted for. Enablement should build battlecards around the tier ladder and the governance wrapper, because those are where discount pressure and expansion conversations will actually happen.