Questions and answers

In 1C projects, the specification is the most important and labor-intensive stage. It defines automation goals and fixes business processes, budget, timeline and scope. Analysts, methodologists, solution architects and project managers all work on it.

It is not just a document. It is the basis for managing risk, quality and results. Implementing 1C without a specification is the main reason projects fail or run late. That is why the specification is a professional service that is paid for separately.

Without a specification, the project turns into a series of rework, conflicts and unmet expectations. There is no clear understanding of goals, functions, deadlines or responsibilities. The team does things the way it understood them, not the way the business needs. Mistakes are found too late, during development or after launch. The budget grows, deadlines slip, and nobody is accountable.

Readiness for 1C depends not on company size but on how mature management decisions are. If business processes are not formalized, key people are overloaded, and the Product Owner and Project Manager roles are not defined, the project is at risk. In that case it is better to start with a brief and a readiness assessment, not with implementation. We will help you build the structure and prepare for full automation.

That does not block the project. Many of our clients use cloud servers, rent virtual machines from hosting providers or run 1C on a regular PC that meets the technical requirements. We will choose the best option based on load, budget and security needs.

Yes, if you plan to grow, improve reporting, automate processes and meet security requirements. 1C:Enterprise 7.7 is no longer supported or updated and is not compatible with modern platforms. The move means a new implementation from scratch, but it brings a big gain in flexibility, speed and analytics. We will help make it as smooth as possible.

Not always required, but recommended in most projects. Licenses let us set up a test environment, model real processes and refine requirements while the specification is being written. This saves time, reduces errors and speeds up implementation. We recommend buying licenses early, especially for complex projects or when IT infrastructure needs to be aligned.

Yes, it is one of the best approaches. Phasing splits the project into logical blocks, reduces the load on employees and lets you test key processes before scaling. We help build a phased roadmap so that every stage is manageable, transparent and ends with a measurable result.

Because we plan not only technical work but also your team's real availability, the risk of delays from third parties and the need for proper testing. Tight deadlines often lead to gaps, conflicts and rework. We don't promise to be the fastest. We implement so that it is done right the first time and lasts.

Our price reflects the real effort, the level of expertise and the project risks. We don't cut costs at the expense of quality, and we don't inflate them: OneSoft's average margin is 10–12%. If someone offers a much lower price, ask about the qualifications of the people involved and whether the offer includes a specification, a pilot period and warranty support.

The main reasons are no approved specification, delays on the client side with approvals and data, low involvement of key employees, and issues with external contractors. We warn about these risks in advance and build them into the plan, but the client's discipline and readiness are the deciding factor.

Payments are tied to the key project stages: specification, implementation, data migration, training and pilot operation. You pay in parts after each stage is accepted and signed. This keeps the project transparent, controlled and mutually accountable.

The main risks are longer timelines, budget overruns and extra resources. Without a specification and a clear client role, rework and repeated approvals can drag on. Beyond direct costs, there are losses from a system that doesn't work, downtime or accounting errors. We reduce these risks through formal processes, phasing and transparent project management.

We include integrations in the specification, agree API specifications and work plans with third-party vendors, and control the whole process on our side, from agreement to integration testing and data migration.

We take on coordination, requirements and making 1C technically ready for the integration. The external vendor is responsible for its own timelines, quality and API stability. This risk sits with the client, since only the client has a contract with that vendor. To avoid delays, we recommend a separate contract with the vendor with clear deadlines and responsibilities.

Data can be hosted on your own local server or on a rented virtual machine from a reliable hosting provider. The choice depends on security, availability, backup needs and budget. We help choose the best option based on your infrastructure and project requirements.

This is common, and we plan for it. We take on most technical tasks: installation, setup and support. Your IT team only needs to provide access to hardware and networks and agree on procedures. If needed, we can bring in an external administrator or offer full turnkey support.

Appoint a Product Owner: a person who knows the business processes well and makes decisions about functionality. Make sure key employees take part in interviews, testing and acceptance, keep approval deadlines, provide data and respond to project questions on time. The higher the client's involvement and discipline, the more precise the result.

The Product Owner is the client's representative who knows the business processes in depth and makes quick decisions. Formally a CEO can take this role, but in practice it rarely works: they are too busy and not close enough to the details. It is better to appoint an experienced operations employee or a business analyst who is available to the team every day.

It is recommended. A client-side project manager handles internal coordination: collects information, organizes meetings, tracks deadlines and communication between departments. Without one, all communication falls on the external team, which increases the risk of misunderstandings and delays. In smaller companies, an administrative employee with good organizational skills can take this role.

At the start, we agree together on the participants, communication channels (email, messengers, Zoom and others) and regular meetings. All tasks are tracked in a shared project management system, and project documentation is maintained throughout. Our senior consultant leads communication on our side, and your project manager on yours.

