Independence · effective 22 July 2026

The conflict is disclosed here, before a buyer discovers it

The principal also co-founds a separate, stealth-stage technology company in agent authorization. That proximity creates expertise and a potential organisational conflict of interest. The answer is structure, not reassurance.

The bright line: this advisory practice does not sell, recommend or implement an affiliated product in a client engagement. Findings remain vendor-neutral and belong to the client.
01

No product recommendation

Every deliverable produces requirements, evaluation criteria and evidence gaps. It never names a preferred vendor or routes a client toward an affiliated product.

02

No solicitation

The advisory practice does not solicit the client for an affiliated product during the engagement or use the engagement as product discovery afterward.

03

Hard data boundary

Client advisory material does not enter the product company, its systems, product roadmap or training data.

04

Disclosure before conflict

A potential organisational conflict is disclosed before work begins. If a client reasonably needs the company identity under NDA for diligence, it is disclosed before contracting.

05

Client termination right

The client may terminate for cause if a conflict is concealed, the data boundary is breached, or advice is used to steer a product decision.

How a conflict is handled

A potential conflict is recorded when the opportunity is qualified, disclosed before contracting and revisited if scope changes. The client decides whether the safeguards are sufficient. If they are not, the work is declined or transferred.

This disclosure is versioned by its effective date. Contract-specific obligations take precedence where they are stricter.

Next step

Put the concern in writing

A buyer should not have to infer the boundary. Send the diligence question and it will be answered before commercial terms are discussed.