No list price. But no mystery either.
Enterprise software sold to Indian financial services is rarely list-priced, and a page that says "contact us" and nothing else wastes your visit. So here is the whole shape: what it is priced on, what moves the number, what is included, and what we never charge for. The figure itself comes from a twenty-minute conversation.
The units
Three things you are charged for
Named user
Anyone who signs in. Named, not concurrent — three people sharing a login is a governance problem, not a saving, and the audit trail stops meaning anything.
Desk
A queue with its own calendar, routing rules and SLA policy. Most organisations start with one and add them as departments come on.
Module
Service desk and QuoteDesk are licensed separately. Reporting and governance are not add-ons; they come with whichever modules you have.
What moves it
Seven things that change the number
Nothing here is a surprise on the second call. If your situation makes one of these large, it is better to know in the first meeting.
| Driver | Direction | Why |
|---|---|---|
| Number of named users | Up | The main line. Banded, so the price per user falls as the count rises. |
| Modules taken | Up | Both modules cost less together than separately, because the shared record is built once. |
| Desks configured | Up | Beyond an included allowance. A desk is a real configuration effort, not a checkbox. |
| Data migration | Up, once | The line that moves most between deployments. Scoped and quoted after we have seen the data, never estimated blind. |
| Integrations | Up, once | Telephony, finance, an identity provider. Quoted per integration against a written interface. |
| Support level | Up | Business hours is included. An extended or named-engineer arrangement is priced separately. |
| Contract term | Down | A longer commitment reduces the annual figure. Monthly is available and costs more. |
Included in the licence
- Upgrades, including major versions. There is no charge to stay current.
- Audit trail retention for the life of the record.
- Reporting and dashboards on the modules you hold.
- Your own data export, self-service, whenever you want it.
- Configuration changes you make yourself — SLA targets, discount bands, routing rules, roles.
- Business-hours support by e-mail and the customer portal.
Never charged extra
- A charge to leave. Your export is yours and it does not cost anything.
- A charge per case, per quote or per e-mail sent.
- A charge to add a user mid-term and then again at renewal for the same user.
- A percentage of anything you sell through QuoteDesk.
A note on the one that catches people. Data migration is quoted after we have looked at your data, not before. An estimate given blind is a number somebody has to defend later, usually by cutting scope.
What a typical deployment looks like
So you can sanity-check the shape
A single operations team
Service desk only, one desk, a dozen or so named users, no migration beyond a contact list. Live in weeks, not quarters. The common starting point.
Operations and sales together
Service desk and QuoteDesk, two or three desks, a price book to load, one integration to finance. The configuration conversation is longer than the software one.
Several businesses, one platform
Desks per entity with scoping so each sees only its own records, shared reporting at the top. Governance does the work here, not licensing.
These are shapes, not price tiers. Two organisations with the same shape can land in different places depending on user count, migration and support level.
Get an actual figure
Tell us roughly how many people and which modules, and Simcomm will come back with a real number rather than a range. One working day.
Why not just publish the price?
Because the honest answer depends on migration and integration, and a published number that excludes them is the number you would quote us back when the invoice looks different. If you would rather have a range before a call, say so in the form and we will send one.
Is there a minimum?
There is a practical one. Below roughly a handful of named users the configuration effort outweighs the licence, and a spreadsheet is genuinely cheaper. We will tell you that rather than sell you something you do not need yet.
Can we start with one module and add the other?
Yes, and it is the usual path. The customer record is shared from the start, so adding QuoteDesk later does not mean re-keying organisations or contacts. The price difference is the module, not a migration.
What happens at renewal if our user count fell?
You renew at the count you have. We do not hold you to a peak. If the count fell because the deployment is not working, we would rather have that conversation than collect a renewal on an unused licence.