Launch Positioning Builder
Research competitors, analyze their messaging, and generate a positioning document with category definition, differentiation claims, value propositions, and proof points. Chains web research, competitor site analysis, and review mining to produce a…
9 steps · start to finish.
- 1Step 1
Environment Setup
▶- Create
results_dirif it does not exist. - Confirm
output_pathis writable. - Capture the current UTC date for the positioning document filename when no explicit
output_pathis supplied. - Initialize a validation report with stages for intake, research, synthesis, output writing, and final verification.
mkdir -p /app/results python - <<'PY' from pathlib import Path for name in ['summary.md', 'validation_report.json']: assert Path('/app/results').exists(), 'results directory missing' print('environment ready') PY - Create
- 2Step 2
Intake
▶Product name + URL — What are you positioning? 2. One-sentence pitch — How do you describe what you do today? 3. Top 2-3 competitors — Names + URLs. Who does your buyer compare you to? 4. ICP…
- 3Step 3
Competitive Landscape Research
▶For each competitor, capture source URLs and short evidence notes. Prefer direct competitor pages and public reviews over secondary summaries.
- 4Step 4
Positioning Framework
▶Build the positioning doc using April Dunford's framework adapted for early-stage:
- 5Step 5
Competitive Positioning Map
▶Create a 2x2 positioning matrix:
- 6Step 6
Generate the Positioning Document
▶Created: [DATE] · Trigger: [launch/rebrand/competitive shift]
- 7Step 7
Validate Outputs
▶Check that the positioning document includes a positioning statement, category rationale, competitive landscape, value propositions, proof points, audience messaging, positioning map, deployment…
- 8Step 8
Iterate on Errors (max 3 rounds)
▶If validation fails, run up to max 3 rounds of targeted fixes. In each round, repair only missing or weak sections, preserve cited evidence, and re-run the validation checklist. Stop early once every…
- 9Step 9
Final Checklist
▶Run the final verification after writing all outputs.