Case Study: In 2019, Typeform had developed just a few integrations and had a backlog of integration requests from customers. Then in 2020, the company adopted an embedded integration solution and developed 20 integrations. By 2021, it had developed 70 more integrations with the help of its partners and, by using its embedded integration solution, had delivered more than 100 integrations in total. Learn more: How Typeform Went From 30 Integrations to 100+ in Just One Year, Crossbeam Blog 10 KEY CRITERIA FOR CUSTOMER INTEGRATIONS 1. Assess integration development velocity, efficiency, and flexibility You’re in the market for an embedded integration platform to clear your backlog and accelerate your roadmap. And that means one thing: The platform you embed must enable substantially faster integration velocity than you have today. So you’ve got to get this one right—because if the platform you choose doesn’t deliver velocity and developer efficiency advantages, it’ll kill your ROI and risk a future tear out. Business case tip: The less engineering effort required to build and maintain integrations than building in-house—the more significant the ROI on your embedded integration. It’s that simple. The solution you choose must speed connectivity to your end customers’ stacks with built-in connectors (we’ll cover what to look for later). But it also must enable the rapid development of reusable business logic, such as branches, lookups, data transformations, and error handling—all while ensuring as little engineering effort as possible with maximum reusability. Modern low-code embedded integration platforms enable your development teams to visually build the whole integration workflow, from your customers’ stack to your product, and all the logic in-between. You’ll also want to look for solutions that give you the option to turn your integrations into reusable templates for any of your customers with similar needs to activate them. Of course, low-code isn’t a panacea; it’s essential to have the ability to add in code to enable more customization if needed. 6
Embedding Integrations in Your Product Page 5 Page 7