poc-best-practices

Proof of Concept (POC) Best Practices

Content Preview
# Proof of Concept (POC) Best Practices

A comprehensive guide for Sales Engineers planning, executing, and evaluating proof-of-concept engagements.

## POC Planning Methodology

### 1. Pre-POC Qualification

Not every deal warrants a POC. Qualify before committing resources:

**POC-Worthy Indicators:**
- Deal value justifies 80-200+ hours of SE and engineering time
- Customer has an identified champion who will actively participate
- Clear decision timeline with POC as a defined evaluation step
How to Use

Recommended: Install to project (local)

mkdir -p .claude/skills
curl -o .claude/skills/poc-best-practices.md \
  https://raw.githubusercontent.com/alirezarezvani/claude-skills/main/business-growth/sales-engineer/references/poc-best-practices.md

Skill is scoped to this project only. Add .claude/skills/ to your .gitignoreif you don't want to commit it.

Alternative: Clone full repo

git clone https://github.com/alirezarezvani/claude-skills

Then reference at business-growth/sales-engineer/references/poc-best-practices.md

Related Skills