Kemlat Header
Kemlat
  • Home
  • About
  • Services
    Business & TransformationA clear view of the problem and a plan you can deliver.8 Project & DeliveryGovernance that connects plans to results.3 ERP & CRMConnected processes and data in systems that fit your work.2 Digital ProductsWebsites, apps and platforms built around your needs.8 AI & AutomationPractical solutions for tasks that should take less time.8 Quality EngineeringMore confidence in every release.3 Cloud & SecurityA dependable foundation for your digital work.5 Managed ServicesStability, support and improvement after launch.3 Brand & CreativeAn identity and experience that tell your story clearly.4 Digital GrowthBetter visibility and decisions based on performance.5 Games & ImmersiveInteractive experiences for learning and for brands.4 Training & EnablementSkills your team can put to work.3
    All services56

    The KEMLAT Method

    KEMLAT
    Build your projectPick the services you need and get an approximate cost range in a minute.
  • Work
  • The Method
  • Insights
  • Contact
ARGet in touch
  • Home
  • About
  • Business & Transformation Project & Delivery ERP & CRM Digital Products AI & Automation Quality Engineering Cloud & Security Managed Services Brand & Creative Digital Growth Games & Immersive Training & EnablementAll services Build your project
  • Work
  • The Method
  • Insights
  • Contact
Get in touch
العربية [email protected] +962 79 122 3241
Check the Main Menu location in Apppearance->Menus->Display Location.
Budgeting for an ERP Project: The Costs People Forget - Kemlat Insights
Kemlat2026-10-21T16:51:56+03:00
All insightsاقرأ بالعربية
Enterprise Systems

Budgeting for an ERP Project: The Costs People Forget

ERP budgets often overrun because of costs that were real from the start but never made it into the budget. These are the lines to add before anyone signs.

14 November 20265 min read
Share
Budgeting for an ERP Project: The Costs People Forget - Kemlat Insights

The enterprise resource planning (ERP) proposal on the general manager’s desk shows licences and an implementation fee. It looks manageable. Eighteen months later the project has cost far more, and the overrun came from a long list of costs that were real from the start but never appeared in the budget.

Why ERP budgets are often incomplete

Vendors and partners quote what they will deliver. That is reasonable, but their quote covers only part of what the project needs. Your own staff time, data cleaning, hardware, integrations, extra training and the months of running two systems side by side all sit outside it. Because nobody owns those costs in the proposal, they are often missed until they arrive.

A realistic ERP project budget starts from the full picture: what you pay the partner, what you pay others, and what you pay in your own people’s time.

The costs that tend to be forgotten

Cost areaWhat it includesWhy it is missed
Internal staff timeKey users in workshops, testing, data checks and training, often for monthsIt never appears on an invoice, but someone has to cover their daily work
Backfill or overtimeTemporary staff or overtime while key users work on the projectPeople are assumed to absorb it, until they cannot
Data cleaning and migrationFixing customer, product and supplier records; reconciling opening balancesThe partner’s quote may only cover loading data you have already cleaned
IntegrationsConnecting point-of-sale (POS) systems, e-commerce, banks, payroll, e-invoicing or other systemsListed as “to be confirmed” in the proposal
Reports and documentsCustom invoice layouts, Arabic documents, management reportsAssumed to be standard, then found to need work
Infrastructure and devicesServers or hosting, scanners, label printers, tablets, network upgradesTreated as an IT (information technology) matter outside the project
Change requestsChanges discovered during the projectEvery project has them; few budgets allow for them
Parallel runningKeeping the old system and its licences alive during transitionOld contracts and renewal dates are not checked
Post-go-live supportAn intensive support period straight after launch, extra consultant days, ongoing support contractThe budget ends at go-live; the problems do not
Annual running costsSubscriptions or maintenance, hosting, support, upgradesProject budget and operating budget are discussed separately

Training deserves a separate mention. The partner’s quote usually covers training key users, who are then expected to train everyone else. That second round of training, often across shifts and branches, takes time from your key users and sometimes needs extra materials in Arabic. It is rarely in anyone’s plan.

A scenario: a distributor’s ERP budget

Consider a consumer goods distributor in Amman with around eighty staff, moving from an older accounting system and several spreadsheets to a modern ERP. The proposal covers licences, configuration and standard training.

