Embedded AI features are useful, but they do not solve the whole GTM workflow. If every tool gets its own assistant, teams still have to coordinate the work across tools.
Industry signal
Gartner expects enterprise apps to rapidly add task-specific AI agents. That means every major SaaS product will offer more AI, but it also means teams may face more fragmented AI surfaces unless a coordination layer emerges.
Why it matters
A Salesforce assistant can help with Salesforce. A support assistant can help with support. A meeting assistant can help with a meeting. The customer workflow still spans all of them.
Our take
The future is not one AI button per SaaS product. It is one operator layer that can use the right SaaS product at the right moment.
What we built
Navigator is designed to sit across HubSpot, Salesforce, Slack, Gmail, Calendar, PostHog, Jira, Zoom, and Gong so the user can start with intent instead of deciding which tab deserves the next click.
Where this goes
The GTM stack will keep adding specialized tools. The more specialized it gets, the more valuable the operator layer above it becomes.
Sources behind this piece
FAQ
Are embedded AI features bad?
No. They are useful inside a product. They are incomplete for workflows that cross products.
What problem does Navigator solve instead?
Navigator coordinates customer-facing work across the GTM stack from one surface.
Want to see Navigator operate your stack?
We'll map one post-call workflow across your GTM systems and show where Navigator can reduce operator burden without replacing the judgment your team needs.
Map your GTM stack