The short answer
Off-the-shelf ERP wins when your operation fits standard workflows: NetSuite's published pricing starts at $999 a month plus $129 to $199 per user. Custom ERP wins when the workflow is the advantage: builds commonly run $150,000 and up, but license math inverts at scale and the system works your way, not the vendor's.
What Do the Two Paths Cost?
Both paths publish enough numbers to compare honestly.
| Off-the-shelf (NetSuite-class) | Custom ERP | |
|---|---|---|
| Entry cost | $999 a month base plus $129 to $199 per user, per published NetSuite pricing guides | Commonly $150,000 to $500,000 to build, per 2026 development cost guides |
| Implementation | $25,000 to $150,000 one-time, per NetSuite implementation guides | Included in the build |
| Year-two cost | $50,000 to $150,000 a year in licenses for mid-market deployments, per published guides | 15% to 25% of build cost annually, per industry guides |
| Fit | Your process adapts to the software | The software encodes your process |
| Speed to live | Months, mostly configuration | Six to eighteen months |
| Key risk | Per-user costs compound; workflow compromises accumulate | Upfront capital and builder quality |
Where Does the License Math Cross Over?
Run a 40-user mid-market operation. NetSuite-class licensing at the published $999 base plus a mid-range $160 per user runs about $7,400 a month, roughly $89,000 a year, plus a published implementation cost of $25,000 to $150,000 in year one. Five-year licensing alone approaches $445,000.
A $250,000 custom build plus the published 20% annual operation rate costs about $250,000 upfront and $50,000 a year, roughly $450,000 over the same five years.
At 40 users the paths cost about the same over five years; the custom path buys exact workflow fit for that money, while the off-the-shelf path buys vendor support, continuous upgrades, and a proven platform. Below 20 users the subscription usually wins outright. Past 75 users the license line becomes the argument for building.
When Is Off-the-Shelf Clearly the Right Choice?
Standard operations should buy, and a builder who says otherwise is selling. Accounting, standard inventory, generic CRM, payroll: mature products do these better than a first-version custom build ever will, with support desks, security teams, and an upgrade train no small build matches. Buy when your workflows are ordinary, when you need to be live in a quarter, when your team is small, or when the capital simply is not there. The expensive mistake in both directions is the same one: forcing the wrong tool to behave like the right one, either by torturing an off-the-shelf product with customizations or by rebuilding commodity features from scratch.
How Do You Decide for Your Operation?
Six questions settle most ERP decisions.
- List the workflows that make you money; if a standard product runs them without contortion, buy
- Count users and run the published per-user math five years out, as above
- Price the customization: heavy configuration on top of licenses often reaches build territory
- Ask who owns the data and how it exits, on either path
- Check integration reach: your POS, processor, and bank feeds must connect either way
- If building: demand staged delivery and source ownership in the contract
Commonly Asked Questions
- What does NetSuite actually cost?
- Published pricing guides put NetSuite at $999 a month for the base platform plus $129 to $199 per user per month, with one-time implementations of $25,000 to $150,000 and typical mid-market annual license totals of $50,000 to $150,000.
- How long does a custom ERP take to build?
- Six to eighteen months for a real operation, per 2026 development guides, staged so core workflows go live early. Anyone promising a full custom ERP in eight weeks is describing a demo, not a system.
- Can we start off-the-shelf and go custom later?
- Yes, and it is often the right sequence: run on a subscription while the operation stabilizes, then build once the workflows that deserve encoding are proven. The migration is real work, so keep your data exportable from day one.
- Who builds custom ERPs at Batch Group?
- Batch Group Software Development, the group's in-house engineering division, builds custom ERPs modeled on how the client actually operates, including vertical systems for salons, restaurants, gyms, events, and charities, and stays on to run them.
Keep reading