During the project, several things happen that nobody priced. The product list turns out to contain hundreds of duplicate codes and discontinued lines, and cleaning it takes two people several weeks. The van sales team needs handheld devices and an integration with the ERP. The finance manager spends most of three months in workshops and testing, so the company hires a temporary accountant. The old system’s licence has to be renewed for another year because go-live moves.

None of this is unusual, and none of it would surprise anyone who has run an ERP project before. It was simply not in the budget, so each item became a difficult conversation with the owner, and each conversation cost the project a little more credibility.

How to build a realistic ERP budget

  1. Ask partners for a complete scope, in writing. Ask them to list what is excluded as clearly as what is included, especially data migration, integrations, reports and post-go-live support.
  2. Estimate internal time by role. For each key user, estimate the days needed for workshops, testing, data and training. Multiply by a realistic daily cost, and decide how their normal work will be covered.
  3. Assess your data early. A short data quality review before signing tells you whether cleaning is a few days or a few months.
  4. List every integration. Include anything the ERP must exchange data with, and get an estimate for each, including local requirements such as e-invoicing.
  5. Check your existing contracts. Know when current licences and support agreements renew, and how much notice they need.
  6. Add a contingency line. Hold a reserve for change requests and surprises, controlled by the sponsor and released only with a recorded decision.
  7. Budget at least the first year of running costs. Make sure the operating budget includes subscriptions, support and hosting from go-live onwards.
Rule of thumb: if your budget has no line for your own staff time and no contingency, what you have is a supplier’s quotation, not an ERP budget.

Cost control during the project

A complete budget is only useful if it is tracked. Review actual spend against each line monthly, including internal time where you can estimate it. Route every change request through a decision that names its cost. Keep the contingency visible, and report how much has been used and why.

When the sponsor sees early that data cleaning is consuming more than planned, there is still time to add people or adjust scope before go-live is at risk. When the same information arrives in the final month, the only options left are expensive ones.

Funding the whole project, not just the software

When ERP projects go over budget, a common cause is a budget that described only the software and the partner. Building a complete picture of costs, internal effort and data work is part of the requirements and planning stage of our Enterprise Systems service. When the full cost is understood at the start, owners can make a clear decision, and the project team can spend its energy on delivery instead of explaining overruns.

Found this useful?Share it with your team or someone who needs it.
  • WhatsApp
  • LinkedIn
  • X
  • Facebook
  • Telegram
  • Email
Related service

Enterprise Systems

We design and build systems, and migrate data into them, based on real operational needs, not generic templates.

Also related: Operations Transformation

Explore our services

Related insights

Cleaning Historical Data Before a System Migration - Kemlat Insights
Enterprise Systems

Cleaning Historical Data Before a System Migration

Moving fifteen years of records into a new system just in case is a frequent reason migrations run late. Decide what to bring, clean it properly…

16 Nov 2026 · 5 min read
Mobile Apps for Field Teams: When They Are Worth Building - Kemlat Insights
Enterprise Systems

Mobile Apps for Field Teams: When They Are Worth Building

Paper job sheets sent by WhatsApp make the case for an app feel obvious. Sometimes a custom app is right. Often a simpler option fits the…

15 Nov 2026 · 5 min read
Reporting Architecture: One Data Model, Many Reports - Kemlat Insights
Enterprise Systems

Reporting Architecture: One Data Model, Many Reports

When the sales report and the finance report disagree, meetings turn into arguments about numbers. A shared data model means every report uses the same definitions,…

13 Nov 2026 · 5 min read

Kemlat Footer
Kemlat
Kemlat

We help organisations transform complex operations into clearer ways of working, practical solutions, and measurable outcomes.

Quick Links

  • Home
  • About Kemlat
  • Our Services
  • Selected Work
  • The Method
  • Contact Us

Services

  • Business & Transformation
  • ERP & CRM
  • Digital Products
  • AI & Automation
  • Cloud & Security
  • Digital Growth
  • All services
  • Build your project

Get in Touch

Email [email protected]
Location Almadina Almunawwara St., Amman, Jordan
WhatsApp & Phone +962 79 122 3241

© 2026 Kemlat. All rights reserved.

Privacy Policy Terms of Use
Kemlat Method

Request a Service

Tell us what you need and we will get back to you within one business day.

By sending this form you agree to our privacy policy.

Request received

Thank you. Our team will review your request and contact you within one business day.