Ampersand favors native integrations over Nylas
Ayan Barua, CEO of Ampersand, on going upmarket with deep native product integrations
This is a wedge for Ampersand to move from CRM plumbing into the full operating surface of a SaaS app. If product teams already trust Ampersand to handle messy Salesforce and HubSpot sync, adding Gmail and Calendar lets it own the other workflow sitting next to CRM in sales, support, and recruiting. That matters because communication data is where follow ups happen, meetings get scheduled, and customer context is created before it is written back into a system of record.
-
Nylas sells a bundled communications layer, email and calendar with hosted auth, sync, webhooks, and scheduling, at $15 per month for 5 connected accounts and $1.50 per extra account on self serve plans. That is useful for broad coverage, but it also adds a per account middleware cost on top of the underlying Google or Microsoft stack, which is exactly the kind of cost sensitive layer an integration platform can try to replace or route around.
-
The bigger issue is control. Nylas built its value around a unified abstraction across Gmail, Outlook, IMAP, and calendar providers, while Ampersand is explicitly built around deep native behavior for each system. In practice that means handling custom workflows, high volume reads and writes, and provider specific quirks instead of forcing everything into one common model.
-
There is evidence that some product teams already prefer direct provider integrations when communication is core to the product. Shortwave chose to work directly with the Gmail API rather than use Nylas so it could tightly tune real time delivery, parsing, and UI behavior. That is the same pattern Ampersand is betting on, abstraction helps, but only if it stays close to the native product surface.
The market is moving toward narrower middleware that feels more native and more composable. As AI agents and vertical SaaS products need CRM, email, calendar, ERP, and analytics in one workflow, the winning infrastructure will look less like a generic universal API and more like a set of deep product specific connectors that can still be orchestrated together.