How do I set up a conflict-of-interest policy when my fractional CRO also advises a competitor in 2027?

The end-to-end process for building a conflict-of-interest policy

The policy you need is not a generic legal form pulled off a template site. It is a working document that maps the actual shape of a fractional engagement — a part-time executive who by design carries several clients at once — onto the specific risks your business carries. Build it in stages, and build it before the first invoice.

Stage 1: Inventory the risk surface. Before you write a single clause, list every relationship that could collide with your fractional CRO's other work. That includes direct competitors selling to the same buyer with the same motion, adjacent vendors whose products sit next to yours in a stack, channel partners and resellers, your ten largest accounts, and any company where your fractional CRO sits on an advisory board or holds equity. Most founders skip this step and jump straight to a non-compete clause, which is the bluntest and least useful tool in the kit.

Stage 2: Require full disclosure, in writing, with specificity. A disclosure that says "I advise several B2B software companies" is worthless. You want company names, the nature of the engagement (board seat, advisory, fractional, paid consultant), the number of hours per month, the start date, and whether the engagement touches your category. Ask for this at the proposal stage, then again at contract signature, then as a standing quarterly refresh. The refresh matters more than the initial disclosure, because a fractional operator's roster turns over — an engagement that ended last quarter may be replaced by one that competes with you this quarter.

Stage 3: Classify each disclosed relationship. Not every overlap is fatal. A useful three-tier scheme: Red — direct competitor in your category, same buyer, same deal size. Red means the engagement is prohibited, or if already underway, the fractional CRO must exit one of the two. Amber — adjacent category, overlapping buyer, plausible future competition. Amber means disclosure is mandatory, the fractional CRO is recused from strategy discussions touching that segment, and you get a written information barrier. Green — unrelated category, no shared buyer, no shared channel. Green requires disclosure but no restriction.

Stage 4: Write the operative clauses. Five clauses carry most of the weight. A confidentiality clause scoped to your specific information categories (pipeline data, pricing, win/loss, roadmap, customer lists) rather than a generic "confidential information" phrase. A non-solicit covering your employees and your customers for the engagement term plus twelve months. A recusal clause obligating the fractional CRO to leave the room — physically or on the call — when a Red or Amber topic is discussed, and to document that they did. An information-barrier clause describing how they will avoid cross-pollinating playbooks, pricing models, and account intelligence between clients. A disclosure-refresh clause making quarterly disclosure a contractual obligation, with breach treated as a material default.

Stage 5: Operationalize it. A policy that lives in a drawer does nothing. Put the disclosure register in your RevOps stack as a living document. Add a standing agenda item to your monthly leadership meeting: "any new engagements, any new overlaps?" Give your own team a channel to flag a concern without going through the fractional CRO. And log recusals, because if the relationship ever sours, the log is your evidence that you ran a real process rather than a paper one.

Stage 6: Set the exit triggers in advance. Decide now what would end the engagement. A fractional CRO taking a Red engagement without telling you is an immediate termination event. Taking an Amber engagement without disclosure is a cure-period event — thirty days to remediate or exit. Deciding this while everyone is friendly is far easier than negotiating it after trust has broken.

The sequence matters. Founders who draft clauses first and inventory risk second end up with a document full of prohibitions that do not match their actual exposure — a sweeping non-compete that the fractional CRO cannot realistically honor across a six-client portfolio, which then gets ignored and trains both parties to treat the whole policy as decorative.

Where the conflict creates or leaks revenue

A conflict-of-interest problem rarely announces itself as a legal issue. It shows up first as a revenue symptom, and the symptoms are specific enough to watch for.

Pipeline leakage through pattern transfer. Your fractional CRO learns your pricing architecture, your discount floors, your objection-handling scripts, and your win themes. Those are not trade secrets in the dramatic sense — they are the accumulated operational judgment of your go-to-market engine. If they also advise a competitor, the transfer is not a dramatic data dump; it is a hundred small adjustments in how that competitor prices, positions, and sequences deals. You will never see it in a log. You will see it as a slow erosion of win rate in head-to-head deals, typically fifteen to twenty-five percent of your competitive opportunities, over two to three quarters.

