Marketplace — Modules & Starter Packs

The Marketplace is the single source of truth for what an account can install. It is used by both humans and the AI Operator, which is exactly why it exists as one catalog with one install path: configuration can never drift between "what a person set up" and "what the AI set up".

The Marketplace has three kinds of entries:

• Modules — installable capability units
• Starter Packs — vertical bundles of modules plus configuration
• Integration Providers — a dynamic catalog of connectable third-party services

Modules

A module is a single installable capability — for example, the Inbox AI module, a channel connector, or a reporting pack. Modules live in the platform-level catalog and are enabled per account. Installing a module makes its capability available inside that account only.

Starter Packs

A Starter Pack is a vertical bundle — a curated collection of modules plus the configuration a particular kind of business needs. Examples of the verticals shipped as packs:

• aesthetic-clinic
• marketing-agency
• ecommerce

A Starter Pack is not a module; it is a bundle. Applying a pack does three things in one operation:

1. Enables the pack's modules in the account
2. Creates the pack's pipeline (the CRM scaffold — pipeline and stages)
3. Creates the pack's message templates

One install path: applyStarterPack

There is exactly one code path that installs a Starter Pack: applyStarterPack. It is shared by:

• Manual install — a human clicking "install" in the Marketplace, and
• The AI Operator — calling its apply_starter_pack tool.

Because both routes call the same function over the same pack definition, the result is identical regardless of who initiated it. Adding a new vertical means adding a new Starter Pack definition — no new code.

Starter Pack (vertical)
  ├── modules    → enabled in the account
  ├── pipeline   → CRM pipeline + stages created
  └── templates  → message templates created

manual install ─┐
AI Operator ────┴──▶ applyStarterPack(pack, account)   // one code path

How the AI Operator uses the Marketplace

The AI Operator does not have a private, parallel notion of "how to set up a business". It reads and acts on the same Marketplace:

• To install a single capability, it calls install_module.
• To set up a whole vertical, it calls apply_starter_pack — the same applyStarterPack path as a manual install.

This is the design guarantee behind AI onboarding: when the Operator configures an account for, say, an aesthetic clinic, it produces exactly the modules, pipeline, and templates a human would have gotten by clicking the same pack. See AI architecture for the Operator's full tool set.

Integration Providers

The third Marketplace surface is the Integration Providers catalog — a dynamic, platform-admin-managed list of connectable services (Anthropic, Stripe, Twilio, and so on). Each entry is a pre-connection: logo, description, auth type, the credential label and hint, and exactly where to find the key. This catalog and the BYOK connect flow are documented separately in Integrations & BYOK.