More articles
All Articles
This article is intended for managers and decision-makers evaluating an ERP system, including its financial module (accounting, cash flow and reporting to the authorities), who want to know before signing whether implementation will be short and controlled, in the cloud or in a hybrid model. Rather than relying on general vendor promises, it presents seven questions whose answers predict the length of the project and its level of risk.
In short: implementation time is largely decided at the selection stage. A system in which most requirements are met through configuration rather than custom code, which already includes the mandatory Israeli interfaces and common third-party connections, and which is implemented and supported by the team that developed it, can go live within months. When the answer to the questions below is “we will develop that for you”, the timeline grows accordingly.
We covered the implementation process at CAV Systems itself, its stages and its typical duration, in the article ERP System for Israeli Companies: Debunking Myths About Complex Implementation. This article deals with the stage before that: how to check these things yourself with every vendor you evaluate.
The perception that every core system implementation is a long and risky project is based on real experience. With traditional systems, the time did not go into the installation itself, but into the gaps between what the system can do and what the business needs: code customizations, building interfaces, adapting to local regulation, and coordination between the software vendor, the integrator and the support provider.
Each of these gaps is visible in advance, if you know to ask about it. The questions below are meant for the demo and vendor-meeting stage, while you can still compare vendors, and before the timeline is already set in a contract.
This is the question that predicts project length more than any other. Choose three processes in which your business departs from the norm, such as special pricing terms for retail chain customers, a complex permissions structure or a dedicated management report, and ask the vendor to show in the demo how each one is implemented. An answer based on parameter settings and existing system tools is measured in days. An answer that starts with “we will specify and develop” adds specification, development and testing stages to every requirement.
It is also worth asking what happens to a customization in the next version update: does it keep working as is, or does it need to be retested with every upgrade?
In CAV ERP, customizations are built using an internal application generator developed by CAV Systems, and every customization automatically inherits the system's security mechanisms, permissions and core logic. This way, adapting the system to a customer's needs does not turn into a separate development project.
In the financial module, much of the implementation time for a system that was not built for the local market goes into interfaces the business is required to have: VAT reporting, withholding tax and Form 856, Masav files, data export to the Israel Tax Authority, and requesting allocation numbers for invoices. Ask the vendor for a list of these interfaces, and ask about each one whether it is part of the system, an external add-on or development that will take place during the project. Every “development” item on this list is another line in the timeline.
In the CAV Systems financial module these interfaces are part of the system, including automatic requests for allocation numbers from the Israel Tax Authority. Full details in the CAV ERP financial module, and for more on the compliance gap between local and global solutions, see the article on the regulatory gap ahead of 2026.
An interface that already exists and runs for other customers goes through configuration and testing. An interface that has to be built goes through specification, development and testing against the other party, and also depends on that party's schedule. Map out in advance the systems your business works with, such as retail chains that order through EDI, a WMS, supplier invoice automation, document scanning or an online store, and check with the vendor whether the connection already exists for each one.
CAV ERP has existing dedicated connections, including StoreNext and Segment for EDI with retail chains, Nipendo for supplier invoice automation, DOKKA for invoice approval workflows, Dun & Bradstreet for credit checks, SPS for document scanning and iSTORES for an online store, alongside two-way WMS interfaces. The full list is on the CAV ERP integrations page.
When development, implementation and support are split between the software vendor, an integrator and a support provider, every requirement and every issue passes between several parties, and each handoff adds time. Ask who will sit in the specification stage, who will carry out the customizations and who will answer the phone after go-live, and check whether it is the same organization.
At CAV Systems, the same team that develops the system also implements and supports it.
A “big bang” approach, in which all modules go live together, is in many cases the longer and riskier route. A phased implementation that starts with the modules critical to day-to-day operations, such as accounting and inventory, and expands gradually, shortens the time to the first go-live and reduces disruption to ongoing operations.
The question for the vendor is whether adding a module later is done on the same platform and in the same database, or whether it requires another integration project.
In CAV ERP, the customer chooses which modules to implement and when, and all modules, from finance and logistics to point of sale and inventory management, were developed on the same proprietary platform.
In the cloud, some of the work that used to be part of the project, such as setting up servers, backups and resilience, moves to the vendor. It is worth confirming that this is actually the case: who is responsible for backups, high availability and disaster recovery, and whether data can be stored on servers in Israel when required.
In a hybrid model the central question is different: are the cloud part and the locally installed part the same system, or two products that need to be connected? In the second case, the connection itself becomes a project. It is also worth asking whether the system is browser-based or requires installation on every workstation, since workstation installations add time for every new user. We covered the considerations in choosing the deployment model itself in the article Cloud, On-Premise or Hybrid.
CAV Systems' systems have run on Amazon AWS since 2012, and backups, resilience, high availability and disaster recovery are managed by CAV Systems. When required, data is stored on servers in Israel. The customer chooses between cloud, on-premise or a hybrid model, and the user interface is browser-based and requires no installation.
Ask the vendor for a typical timeline for a business of similar size and structure to yours, and check what it includes: whether data migration from the existing system, user training and third-party interfaces are included, or added after “go-live”. Two vendors presenting the same number of months may mean two very different things.
A typical CAV ERP implementation takes between two and four months, following a six-stage methodology: mapping and specification, installation and parameter configuration, infrastructure setup and data migration, user training, system activation and ongoing support. For businesses that want to start quickly, there is also a Fast Start option in the cloud that allows going live within a few days.
If one or more of the following signs appear in a vendor's answers, it is safer to assume the project will take longer than presented and to ask for details:
Fast implementation is not a compromise on the depth of the solution, but the result of a system in which most of what the business needs already exists, and a vendor that knows it from the inside. The seven questions above make it possible to check this before signing, and to compare vendors by what they actually show rather than by what they promise.
CAV Systems, which has been developing enterprise core systems since 1979, offers CAV ERP in the cloud, on-premise or in a hybrid model, with one team that accompanies the customer from specification through ongoing support.
Seven questions predict most of the project's length: how a new requirement is met, through configuration or custom code; whether the mandatory Israeli interfaces, such as VAT, Form 856, Masav and allocation numbers, already exist; which third-party connections exist and which will be built; who implements the system and who supports it after go-live; whether it is possible to go live in phases; who manages the infrastructure and what stays on-premise; and what exactly is included in the timeline the vendor presents. Every answer of the “we will develop it for you” kind is another line in the timeline.
Choose three processes in which the business departs from the norm, such as special pricing terms for retail chain customers, a complex permissions structure or a dedicated management report, and ask the vendor to show in the demo how each one is implemented. If the customization is done through parameter settings or existing system tools, it is measured in days. If the answer is specification and development, every such requirement adds development and testing stages. It is also worth asking what happens to a customization in version updates.
Yes, when all modules sit on the same platform and the same database. In that case you can go live first with the modules critical to day-to-day operations, such as accounting and inventory, and later add modules such as procurement, distribution or point of sale without a separate integration project. In CAV ERP, the customer chooses which modules to implement and when, and all of them were developed on the same proprietary platform.
The central question is whether the cloud part and the locally installed part are the same system or two separate products. When they are two products, the connection between them becomes a project in its own right. It is also worth confirming who manages backups, availability and disaster recovery for the cloud part, and whether the system is browser-based or requires installation on every workstation.
A comparable timeline details all stages of the project, not just the go-live date: mapping and specification, installation and parameter configuration, infrastructure setup and data migration, user training, activation and support. It is important to check whether data migration, training and third-party interfaces are included in the timeline or added after it. At CAV Systems, a typical CAV ERP implementation takes between two and four months, and in the cloud there is also a Fast Start option for going live within a few days.
.webp)
