Nylas Chooses Developer Middleware
Isaac Nassimi, SVP of Product at Nylas, on the market for developer middleware
The real point is that a market can reward opposite product choices when each company picks a clear user and builds the whole experience around that user. Stripe went deep on programmable internet payments for developers and online businesses. Square went deep on in person commerce for small merchants, with readers, POS, payroll, banking, and later Cash App. The lesson for communication APIs is that expansion matters less than choosing one center of gravity and compounding around it.
-
Stripe and Square started from the same broad problem, moving money, but solved different workflows. Stripe helps a software team add checkout, subscriptions, billing, and payouts with APIs. Square helps a cafe or retailer take a card, print a receipt, manage staff, and run the back office from one system.
-
That is the analogy Isaac Nassimi is drawing for Nylas. In communication infrastructure, one path is horizontal developer middleware, where one API unifies Gmail, Outlook, IMAP, calendar, and message parsing. Another path is application software for end users, like inbox or customer service tools, where the company owns the workflow instead of the plumbing.
-
Nylas is explicitly choosing the middleware path. The product abstracts OAuth, syncing, webhooks, thread handling, and data cleanup so a customer can drop email and calendar into an app without building connectors for each provider. That makes focus a strategic asset, because every added channel has to reinforce the shared abstraction instead of turning into a bag of unrelated APIs.
Going forward, communication software is likely to split the way fintech did. Some companies will win by becoming the default infrastructure layer for developers. Others will win by owning a specific end user workflow. The durable winners will be the ones that make one hard choice early, then keep stacking adjacent products that make that original choice stronger.