Note: This composite case study is based on patterns Boomi sees across multiple customers. It reflects real challenges and decisions, but does not represent any single company. In Part 1, we covered how a mid-market SaaS company moving upmarket hit a wall with ERP integrations, losing deals, losing customers, and finally deciding that building more in-house wasn’t the answer. They chose to embed an integration platform as a service (iPaaS) instead. Here’s how it unfolded.
The Implementation
The team made a deliberate choice to start narrow. Rather than trying to build all three ERP connectors simultaneously, they picked NetSuite first. It covered the largest share of their current pipeline, and several existing customers had already asked about it. A focused first implementation would also let them work out the process kinks before taking on SAP and Microsoft Dynamics. The initial scoping conversation surfaced the first real decision point: which data objects actually needed to sync at launch? The temptation was to build everything, customers, contacts, inventory items, production orders, purchase orders, invoices. The pre-built connector made all of it technically possible, which paradoxically made the scoping harder. Just because they could sync everything didn’t mean they should. They forced themselves to map the decision back to what their product actually did. For a production planning tool, the non-negotiables at launch were production orders, bills of materials, and inventory levels. Everything else could come in a later release. Cutting scope felt uncomfortable at first, but it kept the first implementation manageable and meant they could get something real in front of customers faster. Field mapping turned out to be more complex than expected, not because of anything wrong with the platform, but because of how differently their customers had configured NetSuite. Two customers running the same version of NetSuite had organized their item records in almost incompatible ways. One used custom segments extensively; the other had a relatively vanilla setup. Building a field mapping experience flexible enough to handle both without requiring engineering involvement for each customer took longer than the initial estimate and went through three design iterations before it felt right. The unexpected issue came about six weeks in, during testing with a pilot customer. NetSuite’s SuiteQL query behavior for large bill of materials hierarchies was returning results inconsistently under certain pagination conditions. It wasn’t a platform issue; it was a quirk in how NetSuite handled a specific query pattern at scale. But it still needed to be solved before they could go live with any customer running complex manufactured goods. Having a vendor with accumulated experience across thousands of implementations meant the workaround was documented and available quickly. What could have been weeks of debugging was resolved in days. It was a reminder that ERP APIs have edges that only show up in production conditions, and that prior exposure to those edges has real value. By week nine, the NetSuite integration was in production with two pilot customers. By week 11, it was generally available.
The After
The most immediate signal came from the sales team, and it came quickly. Within the first quarter after the NetSuite integration went live, the number of late-stage deals where integration was flagged as a blocker dropped by more than half. Enterprise prospects who previously would have triggered a lengthy scoping conversation about custom integration work were instead being walked through a live demo of the self-serve activation flow. For a buying committee that included IT stakeholders, seeing a production-ready integration experience, with in-app monitoring, structured error handling, and clear documentation, landed differently than a promise that the engineering team could build something. It looked like a company that had solved the problem, not one that was still working on it. Two of the enterprise deals that had stalled over integration requirements in the previous two quarters came back into active conversation. One closed within six weeks of the NetSuite launch. On the retention side, the change was harder to measure directly but visible in customer behavior. Support tickets related to integration failures dropped substantially as structured error handling gave the support team enough context to resolve most issues without escalating to engineering. More tellingly, the pattern of customers building their own workarounds largely stopped. When the integration worked reliably and customers could monitor its status themselves, the motivation to go around it disappeared. The engineering impact was quieter but significant. The two engineers who had been spending the largest share of their time on integration maintenance were largely redeployed to core product work within a quarter. The integration backlog, which had been an unofficial but persistent drag on every sprint planning conversation, stopped being a topic. By month six, the team had launched a Microsoft Dynamics connector using the same implementation process. It took half the time of the NetSuite build because the process was established, the design patterns were in place, and the lessons from field mapping complexity and the API edge case were already baked in. SAP was scoped and on the roadmap for the following quarter. The VP of Product framed it simply in a board update: they had gone from integration being a reason to lose deals to integration being a reason to win them. For a company pushing into enterprise, that was the difference that mattered.
What This Means for Your Roadmap
The pattern this company followed — start narrow, scope ruthlessly, expect field mapping complexity, and plan for ERP API surprises — shows up consistently across SaaS companies tackling embedded ERP integrations for the first time. The technology is solvable. The harder part is the sequencing: knowing which connector to build first, which data objects to sync at launch, and how to design a self-serve experience that enterprise IT teams will actually trust. If your pipeline is hitting the same wall, the decisions this company made are a reasonable starting point for your own evaluation.
Boomi Embedded provides the pre-built ERP connectors, authentication flows, and ongoing maintenance that let SaaS companies offer native integration experiences without building from scratch. Learn more about Boomi Embedded or explore the Build or Buy guide to pressure-test your options.