API limits and native AI lock-in
Town
The core risk is distribution and data access collapsing back to the platforms that already own the inbox, calendar, chat history, and document graph. Town can orchestrate work across Google, Slack, and Microsoft only as long as those systems keep exposing enough read and write access at usable speeds, while each incumbent is also building its own AI layer with native access, admin controls, and security positioning inside the same workflow.
-
Microsoft is making Copilot itself a first party data plane. Its Copilot APIs run on Microsoft 365 data, require Copilot licenses, and stay inside Microsoft 365 compliance boundaries, while Graph and Copilot connectors enforce throttling. That makes native Copilot extensions easier to justify than a separate agent that must constantly pull data out through standard APIs.
-
Slack is moving the same way. Slack AI and enterprise search now promise permission aware answers across Slack and connected apps, inside Slack’s trust boundary, while admins can turn AI features on or off and restrict what AI can access. At the same time, Slack’s developer platform still applies explicit rate limits, so an outside automation layer has less room to operate than Slack’s own native features.
-
Google exposes the same structural dependency through quotas and admin controls. Gmail and Calendar APIs are governed by per user and per project limits, while Gemini access to Workspace data is centrally controlled by admins. For Town, that means capability is not just about model quality, it is about whether Google keeps enough throughput and permissions open for a third party to act like a full time coworker.
This market is heading toward a split where horizontal agent startups win only when they do something the suite owner will not do, or cannot do cleanly across rival ecosystems. As Google, Slack, and Microsoft thicken their own AI layers, Town’s best path is to become the cross platform work coordinator that native assistants still cannot match.