What you want to know before you start

There are two ways to work with us. With a subscription you pay a fixed monthly amount and can submit unlimited requests; the plans are on the Subscriptions page and we discuss the monthly fee in a free introductory call. If you want a one-off project with a clear end point, we prepare a project quote. That price depends on the scope: the number of screens, integrations and users, and how many existing systems are involved. After a free introductory call you receive a defined scope, the expected lead time and the cost of maintenance afterwards.

A single integration or automation is often live within a few weeks. A custom application with several user groups takes longer. We split larger projects into phases, so there is quickly a first working version you can use and evaluate. The expected lead time per phase is stated in the quote.

Software we build specifically for you belongs to you. We put that in the agreement and make sure the source code and documentation are available to you, for example in a repository you have access to yourself. That way you are not dependent on Kantex if you later want to continue with another party.

Security is our starting point: encrypted connections, role-based access rights, logging of important actions and regular updates. When personal data is involved, we agree in advance which data is processed, where and by whom, and we sign a data processing agreement. We never process more data than the purpose requires.

Yes, that is usually where we start. Often an existing ERP, CRM or accounting package works fine and what is missing is the connection between them. We look at the integration options your systems offer, such as an API or file exchange, and build around them. We only recommend replacing a system when it is genuinely in the way.

After go-live we stay involved through a maintenance agreement. It covers updates, monitoring of integrations, resolving incidents and the response times we commit to. Existing customers can reach us at support@kantex.nl. If you want to extend the software later, we plan that as a separate follow-up with its own quote.

Send a message through the contact form or email sales@kantex.nl. We then schedule a free introductory call to discuss your process, systems and goals. After that you receive a proposal with the approach, planning and costs. We only start once you agree. The introductory call comes with no obligations.

It can be, with the right agreements. We decide in advance which data an AI application may use, choose providers that do not train on your data and process within the EU wherever possible. Users only see information they already have rights to, and every outcome is logged. For tasks with real impact, an employee approves the result.

Yes. A single integration, the automation of one process or a small internal tool can save a lot of time and is a good way to get to know each other. We tackle larger projects in phases, so every step delivers value on its own. The size mainly determines the approach, not whether we take it on.

Mostly knowledge of your process. We ask for one fixed contact person who can make decisions, access to the systems or test environments involved, and a few conversations with the people who work with them every day. During development we regularly show interim versions and ask for feedback. The sooner it comes, the sooner we can move on.

Yes. We agree in advance which data an AI application may use, where it is processed and who has access. Where possible, we choose processing within the EU and models that do not train on your data.

We build in checkpoints. For tasks with real impact, an employee approves the proposal, and every outcome is logged so mistakes are visible and can be corrected.

For each application we choose the model that fits the task, the cost and the privacy requirements. That can be a large language model through a business API or a smaller model running within your own environment.

Processes that happen often, follow fixed rules and currently involve moving data between systems by hand. Think of order processing, customer registration, approvals and reporting.

Usually not. Automation works on top of your existing systems through their integration options. Only if a system allows no integration at all do we discuss alternatives.

A first automated process is often live within a few weeks. We start with the process that takes the most time, so the gain is visible straight away.

With almost any system that offers an API, webhooks, database access or a structured export. Whether a specific integration is possible is something we assess during the discovery phase, based on the system’s documentation.

Errors are logged and reported. Messages that could not be processed are kept and resubmitted once the problem is solved, so no data is lost.

Kantex can do that under a management agreement, including monitoring and changes when a vendor modifies its API. You can also take over management yourself; in that case we provide documentation.

When your way of working sets you apart from competitors, when off-the-shelf packages require a lot of manual workarounds, or when you are trying to combine several systems into one workflow. For general tasks such as accounting, an off-the-shelf package is often the better choice.

We make clear agreements in advance about ownership of and access to the source code, so you do not become dependent on a single supplier.

We start with the smallest version that already delivers value and then expand step by step. That way you only invest in features that prove necessary in practice.

Databases, your software’s APIs, supplier feeds, spreadsheets and exports. For each source we define how often it is refreshed and who owns the data.

Not always. For many organisations a well-designed database with a few pipelines is enough. We recommend the lightest setup that answers your question reliably.

We match that to the decisions you make with them: from a few minutes for operational overviews to daily for management reports.