Forecast distortion. A fractional CRO who is recused from a segment cannot forecast it. If the recusal is informal, they will still be in the room, still absorbing the numbers, and still shaping the commit. Your forecast accuracy degrades in exactly the segment where the conflict lives, and because forecast quality is the input to hiring, inventory, and spend decisions, the damage compounds downstream.

Account conflict on shared customers. This is the most expensive leak and the easiest to miss. If your fractional CRO advises a company that sells into the same enterprise accounts you do, they may be advising both sides of a renewal, a pilot, or a competitive displacement. Even without bad intent, the natural instinct to be helpful to both clients produces advice that is diluted for both. Deals stall. Cycles lengthen. Champions go quiet.

Referral and channel contamination. If your fractional CRO sits on a partner advisory board or has a referral relationship with a channel, and that channel also works with a competitor, you can end up with your own partner routing opportunities to a rival. This is not hypothetical — it is common in regional markets where the same integrators, agencies, and resellers serve everyone.

Team morale and attrition. Your sellers notice. When a revenue leader is visibly splitting attention and steering clear of certain conversations, the team reads it as either a lack of commitment or something being hidden. Both readings cost you retention, and replacing a mid-market AE costs somewhere between fifty and two hundred percent of annual quota in recruiting, ramp, and lost pipeline.

Board and investor confidence. If you raise, your board will ask about key-person risk and competitive exposure. A disclosed, well-managed conflict policy is a governance positive. An undisclosed one that surfaces during diligence is a valuation problem, and it is the kind of finding that turns a clean term sheet into a re-trade.

The broadened view here is that conflict management is not purely defensive. Companies that run a tight policy get a real benefit: the fractional CRO knows exactly where the lines are, which paradoxically makes them more useful inside the lines. Ambiguity produces cautious, hedged advice. Clarity produces decisive advice.

Concrete numbers and benchmarks

Specific thresholds make the policy enforceable. These are the ranges that practitioners in fractional revenue leadership and RevOps work with.

Portfolio size. A full-time fractional CRO typically carries three to six concurrent clients. Below three, the operator is likely underemployed and may be hunting for a full-time role, which shortens your engagement. Above six, attention per client drops below the threshold where a fractional engagement produces system-building rather than firefighting. If your candidate lists eight or more active engagements, ask directly how many hours per month each receives.

Time commitment. Standard fractional engagements run one to three days per week. Diagnostic phases spike to four or five days per week for four to six weeks. Steady-state often settles at one to two days. Build your disclosure cadence around this: if your fractional CRO is at one day per week, a quarterly disclosure refresh is proportionate. At three days per week, monthly is safer.

Disclosure refresh cadence. Quarterly is the common floor. Monthly is appropriate when the fractional CRO is deeply embedded — three or more days per week, or holding your pipeline and forecast. The refresh should take under fifteen minutes if the register is well maintained.

Recusal documentation. Every recusal should be logged with a date, the topic, and the participants. Target one hundred percent documentation for Red and Amber topics. In practice, teams that log recusals catch roughly one undisclosed overlap per year that the disclosure process alone missed.

Non-solicit duration. Twelve months post-engagement is standard for customers and employees. Twenty-four months is common for enterprise accounts with long cycles. Longer than twenty-four months is hard to enforce in many jurisdictions and rarely worth the friction.

Cure period. Thirty days is the typical window for an Amber disclosure failure. Red engagements taken without disclosure are usually immediate-termination events with no cure.

Contract term. Three to eighteen months is the normal band. Month-to-month or a rolling ninety-day term protects flexibility. If a conflict emerges, a short term means you can exit without paying out a long tail.

Cost of a bad exit. Terminating a fractional engagement mid-term typically costs one to two months of remaining fees plus the replacement search, which runs four to ten weeks. Compare that to the cost of a competitive leak you cannot prove — the asymmetry argues for tight upfront policy.

