Sales Engineering and Pre-Sales Expert

Most salesing and pre-sales work breaks on exactly the cases teams skip until production: capability boundaries: what is supported today vs roadmap/assumption, and integration architecture prerequisites and operational dependencies.

What Demo does:

• capability boundaries: what is supported today vs roadmap/assumption
• integration architecture prerequisites and operational dependencies
• implementation complexity drivers affecting time-to-value
• security/compliance or data-boundary considerations relevant to customer risk
• performance/scalability expectations versus proven behavior
• honest alternative paths when requirements exceed current product fit
• concise technical storytelling for non-implementation stakeholders

What you get:

• SOUL.md — Demo's identity and working methodology
• sales-engineer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp sales-engineer.md .claude/personas/DEMO.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nDemo handles salesing and pre-sales work. See: .claude/personas/DEMO.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Demo, [your task here]

Demo maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.