Budgeting for an ERP Implementation Project

If you’ve ever gotten wildly different quotes from ERP vendors and had no idea why, this session explains exactly what’s driving that variance. Maxime walks through the three things worth sorting out before you even start talking to suppliers — what type of implementation you actually need (a point solution, an accounting add-on, or a true all-in-one system), a real cross-departmental needs analysis, and a realistic selection timeline (typically 8-14 weeks for smaller companies, closer to 19 for larger ones) — before getting into the two variables that swing your budget the most: ERP tier (Tier 1 names like SAP and Oracle aren’t relevant below roughly $250M in sales, no matter how tempting the brand name) and licensing model (subscription vs. perpetual, which behave more like renting versus financing a car). The actual budgeting rule of thumb is refreshingly concrete: 1-2% of annual revenue for your first-year total, split between software and implementation costs, plus a 10-15% contingency for the things that always come up — retraining, incomplete testing, resistance to change, and the wage cost of your own team not being fully productive during the process. If you’re staring down an ERP purchase and don’t know where to even start pricing it out, this gives you real numbers to work from.

What You’ll Learn In This Webinar

Chapter 1 — ERP Implementation Types and Levels

Before shopping for a system, Maxime distinguishes three levels of implementation: a point solution for one specific pain point (like inventory), addressed by simple software rather than a full ERP, at lower cost but with correspondingly narrower benefit; a solution layered onto an existing accounting system (like QuickBooks), where accounting stays standalone and operations get their own separate system; and a true all-in-one ERP with a single centralized database covering everything. This webinar focuses specifically on budgeting for that third, all-in-one option.

Chapter 2 — Pre-Selection Needs Analysis

Before talking to any supplier, assemble a team representing your major departments to surface needs across five areas: functions/processes that could be automated, redundant data entry that could be reduced or eliminated, improved communication between departments (and with customers), your company’s strategic objectives (growth plans, new markets) since these directly affect software and budget choice, and which departments will actually use the system and how. Maxime’s practical tip: build or update your org chart and share it with suppliers — it clarifies licensing needs on both ends and gives you a real baseline for how many users you need. Frank adds that this also helps normalize wildly different vendor licensing quotes into something closer to an apples-to-apples comparison.

Chapter 3 — ERP Selection Timeframes

Two extremes to avoid: trying to decide and implement within three weeks (a sign you’re treating an ERP purchase like a commodity rather than the change-management project it actually is) or starting your research a full year ahead of a decision (you’ll lose momentum and context by the time you finish). Typical selection timeframes run 8-14 weeks for companies around 20-250 employees, with smaller companies (0-49 employees) averaging closer to 14 weeks and larger ones (150-499 employees) closer to 19 weeks (4-5 months) — a topic covered in more depth in a colleague’s separate April 12 webinar. A live poll asking attendees to guess the average timeframe for a 0-49 employee company landed mostly around 10-14 weeks, close to the real figure.

Chapter 4 — ERP Software Tiers and Categories

ERP systems fall into three tiers: Tier 1 (big brand names like SAP and Oracle — highly customizable and extensive, but really only relevant for multinational companies doing $250M+ in annual sales with dedicated full-time ERP staff); Tier 2 (a hybrid, roughly $25-250M in sales though sometimes reaching down to $10-15M, less flexible than Tier 1 but far more affordable, often “package” solutions like SAP Business One built for a broader market); and Tier 3 (niche, industry-specific systems, often newer technology without the track record of older platforms, generally the best fit for smaller companies). Genius is positioned as sitting between Tier 2 and Tier 3.

“If you only have the money for a Toyota, it’s useless to go shopping for a Lamborghini.” — Maxime, on matching your budget to the right ERP tier

Chapter 5 — Subscription Versus Perpetual Licensing

Subscription (SaaS) pricing has a low initial cost but rises over time as user count grows, and stopping payment means losing access to your data. Perpetual licensing has a high upfront capital cost but becomes cheaper long-term as you scale, and you retain access to your data even without ongoing payments — Frank likens the difference to renting versus financing a car. Subscription and “cloud” are also clarified as distinct concepts: subscription is a pricing model, while cloud is a hosting model, so a subscription-priced system can still be hosted on-premise (though some vendors only offer cloud-hosted subscriptions with no on-premise option at all).

Chapter 6 — Process Reengineering and Customization

Many companies try to minimize “process reengineering” by wanting the software to match their current processes exactly — but those existing processes often aren’t actually optimized, and a mature ERP vendor typically embeds real best practices from years of industry experience. Deciding whether to customize the software to match your current process or adapt your process to the system’s built-in best practices has major budget implications, since customization requires both platform flexibility and a larger implementation budget. A live poll on the main reason SMBs implement an ERP found most people guessing “increase efficiency and productivity” or “replace an outdated system” — but the real top market-wide answer is supporting growth, with efficiency gains being more of a means to that end.

Chapter 7 — ERP Budgeting Rules of Thumb

The core rule of thumb for SMBs (not larger corporations): 1-2% of annual revenue, with 1% representing an out-of-the-box implementation and 2% a more customized one. Example figures: roughly $75,000 for a company with $5M in annual revenue, $150,000 for $10M, and $300,000 for $20M — this is the total first-year cost (software plus implementation), not an ongoing annual figure. A subscription-based recurring fee should instead fit within your regular annual IT budget rather than scaling to 1-2% of revenue every year.

Chapter 8 — Comparing Vendor Licensing Models

Costs split into software and implementation (hardware is rarely managed by ERP vendors). Licensing models vary significantly between suppliers — one structure bundles broad role-based licenses (like “Office,” “Shop,” “Warehouse”) each covering many functions, while another breaks licenses down by specific module or function, meaning a single employee might need multiple separate licenses to cover their full role. Maxime’s tip: always request a full license list and options list from each vendor, and use it alongside your org chart to build a true apples-to-apples budget comparison, since bundled versus modular licensing each carry different long-term cost tradeoffs as your usage grows.

Chapter 9 — Implementation Cost Components

Implementation costs vary significantly by vendor and tier — a specialized Tier 3 system usually needs less customization (lower cost), while a more flexible but less industry-specific Tier 2 system often needs more. Implementation typically splits into three areas: consulting (business analysts scoping the project, defining what’s realistically achievable within budget, and building a sandbox environment and schedule), training (hands-on simulation of real day-to-day scenarios so users can operate independently), and support (data migration assistance, plus ongoing help with any customization).

Chapter 10 — Project Contingency and Risk Mitigation

A recommended contingency of 10-15% on top of the base budget figures covers real risks not included in those base numbers: employee wage costs during implementation (non-productive time), retraining needs (part of why Genius built a lower-cost online retraining platform), incomplete testing, process-reengineering surprises (agreeing to a change during scoping, then reversing course once real users hit actual simulation scenarios), resistance to change, unnecessary customization or integration creep, and employee turnover requiring retraining of new hires.