The project goes step by step: from the specification to implementation, testing, training and ongoing support. We follow one methodology regardless of project size. See "Project stages" on the Services page for details.

Each stage ends with an acceptance certificate or a pilot operation report. It is signed by authorized representatives of both sides, usually the client's project manager and our senior consultant. Signing confirms the stage is complete and the next phase can begin.

A stage is complete when all tasks in the specification are done, functionality is tested, data is loaded, users are trained and the client has found no critical issues. A critical issue is one that blocks a business process or makes key functionality unusable. Other minor issues are fixed during operation under warranty support.

Any change after the specification is approved makes the project harder to manage. If a change affects a part where work has not started yet, we will try to accommodate it. Changes to functionality that is already built, or that require new blocks, are recorded separately and scheduled after the main scope is complete.

Errors found after the acceptance certificate is signed are fixed under warranty support. This is normal: many issues only appear in everyday use. That is why pilot operation and warranty support are part of every project.

Warranty support covers fixing errors found during real use of the system and technical support within the delivered functionality: bug fixes, user consulting, monitoring of data exchanges and configuration updates when needed. The warranty period and scope are set in the contract.

After the warranty period, we offer post-warranty support under contract: 1C platform and configuration updates, support for exchanges with external systems, user consulting, data audits and changes within an agreed number of hours. The format is chosen individually, from fixed support packages to on-demand work.

Warranty support means fixing errors found after launch without changing how the system works. It is limited in time and covers only the delivered functionality. Post-warranty support is provided under contract and includes system development, new changes, new modules, extended analytics and SLA-based technical support. It is a long-term partnership, not just support.

The cost depends on the number of 1C products, the complexity of settings, the number of external integrations and the support level. Even with active use, it is far lower than the cost of keeping a full-time 1C specialist. We offer flexible models, from hourly rates to fixed support packages.

It depends on priority and the contract terms. The Elite support package includes a fast response on any day, including weekends and holidays.

Critical incidents (work stopped, accounting failure): response within 2 hours, resolution within 1 day. Standard requests (errors, consulting): response within 1 business day, resolution within 3 business days unless agreed otherwise. Planned changes follow an agreed schedule.

If your current partner solves issues reliably, meets deadlines and you are happy with the service, there is no need to change. But if there are delays, no clear accountability and work is done by guesswork, that is a signal. We offer an audit of your current support and can take on a system of any complexity with clear rules, SLA and quality control. The decision is yours, and a comparison is always useful.

The rights to the 1C platform and standard products belong to 1C Company. Customizations we build during the project remain our technical property, but you get the full right to use them within your organization with no limits on time, scope or number of users. All rights and terms of use are set out in the contract.

No, we don't transfer ready solutions between projects without the parties' consent. Every project is adapted to specific processes and tasks. When needs are similar, we use our experience: not by copying someone else's code, but by applying proven approaches that speed up implementation and reduce risk.

An NDA is signed before work begins. Every project member on our side signs an internal confidentiality commitment. Technical access to your data is limited, logged and granted only to those who need it. We don't share information with third parties and strictly follow the access limits in the contract.

Under the memorandum of 1C franchisees in Armenia, agreed with 1C Company management, any use of unlicensed software is strictly prohibited. All franchise companies must move their clients to licensed versions.

Starting in 2026, official checks of companies for unlicensed software will be carried out in Armenia. This creates direct legal and reputational risks for businesses.

If you use an unlicensed solution, contact us. As the official 1C distributor in Armenia, together with your integrator we will ensure a correct and safe move to licensed software, keeping your data, system stability and access to updates.

ArmSoft is a set of standard solutions with a rigid architecture. 1C is a platform you can configure to fit your business, not the other way around. 1C can be customized without the vendor, unlike the closed ArmSoft, where even API access is limited and available only for a fee.

1C supports EAEU requirements: export VAT, reporting by country and currency settlements. It lets you keep records in different jurisdictions and build analytics for management. This is critical for companies working across borders or growing fast.

If the system only covers accounting and doesn't hold back growth, there is no need to switch. But when new needs appear, such as integrations, management reporting, EAEU operations, or analytics on warehouses, purchasing and sales, ArmSoft becomes a bottleneck. 1C gives you control: it can be customized, scaled and combined into a single architecture.

Yes, this is possible and used in practice: accounting stays in ArmSoft, and other processes run in 1C. But the more systems you have, the higher the risk of mismatches, duplicated data and loss of control. 1C can cover all accounting and management in one architecture, so as a company grows it makes sense to move to a single system.

This is one of the most common arguments, but in practice it is not true. 1C fully supports Armenian tax law, including electronic reporting, VAT specifics, profit reports and formats for working with tax authorities.

The key difference is that 1C can adapt to changes without waiting for the vendor. Since the official 1C distributor in Armenia is part of the OneSoft group, all required updates are released on time and with local specifics in mind.