For productized integrations, the platform you embed should provide: 1. Custom white-labeling 2. An integration activation component for end customers 3. Development of reusable, parameterized integration templates 4. End customer authentication management 5. Robust APIs to enable a seamless embedded experience Services-led integrations The other delivery model is services-led integrations. As the name suggests, your services organization (which may include integration specialists) implements such integrations, often as part of a statement of work (SOW). “For our services team, it was critical to have a platform that non-developers could build customer integrations for workflows on, and transition to an embedded, self-service model, to fully offload integrations over time.” — Clark Hager, Client Solutions Director, Bizzabo Often, services-led integrations are different because they may have higher variation from customer to customer, which makes it impractical to productize them. For example, Customer A might need a homegrown system integrated with your application, while Customer B might have an ERP it has heavily customized, and so on. So while you can templatize certain aspects of your integrations, services will ultimately be scoping, quoting, and building each for custom delivery. Or perhaps your services team is building out a specific integration for the first time for a customer, which means that services teams are looking to take the lead—and that it’s unclear whether the integration is worth productizing. For services-led integrations, your embedded integration solution should provide: 1. A highly flexible, low-code integration builder 2. Collaboration and secure workspaces for project development 3. Single sign-on (SSO) for integration builders 4. On-premises integration to connect complex stacks 5. Easy-to-consume learning materials to enable services teams 20