Campaign Monitor vs Gumloop

Gumloop's window splits cleanly in two. On one side is Gumball, its first agent customers do not have to build, arriving with standing jobs — a morning briefing, meeting prep, and an inbox that sorts and drafts. On the other is the administrative apparatus an enterprise buyer demands: managed tunnels to private MCP servers, model access by role, approval routing, bring-your-own Fireworks keys, and GitHub-synced skill libraries.

Connector expansion continues at a steady clip — Azure, Meta Ads, DataForSEO, Sprout Social, SharePoint, NotebookLM, Zendesk, Gong — but it is no longer the story. The center of gravity has moved to who may use which model, where agents may reach, and who approves it, which is the vocabulary of a platform being bought by organizations rather than adopted by individuals. Distribution is moving the same direction, with agents pushed into Slack workspaces and reachable by people who have no Gumloop account.

Expect Gumball to graduate from beta with more standing jobs attached to the connectors already in the catalog, and expect the governance surface to keep thickening around it — audit and spend controls are the obvious gaps next to the role and approval work already shipped. The Outlook parity push suggests Microsoft-side coverage will continue to close against the Google-side features.