Continuing with last week’s post titled Integrations as Key for Next Generation SaaS Success, there’s a critical point that was missed in that not all product integrations are created equal — not even close. For SaaS 2.0 startups, catching up to the depth and variety of integrations of the incumbents is one of the major challenges. When thinking through integrations, it’s important to understand the three major types:
- Native Integrations – Integrations that are developed in-house to send/receive data as well as call remote functions and expose additional internal functionality are native integrations. Native integrations are the most valuable as the quality is typically higher and the SaaS company is committed to maintain them.
- UI Overlay Integrations – Integrations that are done via a Google Chrome Extension to override the user interface of a third-party app are UI overlay integrations. A common example is the industry of Chrome Extensions that add functionality to Gmail through the user interface and not the API.
- Middleware Integrations – Integrations that are written and maintained by a third-party integration platform to connect two disparate apps are middleware integrations (e.g. MuleSoft or Zapier). Middleware integrations can be more expensive and/or slower depending on the APIs of the products being connected.
When thinking through the integration landscape, it’s important to understand that there are a variety of integration types and they aren’t equal.
What else? What are some more types of integrations with SaaS products?