If you choose an integration platform that’s only good for one use case, chances are you’ll end up having to add another platform in the future for the other. Worse still, you may have to migrate to a totally new platform that can handle both scenarios later on. As such, choosing an embedded integration platform that can handle both productized and services-led integrations from the start tends to be the smarter play. A single platform for services and developers enables reuse “We iterate an integration across multiple customer requests until we end up with a really solid integration template that suits all of their needs. We develop our template through various configuration factors in our processes that gather across different implementations on various customer accounts.” — Will Clifford, Director of Product, Integrations, LeafLink Learn more There’s one other significant benefit of everyone being on the same platform across your services and product organization. Services teams can start by building integrations based on specific customer requirements. They can templatize integrations that have repeatability to improve their margins and accelerate delivery. Even better, they can hand off highly repeatable integrations they have built over to the development team, who can then turn them into productized integrations. As services and product teams create and templatize integrations, smart companies use the process to create a full-on integration pipeline. 9. Get into the weeds on certifications and security Ensuring your provider meets the most stringent security, compliance, and privacy requirements is critical to your company’s reputation and financial integrity, as well as your end customers’ trust. Among other things, it’s vital to confirm that your embedded integration vendor has information security (infosec) measures, procedures, and policies, backed by certifications and annual audits for SOC 2 Type 2, along with independent penetration tests. You’ll want to ensure your provider has fully documented both its technical and organizational security measures (see the complete list below). Also, embedded integration vendors must 22