The Six Questions Every ERP Buyer Asks
Before any ERP contract gets signed, the same six questions get Googled by every committee member. We know because we have answered them in 100+ implementations. This page consolidates those six questions in one place, schema-tagged for AI search citations, and links each answer to a deeper resource where we have written more.
The questions, in the order they get asked: How much does ERP implementation cost? Why do ERP implementations fail? How long does it take? How do I choose an implementation partner? Can I capitalize the cost? What methodology should the partner use?
How Much Does It Cost to Implement an ERP System?
For a North American mid-market business (25–100 users) implementing a modern ERP in 2026, expect $25,000–$200,000 for the implementation alone. The variation is real and driven by three factors: scope (how many modules), complexity (how much customization), and partner type (offshore vs onshore, generalist vs vertical specialist).
Implementation is only one of five cost lines. The realistic 3-year breakdown:
- Software licenses: $7–$500/user/month depending on system. Typically 20–25% of total 3-year cost.
- Implementation (one-time): $25K–$200K for SMB to mid-market. Front-loaded in year one.
- Hosting: $300–$3,000/month. SaaS systems (NetSuite, Dynamics 365) bundle this into the license.
- Support / hyper-care: $1,500–$8,000/month. Often the largest line over 3 years.
- Customization & integration: $5K–$200K depending on what your business needs that is not in the box.
For Odoo specifically, a 25-user mid-market 3-year TCO runs $115K–$300K. NetSuite for the same headcount lands $400K–$900K. SAP Business One $250K–$500K. The full breakdown is in the Odoo pricing 2026 guide and the monthly cost breakdown. For a project-specific number, run our implementation cost calculator.
Why Do ERP Implementations Fail?
Industry studies put ERP implementation failure rates between 30% and 70% depending on definition. From auditing dozens of failed projects, the failure causes cluster into seven repeated patterns:
- Picking the wrong system for the company size or industry. NetSuite at 8 users is overkill; Odoo without a partner at 50 users is underdone.
- Time-and-materials scoping with no fixed price. Open-ended budgets get exhausted faster than open-ended scope gets defined.
- Customization-first instead of configuration-first. Every custom module is a future upgrade headache.
- Skipping data cleanup before migration. Garbage chart of accounts in, garbage chart of accounts out.
- Big-bang go-live across all modules at once. Phased waves work; big-bangs almost never do for SMB.
- No internal owner. An ERP project without a dedicated business sponsor stalls inside three months.
- Generalist partner instead of vertical specialist. A "we do all ERPs" agency is rarely as deep as a partner that ships one ERP every week.
We wrote a longer breakdown in why Odoo implementations fail — 7 warning signs, with the actual incident reports we have seen.
How Long Does It Take to Implement an ERP System?
Honest timelines, by company profile:
- Small business, 5–25 users, standard config: 6–12 weeks (Odoo, QuickBooks Enterprise). 2–4 weeks for QB; 6–10 weeks for Odoo.
- Mid-market, 25–100 users, manufacturing or distribution: 12–18 weeks (Odoo). 4–8 months for SAP B1, NetSuite, or Dynamics 365 BC.
- Multi-entity / multi-country: 6–12 months on any system. We deliver these in waves, never big-bang.
- Plant-floor manufacturing with shop-floor MES: 9–18 months on any tier-one system (Epicor, Infor, IFS).
The "8 weeks to go-live" claim you often see in vendor marketing is technically true for narrow scopes — single entity, 5 users, no inventory, no integrations. It misleads buyers who do not realise their actual scope is 4× larger. Our deeper timeline breakdown is in the implementation services page.
How to Choose an ERP Implementation Partner
The partner you pick matters more than the system you pick. A bad partner on a great system delivers a worse outcome than a great partner on a mediocre system. We codified the seven questions every buyer should ask in the partner audit — 7 questions to ask before you sign.
The shortest version: a partner is worth signing with if all of these are true.
- Officially certified by the ERP vendor (e.g. Odoo Ready, Silver, Gold), not just "we work with Odoo".
- The person you talk to in the discovery call is the one who will write your code or configure your system. No "account manager" handoff.
- Fixed-price scope after 30 minutes of discovery. Time-and-materials is a budget vacuum.
- Public client list and reference customers willing to take a phone call. If they cannot name a customer, walk away.
- Live demos using their actual implementation methodology, not generic vendor demos.
- Transparent published rates. "Custom quote" is fine; "starting from $X" with no real number is a red flag.
- Specialism in your vertical. A generalist who does manufacturing once a quarter is dangerous.
Can You Capitalize ERP Implementation Costs?
In most jurisdictions, yes — implementation costs that produce a usable software asset can be capitalized and depreciated over the asset's useful life (typically 3–7 years). Software license fees are usually expensed. Configuration, customization (custom code), and data migration costs are capitalizable. Training and ongoing support are not.
In US GAAP, the relevant guidance is ASC 350-40 (internal-use software). In Canada, IAS 38 (intangible assets) governs. The specifics depend on whether the ERP is hosted (SaaS) or installed — SaaS implementation costs got tighter capitalization rules in 2018 (FASB ASU 2018-15). Always check with your CFO or auditor before assuming a number. We are not your accountants, but we can structure the implementation invoice to make the capitalizable lines obvious — it usually saves your finance team several hours in year-end close.
What ERP Implementation Methodology Should the Partner Use?
Every serious partner has a documented methodology. Generic Agile is not enough — ERP implementation has specific phase requirements that pure Scrum sprints do not handle well (data migration, parallel running, regulatory cutover dates).
The methodology we use across 100+ Octura implementations follows five phases:
- Discovery (1–2 weeks): Process audit, gap analysis, fit-gap document. Output: fixed-price scope.
- Configuration (3–6 weeks): Standard modules configured to your processes. No custom code yet.
- Customization (parallel, 2–8 weeks): Custom modules, integrations, reports. Only where standard configuration cannot meet a real business need.
- Migration & UAT (2–4 weeks): Data migrated by sprints; parallel run for 2 weeks; user acceptance testing on real workflows.
- Go-live & hyper-care (4 weeks): Cutover on a planned date, named on-call engineer for 30 days, then handoff to standard support.
The full methodology is on our implementation services page. The 90-day post-go-live playbook is covered in "first 90 days after go-live".