A colleague working in administration gets tired of Excel spreadsheets and builds a CRM using an AI-powered development tool. The team starts using it, adding customer data, quotes and follow-up tasks. Then the employee-turned-developer resigns. Who can restart the system? Who pays for the hosting? And who is actually entitled to use, modify or further develop the software?
The 10 Biggest Risks of Vibe Coding topic highlights one of the most serious problems: hidden key-person dependency. Software handover when an employee leaves is simultaneously a business continuity, information security and legal issue. The solution is not to blame the proactive colleague, but to establish corporate control.
The checklist below takes you through the tasks, from clarifying rights and permissions to technical handover and maintenance responsibilities. If the colleague has already announced their departure, section 3 outlines the first steps for securing access and data; clarify the legal issues in parallel.
1. When a Helpful Initiative Becomes Shadow IT
Vibe coding involves users creating or modifying software with AI using natural-language instructions. This enables rapid prototyping, but a working interface does not prove that the underlying system is secure and maintainable.
The term shadow IT refers to technologies used outside IT and organizational control. A self-built CRM can fall into this category even if management knows about it, but there is no designated system owner, approved data processing, access policy or operational agreement.
The hosting and database are linked to a personal email address.
The customer list is uploaded to an unvetted cloud service.
API keys are embedded directly in the source code.
All employees use the same administrator account.
The only backup is stored on the developer's laptop.
The departure does not create these shortcomings; it exposes them. If the company has only checked whether the system “works,” it may soon discover that customer management actually depended on a single person's personal access credentials.
2. Who Owns the CRM If Development Was Not in the Job Description?
You cannot automatically conclude that the software belongs to the employee, nor that the employer necessarily holds all the rights. Under Hungarian law, it is necessary to examine whether creating the work was an employment duty, what agreements were made and the circumstances in which development took place.
The Job Description Matters, but It Is Not the Only Evidence
Under the general rule of Hungarian copyright law, unless otherwise agreed, the employer acquires the economic rights upon delivery of the work if creating it was part of the employee's employment duties. Special rules also apply to software. Alongside the job description, the employment contract, management instructions, task assignments and related correspondence may therefore be relevant.
If an administrator developed the software entirely on their own initiative, the situation may differ from one in which a manager explicitly assigned them to build a CRM. Using a company laptop or working hours does not, in itself, settle the rights. In the event of a dispute, the specific facts should be assessed with a lawyer experienced in IT and copyright law.
Can They Take It with Them or Ask for Payment?
If the necessary rights have not passed to the employer, a licensing or rights assignment agreement may be required, potentially involving payment. However, this does not mean that the departing employee is free to delete the company system, take customer data or use trade secrets without authorization.
Rights relating to the source code, control over service accounts, any legal protection of the database and the processing of personal data must be addressed separately. Whether AI-generated elements qualify for copyright protection also depends on the human creative contribution; licenses for incorporated third-party components may impose further conditions. Using AI therefore does not automatically make the CRM legally compliant.
3. The First Step: Securing Corporate Control and Data
When an employee announces their departure, first identify dependencies that threaten operations. The handover should not start with the employee sending all their passwords in a message. Named company accounts and documented permissions are essential.
Create system inventories: hosting, domains, databases, code repositories, email, AI tools, integrations and subscriptions.
Designate a company owner: grant them appropriate administrative permissions, and ensure that multi-factor authentication and account recovery work.
Address dependencies on personal accounts: where necessary, transfer ownership or migrate in accordance with the service provider's rules. Do not request access to the colleague's entire personal account.
Create a verified backup: back up the database, attachments, configuration and code to an access-controlled company location.
Have an offboarding plan: including revoking personal access rights, terminating sessions and rotating affected secrets.
Access revocation should reflect the risks and the circumstances of the departure. In high-risk situations, immediate restrictions may be warranted, while ensuring that the necessary company oversight remains in place.
4. Technical handover: source code alone is not enough
A ZIP file is not a complete software handover. The goal is to enable another specialist to independently deploy, verify, fix and restore the system. The handover package should include at least the following:
Company code repository: with version history, access rights and clear identification of the production version.
Deployment guide: dependencies, environment variables, release and rollback steps.
Data model and process descriptions: customers, statuses, required fields, automations and access rules.
Integration inventory: connected systems, APIs, webhooks and service limits.
Operational documentation: logs, alerts, backups, known issues and recurring tasks.
License and component list: third-party packages, terms of use and update requirements.
The security review is a separate task. Among other things, it must examine server-side authorization, public database accessibility, secret storage, vulnerable dependencies and data input points. A hidden button is no substitute for access control.
The strongest test of a handover: have another specialist restore the system in an isolated environment using the documentation. Use test data wherever possible. If they need to call the original developer at every other step, the handover is not yet complete.
5. Data protection and maintenance: who is responsible from tomorrow?
If the CRM processes personal data, GDPR requirements apply regardless of the development method. Clarify the purposes and legal bases for processing, retention periods, access rights, data processor relationships and any transfers to third countries.
A separate question is whether real customer data has been included in AI prompts, support tickets or test environments. If so, investigate the service terms and the circumstances of the data processing. A suspected incident requires a documented risk assessment; not every shortcoming automatically triggers a reporting obligation.
By the end of the handover, designate a business system owner and a technical maintainer. Document who receives issue reports, who authorizes changes, who performs updates and which recovery objectives apply. Also establish a contingency plan for CRM outages: sales operations should not continue in improvised personal lists.
6. The xFLOWer approach: processes should not live in one person's head
The immediate handover aims to ensure business continuity; deciding which system should manage processes in the future is a separate matter. An xFLOWer-based approach can play a role in this longer-term restructuring. However, the underlying principle can be applied now: document not only the application's screens, but also how a prospect moves through quotation, approval and follow-up.
Managing processes within a framework can reduce key-person dependency, provided that roles, tasks, decision points and exceptions are documented and operate under organizational control. This means that when an employee leaves, there is no need to reinvent the entire logic of customer management.
Using a workflow framework such as xFLOWer can offer a solution because the employee maps business processes within an existing system rather than rebuilding the entire technical foundation of the CRM. When selecting a framework, require documented testing, a security audit and professional oversight independent of the developer. Custom development can then potentially be limited to interfaces connecting existing systems; these must also be approved, tested and documented, otherwise shadow IT risks remain at the integration points.
The legal and handover arrangements also become clearer: the company's service provider agreement governs the right to use the framework, rather than the legal status of the departing colleague's own development. However, rights to process models, custom code and interfaces created by the employee must still be addressed separately. The handover therefore focuses on documented customizations, connections and company access rights; rules for processing customer data must continue to be defined separately from software rights.
However, the framework does not replace legal clarification, secure configuration or responsible operation. An xFLOWer-based solution also requires handover procedures, controlled access and clear maintenance responsibilities. The goal is not to create another dependency, but to make operations transferable.
7. Summary: the handover must be verified
Before closing the handover, check the following:
The legal basis for using and further developing the CRM has been established and documented.
The designated company representative has access to the necessary systems and has verified account recovery options.
Another specialist has successfully restored the system in an isolated environment using the documentation and backup.
You have designated the business owner and technical maintainer, and documented procedures for issue handling and operations during outages.
You have included the revocation of the departing employee’s access rights and the rotation of affected secrets in the offboarding plan.
Assign an owner and a deadline to each outstanding item. A working demo and delivered source code alone do not demonstrate a complete handover.
As a preventive measure, a workflow framework under corporate oversight, such as xFLOWer, can help ensure that when a colleague leaves, you hand over processes managed within a controlled framework rather than having to rescue software dependent on one person.
Do you have an internal application that only one colleague understands? Start with a dependency assessment before they leave. Discuss with the xFLOWer team how to make the processes behind your CRM more transparent, better governed and easier to hand over.
This article provides general information; specific copyright or employment law disputes require an individual legal assessment.
This article is part of our comprehensive guide: The top 10 risks of vibe coding: a comprehensive business guide from security to copyright
xFLOWer.ai
Design the process behind this article – for free!
AI reads the processes hidden in this article; open any of them in xFLOWer.ai with one click.