Win-rate signal. Track head-to-head win rate by competitor, quarterly. If a specific rival's win rate against you moves more than ten points in two quarters, and your fractional CRO has any adjacency there, investigate the disclosure register before you assume a product problem.

Forecast accuracy. Measure commit-versus-actual variance. A healthy B2B forecast lands within ten to fifteen percent. If variance in one segment widens while other segments hold steady, that segment may be one your fractional CRO is informally recused from — and therefore under-owning.

Pitfalls and how to avoid them

Pitfall 1: Relying on a non-compete as the whole policy. Non-competes are narrow, jurisdiction-dependent, and often unenforceable against a part-time advisor. They also do not address the real risk, which is information flow, not employment. Fix: lead with confidentiality, recusal, and information barriers. Treat the non-compete as a backstop, not the mechanism.

Pitfall 2: Accepting a vague disclosure. "I work with a few SaaS companies" tells you nothing. Fix: require named entities and a category description for each. If a candidate resists naming clients, offer a mutual NDA and a category-only disclosure — but insist on the category, because category is where the conflict lives.

Pitfall 3: Writing the policy once and never revisiting it. A fractional CRO's roster turns over every few months. The engagement that was Green in January can become Amber in July if the client pivots into your category. Fix: contractual quarterly refresh, with a standing calendar invite and a named owner on your side.

Pitfall 4: No recusal mechanism. A recusal clause without a process is aspirational. Fix: define what recusal looks like operationally — who notifies whom, how the meeting notes are redacted, who owns the segment in the fractional CRO's absence. If nobody owns it in their absence, the recusal just means the segment goes unmanaged.

Pitfall 5: Assuming good intent is sufficient. Most fractional CROs are honest and disclose in good faith. The failure mode is not deception; it is drift. An operator with six clients does not always notice that client four has quietly become a competitor of client two. Fix: make the disclosure a structured prompt, not an open question. Send a list of your competitors and ask them to confirm or deny each one.

Pitfall 6: Forgetting your own side of the barrier. Information barriers run both ways. If your team shares a competitor's pricing intel with the fractional CRO, you have created the problem you were trying to prevent. Fix: brief your own leadership team on what not to share, and put it in writing.

Pitfall 7: Letting the policy become adversarial. A policy designed to catch someone produces defensive behavior. A policy designed to keep everyone honest produces candor. Fix: frame the register as a shared tool. Review it together. Make the fractional CRO a co-author.

Pitfall 8: Ignoring the adjacent-relationship risk. The most common real-world conflict is not a direct competitor. It is a company selling a complementary product to the same buyer, where the fractional CRO advises both and ends up shaping a partnership, integration, or co-sell motion that quietly advantages one side. Fix: include complementary vendors and channel partners in the risk inventory, not just direct rivals.

Pitfall 9: No exit plan. If the policy works and a Red conflict emerges, you need a transition plan ready. Fix: document, at signature, what happens if the engagement ends abruptly — who inherits the forecast, who owns the pipeline reviews, how the playbook documentation is handed over.

Pitfall 10: Skipping the equity question. If your fractional CRO holds equity in an adjacent company, the conflict is structural, not incidental. Fix: disclose all equity and advisory grants, and treat equity in a direct competitor as a Red event with no cure.

Selection checklist

Use this as a scoring sheet when you evaluate a fractional CRO candidate, and again at each quarterly refresh. Each item is a yes/no or a scored 1–5, and anything scoring below three on the disclosure items is a stop-and-investigate.

Score each candidate on five dimensions: disclosure completeness (did they name everything without prompting), disclosure speed (how fast did they respond to a follow-up request), recusal willingness (do they volunteer to step out, or negotiate), barrier literacy (do they already run information barriers with other clients), and exit clarity (can they describe what a clean handover looks like). A candidate who scores high on all five is rare and worth paying a premium for. A candidate who scores high on disclosure but low on recusal willingness is a warning — they may be disclosing accurately but intending to stay in every room.

The checklist also works as a renewal gate. At each quarterly refresh, re-score. If disclosure completeness drops, the register is going stale. If recusal willingness drops, the engagement is drifting toward a problem.

Related questions

