What independence actually means in advisory work — and why we turn down half our inbound

The conflict that's invisible until it shows up in the deliverable

Conflicts of interest in advisory work are rarely the cartoon version. There is no envelope of cash; there is no wink and a nod. The conflict is structural and gradual. An advisor builds a relationship with a vendor over years. The vendor sends them business. The advisor finds it easier to recommend the vendor to operators who have questions adjacent to the vendor's capabilities. Over time, the recommendation hardens into a default.

The conflict shows up in the deliverable as the omission of an alternative — the option that wasn't researched, the question that wasn't asked, the supplier that wasn't named. A reader of a single deliverable will not see the conflict; they will see a clean recommendation. A reader who has seen ten deliverables from the same advisor will notice that the same vendor keeps appearing. The conflict is in the pattern, not in the page.

Three categories of conflict

We screen new engagements against three categories of conflict. Each has its own test, its own disclosure standard, and its own bar for declining the work.

Financial conflictsare the easiest to identify. Any economic relationship between the advisor and a party named in the engagement — a referral fee, an equity stake, a consulting retainer, a board seat, a family member's ownership interest — is a financial conflict. The test is binary: does any money or equity move between the firm and a party to the question? If yes, the engagement is declined or the relationship is wound down before the engagement begins.

Relational conflictsare subtler. They cover the cases where no money has moved but a personal relationship colors the analysis: the advisor used to work for the vendor, the founder is a long-time friend, the firm has a standing referral pattern with the vendor's sales team. These conflicts are not automatic disqualifications, but they require written disclosure to the client and an explicit decision by the client to proceed.

Structural conflictsare the hardest to see. They cover the cases where the firm's business model itself creates a bias: an advisor who is paid by the vendor to make introductions, a firm that takes a percentage of vendor revenue, a consultancy that runs a quarterly conference whose sponsorships are sold to the same vendors clients ask about. These are business-model conflicts, and they cannot be cured by disclosure. They require a different business model.

Our policy: vendor-side relationships disqualify us from operator-side engagements

Pure Chain Advisory does not take retainers from vendors. We do not accept referral fees from vendors. We do not hold equity in vendors we research. The firm's revenue comes from operator-side clients only — the brands and founders asking the question, not the suppliers being asked about.

That single rule resolves most of the structural conflict question. If we have a financial relationship with a vendor, we cannot work on the operator side of an engagement involving that vendor. If we want to work on the operator side, we cannot have a vendor-side relationship. The directionality is the point. Choosing one side fixes the bias; trying to play both sides is what introduces it.

The cost of this rule is the work we don't get to do. There are operators we like, with questions we would enjoy researching, that we have to decline because we know one of the parties already. There are vendors we respect that we have declined to take retainer relationships with so that we can stay available for operator-side work. The line is bright on purpose.

The kinds of inbound we routinely decline

In a typical month, roughly half of our inbound is declined for conflict reasons. The biggest category is vendor-led engagements — a manufacturer or supplier who wants us to validate a claim they are making to their own customers. We do not accept that work; the moment the vendor is paying, the analysis is no longer independent.

The second category is referrals from venture investors who hold positions in both the operator and the vendor under review. The investor's incentive to see a clean outcome is structural; we are not the right firm to deliver a clean conclusion the investor has already implicitly priced into the round. We say so and decline.

The third category is engagements with too narrow a scope to support an honest answer. A founder asking us to validate a vendor they are committed to is not asking for diligence; they are asking for a writeup. We decline that work too — not because the founder is wrong to proceed, but because the deliverable they are asking for is not the deliverable that protects them.

Why this matters for the deliverable's authority

A research note from an advisor who takes vendor retainers reads the same on the page as a research note from an advisor who does not. The reader cannot tell the difference at the level of the document; they can only tell at the level of the practice. The reason independence policy belongs on the firm's public website is that it is the only way a reader who has not hired us yet can verify the standard.

The deliverable's authority comes from the work we decline as much as from the work we accept. Every engagement we turn down on conflict grounds is a small vote of confidence in every engagement we accept. That's the trade. The discipline of declining creates the authority to be believed.

What this means for operators

• Ask any advisor about their economic relationships before you hire them. The answer should be specific, not abstract: who pays them, who they hold equity in, who they refer business to.
• Ask whether they take retainers from vendors. A firm that takes both vendor-side and operator-side retainers cannot give you a fully independent answer on the vendors it serves.
• Read the conflict disclosure before the deliverable. A clean engagement begins with a written disclosure of any relationship that could color the analysis. Absence of disclosure is itself a signal.
• Watch for patterns across multiple deliverables. The conflict is rarely visible in one report; it is often visible in three.
• Pay for independence on the front end. Free advice from a referral-fee-paid advisor is more expensive than a fixed fee from an independent one. The cost is hidden in the recommendation.