I Run a Consulting Side Business and a Direct Competitor Just Offered Me a Project. I Won’t Share Anything Confidential — Just General Industry Expertise That’s Mine to Share. Is There a Conflict of Interest?

Quick Answer

Does consulting for a direct competitor create a conflict of interest even when no confidential information will be shared?

Yes — and the reason goes deeper than information sharing. A conflict of interest exists when a personal interest has the potential to influence professional judgment, regardless of whether that influence is intentional. When you consult for a competitor, your professional judgment at your primary employer is compromised in ways that are structural rather than deliberate: decisions about pricing, strategy, product direction, and customer targeting are all made with knowledge of what a competitor is working on and needs. Even with perfect integrity, the conflict is real because the potential influence exists. Most employment agreements and COI policies address this explicitly — and even those that don’t are typically interpreted to cover direct competitor consulting.

The Situation

A senior product manager at a mid-size software company runs an approved consulting side business. The side business has been disclosed to HR and is on file — it covers general product strategy consulting for companies outside the industry. She’s been doing it for two years without issue. Last week, a recruiter reached out on behalf of a client who wants a three-month engagement to help develop their product roadmap. The client is a direct competitor—a company that competes in the same software category as her employer and has several overlapping enterprise accounts.

The project scope doesn’t require her to share anything from her current employer. She’d be advising on general product strategy principles, user research methodologies, and roadmap prioritization frameworks — all expertise she’s built over her career and considers hers to apply wherever she works. The pay is significant, and the project is interesting.

Her reasoning: “I’m not sharing trade secrets. I’m sharing my expertise. There’s a difference. And my consulting was already approved.”

Choice AAccept the project. The consulting was already approved. She’s sharing her own expertise, not company confidential information. The project scope is clearly defined and doesn’t require access to any proprietary information. Her prior approval covers this engagement.

Choice BDisclose this specific opportunity to HR and her manager before accepting, explaining that the potential client is a direct competitor and requesting a specific determination on whether this engagement falls within her approved consulting scope. The prior approval covered non-industry clients. This is a materially different situation that requires its own assessment.

Choice CDecline the project without disclosing it. She recognizes it creates a conflict and removes herself from the situation. No disclosure needed because she’s not going to do it.

The Right Call

Choice B — Disclose this specific opportunity to HR before accepting. Prior approval of general consulting does not cover direct competitor engagements.

Choice A misreads the scope of the prior approval. The approved consulting practice covered companies outside the industry. A direct competitor is categorically different — it’s the specific situation most COI policies are written to prevent, and “general consulting was approved” does not transfer to “direct competitor consulting is approved.” Choice C is better than A but incomplete: declining the project removes the immediate conflict, but doesn’t give the organization the opportunity to assess whether the competitive approach itself signals a scope gap in the approved consulting practice that should be addressed going forward. Choice B is the right sequence — disclose first, let the organization make an informed decision, then accept or decline based on that determination.

“I’m sharing my expertise, not their secrets” is true — and insufficient.

The distinction between personal expertise and proprietary information is real and legally meaningful. But it doesn’t resolve the conflict-of-interest question. A conflict of interest is not only about what you share — it’s about the structural position you occupy. When you consult for a competitor, you know their product strategy challenges, their roadmap gaps, and their resource constraints. That knowledge influences how you think about your primary employer’s decisions, even without any deliberate information transfer. Competitor engagement creates a dual-perspective problem that pure expertise-sharing analysis doesn’t address.

Prior approval of general consulting is not a blanket authorization.

When HR approved the consulting practice two years ago, the context was non-industry clients with no competitive overlap. That approval was based on a specific risk profile that a direct competitor engagement would change materially. Treating a categorical approval as covering any specific engagement that arguably fits the category is the interpretation error most employees make — and most employment agreements specify that outside employment approvals are situation-specific and require disclosure of material changes in scope.

Most employment agreements have non-compete or competitive activity provisions that address this specifically.

Regardless of what the COI policy says, many employment agreements include provisions that prohibit providing services — consulting or otherwise — to direct competitors during the employment period. These provisions are enforceable in most jurisdictions for senior employees with access to competitively sensitive information. Accepting the engagement without reviewing the employment agreement and getting HR’s sign-off on this specific opportunity creates legal exposure that “I wasn’t sharing secrets” doesn’t resolve.

Can an employee consult for a competitor if they don’t share confidential information?

Potentially not — depending on the employment agreement, COI policy, and the nature of the employee’s role. Most employment agreements for employees with access to competitively sensitive information include provisions prohibiting competitive consulting activity during employment, regardless of whether confidential information is shared. The conflict of interest exists structurally — because the employee now holds dual perspectives on a competitive relationship — independent of whether any specific information transfers.

Does a prior HR approval for outside consulting cover a new engagement with a direct competitor?

Almost certainly not without specific disclosure and re-approval of the new engagement. Outside employment approvals are typically assessed based on the specific nature, client, and scope of the work, and a direct competitor engagement has a fundamentally different risk profile than non-industry consulting. The prior approval assessed a different risk. This engagement requires its own assessment.

What should an employee do when a consulting opportunity arises that wasn’t contemplated in the original disclosure?

Disclose the specific opportunity to HR before accepting — including the identity of the potential client, the nature of the work, the estimated time commitment, and any connection to the employee’s primary role. HR can assess whether the specific engagement falls within the existing approval, requires an updated approval, or creates a conflict that can’t be accommodated. This disclosure protects the employee, the consulting client, and the organization — and it’s almost always faster than employees expect.

How to Use This Scenario in Training

Recommended for senior individual contributors, managers, and professionals in roles with access to competitively sensitive information — particularly in technology, professional services, financial services, and consulting organizations where outside consulting practices are common. Most effective when delivered alongside a review of the organization’s outside employment policy and the specific provisions of standard employment agreements covering competitive activity.

This scenario demonstrates the self-serving reasoning rationalization from the Decision Readiness Engine™ — “I’m sharing expertise, not secrets” is the framing that makes accepting the engagement feel principled. Decision-ready employees recognize that the conflict of interest analysis includes the structural position created by the engagement, not just the information flow within it — and that prior approval of general consulting does not transfer to specific high-risk engagements without disclosure.

More Side Hustle & Outside Employment Scenarios