Two ERP agencies quote for the same software. One costs considerably less. But are they actually selling the same project?  Picture a finance director in Pune with both proposals open side by side. They run to different lengths, use different headings and carry numbers that do not line up. The cheaper one is attractive, especially after a quarter of tight cash. It is also the one with fewer lines in it. Whether a gap like that is a saving or a postponed invoice is the real question for anyone choosing a SAP Business One agency. This article is written for CFOs and ERP buyers who want to find that out before the contract is signed. It explains where budgets slip, what a proposal should show, and the seven questions that expose the difference between a price and a project. 

Why do ERP budgets increase? 

Most ERP budgets grow because the first quotation prices only what the agency has decided to include: licences and a core implementation. Data migration, integrations, custom development, training, go-live support, hosting, yearly support and the time your own staff spend on the project are often left out or only vaguely described. They surface later as change requests and extra invoices. The cheapest quotation is therefore not always the cheapest project, so compare what each proposal covers before comparing totals. 

Why Is the Initial ERP Quotation Rarely the Complete Project Cost? 

A quotation is a document written by the seller to win the work. It is not a forecast of everything you will spend, and nobody is being dishonest when it falls short of that. The agency prices what it is confident about, and anything uncertain tends to be either excluded or described in a sentence that sounds generous and commits to nothing.  Look at what a first proposal usually contains: the software licences, an implementation fee, perhaps some training. Now look at what a live ERP needs to run: your old data moved across and checked, connections to the web shop and the bank, reports your auditors accept, a hosting arrangement, someone to call when a posting fails, and a few months of hand-holding after go-live. Those items exist whether or not they appear on page two.  There is also a cost that never reaches any proposal, which is your own people. The finance lead who spends two days a week in workshops is not doing month-end at full speed. Warehouse staff who learn a new screen while orders keep arriving make mistakes for a while. These are real costs, and they belong in the budget even though no agency will invoice them.  This is where ERP hidden costs come from. They are rarely hidden on purpose. They are hidden because the proposal was never built to show them, and because most buyers compare the bottom line instead of the scope above it.

Which Expenses Should Appear in a SAP Business One Proposal? 

A useful proposal is boring to read. Every line names a thing, says who does it and says how it is priced. If you remember one test, make it this: for each cost line, could someone who was not in the sales meetings tell what is and is not included?  Ingold Solutions publishes its implementation packages under the names Basic, Standard, Plus and Professional, with go-live helpdesk hours and training hours that rise with each tier. That is the right instinct, because it puts a number of hours on support instead of a promise. Whichever agency you speak to, ask for the same level of detail.

What is included in SAP Business One implementation costs? 

A complete SAP Business One implementation cost covers the software licences, implementation and configuration work, data migration, integrations, any custom development, user training, go-live support, and the running costs that follow: annual maintenance, hosting if the system is in the cloud, and support after go-live. A proposal that lists only licences and an implementation fee has not yet told you the full price. 

Cost line	What the proposal should state	A warning sign
Licences	Licence type, number of each, one-time or subscription, price for extra users later	A single “licences” total with no user breakdown
Implementation	Modules, entities, warehouses and workshops in scope; fixed price or time and materials	“As required” or “subject to analysis”
Data migration	Which records move, who cleans them, number of trial loads	Not mentioned at all
Integrations	Each connection named, with who maintains it afterwards	A line that says “integration” once
Custom development	Each item listed and priced, with its yearly cost to keep working	A lump sum for “customisation”
Training	Hours, who is trained, online or on site	Training described but not priced
Go-live support	Duration and number of hours	Support with no end date or hour cap
Maintenance and support	Percentage, the base it applies to, what it covers	No percentage stated
Hosting	Billing basis, backups, data location, exit terms	Hosting “to be confirmed”

How Do Licensing, Hosting and Implementation Costs Differ? 

Buyers often treat these three as one number. They behave differently, and mixing them up is a common reason a three-year budget misses. 

SAP B1 licensing 

Licensing is what you pay to use the software. SAP B1 licensing comes in different user types, and Ingold Solutions lists Starter Package, Limited and Professional licences, available as a perpetual purchase paid once or as a monthly subscription. The choice matters for cash flow and for the long run. A perpetual licence costs more at the start and then carries yearly maintenance. A subscription spreads the cost out but never stops. Neither is automatically better. What counts is which one you can afford now and how many users you will have in year three. The yearly maintenance fee is where proposals differ most in how clearly they speak. Ingold Solutions states its maintenance as 19% of the contract value per year. Whatever an agency charges, get the percentage in writing together with the amount it is calculated on. A 19% rate on licences alone and the same rate on licences plus services are very different sums. 

Hosting 

Hosting is a running cost and not a project cost. If your system lives in the cloud, it is billed as a subscription, and on Ingold Solutions’ published description it depends on the number of users, the features you use and the amount of customisation. So hosting rises when your business does, and a flat figure in a proposal should make you ask what it assumes. 

Implementation 

Implementation is the one-time work of configuring the system, bringing in your data, connecting it to other tools and training your people. It is the line most buyers watch, and for that reason the one most often shaved to win the deal. If one proposal’s implementation fee is much lower than another, check whether the two include the same number of workshops, trial migrations and training hours before assuming one agency is simply more efficient.  Anyone searching for SAP Business One implementation cost India will find a wide spread of figures, and the spread is mostly explained by scope: how many users, how many modules, how much data and how much customisation. A number without those four details tells you very little. That is why this article avoids quoting a single price and gives you a method for building one instead.

What Happens When Data Migration Is Underestimated? 

