Design Pattern
The customer Eidolon and its limits
Enough reflection of an account that anyone can prepare before acting, bounded by confidentiality terms, privacy obligations, and contractual restrictions. The customer Eidolon is useful only if restricted material is decided and held separately before writing, because a reflection that keeps material the company had no right to retain is a liability.
The content
What the customer does, why they buy, who decides, what they run, what has been promised, what has gone wrong, what remains open, and the evidence behind each claim that matters. Written so a competent stranger could prepare for a call from it.
The boundary
Claim: recommendation
Decide before writing which material is contractually restricted, personally identifying, or shared under confidentiality. Hold restricted material in a separate tier with its own access rules, and let the general projection reference its existence without reproducing it.
A reflection that quietly accumulates material the company had no right to retain is a liability, however useful it is.
What would show this claim is wrong
- Account teams prepare no better with the reflection than with the existing CRM record.