Custom ERP development vs customizing an existing platform
Customizing standard platforms like NetSuite or SAP for specialized workflows requires massive, expensive consulting fees and painful modifications, yet building from scratch is intimidating for a small team. This leaves companies stuck between massive customization bills and the heavy lift of custom software development.
What the numbers show
Counted from the threads quoted below. How we count
- The most recent one is from October 2026.
- This comes up 95.8× more often in r/Netsuite than across the site as a whole.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Evaluating and buying standard horizontal or vertical ERP software and heavily customizing itDid this help you?
- 2Adapting internal business operations to fit the standard workflows of off-the-shelf systemsDid this help you?
- 3Using best-of-breed systems for financials and building custom, isolated MRP or tooling that integrates with themDid this help you?
- 4building custom portals in-houseDid this help you?
- 5hiring consultants to build custom solutionsDid this help you?
- 6navigating the native enterprise software interface directlyDid this help you?
- 7Making the CRM free for everybodyDid this help you?
- 8Targeting SMBs instead of large companiesDid this help you?
- 9Using existing big players like HubSpot, Salesforce, Pipedrive, Zoho, or MondayDid this help you?
- 10Buying a dedicated visitor management systemDid this help you?
- 11Building a custom solution using Power Apps, SharePoint, and Power AutomateDid this help you?
- 12Developing an in-house web-server hosted applicationDid this help you?
- 13Building a custom solution from scratch using AI tools like Claude to write the codeDid this help you?
- 14Using established, paid plugins like WooCommerce BookingsDid this help you?
- 15Building prototypes using Claude Artifacts, Claude Code, GitHub, Vercel, and Supabase.Did this help you?
- 16Evaluating built-in CRM configuration features (e.g., Salesforce Einstein Activity Capture or Inbox) and clean up existing data first.Did this help you?
- 17Keeping the existing CRM as the source of truth while testing limited read-only custom integrations on a small subset of users.Did this help you?
- 18Use a real CRM (like HubSpot or Salesforce) as the source-of-truth database for core records and permissions, and only build custom AI features on top.Did this help you?
- 19Leverage existing CRM features and official integrations (e.g., native Outlook add-ins, built-in call recorders, workflows) to cover baseline requirements before coding custom tools.Did this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“We’re intimidated by having to customize an existing ERP platform so we’re considering building an entirely custom ERP platform from scratch”source ↗
“Ideally we don't build it ourselves because my team is tiny but also don't want to pay our netsuite consultant 200k for this.”source ↗
“I work for a specialty food distributor with a lot of specific, non-standard operational workflows. We’ve evaluated standard platforms like NetSuite, Dynamics, and SAP, but fitting our day-to-day processes into them looks like it'll require massive, expensive customization regardless. Because of that, we're currently in talks with a dev shop about custom erp software development built specifically around our process.”source ↗
“my attempt last year ate closer to 300 before I even had something that didn't crash when you clicked the wrong button”source ↗
“spent months obsessing over real-time dashboards only to realize most users just want a place to dump names and phone numbers without fighting the interface”source ↗
“But now I’m wondering if I’m overcomplicating things by trying to build an entire CRM from scratch.”source ↗
“Would it make more sense to keep Salesforce, move to HubSpot, or use another established CRM as the underlying database and build the AI functionality separately?”source ↗
“I’m comfortable learning the technical fundamentals and using Claude Code to help build the application, but I’m trying to avoid creating a massive infrastructure project that becomes difficult to maintain.”source ↗
“I’m wondering if I’m overcomplicating things by trying to build an entire CRM from scratch.”source ↗
“Would it make more sense to keep Salesforce, move to HubSpot, or use another established CRM as the underlying database and build the AI functionality separately?”source ↗
“I’m comfortable learning the technical fundamentals and using Claude Code to help build the application, but I’m trying to avoid creating a massive infrastructure project that becomes difficult to maintain.”source ↗
“Trying to work out whether this is a good use of the Microsoft 365 stack or if I'd be reinventing the wheel.”source ↗
Where this came up
People with this problem also raised
- 16Should I register a business before making any money?
- 2Should I keep building my solo practice or take a safe job?
- 43How to find a cheaper CRM when HubSpot gets too expensive
- 57How do I know if I can DIY a repair or need a pro?
- 3Is enterprise software support actually worth the cost for small teams?
- 33Should customer support live inside our CRM?