Data migration is the most commonly underestimated item in an ERP project, partly because it looks simple. Move the customers, the items, the open orders. How hard can it be?  Then the old system turns out to hold three versions of the same customer, item codes that follow no rule, prices stored in a spreadsheet one person understands, and open balances that do not agree with the ledger. Cleaning that up is slow, it needs people from your side who know the history, and it cannot be hurried by adding developers. Each trial load throws up a fresh list of problems, and each list takes days.  When the quotation allowed for one trial load and the project needs three, the extra work lands as a change request. When nobody on your side was freed up to check the data, the go-live date slides, and the longer the project runs, the more every other line grows. A realistic proposal states how many trial migrations are included, who is responsible for correcting data, and what happens if the data turns out to be messier than expected. 

How Can Custom Development Increase Future Costs? 

Custom development is rarely a mistake. Sometimes your process is the reason customers choose you, and the standard system should bend to it. The trouble is the price tag attached to the word “custom,” which is usually only the build cost. The cost of owning it comes later.  Every customised screen, report or workflow has to be tested when the software is upgraded. It has to be understood by whoever supports it next, and documented well enough that it survives a change of staff. A custom item built for ₹1.5 lakh today may cost a further amount each year to keep working, and that second number is almost never in the proposal.  It helps to sort each requested change into one of three groups. Does the standard system already do this in a slightly different way? Could a configuration setting or a small adjustment solve it? Or is it a real gap that only development will close? Many buyers discover that a good share of their “must haves” belong in the first or second group. For a longer look at this trap, our earlier piece on over-customising SAP Business One goes through it in detail. Whichever group an item lands in, ask the agency to price its yearly upkeep. 

Seven Questions Every Buyer Should Ask a SAP Business One Agency 

These are the questions we would put to any agency in your place, including ours. They are written so a finance director can ask them without technical vocabulary, and each one is aimed at a place where budgets tend to move. 

1. What exactly is in scope, and what is not? 

Ask for the exclusions in writing. A list of what is left out is often more informative than the list of what is in. If the agency cannot name them, the scope is still loose. 

2. Is the implementation price fixed, or time and materials? 

Fixed prices move risk to the agency, but only for the scope that is written down. Time and materials can be perfectly honest, as long as you get an estimate range and a rule for when you are told the estimate is being exceeded. 

3. How many data migration trials are included, and who cleans the data? 

One trial load is rarely enough. Find out how many are priced in and what an extra one costs. Also agree who owns the clean-up, because “the customer provides clean data” can quietly become your largest line. 

4. Which integrations are included, and who maintains them after go-live? 

Name every connection: web shop, bank, logistics partner, tax or e-invoicing tools. For each, ask who fixes it when the other system changes its interface, and whether that is covered by support or billed separately. 

5. Which custom items are in the quote, and what does each cost to keep? 

Ask for each item priced separately, with an annual figure for keeping it compatible. A lump sum for “customisation” cannot be compared with anything. 

6. What happens after go-live, in hours and in money? 

Find out how many support hours are included and for how long, what the response times are, and what counts as a chargeable request. The first two months are when most surprises appear, so this is not a footnote. 

7. What will the next three years cost, not just the first? 

Ask the agency to set out maintenance, hosting, support and upgrade costs for each year, including the likely yearly increase. Any SAP Business One agency confident in its proposal will be happy to show this. If the answer is vague, treat that as information about the proposal.

How to Compare Two ERP Quotations Fairly 

Once you have the answers, put both proposals into one frame. The method is short. List every cost line from the table above. Write down what each proposal says for that line. Where a proposal is silent, do not leave the cell blank. Enter your own estimate and label it as such. Then add contingency, and extend the recurring costs across three years.  That is the idea behind ERP total cost of ownership: the one-time price, plus everything you pay to keep the system running over a defined period, plus the money you were not told about. We have turned it into a worksheet you can download and edit, with every assumption in its own cell. Here is what it does with the two quotations from the opening. The figures are invented to show the arithmetic. They are not Ingold Solutions prices and not market benchmarks. They are in ₹ lakh, for 15 users, with 5% yearly growth on recurring costs, 19% maintenance on licences and a 10% contingency on one-time costs. 

₹ lakh, three-year view	Quotation A (cheaper)	Quotation B
Headline one-time price in the proposal	14.30	23.70
One-time items the proposal leaves out (estimated)	10.40	3.50
Contingency (10% of one-time costs)	2.47	2.72
Recurring costs, Years 1 to 3	14.56	14.56
Three-year total cost of ownership	41.73	44.48

At headline, Quotation A looks about 40% cheaper (14.30 against 23.70). Once the missing items are priced, the gap over three years falls to roughly 6% (41.73 against 44.48). Quotation A left out data migration, integrations and most of the hosting and support. Quotation B included them. The two agencies were not selling the same project, which is exactly what the opening question was getting at.  This does not mean the cheaper agency is the wrong choice. It may still be the better partner, and 6% is a real saving. It means you can now decide on the figures that matter, and you can go back to Agency A with specific questions instead of a general feeling. 

What should an ERP quotation include? 

An ERP quotation should itemise licences (type and number), implementation scope, data migration, integrations, custom development, training, go-live support, annual maintenance with its percentage and base, hosting, and support after go-live. It should also state what is excluded, whether prices are fixed or estimated, how change requests are handled and how long the quote stays valid. If a line is missing, ask for it before you sign. 

How Should You Choose a SAP Business One Agency After This? 

Price is one input. The others are harder to put in a table: whether the agency listens before it quotes, whether the people who sold the project are the people who will deliver it, and whether it has credentials you can verify. Ingold Solutions is an SAP Silver Partner and a Microsoft Solutions Partner, and holds ISO 9001 and ISO 27001 certification, as shown on the Ingold Solutions India website. Check the same for any agency you shortlist.  Ask to speak to a customer of similar size, in a similar industry. Ask what went over budget on their project and why. A reference who can answer that honestly is worth more than a polished case study.