100% Product matching accuracy after SKU restructuring
Skid Pro is a family-owned manufacturer of skid steer attachments running NetSuite as the system of record for finance, inventory, and 109,000+ contacts across thousands of accounts. They had no CRM, no marketing engine, and no way to give sales reps real-time visibility into orders being created in NetSuite. INSIDEA spent the first phase auditing the NetSuite environment, diagnosing the missing-SKU root cause, and designing a hybrid integration that paired HubSpot’s native NetSuite connector with custom APIs for the objects that needed real-time sync, accurate pricing, and SKU-level matching. We then shipped the work in three phases, and Skid Pro now has a HubSpot and NetSuite ecosystem that finally works the way a manufacturer needs it to.
Numbers That Tell the Story
- Industry
- Manufacturing
- Location
- Alexandria, Minnesota, USA
- Service
- Marketing Hub Enterprise + Sales Hub Pro + NetSuite Integration
- Timeline
- June 2024, Ongoing Multi-Year Partnership
Build a HubSpot-native engine
A Manufacturer Running Without a CRM
Skid Pro had built a successful manufactured product business. NetSuite held everything: 112,722 contacts, 26,112 orders, 76,445 invoices, and 5,068 products across an architecture optimized for ERP workflows, not CRM consumption. But the commercial layer that connects all of that data to a sales rep on a Tuesday morning did not exist.
There was no marketing engine, no pipeline, no lead scoring, no attribution, no SLA on lead response. Sales reps had no way to see live order status during customer calls. Product matching was failing because SKUs were inconsistent. Pricing lived in a separate NetSuite price level table that the native connector could not extract correctly. And with 22 users about to come onto HubSpot, there were no role-based permissions in place. Unit cost and purchase price would have been visible to every sales rep on day one.
Every leadership decision the company was making was based on operational data nobody could see in one place.
Missing SKUs Broke Product Matching
Products in NetSuite did not have a clean unique identifier flowing to HubSpot. API calls failed to match records. Bulk updates broke. Quote generation could not reliably tie back to the right product.
Pricing Lived in the Wrong Place
Retail pricing was held in a separate NetSuite price level table, not the product object. The native connector could not extract it correctly. Sales reps quoting from HubSpot would have been quoting wrong numbers.
Native Sync Was Not Fast Enough for Sales Orders
The native connector runs on a polling schedule. For a sales rep on a call asking 'did the order go through,' a multi-hour batch delay is the difference between a clean conversation and a lost moment of trust.
No Governance, Real Exposure Risk
With 22 users about to come onto HubSpot, there were no role-based permissions in place. Unit cost and purchase price fields would have been visible to every sales rep. One careless export would have leaked margin data.
8,500+ Tax Codes With No Native Equivalent
HubSpot does not natively reconcile NetSuite's full tax matrix. Without a strategy here, every quote and order would have been routed to manual review, breaking the velocity of the sales team.
No Marketing Engine, No Measurement
No email program. No ads integration. No lead scoring. No attribution. No SLA on lead response. Leadership had zero visibility into lead quality or marketing ROI.
A Hybrid HubSpot and NetSuite Architecture, Built in Phases
INSIDEA’s guiding rule on this engagement was simple: no workflow gets built, no integration gets activated, and no pipeline gets configured until the underlying data model is sound. We approached the engagement as an architecture problem first and a configuration problem second.
The diagnosis was that Skid Pro did not have a HubSpot problem. They had an ERP holding the operational truth, a CRM ambition with no foundation, and no architectural bridge between the two. The native connector alone was never going to be enough. Patching live data would never have been enough. We needed three systems doing three jobs, working together.
We then ran the engagement in three phases, not a single big-bang implementation, because the business could not pause its commercial operations while we rebuilt them. Marketing Hub first. Sales Hub second. Custom API layer third.
Clean Reset, Not a Patch
When the missing-SKU root cause was identified, products, orders, and deals were rebuilt from scratch instead of patching live data. The architectural fix turned a sprawling list of integration symptoms into a single root-cause solution.
Native First, Custom Where It Counts
The HubSpot to NetSuite native connector handles standard sync for the five core objects. Custom APIs handle the objects where the native connector was never designed to deliver: real-time order webhooks, price-level extraction, and SKU matching.
Phased Scope With Hard Boundaries
Marketing Hub, then Sales Hub, then the custom API layer. Each phase had clear deliverables before the next began. No parallel workstreams, no scope drift, no quality compromise.
Governance Before Users
Role-based permissions, sensitive-field exclusion, and a staging access role were designed and tested before the first sales rep logged in. Permissions are a backstop, not a primary defense.
Sales Usability as a Design Constraint
High visibility, low control. Reps see exactly what they need to do their job. Financial fields stay in NetSuite. Edit and export controls scoped per role.
Dual-Platform Expertise in One Team
NetSuite price levels, tax matrix, and object structure live in one world. HubSpot custom objects, workflows, and reporting live in another. Holding both inside one team is what made the architecture work.
A Revenue Engine the Sales Team Can Trust
The result is a unified HubSpot and NetSuite ecosystem with clean data, real-time sync where it matters, governed access, and automated workflows the team actually uses. Skid Pro walked into this engagement with no CRM. They walked out with HubSpot as the system of record for the entire commercial operation, integrated with NetSuite without exposing the data NetSuite is supposed to protect.
Real-time via webhooks Order sync latency, replacing hours of batch polling
- Product matching accuracy
- Failing → 100%
- Sales order sync latency
- Hours → Real-time
- Pricing sync
- Broken → Accurate
- Sales pipeline visibility
- 0% → 100%
- Permission framework
- None → Role-based
- Margin data exposure
- High → Eliminated
- Historical notes migrated
- 0 → 100%
Skid Pro is not a one-off engagement. The shape of the work and the failure modes that necessitated it recur across the broader manufacturing industry. ERP systems evolve faster than the CRM infrastructure tracking them. New product lines get added. Pricing tiers get negotiated. Tax matrices expand. Each of these gets bolted onto manual processes because HubSpot was never set up to handle them. If you are running a B2B manufacturing business and the patterns from this case study sound familiar, NetSuite-to-HubSpot data drift, sales reps blind to live order status, margin data exposure risk, manual lead routing, the architectural moves we made for Skid Pro will transfer to your business. The pricing logic, ERP brand, and product catalog will be different. The shape of the work will not.
- B2B manufacturers running NetSuite, SAP, or Microsoft Dynamics
- Industrial equipment manufacturers with deep SKU catalogs
- Component and parts manufacturers with tiered pricing
- Specialty and contract manufacturers with bespoke product data
- Custom and engineered-to-order manufacturers with long pipelines
- Dealer-network manufacturers selling direct and through partners
- Manufacturing leaders making decisions on data nobody trusts
Answers to the questions teams ask before they start
What does a HubSpot-NetSuite integration involve for manufacturers?
It starts with a full audit of the NetSuite environment, the existing HubSpot configuration if any, and every manual process the commercial team is running. From there it includes data model redesign, calculated property architecture, native connector configuration, custom API development for the objects the native connector cannot handle, governance and permissions, and dashboard build. For Skid Pro, it also included a custom Azure-hosted API layer for real-time order sync, pricing extraction, and SKU-based matching. The work is delivered in phases over a multi-year retainer, not as a one-time implementation.
How does INSIDEA bridge the gap between NetSuite and manufacturer workflows?
The native HubSpot connector is excellent for the objects it was designed to handle: contacts, companies, products, orders, and invoices on a polling schedule. But it was not built for real-time order visibility during a customer call, for pulling pricing from a NetSuite price level table, or for matching records by SKU. INSIDEA’s hybrid architecture keeps the native connector active for what it does well, and adds custom APIs only for the specific objects that require real-time sync, complex data extraction, or precision matching.
How long does HubSpot onboarding take for first-time CRM teams?
For Skid Pro, the full sales team was onboarded and operational on HubSpot within six weeks of Phase 2 kickoff. That timeline is achievable when the data model is sound, the permission framework is designed before users log in, and the pipeline configuration matches how the team actually sells. The pace is not the same in every engagement, but six weeks is a realistic target for manufacturers with a single core pipeline and 20 to 40 sales users.
How does INSIDEA protect financial data in NetSuite-HubSpot syncs?
At the architecture level, not at the permission level. HubSpot does not support property-level restrictions on product properties, so we exclude sensitive fields from sync entirely rather than relying on permission controls alone. For Skid Pro, this means Unit Cost and Purchase Price never leave NetSuite. Permissions are a backstop, not the primary defense. This is a far safer design than relying on every permission setting and every export restriction to hold the line.
What if our ERP is SAP, Dynamics, or Epicor instead of NetSuite?
The methodology transfers. The audit, the product catalog integrity work, the hybrid integration architecture, the financial boundary enforcement, the governance design, and the phased delivery all apply regardless of which ERP holds the operational truth. The native connectors and the custom API specifics will differ, but the sequencing and the architectural principles are the same.
How long would a similar engagement take for another manufacturer?
Typical scope is 3 to 9 months for the foundational rebuild across Marketing Hub, Sales Hub, and the custom API layer, with continuous optimisation as a monthly retainer afterward. Skid Pro’s engagement is multi-year because the system keeps evolving as the business grows: payments integration, AI agents, scalable tax engine, and full-funnel attribution all came after the foundation was solid.
More from Manufacturing.
Picked by industry and service line match. Three closest stories.
Ready to be the next case study?
30 minutes with a senior consultant. We map your specifics, share what we'd ship, deliver a written one-pager.
How INSIDEA works
