Some are choosing a system and need an implementation. Others have had enova365 for years and need someone to run it. The scope differs at the start, the care is the same.
The company runs on spreadsheets, a few disconnected programs, or a system nobody develops any more. We start with a process analysis, not with a licence purchase.
The system works, but updates keep getting pushed to next quarter, and you hear about a bug from accounting on the day a filing is due.
Accounting, HR and Payroll, Sales, CRM, cross-system integrators and other modules.
From the pre-implementation analysis, through configuration and data migration, to user training and post-implementation care.
We talk to the people who run the processes and describe the current state. The module scope follows from the analysis, not from a price list.
We set up modules, permissions and documents around the company's processes. Changes are tested on a test environment.
We move records, balances and documents from the existing systems and then verify that they match.
We train teams on their own data and documents – separately for accounting, HR and sales.
We stay for the first month close and the first payroll run, then move to standing care.
We don't step away from an implementation after the first group of users is trained. We are there for the first month close, the first payroll run and the first filing. Only then do we move to the care mode.
Four areas we take over once the contract is signed. Tap a row – a list of points opens.
The server, the backup and the network are part of the same project. We supply them together with the system, so at the moment of a failure there's no dispute about who is responsible for the database.
A dedicated server in the OVH data centre or a machine on your own premises, with a Windows Server licence and configuration set up for the enova365 database.
A NAS device for local backups, an off-site copy and a database restore test – instead of assuming that the backup simply runs.
A router, switches and Wi-Fi access points in a single standard, plus UPS backup power for the server and network devices.
An ERP is chosen once every dozen or so years. The partner who runs it matters just as long.
For over two decades we have provided full-scope IT services to business clients. Technologies, regulations and system versions have changed in that time – the company stayed.
We don't hand clients between consultants. The people who ran the implementation still pick up the phone years later – with no need to explain the configuration history from scratch.
For system-level bugs, we work directly with enova365's manufacturer. A ticket doesn't stop at the first line of support.
We check the system version, module configuration, the state of backups and integrations. We come back with a list of risks and a scope of work. Prefer to write: enova@widget.pl.