Does a conflict-of-interest policy need to be in the contract itself?

Ideally yes, as an exhibit or schedule. A standalone policy document referenced by the contract is enforceable, but attaching the disclosure register and the operative clauses directly to the agreement removes ambiguity about what was agreed and when.

What if my fractional CRO refuses to name their other clients?

Offer a mutual NDA and accept category-level disclosure instead of names, but do not accept a blanket refusal. Category is the minimum. If they will not even describe the category, that is a stop signal.

Can I enforce a non-compete against a part-time advisor?

Enforceability varies widely by jurisdiction, and part-time advisory relationships are often treated differently from employment. Treat the non-compete as a secondary protection and lean on confidentiality, recusal, and non-solicit clauses, which are more consistently enforceable.

How do I handle a conflict that emerges mid-engagement?

Apply the tier: Amber means immediate recusal plus a written barrier plus a disclosure update. Red means a thirty-day cure period or an exit. Document everything, and do not let the conversation stay verbal.

Should the fractional CRO disclose equity and board seats too?

Yes. Equity and board seats create structural alignment that is stronger than a paid advisory relationship. Any equity in a direct competitor should be treated as a Red event, and any equity in an adjacent company should be disclosed and reviewed.

FAQ

What is the single most important clause in a fractional CRO conflict policy? The disclosure-refresh clause. Everything else depends on knowing the current roster. Confidentiality and recusal clauses only work if you know which relationships exist, and a fractional CRO's portfolio changes every few months. Make quarterly refresh a contractual obligation with a named owner on your side.

How is a conflict-of-interest policy different from a non-compete? A non-compete restricts where someone can work. A conflict policy governs how they work while working for you — what they disclose, what they recuse from, what information they can carry. For a part-time advisor with multiple clients, the conflict policy does most of the real work.

Do I need a lawyer to draft this? For the operative clauses — confidentiality, non-solicit, recusal, cure periods — yes, have counsel review, because enforceability is jurisdiction-specific. The risk inventory, the tiering scheme, and the operational register you can build yourself with your RevOps lead.

How do I handle a fractional CRO who advises a company in an adjacent category? Treat it as Amber. Require written disclosure, apply a recusal on strategy discussions touching that segment, put an information barrier in place, and give someone else ownership of the overlapping segment so it does not go unmanaged.

What happens if I discover an undisclosed conflict? Document what you found and when. If it is a Red overlap, invoke the cure period or terminate. If it is Amber, require immediate disclosure and apply the barrier retroactively. Either way, treat the failure to disclose as the more serious issue than the overlap itself.

Does this policy change if my fractional CRO is remote versus on-site? The clauses are the same, but the operational risk shifts. A remote fractional CRO has less ambient exposure to hallway conversations and whiteboard sessions, which reduces incidental information flow. An on-site fractional CRO absorbs more context, so recusal needs to be more explicit and more documented.

Sources

• U.S. Federal Trade Commission — Non-Compete Clause Rulemaking
• U.S. Securities and Exchange Commission — Regulation S-K Item 404 Related Person Transactions
• Society for Corporate Governance — Conflicts of Interest Resources
• Harvard Business Review — Managing Conflicts of Interest
• SHRM — Confidentiality and Non-Solicitation Agreements
• National Association of Corporate Directors — Board and Advisor Conflicts
• Association of Corporate Counsel — Conflict of Interest Policies
• Project Management Institute — Code of Ethics and Professional Conduct
• Institute of Internal Auditors — Conflict of Interest Guidance

Related on PULSE

• [Fractional versus full-time revenue leadership](/knowledge/fractional-vs-fulltime-cro)
• [Revenue-leader vetting scorecard](/knowledge/cro-vetting-scorecard)
• [Matching revenue leadership to your go-to-market motion](/knowledge/gtm-motion-leadership-fit)
• [Building a forecast you can actually trust](/knowledge/forecast-accuracy-basics)
• [Designing a RevOps disclosure register](/knowledge/revops-vendor-register)
• [When to graduate a fractional CRO to a full-time hire](/knowledge/fractional-to-fulltime-transition)