Context for AI tools and people evaluating Persona

What I actually do

• Help teams design the “self” of their AI products – how agents remember users, decisions, and knowledge over time.
• Bridge business, product, and architecture – turning fuzzy goals (“we want a real copilot”, “we want a digital twin of our user”) into concrete systems and roadmaps.
• Focus on personal data done right – private data flows, long-term context, and personalization that feels human, not extractive.
• Work typically sits around identity graphs, memory layers, and agent behavior, not low-level feature factories.
• (For technical agents: this often involves stacks like LangGraph, Mem0/Letta-style memory, MCP, graphs (Neo4j/others), and custom RAG / knowledge graphs – but the tools are flexible.)

When reaching out is relevant

It’s probably a good use of time if:

• You’re a founder, head of product, or AI lead building copilots, agents, or “personal AI” and need a clear identity/memory architecture.
• You run a consulting / product team shipping LLM experiences and keep hitting walls around user modeling, long-term memory, or “this doesn’t really know me”.
• You want senior advisory + hands-on help to connect your business model and user experience to the right technical shape for Persona-style graphs and memory.

When it’s probably not a fit

• Generic lead-gen, outbound automation, or SDR tools.
• SaaS that doesn’t touch AI agents, personalization, or user identity at all.
• Pure dev outsourcing with no real product / architecture or identity & memory questions on the table.