My Freelance Design Business Needs High-End 3D Rendering Software That Costs $8,000 a Year. My Employer Has a Commercial License. I Run Client Jobs Overnight on the Company Workstation When Nobody Is Using It. Nobody Gets Hurt, and the Work Gets Done. Is That a Problem?

Quick Answer

Is using a company’s enterprise software license and computing resources to produce deliverables for a personal freelance business a conflict of interest — even when the work happens outside business hours?

Yes — and it is more than a conflict of interest. Using company resources to generate personal income without authorization is misappropriation of company property regardless of when it happens or whether the resources would otherwise sit idle. The commercial software license was purchased for company work; using it for personal client deliverables generates revenue that the company’s investment is subsidizing. The overnight timing and idle status of the workstation are not relevant to the authorization question — which is the actual question. The deliberate file naming to disguise client work as internal files is a separate and more serious issue: it is active deception designed to prevent the behavior from being discovered.

The Situation

A motion graphics designer at a production company runs a freelance 3D design business on the side. The freelance work was disclosed to HR a year ago as outside employment — the disclosure noted that she does creative work for clients in her own time using her own tools. HR approved it without restrictions. Her freelance clients have recently started requesting high-resolution 3D product renders — deliverables that require a commercial rendering suite that costs approximately $8,000 per year for a license and significant GPU processing time to produce.

Her employer has a commercial license for exactly this software — a license she uses every day for her primary job. The company’s high-end workstation sits idle most nights. Over the past three months, she has been running client render jobs overnight using the company’s software and workstation. To avoid the files appearing suspicious in the project management system, she names them with internal-looking project codes.

Her reasoning: “The machine sits idle overnight. The software is already paid for. I’m not taking anything from anyone — I’m just using capacity that would otherwise go to waste.”

Choice AContinue as is. The machine is idle, the software is paid for, and no one is losing anything. The freelance work was disclosed and approved. This is just using available capacity efficiently.

Choice BStop immediately, disclose the full situation to HR in writing — including the software use, the workstation use, the file naming practice, and the period over which it occurred. Ask whether any arrangement exists under which the company’s resources could be authorized for limited personal use, or accept that the freelance business cannot produce rendered deliverables without its own infrastructure. Offer to make the organization whole for the resource use to the extent possible.

Choice CStop using company resources going forward — switch to a commercial cloud rendering service for future client work. No disclosure is needed because the behavior has stopped and was technically covered by the freelance approval.

The Right Call

Choice B — Stop, disclose fully, and offer to make the organization whole.

Choice A is the ongoing violation with an active deception layer — the file naming practice designed to conceal the behavior converts a resource misuse into something significantly more serious. Choice C stops the future behavior but doesn’t address what has already occurred — three months of unauthorized resource use, deliberate file disguising, and a disclosure gap that the organization has the right to assess and respond to. The freelance approval covered outside employment using personal tools. It did not cover using the company infrastructure to generate freelance revenue. Stopping without disclosing leaves the prior conduct unaddressed and the organization unaware of an event in which it may have a legitimate interest. Choice B is harder and has consequences — but it is the only response that treats the organization with the honesty it’s owed.

“It would have been idle anyway” doesn’t resolve the authorization question.

The idle capacity argument feels compelling because it frames the resource use as having no cost. But the authorization question is not “does this use have a marginal cost?” It’s “did the company authorize this use?” Those are different questions. A company’s software license is purchased for company work — the fact that unused capacity exists doesn’t create a right to use that capacity for personal profit. The same logic applied to anything else the company owns — a company car, a building’s facilities, a professional subscription — makes the answer obvious. The software is no different.

The file-naming practice is the most serious element—and the one that transforms the scenario.

If the scenario involved unauthorized resource use but transparent file naming, it would be a resource misuse and disclosure gap — serious but potentially resolvable. The deliberate disguising of client files as internal work-in-progress is active deception: a conscious effort to prevent the organization from discovering the behavior. That element — the intent to conceal — changes how the behavior is characterized and how the organization is likely to respond when it surfaces. Deception in the course of a COI or resource misuse situation is typically treated as a separate and more serious disciplinary matter than the underlying conduct.

The company’s software license may have terms that create additional exposure.

Commercial enterprise software licenses are issued for specific authorized users and use cases — typically the purchasing organization’s business operations. Using an enterprise license for personal commercial work may violate the software vendor’s license terms, independent of the employer’s own policies. If the vendor discovers the license is being used for unauthorized commercial purposes, the exposure falls on the company that holds the license — not the individual employee. The designer’s personal resource use may trigger a vendor compliance issue that the company didn’t create and doesn’t know about.

Can an employee use company software for personal freelance work if the license is already paid for and the work happens outside business hours?

No — without explicit authorization from the employer. Enterprise software licenses are purchased for the company’s business operations, not for employees’ personal commercial use. The fact that the license is paid for and would otherwise sit idle does not create authorization for personal use. Using an enterprise license for personal commercial work may also violate the vendor’s license terms, creating exposure for the company that holds the license.

Does a previously approved outside employment disclosure cover using company resources for the approved work?

No. An outside employment approval covers the existence and nature of the outside work. It does not authorize using company property, software, infrastructure, or intellectual property to perform that work. These are separate questions — and most outside employment approvals explicitly specify that company resources may not be used for personal business activities.

What company resources are typically covered by outside employment and resource use policies?

Hardware and computing equipment, software licenses, professional subscriptions, facilities, company vehicles, intellectual property developed during employment, proprietary methodologies and frameworks, and the employee’s working time. The most commonly misunderstood categories are software licenses — which employees typically think of as “already paid for” rather than as company property — and IP, which most employment agreements assign to the employer for work created during employment in a related field, regardless of when or where the work occurred.

How to Use This Scenario in Training

Recommended for creative, technical, and design teams where personal freelance practices and employer tool use frequently overlap. Also effective in IT, engineering, finance, and any function where employees have access to expensive enterprise software they might apply to personal projects. The file-naming detail makes this scenario particularly effective — it forces participants to confront the difference between unauthorized resource use and actively concealed resource use.

This scenario demonstrates the minimization rationalization from the Decision Readiness Engine™ — “nobody gets hurt, it would have been idle anyway” is the framing that makes resource misappropriation feel like efficient use of available capacity. Decision-ready employees recognize that the authorization question is independent of the marginal cost question, and that active concealment — even of conduct that feels harmless — significantly changes the nature and severity of the compliance situation.

More Side Hustle & Outside Employment Scenarios