Once companies become more data-driven, they need better processes and tools. But, so many solutions work in silos and make the work time-consuming and inefficient. Therefore, many businesses consider integrating data from various systems.
However, the process itself is a vast unknown to many organizations, and so we decided to invite Henry VanKampen Dufloth, a technical consultant at Denamico, Inc. to the show and asked him to bring these solutions closer to the audience.
As we talk about how integrating your data can drive growth, Henry explains the difference between native and non-native integrations, configuration and customization, and low-code and no-code solutions. He also delves into how companies choose one over another.
Native vs. non-native integration. When considering a system integration, most companies come across these two options but rarely know what they involve. Therefore, we asked Henry to explain the two. ''A native integration is going to be offered by a large community. It's managed by a big company, or it's offered by the platform that you're working on. So I'll put it in our terms with HubSpot: [...] HubSpot has a whole marketplace where either it's HubSpot themselves building and managing it or another larger company that builds and manages it and meets HubSpot standards to list it on there. That's what we would consider native. [...] A non-native is going to be anything outside of that. That's going to be something that someone's going to have to build out. [...] You have to put some forethought into it. You have to do the planning and get everything in the right spot, taking it even a step further. It could be coded integration, [...] where it's fully coded by a development team, and maybe they're managing it.''
Let's talk about low-code/no-code solutions. So, as the podcast goes on, we hear two new terms which, according to Henry, have been a big thing for the last few years and are only getting bigger. So what do these two mean, and why are they worth considering? ''So low-code/no-code is converse to fully coded custom integration. It's easier for a company to have an admin go in and make some edits on these low-code integrations than hire a full-time developer to manage these or custom-coded applications. Zapier is a good example of it. [...] Essentially, they hit an endpoint. Generally, these SaaS software allow them to edit certain things. In HubSpot's case, it could be going and updating a deal, creating a deal, or updating the contact. And what these low-code/no-code solutions do is that they give you a user interface to add things or create workflows.''
Low-code/no-code or a custom-coded solution? Now that we know the benefits of a low-code solution, why should we opt for a custom solution? As Henry explains, it all depends on several factors. ''I always think of pricing. So with the low-code/no-code solutions, you're giving up that huge amount of development time in the front end. And it's a huge price in the front end that you would have with a custom-coded solution. But you're spreading that out maybe a little over time. So you're paying a monthly fee to Zapier or something like that. [...] And you sometimes run into data limits where those systems will say, 'Hey, you're overloading our servers. We're going to put you on pause until the 24-hour cycle runs around.' So is that something you can stomach as a business?''
Subscribe to RevOps Champions email updates
Stay informed when new podcasts are released
Make your customer-facing operations your competitive advantage.
Grade your revenue operations and technology by answering a series of statements in eight areas of impact. Then learn how to improve each area for free.