Pricing
What you are buying, and how the price is built
Clear pricing arrangements, settled from the start. Amounts vary with complexity and with the resources made available.
Billing
Each component has its own billing mode
Each is billed according to its nature: a subscription for a continuous service, a fixed fee for bounded work, an adjustable commitment for support that varies.
- Required
First component
The platform
Subscription
- A monthly subscription, taken out under a service agreement
- A fixed part, and a variable part tied to the number of legal entities in scope
- Options you can turn on as needed: additional functional modules, subscribed separately, each with its own subscription line
- Worth remembering
- The license is not priced per user.
- Required
Second component
The setup
Fixed fee
- Billed once, calibrated on the scope after the scoping conversation
- Based on the profiles involved: project coordination, deployment and functional configuration, support in migrating the data
- Software engineering in addition, if specific connectors are needed
- Built from an estimated workload per profile: the proposal says what it is built on, and stays verifiable
- Worth remembering
- The configuration is carried out by the EPMind teams themselves.
- Optional
Third component
FP&A support
A set of services offered to help teams and ease their way through periods of transition, billed on time committed
- First-level support — a few days on top of the deployment
- Support in producing the monthly reporting — for as long as the need lasts
- In both cases, monthly billing, on the time actually committed
- Worth remembering
- This component adjusts; it does not lock you in over time.
The differentiator
The license is not priced per user
The subscription is sized on the consolidated scope: the number of legal entities, whatever the number of people who sign in.
That choice follows from the model itself. Per-seat pricing forces a decision, with every new arrival, between cost and adoption — and that decision almost always goes against adoption. Access narrows, the figures go back into spreadsheets among those who have none, and the single set of figures comes apart.
Reporting is only worth something if it is read where the decisions are made: in the entities, in the divisions, among operational teams as much as in the finance function. Opening the platform to one more financial controller, to a division head, or to an operational manager therefore does not change the license amount.
One reservation, and it is in the contract: above a high volume of active users, additional hosting costs may be passed on. This is an infrastructure cost: the threshold and how it is handled are set out in the service agreement.
The levers
What makes the amount vary
Four levers, known upfront.
The number of legal entities consolidated
This is the variable part of the subscription. A scope that widens pushes it up, a scope that narrows brings it down.
The options turned on
Each optional module adds its own subscription line. Not turning it on means not paying for it.
The extent of the setup
The number of sources to connect, how complex the business rules are, the statements to produce, the history to migrate: that is what calibrates the fixed fee.
The intensity of the support, if you take it
The volume and the duration are decided, and revised. It is the only lever that stays adjustable once the platform is live.
SaaS subscription
What the subscription covers, and what it does not
This list will spare you an unpleasant conversation the day a need falls outside the agreed scope.
Included in the subscription
- The modules subscribed to, in the functional scope they have on the deployment date
- Hosting, on the infrastructure of a major cloud provider; availability commitments are set out in the service agreement
- Technical product updates, released on our own initiative
Not included, and billed separately
- Extensions developed on request
- Optional modules
- Changes requested after the project
- The consequences of a change in your systems — a change of ERP, a modified export format — that forces the configuration to be reworked
- Any request outside the agreed scope is quoted first, with a workload estimate, before any commitment
Let’s talk about your scope before we talk numbers
The amount depends on the number of entities, the sources to connect, and the level of support you want: hence a written proposal on your own scope after a first conversation, rather than a rate card that would fit nobody. That conversation starts from your legal structure, your analytical dimensions, and the deadlines you hold — an hour is enough to settle it.