Everything people ask
before they sign.

From 18 EUR a month on the Start plan; Grow is 49 EUR, Premium 129 EUR, and Expert is quoted individually. That covers a separate application instance with its own database, the Core module and the base modules. Growing the app through requests is quoted separately - on Grow and Premium with 10% and 20% off every quote.

No. The subscription covers hosting your instance, Core and the base modules; every change you order as a request is quoted separately. A small change is usually 25-100 EUR, a larger one 100-250 EUR.

You get a quote before any work starts - the price in your currency, an estimated time and a one-sentence summary of the scope. Quoting is always free, whatever your plan.

Yes. EU businesses with a valid EU VAT number, verified in VIES, are invoiced under the reverse charge; Polish businesses receive an invoice with domestic VAT. We sell to businesses only.

After it is delivered. We invoice a change only once it is live in your application and you have accepted it - there is no prepayment and no deposit for a request. Hosting is billed separately, on its own billing cycle.

Nothing happens. Turning a quote down costs nothing, carries no consequences and does not affect how your next requests are handled. You can also trim the scope and ask for a new quote.

There is none. You pay the subscription for your plan and nothing else - we charge no fee for starting your instance or for onboarding. If you need data migrated from your current tool, that is an ordinary request: you get a quote before anything starts and you decide.

Nine stages, always the same. You write a request inside your app; we read it and ask if something is missing; you get a quote; you accept it; we start work; you get the change to check; you accept it; the change runs in production; only then do we invoice. You can follow the status on the request card at any time.

On average 48 hours from your accepting the quote. That is an average from our own deployments - we build NEXAENVISION with the same process. Bigger requests take longer, and you get the estimate for yours together with the price, before you accept anything.

You do not pay up front, so a delay costs you no money. The stated time is an estimate, not a binding deadline, and there is no refund guarantee attached to it - we invoice only after delivery and your acceptance. You can see the progress of your request in its status the whole time.

AI writes the code and a developer verifies it and runs the deployment. A person reads your request first and writes down, in their own words, what needs to be built - only that description and the source code reach the AI tools, never the text of your request or any data from your application.

You report a defect and it goes back for a fix, with no new quote. The request automatically returns to work, and once no open defects remain it comes back to you to check. That loop is enforced by the system; it does not depend on anyone remembering it.

It depends on your instance. If it has a separate test environment, you get the address of the test version to check; if not, the change goes straight into your application and you look at it there. Either way we invoice only after you accept it.

Yes. One request can hold several tasks and each is quoted separately - you can accept some, park or reject the rest, and get a new quote for the narrowed scope.

You set the priority - low, normal or high - and you can give a target date. We decide the running order, taking your priority into account. Trial requests are handled after the requests of paying customers.

In one region, agreed with you before your application starts - the European Union by default. The application, its database and its backups sit in that same region, and today no subprocessor processes them outside it.

No. A person reads your request and writes down in their own words what needs to be built - only that description and the source code reach the AI tools, never the text of your request or any data from your application. Customer data is not used to train any model either.

Yes, and you do not have to ask for it. The DPA is public, available before the main contract is concluded and forms part of it - there is no separate document to sign and return. The subprocessor list is part of it, and we announce any intended change at least 30 days in advance.

Only the people who need it to run the service, bound by confidentiality - and every such access is logged. Work on changes does not happen on your production instance.

Daily, and verified by restoring them - a backup nobody has restored is only an assumption. Backups sit in the same region as the application.

Yes, with one click and at any time during the contract. The export covers the complete data set and stays available after the contract ends, for 30 days.

You have 30 days to download it, after which the application and its backups are deleted. You can end the contract at any time, effective at the end of the billing period you have paid for - no notice period and no exit fee.

No, we hold neither today. We say so plainly, because procurement will check anyway and finding silence here costs more than the answer itself. Our technical and organisational measures are described in detail in the trust centre and in the data processing agreement.

No. The application, the Core module, the base modules and the code of the changes you order remain the property of REDOC; for the duration of the contract you get a non-exclusive right to use them. The data and content you put into the application stay yours. If it matters to you that a particular solution does not reach anyone else, tell us before you accept the quote - we settle those cases individually.

No, and that is a deliberate decision. Every NEXAENVISION app shares the same interface: the same lists, the same forms, the same menu, the same colours. That sameness is exactly why a new screen costs hundreds rather than tens of thousands.

Yes. Every application starts on the same core with the same set of base modules, but whatever you do not need at the start can be switched off and brought back later.

Yes, through statement import. The banking module reads ING statements in the STA and MT940-XML formats, detects duplicates and lets you match operations to expenses. It is a file import, not a live connection to the bank.

There is no ready integration with accounting software today. We can build one if your program exposes an API or a file import - that is a request like any other: you get a quote before anything starts. Either way you can export the complete data set from the application with one click.

The plans set no user limit - the licence does not cap the number, and your instance runs on its own, so you do not share resources with other customers. We do not quote a measured number of concurrent users, because we have not run a load test and we will not guess. If you are planning for a specific team size, we will measure it before you commit.

Yes, with one caveat. The application runs in a phone browser and there is nothing to install. It is, however, a dense application that shows a lot of data at once, so day-to-day work from a phone can be awkward. If a particular module is meant to be used mainly on mobile, we build it a separate, simplified view - an ordinary request, quoted like any other.

Not in the usual sense. We are not a multi-tenant platform - every customer gets their own application instance with their own database, started separately. There is no shared table where your data sits next to someone else's.

In three ways: you have the application from day one instead of after a long project, a single change is quoted from around 25 EUR instead of a whole team hours, and the fit is built in small steps instead of being frozen at the start. An agency will build anything, but it quotes a project; we quote a single request.

We say this before anyone pays, because finding it out afterwards costs both sides more. It is not for you if you need a uniquely branded interface; if you are buying as a consumer rather than for a business; if SOC 2 or ISO 27001 certification is a condition of purchase; if you need a contractual availability percentage; or if the app is meant for occasional use and you do not expect to send change requests.

It usually replaces spreadsheets plus two or three tools nobody likes. We start with the area that hurts most and grow from there, one request at a time.

Yes, for 7 days and without a card. We start the trial once you ask for it. The trial application and its backups are deleted within 30 days after the trial ends.

We do not measure it in headcount. NEXAENVISION makes sense where a company has a recurring process that hurts today - and where someone genuinely wants to improve that process step by step. It makes no sense where the app is meant for occasional use and nobody will send change requests: then you are paying for a capability you never use.

You already hold the right to it. The terms grant you - under the contract itself, not a future promise - a perpetual right to use the version of the application running in your instance if we cease providing the service. We then hand you an installation package with the application image, which you run on your own infrastructure. The same applies if the application stays unavailable for 30 consecutive days and we do not tell you why and when it will be back.