Free resource
Your CRM stores names and email addresses. An entity file stores how someone thinks, what motivates their decisions, and what they said last Tuesday. That's the difference between generic AI and AI that sounds like you've been paying attention.
Instant delivery. Plus the walkthrough video showing the entity system in action.
What is inside
How it works
Your CRM knows Sarah is VP of Operations at Acme Corp. Her email, her phone number, maybe a note from two months ago.
It doesn't know that Sarah prefers bullet points over paragraphs, makes tech decisions solo without committee, and mentioned her CFO pushed back on the budget in the last board meeting. AI without this context writes generic follow-ups that sound like every other email in her inbox.
Contact record = who they are
Entity file = how they think
An entity file is a structured markdown file per person. Five sections: who they are, how they think, current status, watch items, and interaction history. One file per person, stored in your memory directory.
Your AI reads these before every meeting, email draft, and follow-up. It knows what you discussed last time, what motivates their decisions, and what topics to handle carefully.
One file per person → auto-read → contextual AI
Who They Are (role, connection, status). How They Think (decision style, motivations, communication preferences). Current Status (active projects, next steps). Watch Items (risks, sensitivities, patterns). Interaction History (chronological memory).
The 'How They Think' section is the moat. It's what turns 'draft a follow-up' into 'draft a follow-up knowing Marcus prefers bullet points and his CFO just pushed back on the budget.'
Entity files compound. After 5 interactions, your AI knows someone's decision style, communication preference, active projects, and past concerns. After 20 interactions, it's the best briefing document you've ever had.
Meeting prep takes 30 seconds: the AI reads the entity file and gives you a prep card. Follow-ups reference what was actually discussed. Nothing falls through the cracks because the AI checks for overdue items automatically.
5 interactions: useful
20 interactions: irreplaceable
The system works because of a simple ritual: after every interaction, update the entity file. Two minutes. What happened, what changed, what to watch for next time.
Consistent small updates compound into a system that knows your relationships deeply. The ritual matters more than perfection. A rough update today is worth more than a perfect one next week.
2 minutes after every call → compounds forever
Inside: the entity file template plus three anonymized examples showing how entity files work in practice (tenant, partner, prospect). Copy the template, create your first 3-5 entities, and watch your agent's replies change.
Drop your email below. I'll send you the template plus the walkthrough video.
Free resource
The entity file template plus three real anonymized examples. Start tracking how your clients think, not just who they are.
