# Conversational Commerce The category where the storefront is the conversation. Buying, asking, support, re-engagement — all happen inside a chat surface (messaging app, DM, social thread, chat widget) rather than through a classical web-store funnel. The surface may be synchronous or asynchronous; the defining feature is that **the purchase decision is completed in-thread, not in a cart**. ## Why the category exists - Mobile-first buyers spend the majority of their attention in messaging apps, not in browsers. - Social platforms have become discovery engines; the friction cost of jumping out to a classical checkout is high enough to lose the sale. - Lightweight merchants cannot afford bespoke checkout UX; embedding commerce in existing conversational surfaces collapses the build. ## The three commerce jobs 1. **Acquire** — turn impressions and organic engagement into a first conversation. 2. **Support** — turn support requests into resolved issues (and often into additional sales). 3. **Retain** — bring the buyer back, ideally before they'd come back on their own. Any product in the space should be mapped to which of these jobs it actually performs end-to-end. See §2 of [[AI Agent Vertical SaaS DD MOC]] on jobs-to-be-done vs. features. ## Structural features of the category - **Multiple surfaces** (native chat, SMS, WhatsApp, Instagram DM, web chat) — integration breadth matters, but depth matters more. - **Data fragmentation** — customer identity, order history, support history, and marketing consent live in separate silos. Unification is both a pain point and a wedge. - **Trust gradient** — conversational commerce is high-trust; tone, latency, and accuracy compound or erode that trust quickly. - **Locale sensitivity** — language, script, dialect, and cultural conventions change the product in a non-trivial way per region. See [[Emerging Market SaaS DD]]. ## What to probe in DD - Which of the three jobs does the product actually complete today vs. aspire to complete? - Which surfaces are integrated deeply vs. surface-level? - Is the merchant's data unified inside the product, or is the product another silo? - What is the attachment rate per merchant across the three jobs (the real platform test)? Related: [[AI Agent Vertical SaaS DD MOC]], [[Interoperability of Messaging]], [[AI Eats Services Not Software]] --- Tags: #verticalAI #businessmodel #category