Clear before you start.
The price depends on which parts of Supportifier you need, your volumes and the work on rollout and connections. We go through the scope before you take a position.
Three parts to keep separate.
A useful pricing basis shows what you pay for at the start and what recurs.
- Platform and operation
- Which channels and features are included, how volume and AI usage are counted and how any excess volume is handled.
- Rollout and knowledge work
- Which sources we work with, how the review is done and what is included in the launch.
- Integrations and ongoing responsibility
- Which connections are to be built or used and what is included in maintenance and improvements.
Bring what you already know.
An approximate ticket volume, the number of agents, your most important channels and the names of the systems support uses are enough as a starting point for a first conversation. You do not need a finished requirements specification.
Start smaller when that is right.
A limited flow can be a better first step than a large system replacement. The knowledge analysis is a separate way to examine the material before you decide on the next step. Scope, delivery and price for the analysis are agreed in advance.
Start from your everyday work.
Tell us which question takes time today. We go through what a first step could look like.
A clear first step beats a big promise.
See how the knowledge work, the review and the first channel fit together.
How the rollout works