1C Implementation Turnkey, in Stages

Business review and choice of configuration

The first one or two weeks go into understanding your company.

We talk to management, sales, warehouse and accounting. We look at where data is kept now, which documents are printed and which reports are needed. The output is a short document: which processes move into 1C, in what order and what will need customization.

We choose the configuration for your needs: 1C:Accounting for Kazakhstan, 1C:Small Business Management (UNF), 1C:Trade Management, 1C:Integrated Automation or ERP. Licenses are bought from an official 1C partner; we will tell you which ones and how many you need, and take over the setup after purchase.

Choosing the wrong configuration is costly. Software that is too simple quickly hits its limits, and in a year you have to migrate again. Software that is too complex requires a long implementation and expensive support. So we compare options against the company's needs: how many users, warehouses and legal entities, whether production accounting is needed, which integrations with external systems are required.

If the company already has 1C but uses it only partly, the review shows what is in the way. Sometimes it is enough to customize the current database rather than start over.

Setup and customization

Standard features first, code second.

We set up the accounting policy, price types, warehouses, user permissions and print forms. Many tasks are solved by configuration settings. Where the standard configuration falls short, we customize it with an extension, so the database stays on vendor support and updates normally.

Typical customizations during implementation: custom print forms, posting checks, management reports, bank statement import, integration with the website and Kaspi. More on the 1C customization page.

We try to keep the number of customizations at launch to a minimum. Many requests that seem essential before launch turn out to be unnecessary after a few weeks in 1C, because the standard mechanism is more convenient. So critical customizations are done before launch, and the rest go into a list we review after a month of use.

Staff training

We train on the company's own data, not on a demo database.

Each role is shown only what it needs: orders and prices for sales managers, receiving and shipping for storekeepers, period closing for accountants. Short illustrated instructions stay with you. For the first weeks after launch we answer questions in a work chat.

We pay special attention to employees who used another system or spreadsheets before. They need to understand not only which buttons to press but why: why a document must be posted, not just saved, and why dates cannot be changed retroactively. This reduces errors in the first months.

What makes us different

We do not sell licenses; we make sure 1C works for you.

We are a development team, not a software shop. Our job is not to sell a box but to bring your accounting to a working state. That is why we say honestly where settings are enough and where customization is unavoidable, and give the price of each stage before it starts.

We also handle what is usually split between different contractors: integrations with websites, marketplaces and banks, and mobile apps that work with 1C directly.

We work across Kazakhstan and do most tasks remotely; the business review and training can be held on site or online if needed.

Common 1C implementation mistakes

Why implementations drag on and what we do differently.

Starting with setup instead of processes. The software was set up the way a consultant suggested, not the way the company works. A month later it turns out the warehouse ships differently and sales managers give discounts the system does not have. We start with a business review and record the real processes.

Migrating everything at once. Along with balances, duplicates, errors and outdated catalogs moved into the new database. We clean up before migration, not after.

Launching everything in one day. If sales, warehouse, purchasing and accounting switch at the same time, any error stops the whole company. So we launch areas one at a time, with a period of parallel work.

Training once. A single one-day training for all staff achieves almost nothing. We train by role on real data and stay in touch for the first weeks after launch.

Customizing by editing the standard configuration. The wish to tailor everything at once takes the database off vendor support and stops updates. We build customizations as extensions.

No owner on the company side. Implementation goes faster when the company has a person who makes process decisions. We ask for such a person to be appointed at the start.

Integrations not planned. After launch it turns out 1C must be connected to the website, Kaspi or a bank, and this is neither in the timeline nor in the budget. We identify such tasks during the review and plan them into the stages right away.