Sacra Logo

How does Nylas save developers time compared to other API providers, and what are some specific use cases of this time-saving integration?

Isaac Nassimi

SVP of Product at Nylas

I've actually got a pretty good one. Before I joined Nylas, I was at a company called Cience. I actually went the build route and ran the engineering and product department. For an application we were building, I championed us building these connectors ourselves to Gmail, Microsoft, and IMAP.

A year later, with a lot of intellectual fire power put into the application, it still wasn't there. Every time we'd look at it or breathe on it, it would break. It was one of those things that began to feel intractable. We weren't here to build connectors to Gmail. That's not what we set out to do, yet it was making up 30% of our total engineering time. 

When we rebooted the project, I actually bought Nylas. That was my first interaction with Nylas and it ended up not even being in any of our sprints. We integrated it once and forgot about it, and I mean that in the best way. 

We were able to reduce development overhead by 30%, but probably stress by somewhere around 80%, because when these things broke, this wasn't just like, "Our email’s out." These were “P0” fixes that we'd have to wake up in the middle of the night to do. 

Find this answer in Isaac Nassimi, SVP of Product at Nylas, on the market for developer middleware
lightningbolt_icon Unlocked Report