Integration scope is sellable
CRM, analytics, webhook, support desk, live chat, and AI hooks belong in public discovery because they are commercial differentiators.
Integrations are active sellable scope, not background implementation detail. This route keeps CRM, analytics, webhook, support, and AI hooks visible with honest state markers.
CRM, analytics, webhook, support desk, live chat, and AI hooks belong in public discovery because they are commercial differentiators.
The route explains what is possible but avoids any subscription or subscription mutation while logged out.
Surface breadth is shown now; full tenant-operable integration routes land in later runtime workflows.
These are future-facing add-on capabilities routed into pricing without implying that every connector is already fully shipped.
Integration-family add-on tracked in the public discovery setup.
Commercial handoff: See add-on pricing via /pricing
Integration-family add-on tracked in the public discovery setup.
Commercial handoff: See add-on pricing via /pricing
Integration-family add-on tracked in the public discovery setup.
Commercial handoff: See add-on pricing via /pricing
Integration-family add-on tracked in the public discovery setup.
Commercial handoff: See add-on pricing via /pricing
Integration-family add-on tracked in the public discovery setup.
Commercial handoff: See add-on pricing via /pricing
Integration-family add-on tracked in the public discovery setup.
Commercial handoff: See add-on pricing via /pricing
Integration-family add-on tracked in the public discovery setup.
Commercial handoff: See add-on pricing via /pricing
Integration-family add-on tracked in the public discovery setup.
Commercial handoff: See add-on pricing via /pricing
Integration-family add-on tracked in the public discovery setup.
Commercial handoff: See add-on pricing via /pricing
Integration-family add-on tracked in the public discovery setup.
Commercial handoff: See add-on pricing via /pricing
The route can sell the family, but it must keep planned integrations visibly planned until their runtime and verification surfaces really exist.
Public selling routes stay browse-safe until pricing, signup, and signed-in subscription flows take over.
Montie
Browse-safe guidance only. Billing and checkout still require your explicit confirmation.
Text mode is live now. Voice preview requires explicit consent, stays browse-safe, and cools down if repeated public requests trip abuse protection.