Their price has your headcount in it. Ours does not.
Per-seat pricing is the one line in an ERP quote that is not a number — it is a multiplication, and the thing it multiplies by is how many people you hire. Put in the rate you were quoted and watch what your own growth costs you.
The same sum, as you grow5 rungs
| Headcount | Seats alone, 3 years | DBS One, 3 years | Times over |
|---|---|---|---|
| 10 people | — | ₱6.5M | — |
| 25 people | — | ₱6.5M | — |
| 50 people | — | ₱6.5M | — |
| 100 people | — | ₱6.5M | — |
| 200 people | — | ₱6.5M | — |
Put in the rate you were actually quoted. We do not publish what any other vendor charges, because we do not know it and neither does anyone who has not asked them in writing. The column on the right is the figure this site already publishes on the cost page — implementation and two years of maintenance, for a company of around a hundred and fifty staff.
Four things a per-seat quote does that the quote does not mention.
None of these appear on the first proposal. All four appear by year three.
You pay for the hire before the hire pays you
A new branch manager costs a seat on day one and earns you nothing until month four. Per-seat pricing bills you for growth in advance, every time, and it never nets off against the growth that did not work.
The seat does not end when the year does
A license renews. So the seat you bought in year one is bought again in year two, and in year three, and in the year after you have forgotten why you bought it. Nobody audits a seat count downwards.
So access gets rationed
This is the real cost and it never appears on an invoice. When a login has a price, supervisors share one, branches send figures to head office by message, and the people closest to the problem are the ones locked out of seeing it.
And the number only goes one way
Every ERP quote is priced at the headcount you have today. You are not buying the company you are; you are buying the company you are about to become — at a rate agreed before you became it.
Nothing.
Users are unlimited on every plan, and that is not a promotion. A system people are rationed out of stops being where the answer lives — the supervisor shares a login, the branch sends its figures by message, and the person closest to the problem is the one who cannot see it. We would rather everybody was in it.
Four questions, and the answers are the whole story.
Ask us the same four. Our answers are on this page.
- 01
“What is the per-user price, in writing, for three years?”
Not the first-year discount. The renewal rate, and what governs how much it may rise.
- 02
“Is it named users or concurrent?”
Named means every person who might ever log in. Concurrent sounds cheaper and is how you end up with staff waiting for somebody else to log out.
- 03
“What does a read-only user cost?”
The warehouse supervisor who only ever looks. If that is a full seat, you will not give them one, and the system stops being the place the answer lives.
- 04
“What happens at renewal if we have shrunk?”
Seats go up easily. Ask, in writing, what happens when you need fewer.
Bring the quote you already have.
We will put your real rate and your real headcount into this, in front of you, and you can keep the arithmetic whichever way you decide.