"I can't make sense of this quotation, but the total feels a bit high."
I have heard that sentence too many times. The owner pushes an A4 sheet across the table. A dozen-plus lines: "Standard module license (10U)", "Implementation services, 45 person-days", "Data conversion, lump sum", "Annual maintenance (from year two)". Every line has a number after it. The bottom line is the total, plus tax.
The problem is that the only line the owner understands is the last one. The dozen lines in the middle — he doesn't know what he's buying in any of them.
So the negotiation turns into a guessing game. The salesperson says "this is already our lowest." The owner says "run the numbers again for me." A figure gets cut, everyone shakes hands. Three months later the change-order quotation arrives, and the owner finds out that what he cut was exactly what he needed.
I'm Johnny Yang, Brightstream Technology, Taiwan. I've led teams doing implementation for seven years, across 252+ projects in 32+ industries. Over these years I've done the same thing for a lot of owners: they get a quotation, ask me to take a look, I break down every line for them, then tell them which lines to question, which they can cut, and which will cause trouble if cut.
This article writes that process down. I won't tell you "what the going rate is" — headcount, modules and complexity vary too much between companies, and any price range I hand you will only anchor you to the wrong number. What I'll teach you is how to read it. After that, you can judge the quotation in your hand yourself.
The conclusion up front: the real risk in an ERP quotation is not the unit price. It's the scope. License fees are the easiest item to compare and the least likely to go wrong. Consultant person-days and custom development are the two items most likely to be misestimated and most likely to grow mid-project. What actually hurts you are the five things the quotation never mentions — acceptance criteria, when the warranty starts, how additional requests are priced, data ownership, and exit terms. Your job isn't to cut the total. It's to get the scope written down clearly.
What an ERP quotation usually looks like: eight items, one by one
Whether your quotation comes from Digiwin, Chenhang or Tiansin (Taiwanese ERP vendors), an SAP reseller or a local system integrator, the structure is about the same. Your quotation probably has six to eight of the items below. I'll go through each: what you're actually buying, how to judge whether it's reasonable, and where it's most often padded.
1. Software license fees: you're buying the right to use it, not the software
On most quotations this is the biggest number. Understand one thing first: what this money buys is the right to use the software within a defined scope. Not ownership of the software, and not the source code.
There are two common pricing methods in Taiwan. One is per user (per account) — the quotation says "10U" or "20U"; U means user. The other is per module — you pay for each module you turn on, with unlimited users or a loose cap. Plenty of vendors mix the two: the base package includes a few accounts, and beyond that you buy them one at a time.
How do you judge whether it's reasonable? The question isn't the unit price. Ask these three:
First, are these concurrent licenses or named licenses? The difference is big. Concurrent means the maximum number of people logged in at the same time. Named means each person has a fixed account. If your company has shifts, part-timers, or an owner who logs in twice a month, concurrent licenses are much cheaper than named ones. If everyone keeps the system open all day, the two come out about the same. The salesperson won't do this math for you. You have to ask.
Second, do warehouse and production-floor staff each count as an account? Many companies get oversold here. If the floor staff only scan barcodes and report work, and the vendor has something like a "light user" or "mobile license", the price is usually different. If you don't ask, he'll quote you standard accounts.
Third, is the price for adding licenses later written into the contract? This one matters a lot. Companies grow. Headcount goes up. If the contract doesn't say "future add-on unit price is the same as this order" or "add-on discount no less than this order", then when you need ten more accounts in three years, the price is whatever he says.
Where is it most often padded? Account count. The owner gets asked "how many people does your company have?" and the quote follows total headcount. But not everyone needs ERP. The people who actually need accounts are the ones who touch document workflows: sales, purchasing, warehouse, production control, accounting, managers. Operators, drivers, cleaners and contractors mostly don't. First list who actually needs to get into the system and create documents, then check that against the number on the quotation. That list usually cuts the account count by a third or more.
2. Module fees: the part most often sold as a bundle
Modules are feature packages. Inventory and sales, production management, costing, finance and accounting, receivables and payables, fixed assets, project management, quality assurance, subcontracting — sold one by one.
What are you buying here? You're buying "which parts of the business this system will manage for you." So there's only one test: will I actually use this module next year?
I've seen too many quotations listing twelve modules where only five were actually running in the first year after go-live. The other seven: paid for, licensed, and the consultant "taught" them, but no process was ever built and nobody maintained the data. They just sat there. Two years later, when the company actually needs them, everyone who attended the training has left, and it pays implementation fees all over again.
How do you judge whether it's reasonable? Cut it by timeline. Sort the modules into three piles:
- Must run in year one: without this module, daily operations break. Buy these.
- Won't run in year one, but probably within two years: for these, ask "can you hold the add-on price and let me turn it on when I need it?" Many vendors will agree. They just won't offer it unless you ask.
- The ones the salesperson says are "free" or "cheaper if you buy them together": this pile is the most dangerous. A free module isn't free, because it brings implementation person-days, training and data setup with it. Ask plainly: if I don't turn this module on now, how much lower is the total? If the answer is "no lower", it really is free. If the answer is "a bit lower, but not much", then you are paying for it.
Where is it most often padded? The line "buying the full suite is better value." Of course the vendor wants you to buy the full suite — the license fees land all at once. But remember: the module fee is only the entry ticket. What's really expensive is the implementation person-days to get that module running. Buying modules you won't use means paying for the waste twice.
If you haven't even decided whether to roll out module by module, read the SME ERP buying guide first. Finish your needs inventory, then come back to the quotation. The order makes everything easier.
3. Implementation consultant person-days: the vaguest, most disputed line on the quotation
I'll give this a full section later, because it's where things most often go wrong on the whole quotation. Here's the conclusion now: person-days are estimated, not calculated. The number reflects the vendor's judgment of how complex your company is, and at signing that judgment usually doesn't have enough information behind it.
If the quotation just says "Implementation services, 45 person-days" with no breakdown of how many days per phase, what gets done and who does it — that line says nothing. Make them break it down.
4. Data conversion: one line on the quotation, the dirtiest job in the whole project
"Data conversion, lump sum" — under those words is the work most likely to blow up the project.
What are you buying here? You're buying the job of taking the data in your old system, old Excel files and old handwritten ledgers, putting it into a format the new system can take, and importing it. Sounds simple. In practice it's three jobs: cleaning, mapping, verifying.
Cleaning means taking data where part numbers mix full-width and half-width characters, specifications are typed into the notes field, and the same customer is spelled three ways, and making it consistent. Mapping means matching old fields to new ones. Verifying means checking, after import, that record counts, amounts and inventory quantities match.
How do you judge whether it's reasonable? Ask these three questions:
First, how many years of data are being moved? Many owners instinctively say "all of it." All of it is a disaster. Load ten years of historical transactions and the system gets slow, queries get messy, and the quality of that data is unusable anyway. The sensible approach: opening balances and master data (customers, suppliers, part numbers, BOMs) must move. Historical transaction detail only moves for the recent period you still need to reconcile. Older data stays in the old system as read-only, or gets exported to files and archived.
Second, whose job is the cleaning? This is the biggest point of dispute. The vendor usually means: you provide clean Excel files, I import them. The owner hears: you move the data. The workload differs by a factor of ten. The quotation must state in black and white who is responsible for data cleaning, who provides the format, and how rework is charged if the client's data doesn't match the format.
Third, how many import runs? There must be trial conversions before go-live, and there won't be just one. The first import always has errors. Fix, reimport, maybe three or four rounds. Does the quotation say "includes N trial conversions"? If not, when the vendor tells you on the third run that "this is extra", you have nothing to say.
Where is it most often padded? This item is padded less often. What's more common is that it's quoted too low. To make the total look good, the salesperson squeezes data conversion into a small number, then adds charges mid-project on the grounds that "your data is more complicated than expected." That's worse than padding, because by then you have no way back.
5. Training: priced by days or by sessions — it matters
What are you buying here? You're buying "your employees can use it."
How do you judge whether it's reasonable? Look at three things:
- Sessions and audience: one big class for the whole company, or separate sessions by department? By department is always more effective, but means more sessions. Does the quotation say how many sessions, how long each, and who attends?
- Operating training or process training? Operating training teaches which button to press. Process training teaches how the new way of working runs. Teach buttons without process and things will be a mess after go-live.
- Is there any after go-live? The first month after go-live is when the most problems hit, and when you most need people. If all the training in the quotation is before go-live, do you pay every time you call for help afterward?
Where is it most often padded? Usually it isn't padded. It's squeezed. Training is the item vendors most readily cut to make the total look better. Cut it, and the money you saved comes back three months after go-live, in the form of "staff can't use it, everyone's back on Excel." I go into more detail in Why ERP implementations fail — a high proportion of those failed projects started with training getting cut.
6. Custom development: the only item that can grow without limit
What are you buying here? Features the standard system can't do but you can't do without.
How do you judge whether it's reasonable? First ask yourself: is this customization needed because my process is genuinely special, or because I don't want to change my process?
It's a harsh question, but you have to ask it. In a great many projects I've seen, half the items on the customization list come down to "this is how we've always done it." Having always done it that way doesn't make it right. Standard system workflows come out of thousands of companies running them. Your process isn't necessarily better.
For every customization, make the vendor answer: if we don't build this, what happens to me? If the answer is "two extra clicks" or "you'll have to pull a report yourself", it's probably not worth building. If the answer is "you can't issue this document" or "you'll have a regulatory problem", then it has to be built.
I wrote a separate post on whether to customize at all — Should your ERP be custom-built? — with a fuller decision framework. Worth reading once before you sign.
Where is it most often padded? Two places. One is vague specifications — the quotation says "five custom reports" but not which five, what fields they have, or where the data comes from. When what gets built isn't what you wanted, every revision is billed. The other is no maintenance responsibility — custom features can break after a system version upgrade. When they break, who fixes them? Free or paid? If that sentence isn't in the contract, every future upgrade is a gamble.
7. Hardware or cloud hosting: watch who pays, and for how many years
If you go on-premises, the quotation will include servers, operating system, database licenses and backup equipment. If you go cloud, it's a monthly or annual fee.
How do you judge whether it's reasonable? On-premises, ask: who decided this server's specs, does it need replacing in three years, and who runs it? Plenty of owners buy a server, put it in a corner of the office, nobody backs it up, nobody updates it, and on the day something breaks they discover the whole system existed as a single copy.
In the cloud, ask: what does the monthly fee include? Hosting only, or backups, monitoring and offsite redundancy too? Is bandwidth capped? Does the fee jump a tier as your data grows?
The long-term cost structures of these two paths are completely different. I took them apart in Cloud vs on-premises ERP. If you only compare year one when reading the quotation, it's easy to make the wrong call.
Where is it most often padded? On-premises database licenses. For non-specialists this item is a complete black box, and the amount isn't small. At minimum, ask: how many cores is this license for? Do I need to buy more when I add users? Is the license registered to my company or to the vendor?
8. Annual maintenance: once signed, it's a long-term expense
What are you buying here? Usually three things: version updates, technical support, and troubleshooting. Some vendors also include a small amount of support hours.
How do you judge whether it's reasonable? Find out exactly what it covers. This is the item ERP clients across Taiwan fight about most, because the client and the vendor mean completely different things by "maintenance".
The client thinks: I call, you handle it. The vendor thinks: if the system breaks, I fix it. But changing processes, new reports, training new hires — those are separate services.
So before signing, go through the following one by one and require them in the contract:
- How many service hours are included per year? How is overage charged?
- Phone / remote / on-site — which are charged? What response time is committed?
- Are version updates free? What about major version upgrades?
- If I want one more report after go-live, is that maintenance or customization?
- Year one is included in the total — how is year two onward priced? Is there a cap on increases?
The last one matters most. Many quotations include maintenance in year one and look like good value, but from year two the fee floats, with no cap clause. Once you sign, you're locked in, because switching systems costs far more than putting up with the increase.
What exactly is a "person-day"? Understand this and you've read half the quotation
Now the unit that confuses owners most: the person-day.
One person-day — whose day?
A person-day literally means "one person working one day." The key is: whose day.
A senior consultant's day and a fresh graduate engineer's day produce wildly different output, yet many quotations just say "Implementation services, 45 person-days" with no distinction by level. What does that mean? It means the vendor kept flexibility — he can send senior people or juniors, and you have no way of knowing in advance.
So the first question you must ask: which roles make up these 45 person-days, and how many days each? A healthy project usually has a project manager, product consultant, technical/development, and a training instructor, and each role's time should be separable. If the vendor won't break it down, be careful.
The second question you must ask: can I name this person in the contract? The consultant who presented so well at the pre-sales meeting may well disappear after signing, replaced by someone you've never met. This is common in the industry. If that person matters to you, require their name in the contract, with any replacement requiring advance notice and a replacement no less experienced than the original.
What a person-day includes, and what it doesn't
This is the core of the dispute. In general, person-days should include:
- Coming to your company for meetings, interviews and current-state review
- System parameter setup and master data configuration
- Running tests with you and fixing configuration
- Teaching training sessions
- On-site support on go-live day and in the early weeks after
But you need to confirm what's not included. Common exclusions:
- Travel and accommodation (you're in central or southern Taiwan, the vendor is in Taipei — who pays?)
- Data cleaning on your side (covered above)
- Rework after requirement changes
- Development hours for custom programs (usually a separate line)
- Support after the warranty period
And one thing many people don't think of: documentation. Process review reports, system configuration documents, training materials, acceptance documents — are these produced or not? If not, when someone new takes over or you want to change vendors, you'll find the system has run in your company for three years without a single document explaining how it's configured.
Why underestimated person-days always end in extra charges
I'll say something that doesn't help my own side: quotations in this business are underestimates by nature.
Not because every vendor wants to cheat you. Because at the moment of quoting, nobody really knows how messy your company's processes are. The salesperson visited twice, sat through an hour of presentation, asked a few departments how they work, then went back and estimated a number. That number reflects the complexity of an "average company", not yours.
And almost every company is more complex than the "average company". You have a pricing rule only the old-timers know, a returns process that was never written down, three customers whose reconciliation works differently from everyone else's. None of this comes up in pre-sales interviews. It surfaces halfway through implementation.
So extra person-days are structural, not a moral issue. Your job isn't to demand a promise of no extra charges (even if he promises, he can't deliver, and will just recover it some other way). It's to agree the rules for extra charges up front:
- Beyond the agreed person-days, does the vendor need written notice first, or can they do the work and bill later?
- Is the extra unit price the same as the original?
- What counts as "client requirement change" (should be billed) versus "vendor underestimate" (should not)? Define that line in advance.
- Is there a ceiling? For example, beyond a certain percentage over the original person-days, both sides sit down and renegotiate.
After this section you'll notice something: the point of reading a quotation was never "how much". It's "under what conditions does this number hold." For how overall implementation cost is built up, I have a fuller breakdown in How ERP implementation cost is calculated. That one is about budget planning, this one is about checking the quotation. Read them together.
What's not on the quotation is what actually kills you
So far we've covered what's on the page. Now what isn't — and these five things matter more than the eight items above combined.
First, acceptance criteria. What counts as "done"? If the contract only says "acceptance after system go-live", what does "go-live" mean? Data imported? Or a full month of operations running stably? Without quantified acceptance criteria, you have no standing to withhold the final payment. Write acceptance conditions as a checklist you can tick: which documents can be issued, which reports can be produced, which numbers must reconcile, how many consecutive days of stable operation.
Second, the date the warranty starts. A single word of difference can mean six months. Counting from the "installation complete date" and from the "acceptance date" are two entirely different things. Installation to real go-live can drag on for three to six months. If the warranty counts from installation, by the time you actually start using the system the warranty is almost over. Always push for the acceptance date.
Third, how additional requests are priced. Covered above, but worth repeating: if this isn't written down, every small request after go-live is a fresh negotiation.
Fourth, data ownership. Your transaction data, customer lists and cost structure live in the system. If you change vendors one day, do you have the right to get all of it back? In what format? A readable database backup, or a few encrypted files you can't open? Does the vendor charge for it? How much? This one matters especially for cloud setups, because the data is not physically in your hands.
Fifth, exit terms. The least romantic clause and the most practical. If the relationship breaks down halfway, how does it end? What happens to payments already made? How is completed work recognized? How is data returned? Do system configuration documents get handed over? Without this clause, you're signing a contract that only goes forward and never back.
I know you'll think: isn't it bad luck to discuss this at signing? It isn't. A vendor willing to settle these five points with you is a vendor who can actually see the project through. The ones who start dodging the moment you raise them and say "we've worked with so many clients and never had a problem" — be more careful with those. This is also the core test I describe in How to choose an ERP vendor: don't look at how polished the presentation is. Look at whether they dare to commit.
How to compare three quotations side by side: convert them to the same baseline first
This is the step most owners get wrong. Three quotations on the table, the eyes go straight to the bottom line, and the cheapest one wins.
Compare that way and you will get burned, because the three scopes aren't the same. Vendor A's total includes first-year maintenance, 20 accounts and 40 person-days. Vendor B's total excludes maintenance, gives 10 accounts and only 25 person-days. B looks 30% cheaper, but what you'll have to add once you actually use it makes it the most expensive of the three.
The right way: build a conversion table that puts all three on the same baseline.
| Comparison item | Bad approach (what most owners do) | Good approach (what you should do) |
|---|---|---|
| Price | Compare the totals at the bottom of each quotation | Work out three-year total cost of ownership: year-one total + year-two and year-three maintenance + expected add-ons |
| Accounts | Take the number of U on the quotation at face value | Normalize to the same account count before comparing, and confirm concurrent or named |
| Modules | Whoever offers more modules seems like better value | Compare only modules that will actually run in year one; exclude everything else |
| Person-days | Compare total person-day figures | Require a breakdown by phase and role; compare the scope of work each person-day covers |
| Customization | Believe "we can do all of this" | Require specs and acceptance method for each customization; anything not written down doesn't exist |
| Maintenance | Be happy that year one is free | Ask about year-two pricing, caps on increases, coverage and service hours |
| Vendor | Compare whose presentation is prettier and whose customer list is bigger | Compare who will write acceptance, warranty, data ownership and exit terms into the contract |
| Decision | Pick the lowest total | Pick the one with the clearest scope; negotiate the price gap |
The chart says one simple thing: spend your questioning effort on the items most likely to get out of control. Software licenses are the most standardized and easiest to compare. You can haggle there for hours and save less than you would by writing the customization specs clearly once.
One more advanced technique: have all three vendors quote against the same requirements list. Write your own list first — "I need these modules, these roles will use it, these documents must be issuable, these reports must exist" — send it to all three and ask them to quote against it. Only then are the three quotations genuinely comparable side by side. Two extra days of your time saves six months of disputes later.
Questions to ask on the spot when you get a quotation
You can print this last section and work through it next time a salesperson sits across from you. If he answers clearly and directly, keep talking. If he starts dodging and saying "we'll deal with that when we get there", you'll know where you stand.
On licenses:
- Is this account count concurrent or named?
- Do floor staff who scan barcodes and report work need a full account each?
- Can the unit price for future add-ons go into the contract?
On modules:
- Of these modules, which do you recommend going live in year one, and which can wait?
- If I don't buy a given module now, how much lower is the total?
- Can the price for deferred modules be locked in?
On person-days:
- What phases do these person-days break into? How many days each, doing what?
- What level of consultant will you send? Can I name the person in the contract?
- Do the person-days include travel? Do they include documentation?
- If person-days overrun, what counts as my requirement change and what counts as your underestimate?
On data and training:
- Who is responsible for data cleaning? Who provides the format?
- How many trial conversions are included? How is overage charged?
- How many training sessions, for whom, and is there any after go-live?
On customization:
- When will I get the specification for each customization?
- If a custom feature breaks after a system upgrade, who fixes it? Is it charged?
On maintenance and exit:
- What are the acceptance criteria? Please write them as a checklist I can tick item by item.
- From what date does the warranty start?
- How is maintenance priced from year two? Is there a cap on increases?
- If I change systems in three years, how do I get my data back? In what format? Is it charged?
- If we end the engagement midway, how is it settled?
Twenty questions, about twenty minutes. Those twenty minutes may be the highest-return twenty minutes of your entire project.
Frequently asked questions
Can I negotiate down the license fees on an ERP quotation?
License fees have relatively clear discount room, because they're a standard product and the vendor has a list price and internal discount authority. But I'd advise against spending all your effort here. What really drives your total spend is implementation person-days, customization scope, and maintenance from year two. Whatever you knock off the license fee may all come back in one go as extra person-days. The smarter move is to use the license discount as a bargaining chip for things you need more — a few more training sessions, a few more trial conversions, a cap on year-two maintenance increases written into the contract. Getting those is worth far more than a few percent off the unit price.
The ERP quotation isn't broken down in detail. Can I ask the vendor to redo it?
Of course, and you should. A quotation that only says "Implementation services, lump sum" and "Custom development, lump sum" commits to nothing. You can say it directly: please break implementation services into phases, person-days and roles, and break customization into specs and hours for each item. That's not being difficult. It's a capability any vendor who can deliver projects should have. If they won't break it down, or say "this is how we always quote", that in itself is an important signal. The vendor willing to lay the details open for you is usually also the one less likely to cause trouble later.
Is the vendor quoting fewer ERP person-days the better deal?
Usually not. Be more careful, not less. A low person-day count has only two explanations: either they genuinely are more efficient and have ready-made industry templates, or they're winning the deal with a low price and plan to add charges midway. You tell them apart by asking how those person-days are allocated. A genuinely efficient vendor can give concrete reasons like "we have a standard process package for your industry, so parameter setup saves this many days." A vendor who just quoted low gives vague answers. Also check whether the contract has rules for extra charges. A low quotation without rules for extra charges is the most expensive quotation.
Do I have to pay the annual maintenance fee on the quotation? Can I not renew?
Technically you usually can not renew, but understand the consequences first. Common ones: no version updates, no vendor support when problems come up, the system can't keep up with regulatory changes (for example tax rules or Taiwan's e-invoice format revisions), and if you want service back later you pay the fees you skipped. So the question isn't "do I pay", it's "can I bear the risk of not paying." If your company can run the system in-house and it's stable, dropping maintenance is an option worth evaluating. But if nobody even manages server backups, the maintenance money you saved will come back tenfold on the day the system fails.
I've already signed and only now found the quotation left a lot out. Is it too late?
It's not too late, but move fast, and deal with it before the project gets too far. Here's how: list each gap you've found — acceptance criteria, warranty start date, rules for extra charges, data return — then proactively set up a meeting with the vendor and add them through a supplementary agreement or meeting minutes. Vendors are usually willing early in a project, because they don't want fights later either. The worst approach is to say nothing and blow up right before go-live. By then you've paid most of the money, your data is in their system, and you have no leverage left. The earlier you catch it, the better your negotiating position.
Finally: if you can read the quotation, nobody leads you around
I opened with "I can't make sense of this quotation, but the total feels a bit high." By now you should see it: whether it's expensive isn't the point. Whether the scope is clear is.
A quotation with a clearly written scope, even if it costs a bit more, tells you what every dollar you pay is buying. A vague quotation, even 30% cheaper, leaves you not knowing what you've stepped into.
If you happen to have a quotation you can't read and you're stuck at "I don't know what to ask", print the twenty questions above and go through them yourself first. If after that a few items still have no answer, or the vendor's answers feel off, that's usually where the problem is. Bring those items to us for a free diagnostic. We won't rush to push our own system. We'll help you understand the quotation first. Because honestly, plenty of owners, once they understand the quotation, conclude "I don't actually need to spend this money at this stage" — and that's a good conclusion too.
Only when you can read it do you have a choice.




