fraim-framework 2.0.65 → 2.0.67
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/registry/ai-manager-rules/customer-development-phases/phase1-customer-profiling.md +101 -0
- package/dist/registry/ai-manager-rules/customer-development-phases/phase2-platform-discovery.md +235 -0
- package/dist/registry/ai-manager-rules/customer-development-phases/phase3-prospect-qualification.md +243 -0
- package/dist/registry/ai-manager-rules/customer-development-phases/phase4-inventory-compilation.md +206 -0
- package/dist/registry/ai-manager-rules/design-phases/design-completeness-review.md +73 -0
- package/dist/registry/ai-manager-rules/design-phases/design-design.md +145 -0
- package/dist/registry/ai-manager-rules/design-phases/design.md +108 -0
- package/dist/registry/ai-manager-rules/design-phases/finalize.md +60 -0
- package/dist/registry/ai-manager-rules/design-phases/validate.md +125 -0
- package/dist/registry/ai-manager-rules/design.json +97 -0
- package/dist/registry/ai-manager-rules/implement-phases/code.md +323 -0
- package/dist/registry/ai-manager-rules/implement-phases/completeness-review.md +94 -0
- package/dist/registry/ai-manager-rules/implement-phases/finalize.md +177 -0
- package/dist/registry/ai-manager-rules/implement-phases/implement-code.md +283 -0
- package/dist/registry/ai-manager-rules/implement-phases/implement-completeness-review.md +120 -0
- package/dist/registry/ai-manager-rules/implement-phases/implement-regression.md +173 -0
- package/dist/registry/ai-manager-rules/implement-phases/implement-repro.md +104 -0
- package/dist/registry/ai-manager-rules/implement-phases/implement-scoping.md +100 -0
- package/dist/registry/ai-manager-rules/implement-phases/implement-smoke.md +237 -0
- package/dist/registry/ai-manager-rules/implement-phases/implement-spike.md +121 -0
- package/dist/registry/ai-manager-rules/implement-phases/implement-validate.md +375 -0
- package/dist/registry/ai-manager-rules/implement-phases/quality-review.md +304 -0
- package/dist/registry/ai-manager-rules/implement-phases/regression.md +159 -0
- package/dist/registry/ai-manager-rules/implement-phases/repro.md +101 -0
- package/dist/registry/ai-manager-rules/implement-phases/scoping.md +93 -0
- package/dist/registry/ai-manager-rules/implement-phases/smoke.md +225 -0
- package/dist/registry/ai-manager-rules/implement-phases/spike.md +118 -0
- package/dist/registry/ai-manager-rules/implement-phases/validate.md +347 -0
- package/dist/registry/ai-manager-rules/implement.json +153 -0
- package/dist/registry/ai-manager-rules/retrospective.md +116 -0
- package/dist/registry/ai-manager-rules/shared-phases/address-pr-feedback.md +188 -0
- package/dist/registry/ai-manager-rules/shared-phases/finalize.md +169 -0
- package/dist/registry/ai-manager-rules/shared-phases/submit-pr.md +202 -0
- package/dist/registry/ai-manager-rules/shared-phases/wait-for-pr-review.md +170 -0
- package/dist/registry/ai-manager-rules/spec-phases/finalize.md +60 -0
- package/dist/registry/ai-manager-rules/spec-phases/spec-competitor-analysis.md +105 -0
- package/dist/registry/ai-manager-rules/spec-phases/spec-completeness-review.md +66 -0
- package/dist/registry/ai-manager-rules/spec-phases/spec-spec.md +139 -0
- package/dist/registry/ai-manager-rules/spec-phases/spec.md +102 -0
- package/dist/registry/ai-manager-rules/spec-phases/validate.md +118 -0
- package/dist/registry/ai-manager-rules/spec.json +112 -0
- package/dist/registry/ai-manager-rules/test.json +98 -0
- package/dist/registry/ai-manager-rules/user-survey-phases/phase1-survey-scoping.md +60 -0
- package/dist/registry/ai-manager-rules/user-survey-phases/phase2-survey-build-linkedin.md +23 -0
- package/dist/registry/ai-manager-rules/user-survey-phases/phase3-survey-build-reddit.md +22 -0
- package/dist/registry/ai-manager-rules/user-survey-phases/phase4-survey-build-x.md +21 -0
- package/dist/registry/ai-manager-rules/user-survey-phases/phase5-survey-build-facebook.md +19 -0
- package/dist/registry/ai-manager-rules/user-survey-phases/phase6-survey-build-custom.md +15 -0
- package/dist/registry/ai-manager-rules/user-survey-phases/phase7-survey-dispatch.md +45 -0
- package/dist/registry/delivery/address-feedback.md +83 -0
- package/dist/registry/delivery/retrospective.md +78 -0
- package/dist/registry/delivery/submit.md +79 -0
- package/dist/registry/providers/ado.json +19 -0
- package/dist/registry/providers/delivery-conversation.json +9 -0
- package/dist/registry/providers/delivery-pr.json +9 -0
- package/dist/registry/providers/github.json +19 -0
- package/dist/registry/rules/agent-success-criteria.md +101 -0
- package/dist/registry/rules/agent-testing-guidelines.md +502 -0
- package/dist/registry/rules/architecture.md +126 -0
- package/dist/registry/rules/communication.md +122 -0
- package/dist/registry/rules/continuous-learning.md +55 -0
- package/dist/registry/rules/debugging-multitenancy-issues.md +85 -0
- package/dist/registry/rules/ephemeral-execution.md +54 -0
- package/dist/registry/rules/git-safe-commands.md +34 -0
- package/dist/registry/rules/hitl-ppe-record-analysis.md +302 -0
- package/dist/registry/rules/integrity-and-test-ethics.md +275 -0
- package/dist/registry/rules/local-development.md +275 -0
- package/dist/registry/rules/mandatory-pre-completion-reflection.md +193 -0
- package/dist/registry/rules/merge-requirements.md +238 -0
- package/dist/registry/rules/simplicity.md +118 -0
- package/dist/registry/rules/software-development-lifecycle.md +105 -0
- package/dist/registry/rules/spike-first-development.md +205 -0
- package/dist/registry/rules/successful-debugging-patterns.md +488 -0
- package/dist/registry/scripts/build-scripts-generator.js +205 -0
- package/dist/registry/scripts/cleanup-branch.js +287 -0
- package/dist/registry/scripts/evaluate-code-quality.js +66 -0
- package/dist/registry/scripts/exec-with-timeout.js +142 -0
- package/dist/registry/scripts/fraim-config.js +61 -0
- package/dist/registry/scripts/generate-engagement-emails.js +705 -0
- package/dist/registry/scripts/generic-issues-api.js +100 -0
- package/dist/registry/scripts/newsletter-helpers.js +671 -0
- package/dist/registry/scripts/openapi-generator.js +664 -0
- package/dist/registry/scripts/performance/profile-server.js +390 -0
- package/dist/registry/scripts/profile-server.js +389 -0
- package/dist/registry/scripts/run-thank-you-workflow.js +92 -0
- package/dist/registry/scripts/send-newsletter-simple.js +85 -0
- package/dist/registry/scripts/send-thank-you-emails.js +54 -0
- package/dist/registry/scripts/validate-openapi-limits.js +311 -0
- package/dist/registry/scripts/validate-test-coverage.js +262 -0
- package/dist/registry/scripts/verify-test-coverage.js +66 -0
- package/dist/registry/stubs/workflows/azure/cost-optimization.md +11 -0
- package/dist/registry/stubs/workflows/bootstrap/create-architecture.md +11 -0
- package/dist/registry/stubs/workflows/bootstrap/detect-broken-windows.md +11 -0
- package/dist/registry/stubs/workflows/bootstrap/evaluate-code-quality.md +11 -0
- package/dist/registry/stubs/workflows/bootstrap/verify-test-coverage.md +11 -0
- package/dist/registry/stubs/workflows/brainstorming/blue-sky-brainstorming.md +11 -0
- package/dist/registry/stubs/workflows/brainstorming/codebase-brainstorming.md +11 -0
- package/dist/registry/stubs/workflows/business-development/create-business-plan.md +11 -0
- package/dist/registry/stubs/workflows/business-development/ideate-business-opportunity.md +11 -0
- package/dist/registry/stubs/workflows/business-development/price-product.md +18 -0
- package/dist/registry/stubs/workflows/compliance/detect-compliance-requirements.md +11 -0
- package/dist/registry/stubs/workflows/compliance/generate-audit-evidence.md +11 -0
- package/dist/registry/stubs/workflows/compliance/soc2-evidence-generator.md +11 -0
- package/dist/registry/stubs/workflows/customer-development/insight-analysis.md +11 -0
- package/dist/registry/stubs/workflows/customer-development/insight-triage.md +11 -0
- package/dist/registry/stubs/workflows/customer-development/interview-preparation.md +11 -0
- package/dist/registry/stubs/workflows/customer-development/linkedin-outreach.md +11 -0
- package/dist/registry/stubs/workflows/customer-development/strategic-brainstorming.md +11 -0
- package/dist/registry/stubs/workflows/customer-development/thank-customers.md +11 -0
- package/dist/registry/stubs/workflows/customer-development/user-survey-dispatch.md +11 -0
- package/dist/registry/stubs/workflows/customer-development/users-to-target.md +11 -0
- package/dist/registry/stubs/workflows/customer-development/weekly-newsletter.md +11 -0
- package/dist/registry/stubs/workflows/deploy/cloud-deployment.md +11 -0
- package/dist/registry/stubs/workflows/improve-fraim/contribute.md +11 -0
- package/dist/registry/stubs/workflows/improve-fraim/file-issue.md +11 -0
- package/dist/registry/stubs/workflows/learning/build-skillset.md +11 -0
- package/dist/registry/stubs/workflows/learning/synthesize-learnings.md +11 -0
- package/dist/registry/stubs/workflows/legal/contract-review-analysis.md +11 -0
- package/dist/registry/stubs/workflows/legal/nda.md +11 -0
- package/dist/registry/stubs/workflows/legal/patent-filing.md +11 -0
- package/dist/registry/stubs/workflows/legal/saas-contract-development.md +11 -0
- package/dist/registry/stubs/workflows/legal/trademark-filing.md +11 -0
- package/dist/registry/stubs/workflows/marketing/content-creation.md +11 -0
- package/dist/registry/stubs/workflows/marketing/convert-to-pdf.md +11 -0
- package/dist/registry/stubs/workflows/marketing/create-modern-website.md +11 -0
- package/dist/registry/stubs/workflows/marketing/domain-registration.md +11 -0
- package/dist/registry/stubs/workflows/marketing/evangelize.md +11 -0
- package/dist/registry/stubs/workflows/marketing/hbr-article.md +11 -0
- package/dist/registry/stubs/workflows/marketing/launch-checklist.md +11 -0
- package/dist/registry/stubs/workflows/marketing/marketing-strategy.md +11 -0
- package/dist/registry/stubs/workflows/marketing/storytelling.md +11 -0
- package/dist/registry/stubs/workflows/performance/analyze-performance.md +11 -0
- package/dist/registry/stubs/workflows/product-building/design.md +11 -0
- package/dist/registry/stubs/workflows/product-building/implement.md +11 -0
- package/dist/registry/stubs/workflows/product-building/iterate-on-pr-comments.md +11 -0
- package/dist/registry/stubs/workflows/product-building/prep-issue.md +11 -0
- package/dist/registry/stubs/workflows/product-building/prototype.md +11 -0
- package/dist/registry/stubs/workflows/product-building/resolve.md +11 -0
- package/dist/registry/stubs/workflows/product-building/retrospect.md +11 -0
- package/dist/registry/stubs/workflows/product-building/spec.md +11 -0
- package/dist/registry/stubs/workflows/product-building/test.md +11 -0
- package/dist/registry/stubs/workflows/productivity-report/productivity-report.md +11 -0
- package/dist/registry/stubs/workflows/quality-assurance/browser-validation.md +11 -0
- package/dist/registry/stubs/workflows/quality-assurance/iterative-improvement-cycle.md +11 -0
- package/dist/registry/stubs/workflows/replicate/replicate-discovery.md +11 -0
- package/dist/registry/stubs/workflows/replicate/replicate-to-issues.md +11 -0
- package/dist/registry/stubs/workflows/reviewer/review-implementation-vs-design-spec.md +11 -0
- package/dist/registry/stubs/workflows/reviewer/review-implementation-vs-feature-spec.md +11 -0
- package/dist/registry/stubs/workflows/startup-credits/aws-activate-application.md +11 -0
- package/dist/registry/stubs/workflows/startup-credits/google-cloud-application.md +11 -0
- package/dist/registry/stubs/workflows/startup-credits/microsoft-azure-application.md +11 -0
- package/dist/registry/templates/bootstrap/ARCHITECTURE-TEMPLATE.md +53 -0
- package/dist/registry/templates/bootstrap/CODE-QUALITY-REPORT-TEMPLATE.md +37 -0
- package/dist/registry/templates/bootstrap/TEST-COVERAGE-REPORT-TEMPLATE.md +35 -0
- package/dist/registry/templates/business-development/IDEATION-REPORT-TEMPLATE.md +29 -0
- package/dist/registry/templates/business-development/PRICING-STRATEGY-TEMPLATE.md +126 -0
- package/dist/registry/templates/customer-development/customer-interview-template.md +99 -0
- package/dist/registry/templates/customer-development/customer-persona-template.md +69 -0
- package/dist/registry/templates/customer-development/follow-up-email-templates.md +132 -0
- package/dist/registry/templates/customer-development/insight-analysis-template.md +74 -0
- package/dist/registry/templates/customer-development/prospect-inventory-template.csv +3 -0
- package/dist/registry/templates/customer-development/search-strategy-template.md +123 -0
- package/dist/registry/templates/customer-development/strategic-recommendations-template.md +53 -0
- package/dist/registry/templates/customer-development/thank-you-email-template.html +124 -0
- package/dist/registry/templates/customer-development/thank-you-note-template.md +16 -0
- package/dist/registry/templates/customer-development/triage-log-template.md +278 -0
- package/dist/registry/templates/customer-development/weekly-newsletter-template.html +204 -0
- package/dist/registry/templates/evidence/Design-Evidence.md +30 -0
- package/dist/registry/templates/evidence/Implementation-BugEvidence.md +122 -0
- package/dist/registry/templates/evidence/Implementation-FeatureEvidence.md +160 -0
- package/dist/registry/templates/evidence/Spec-Evidence.md +19 -0
- package/dist/registry/templates/help/HelpNeeded.md +14 -0
- package/dist/registry/templates/legal/NDA-TEMPLATE.md +170 -0
- package/dist/registry/templates/legal/PATENT-TEMPLATE.md +372 -0
- package/dist/registry/templates/legal/TRADEMARK-TEMPLATE.md +339 -0
- package/dist/registry/templates/legal/contract-review-checklist.md +193 -0
- package/dist/registry/templates/legal/review-report-template.md +198 -0
- package/dist/registry/templates/legal/saas-terms-template.md +174 -0
- package/dist/registry/templates/legal/sow-template.md +117 -0
- package/dist/registry/templates/legal/template-variables.md +131 -0
- package/dist/registry/templates/marketing/DOMAIN-REGISTRATION-TEMPLATE.md +194 -0
- package/dist/registry/templates/marketing/EVANGELIZE-TEMPLATE.md +102 -0
- package/dist/registry/templates/marketing/HBR-ARTICLE-TEMPLATE.md +66 -0
- package/dist/registry/templates/marketing/STORYTELLING-TEMPLATE.md +130 -0
- package/dist/registry/templates/marketing/WEBSITE-TEMPLATE.md +262 -0
- package/dist/registry/templates/marketing/github-pages-workflow.yml +64 -0
- package/dist/registry/templates/replicate/implementation-checklist.md +39 -0
- package/dist/registry/templates/replicate/use-cases-template.md +88 -0
- package/dist/registry/templates/retrospective/RETROSPECTIVE-TEMPLATE.md +55 -0
- package/dist/registry/templates/specs/BUGSPEC-TEMPLATE.md +37 -0
- package/dist/registry/templates/specs/FEATURESPEC-TEMPLATE.md +66 -0
- package/dist/registry/templates/specs/TECHSPEC-TEMPLATE.md +39 -0
- package/dist/registry/workflows/azure/cost-optimization.md +772 -0
- package/dist/registry/workflows/bootstrap/create-architecture.md +37 -0
- package/dist/registry/workflows/bootstrap/detect-broken-windows.md +300 -0
- package/dist/registry/workflows/bootstrap/evaluate-code-quality.md +35 -0
- package/dist/registry/workflows/bootstrap/verify-test-coverage.md +36 -0
- package/dist/registry/workflows/brainstorming/blue-sky-brainstorming.md +211 -0
- package/dist/registry/workflows/brainstorming/codebase-brainstorming.md +159 -0
- package/dist/registry/workflows/business-development/create-business-plan.md +737 -0
- package/dist/registry/workflows/business-development/ideate-business-opportunity.md +55 -0
- package/dist/registry/workflows/business-development/price-product.md +325 -0
- package/dist/registry/workflows/compliance/detect-compliance-requirements.md +80 -0
- package/dist/registry/workflows/compliance/generate-audit-evidence.md +80 -0
- package/dist/registry/workflows/compliance/soc2-evidence-generator.md +332 -0
- package/dist/registry/workflows/customer-development/insight-analysis.md +156 -0
- package/dist/registry/workflows/customer-development/insight-triage.md +933 -0
- package/dist/registry/workflows/customer-development/interview-preparation.md +452 -0
- package/dist/registry/workflows/customer-development/linkedin-outreach.md +599 -0
- package/dist/registry/workflows/customer-development/strategic-brainstorming.md +146 -0
- package/dist/registry/workflows/customer-development/thank-customers.md +203 -0
- package/dist/registry/workflows/customer-development/user-survey-dispatch.md +312 -0
- package/dist/registry/workflows/customer-development/users-to-target.md +427 -0
- package/dist/registry/workflows/customer-development/weekly-newsletter.md +366 -0
- package/dist/registry/workflows/deploy/cloud-deployment.md +310 -0
- package/dist/registry/workflows/improve-fraim/contribute.md +32 -0
- package/dist/registry/workflows/improve-fraim/file-issue.md +32 -0
- package/dist/registry/workflows/learning/build-skillset.md +212 -0
- package/dist/registry/workflows/learning/synthesize-learnings.md +369 -0
- package/dist/registry/workflows/legal/contract-review-analysis.md +382 -0
- package/dist/registry/workflows/legal/nda.md +69 -0
- package/dist/registry/workflows/legal/patent-filing.md +76 -0
- package/dist/registry/workflows/legal/saas-contract-development.md +204 -0
- package/dist/registry/workflows/legal/trademark-filing.md +77 -0
- package/dist/registry/workflows/marketing/content-creation.md +40 -0
- package/dist/registry/workflows/marketing/convert-to-pdf.md +265 -0
- package/dist/registry/workflows/marketing/create-modern-website.md +456 -0
- package/dist/registry/workflows/marketing/domain-registration.md +323 -0
- package/dist/registry/workflows/marketing/evangelize.md +426 -0
- package/dist/registry/workflows/marketing/hbr-article.md +73 -0
- package/dist/registry/workflows/marketing/launch-checklist.md +37 -0
- package/dist/registry/workflows/marketing/marketing-strategy.md +45 -0
- package/dist/registry/workflows/marketing/storytelling.md +65 -0
- package/dist/registry/workflows/performance/analyze-performance.md +65 -0
- package/dist/registry/workflows/product-building/design.md +263 -0
- package/dist/registry/workflows/product-building/implement.md +771 -0
- package/dist/registry/workflows/product-building/iterate-on-pr-comments.md +70 -0
- package/dist/registry/workflows/product-building/prep-issue.md +41 -0
- package/dist/registry/workflows/product-building/prototype.md +60 -0
- package/dist/registry/workflows/product-building/resolve.md +175 -0
- package/dist/registry/workflows/product-building/retrospect.md +86 -0
- package/dist/registry/workflows/product-building/spec.md +303 -0
- package/dist/registry/workflows/product-building/test.md +125 -0
- package/dist/registry/workflows/productivity-report/productivity-report.md +263 -0
- package/dist/registry/workflows/quality-assurance/browser-validation.md +221 -0
- package/dist/registry/workflows/quality-assurance/iterative-improvement-cycle.md +562 -0
- package/dist/registry/workflows/replicate/replicate-discovery.md +336 -0
- package/dist/registry/workflows/replicate/replicate-to-issues.md +319 -0
- package/dist/registry/workflows/reviewer/review-implementation-vs-design-spec.md +694 -0
- package/dist/registry/workflows/reviewer/review-implementation-vs-feature-spec.md +734 -0
- package/dist/registry/workflows/startup-credits/aws-activate-application.md +535 -0
- package/dist/registry/workflows/startup-credits/google-cloud-application.md +647 -0
- package/dist/registry/workflows/startup-credits/microsoft-azure-application.md +538 -0
- package/package.json +2 -1
package/dist/registry/ai-manager-rules/customer-development-phases/phase1-customer-profiling.md
ADDED
|
@@ -0,0 +1,101 @@
|
|
|
1
|
+
# Phase 1: Customer Profiling
|
|
2
|
+
|
|
3
|
+
## Objective
|
|
4
|
+
Define target customer characteristics and search criteria to guide systematic prospect discovery across multiple platforms.
|
|
5
|
+
|
|
6
|
+
## Key Questions to Ask
|
|
7
|
+
|
|
8
|
+
### Understanding the Business
|
|
9
|
+
1. "What specific problem does your product or service solve?"
|
|
10
|
+
2. "How do customers currently solve this problem without your solution?"
|
|
11
|
+
3. "What makes your solution different from existing alternatives?"
|
|
12
|
+
4. "What's the cost of not solving this problem for your customers?"
|
|
13
|
+
5. "How urgent is this problem for your target customers?"
|
|
14
|
+
|
|
15
|
+
### Defining the Target Customer
|
|
16
|
+
6. "Who experiences this problem most acutely in their daily work?"
|
|
17
|
+
7. "What job titles would typically have this problem?"
|
|
18
|
+
8. "What industries or sectors are most affected by this problem?"
|
|
19
|
+
9. "What size companies (startup, SMB, enterprise) are your ideal customers?"
|
|
20
|
+
10. "What geographic regions should we focus on?"
|
|
21
|
+
|
|
22
|
+
### Identifying Pain Points
|
|
23
|
+
11. "What specific symptoms or frustrations do customers experience?"
|
|
24
|
+
12. "What keywords or phrases would customers use to describe their problem?"
|
|
25
|
+
13. "How do customers currently search for solutions to this problem?"
|
|
26
|
+
14. "What triggers customers to actively seek a solution?"
|
|
27
|
+
15. "What objections or concerns do customers typically have?"
|
|
28
|
+
|
|
29
|
+
### Platform Behavior
|
|
30
|
+
16. "Where do your target customers spend time online professionally?"
|
|
31
|
+
17. "What communities, forums, or groups do they participate in?"
|
|
32
|
+
18. "What type of content do they share or engage with?"
|
|
33
|
+
19. "How do they prefer to be contacted or approached?"
|
|
34
|
+
20. "What social proof or credibility signals matter to them?"
|
|
35
|
+
|
|
36
|
+
## Validation Criteria
|
|
37
|
+
|
|
38
|
+
### Customer Persona Completeness
|
|
39
|
+
- [ ] Clear problem statement defined
|
|
40
|
+
- [ ] Target demographics specified (job titles, industries, company size)
|
|
41
|
+
- [ ] Pain points articulated with specific language customers use
|
|
42
|
+
- [ ] Geographic and market constraints identified
|
|
43
|
+
- [ ] Behavioral patterns and preferences documented
|
|
44
|
+
|
|
45
|
+
### Search Strategy Readiness
|
|
46
|
+
- [ ] Platform-specific keywords identified for each channel
|
|
47
|
+
- [ ] Search terms validated against how customers actually describe problems
|
|
48
|
+
- [ ] Qualification criteria established (scoring system 1-10)
|
|
49
|
+
- [ ] Success metrics defined (quantity and quality targets)
|
|
50
|
+
|
|
51
|
+
## Evidence Required
|
|
52
|
+
|
|
53
|
+
### Customer Persona Document
|
|
54
|
+
Create: `docs/customer-development/customer-persona-{timestamp}.md`
|
|
55
|
+
|
|
56
|
+
**Required Sections:**
|
|
57
|
+
- Problem statement and solution overview
|
|
58
|
+
- Target customer demographics
|
|
59
|
+
- Pain points and symptoms
|
|
60
|
+
- Search keywords by platform
|
|
61
|
+
- Qualification criteria
|
|
62
|
+
- Success metrics
|
|
63
|
+
|
|
64
|
+
### Search Strategy Document
|
|
65
|
+
Create: `docs/customer-development/search-strategy-{timestamp}.md`
|
|
66
|
+
|
|
67
|
+
**Required Sections:**
|
|
68
|
+
- Platform-specific search terms
|
|
69
|
+
- Qualification scoring rubric
|
|
70
|
+
- Target prospect quantities per platform
|
|
71
|
+
- Quality thresholds and filters
|
|
72
|
+
|
|
73
|
+
## Common Pitfalls
|
|
74
|
+
|
|
75
|
+
### Vague Problem Definition
|
|
76
|
+
- **Problem**: "We help businesses be more efficient"
|
|
77
|
+
- **Better**: "We help SaaS companies reduce customer churn by identifying at-risk accounts 30 days before they cancel"
|
|
78
|
+
|
|
79
|
+
### Too Broad Target Market
|
|
80
|
+
- **Problem**: "Anyone who uses software"
|
|
81
|
+
- **Better**: "VP of Customer Success at B2B SaaS companies with 50-500 employees and $10M+ ARR"
|
|
82
|
+
|
|
83
|
+
### Generic Pain Points
|
|
84
|
+
- **Problem**: "Customers want to save time and money"
|
|
85
|
+
- **Better**: "Customer Success teams spend 15+ hours per week manually analyzing usage data to identify churn risk, often missing early warning signs"
|
|
86
|
+
|
|
87
|
+
## Next Steps
|
|
88
|
+
|
|
89
|
+
Once validation criteria are met:
|
|
90
|
+
1. **Proceed to Phase 2**: Multi-Platform Discovery
|
|
91
|
+
2. **Use validated persona** to guide platform searches
|
|
92
|
+
3. **Apply qualification criteria** consistently across all prospects
|
|
93
|
+
4. **Track metrics** against defined success criteria
|
|
94
|
+
|
|
95
|
+
## Success Indicators
|
|
96
|
+
|
|
97
|
+
- Customer persona resonates with founder's deep understanding of the market
|
|
98
|
+
- Search keywords reflect actual language customers use
|
|
99
|
+
- Qualification criteria are specific and measurable
|
|
100
|
+
- Success metrics are realistic and achievable
|
|
101
|
+
- Founder feels confident about who they're looking for and where to find them
|
package/dist/registry/ai-manager-rules/customer-development-phases/phase2-platform-discovery.md
ADDED
|
@@ -0,0 +1,235 @@
|
|
|
1
|
+
# Phase 2: Multi-Platform Discovery
|
|
2
|
+
|
|
3
|
+
## Objective
|
|
4
|
+
Execute systematic prospect discovery across multiple platforms using browser automation while maintaining authentic, respectful engagement patterns.
|
|
5
|
+
|
|
6
|
+
## Platform-by-Platform Guidance
|
|
7
|
+
|
|
8
|
+
### LinkedIn Professional Network Search
|
|
9
|
+
|
|
10
|
+
#### Authentication Check
|
|
11
|
+
Before starting LinkedIn search:
|
|
12
|
+
1. Use `mcp_playwright_browser_navigate` to open LinkedIn
|
|
13
|
+
2. Take `mcp_playwright_browser_snapshot` to check authentication status
|
|
14
|
+
3. **If login form visible**: Prompt user "Please log into LinkedIn in the browser window. Type 'ready' when logged in"
|
|
15
|
+
4. **If authenticated**: Proceed with search
|
|
16
|
+
|
|
17
|
+
#### Search Strategy
|
|
18
|
+
1. **Advanced People Search**:
|
|
19
|
+
- Navigate to LinkedIn's advanced search
|
|
20
|
+
- Apply filters: Job titles, industries, company size, location
|
|
21
|
+
- Use keywords from Phase 1 persona development
|
|
22
|
+
|
|
23
|
+
2. **Prospect Evaluation**:
|
|
24
|
+
- Use `mcp_playwright_browser_click` to open individual profiles
|
|
25
|
+
- Look for pain point indicators in recent posts/activity
|
|
26
|
+
- Check for authority signals (job title, company, connections)
|
|
27
|
+
- Take `mcp_playwright_browser_take_screenshot` for evidence
|
|
28
|
+
|
|
29
|
+
3. **Data Extraction**:
|
|
30
|
+
- Name, headline, company, location
|
|
31
|
+
- Profile URL for follow-up
|
|
32
|
+
- Recent activity that indicates pain points
|
|
33
|
+
- Connection level (1st, 2nd, 3rd degree)
|
|
34
|
+
|
|
35
|
+
### Reddit Community Discussions
|
|
36
|
+
|
|
37
|
+
#### Authentication Check
|
|
38
|
+
1. Navigate to Reddit with `mcp_playwright_browser_navigate`
|
|
39
|
+
2. Check login status with `mcp_playwright_browser_snapshot`
|
|
40
|
+
3. **If not logged in**: "Please log into Reddit for better search access. Type 'ready' to continue"
|
|
41
|
+
|
|
42
|
+
#### Search Process
|
|
43
|
+
1. **Subreddit Identification**:
|
|
44
|
+
- Navigate to relevant subreddits based on target customer industries
|
|
45
|
+
- Examples: r/entrepreneur, r/startups, r/sysadmin, r/marketing
|
|
46
|
+
|
|
47
|
+
2. **Keyword Search**:
|
|
48
|
+
- Search for posts containing pain point keywords
|
|
49
|
+
- Look for complaint posts, help requests, tool recommendations
|
|
50
|
+
|
|
51
|
+
3. **User Identification**:
|
|
52
|
+
- Click on usernames of people expressing relevant pain points
|
|
53
|
+
- Check their post history for consistency and authority
|
|
54
|
+
- Extract: Username, post context, pain point expressions
|
|
55
|
+
|
|
56
|
+
### X (Twitter) Conversations
|
|
57
|
+
|
|
58
|
+
#### Authentication Check
|
|
59
|
+
1. Navigate to X with `mcp_playwright_browser_navigate`
|
|
60
|
+
2. Check authentication with `mcp_playwright_browser_snapshot`
|
|
61
|
+
3. **If not authenticated**: "Please log into X (Twitter) for full search capabilities. Type 'ready' when ready"
|
|
62
|
+
|
|
63
|
+
#### Search Strategy
|
|
64
|
+
1. **Advanced Search**:
|
|
65
|
+
- Use Twitter's advanced search for pain point keywords
|
|
66
|
+
- Filter by recent tweets, location, language
|
|
67
|
+
- Look for complaint tweets, help requests, tool discussions
|
|
68
|
+
|
|
69
|
+
2. **User Analysis**:
|
|
70
|
+
- Click on profiles of users expressing relevant problems
|
|
71
|
+
- Check bio for job title, company, authority indicators
|
|
72
|
+
- Review recent tweets for consistency and engagement level
|
|
73
|
+
|
|
74
|
+
### Facebook Groups and Discussions
|
|
75
|
+
|
|
76
|
+
#### Authentication Check
|
|
77
|
+
1. Navigate to Facebook with `mcp_playwright_browser_navigate`
|
|
78
|
+
2. Handle Facebook authentication if required
|
|
79
|
+
3. **If not logged in**: "Please log into Facebook to access groups. Type 'ready' when authenticated"
|
|
80
|
+
|
|
81
|
+
#### Group Search
|
|
82
|
+
1. **Relevant Group Identification**:
|
|
83
|
+
- Search for groups related to target customer industries
|
|
84
|
+
- Join relevant groups if not already a member
|
|
85
|
+
|
|
86
|
+
2. **Discussion Analysis**:
|
|
87
|
+
- Search group posts for pain point keywords
|
|
88
|
+
- Identify active members discussing relevant challenges
|
|
89
|
+
- Note group context and member engagement levels
|
|
90
|
+
|
|
91
|
+
### Industry Forum Search
|
|
92
|
+
|
|
93
|
+
#### Custom Forum Navigation
|
|
94
|
+
1. **Ask User for Specific Forums**:
|
|
95
|
+
- "Are there specific industry forums your customers use? Please provide URLs"
|
|
96
|
+
- Common examples: Stack Overflow, Hacker News, industry-specific forums
|
|
97
|
+
|
|
98
|
+
2. **Forum-Specific Search**:
|
|
99
|
+
- Navigate to each provided forum
|
|
100
|
+
- Use forum search functionality for pain point keywords
|
|
101
|
+
- Identify active users with relevant expertise and problems
|
|
102
|
+
|
|
103
|
+
### General Web Search
|
|
104
|
+
|
|
105
|
+
#### Search Strategy
|
|
106
|
+
1. **Targeted Google Searches**:
|
|
107
|
+
- "[pain point keywords] + blog"
|
|
108
|
+
- "[industry] + challenges + [year]"
|
|
109
|
+
- "problems with [current solutions]"
|
|
110
|
+
|
|
111
|
+
2. **Content Analysis**:
|
|
112
|
+
- Navigate to relevant blog posts and articles
|
|
113
|
+
- Identify authors expressing target pain points
|
|
114
|
+
- Check for contact information and social media profiles
|
|
115
|
+
|
|
116
|
+
## Browser Automation Best Practices
|
|
117
|
+
|
|
118
|
+
### Respectful Automation
|
|
119
|
+
- Use realistic delays between actions (1-3 seconds)
|
|
120
|
+
- Scroll pages naturally to load content
|
|
121
|
+
- Don't overwhelm platforms with rapid requests
|
|
122
|
+
- Respect rate limits and platform terms of service
|
|
123
|
+
|
|
124
|
+
### Error Handling
|
|
125
|
+
|
|
126
|
+
#### Authentication Failures
|
|
127
|
+
- **Issue**: User not logged into platform
|
|
128
|
+
- **Action**: Prompt user to log in manually, wait for confirmation
|
|
129
|
+
- **Recovery**: Verify authentication before proceeding
|
|
130
|
+
|
|
131
|
+
#### Rate Limiting
|
|
132
|
+
- **Issue**: Platform blocks or limits requests
|
|
133
|
+
- **Action**: Implement longer delays, reduce request frequency
|
|
134
|
+
- **Recovery**: Continue with other platforms, return later
|
|
135
|
+
|
|
136
|
+
#### Technical Issues
|
|
137
|
+
- **Issue**: Page load failures, element not found
|
|
138
|
+
- **Action**: Log error, take screenshot for debugging
|
|
139
|
+
- **Recovery**: Skip problematic prospect, continue with others
|
|
140
|
+
|
|
141
|
+
## Data Collection Standards
|
|
142
|
+
|
|
143
|
+
### Required Data Points
|
|
144
|
+
For each prospect discovered:
|
|
145
|
+
- **Name**: Full name from profile
|
|
146
|
+
- **Platform**: Where they were found
|
|
147
|
+
- **Profile URL**: Direct link for follow-up
|
|
148
|
+
- **Contact Info**: Email, LinkedIn, Twitter handle (if available)
|
|
149
|
+
- **Pain Points**: Specific quotes or context showing relevant problems
|
|
150
|
+
- **Authority Indicators**: Job title, company, follower count, engagement
|
|
151
|
+
- **Discovery Context**: Post, comment, or profile section where pain point was identified
|
|
152
|
+
|
|
153
|
+
### Evidence Documentation
|
|
154
|
+
- **Screenshots**: Save evidence of pain point expressions
|
|
155
|
+
- **URLs**: Record exact links to posts, profiles, discussions
|
|
156
|
+
- **Timestamps**: Note when prospect was discovered
|
|
157
|
+
- **Search Terms**: Document which keywords led to discovery
|
|
158
|
+
|
|
159
|
+
## Quality Assurance
|
|
160
|
+
|
|
161
|
+
### Prospect Validation
|
|
162
|
+
Before adding to final list:
|
|
163
|
+
- [ ] Pain point clearly matches target customer profile
|
|
164
|
+
- [ ] Authority/influence indicators present
|
|
165
|
+
- [ ] Contact information available or obtainable
|
|
166
|
+
- [ ] Recent activity shows engagement and authenticity
|
|
167
|
+
- [ ] No obvious spam or fake accounts
|
|
168
|
+
|
|
169
|
+
### Data Accuracy
|
|
170
|
+
- [ ] All required fields populated
|
|
171
|
+
- [ ] URLs are valid and accessible
|
|
172
|
+
- [ ] Contact information formatted correctly
|
|
173
|
+
- [ ] Pain point quotes are accurate and in context
|
|
174
|
+
- [ ] Screenshots saved for verification
|
|
175
|
+
|
|
176
|
+
## Success Metrics
|
|
177
|
+
|
|
178
|
+
### Quantity Targets
|
|
179
|
+
- **LinkedIn**: 30-50 qualified prospects
|
|
180
|
+
- **Reddit**: 20-30 prospects from relevant discussions
|
|
181
|
+
- **X (Twitter)**: 15-25 prospects from recent conversations
|
|
182
|
+
- **Facebook**: 10-20 prospects from group discussions
|
|
183
|
+
- **Forums**: 10-15 prospects from industry-specific forums
|
|
184
|
+
- **Web Search**: 5-10 prospects from blog/article authors
|
|
185
|
+
|
|
186
|
+
### Quality Indicators
|
|
187
|
+
- 70%+ of prospects have clear pain point expressions
|
|
188
|
+
- 60%+ have identifiable contact information
|
|
189
|
+
- 80%+ have authority indicators (job title, company, influence)
|
|
190
|
+
- 90%+ are recent/active (posted within last 6 months)
|
|
191
|
+
|
|
192
|
+
## Common Pitfalls
|
|
193
|
+
|
|
194
|
+
### Over-Automation
|
|
195
|
+
- **Problem**: Moving too fast, triggering platform defenses
|
|
196
|
+
- **Solution**: Use human-like delays, respect platform limits
|
|
197
|
+
|
|
198
|
+
### Poor Qualification
|
|
199
|
+
- **Problem**: Adding prospects without clear pain point match
|
|
200
|
+
- **Solution**: Stick to qualification criteria from Phase 1
|
|
201
|
+
|
|
202
|
+
### Incomplete Data
|
|
203
|
+
- **Problem**: Missing contact information or context
|
|
204
|
+
- **Solution**: Don't add prospects without sufficient information for follow-up
|
|
205
|
+
|
|
206
|
+
## Evidence Required
|
|
207
|
+
|
|
208
|
+
### Platform Search Results
|
|
209
|
+
Create: `docs/customer-development/platform-search-results-{timestamp}.md`
|
|
210
|
+
|
|
211
|
+
**Required Documentation:**
|
|
212
|
+
- Search terms used per platform
|
|
213
|
+
- Number of prospects found per platform
|
|
214
|
+
- Quality assessment of search results
|
|
215
|
+
- Screenshots of key findings
|
|
216
|
+
- Platform-specific insights and patterns
|
|
217
|
+
|
|
218
|
+
### Raw Prospect Data
|
|
219
|
+
Create: `docs/customer-development/raw-prospects-{timestamp}.csv`
|
|
220
|
+
|
|
221
|
+
**Required Columns:**
|
|
222
|
+
- Name, Platform, Profile URL, Contact Info
|
|
223
|
+
- Pain Points (specific quotes)
|
|
224
|
+
- Authority Indicators
|
|
225
|
+
- Discovery Context
|
|
226
|
+
- Date Found
|
|
227
|
+
- Search Terms Used
|
|
228
|
+
|
|
229
|
+
## Next Steps
|
|
230
|
+
|
|
231
|
+
Once platform discovery is complete:
|
|
232
|
+
1. **Proceed to Phase 3**: Prospect Qualification
|
|
233
|
+
2. **Apply systematic scoring** to all discovered prospects
|
|
234
|
+
3. **Prioritize prospects** based on qualification criteria
|
|
235
|
+
4. **Prepare for outreach** with documented context and pain points
|
package/dist/registry/ai-manager-rules/customer-development-phases/phase3-prospect-qualification.md
ADDED
|
@@ -0,0 +1,243 @@
|
|
|
1
|
+
# Phase 3: Prospect Qualification
|
|
2
|
+
|
|
3
|
+
## Objective
|
|
4
|
+
Systematically evaluate and score all discovered prospects using consistent criteria to prioritize outreach efforts and maximize conversion potential.
|
|
5
|
+
|
|
6
|
+
## Scoring System (1-10 Scale)
|
|
7
|
+
|
|
8
|
+
### Pain Point Match (Weight: 25%)
|
|
9
|
+
**Evaluates how well the prospect's expressed problems align with your solution**
|
|
10
|
+
|
|
11
|
+
- **10**: Explicitly mentions the exact problem your product solves, uses your target keywords
|
|
12
|
+
- **9**: Describes symptoms that directly indicate your target problem
|
|
13
|
+
- **8**: Discusses related problems that your solution addresses
|
|
14
|
+
- **7**: Works in target role/industry but pain points are implied rather than explicit
|
|
15
|
+
- **6**: General frustrations that could be related to your solution
|
|
16
|
+
- **5**: Tangentially related challenges in their domain
|
|
17
|
+
- **4**: Works in relevant industry but no clear pain point identified
|
|
18
|
+
- **3**: Weak connection to target problem
|
|
19
|
+
- **2**: Minimal relevance to your solution
|
|
20
|
+
- **1**: No identifiable pain point match
|
|
21
|
+
|
|
22
|
+
### Authority/Influence (Weight: 25%)
|
|
23
|
+
**Assesses the prospect's ability to make or influence purchasing decisions**
|
|
24
|
+
|
|
25
|
+
- **10**: C-level executive (CEO, CTO, CMO) with clear budget authority
|
|
26
|
+
- **9**: VP level with department budget responsibility
|
|
27
|
+
- **8**: Director level with team budget influence
|
|
28
|
+
- **7**: Senior Manager with project budget input
|
|
29
|
+
- **6**: Manager with some purchasing influence
|
|
30
|
+
- **5**: Team Lead with technical input on tool selection
|
|
31
|
+
- **4**: Senior Individual Contributor with expertise influence
|
|
32
|
+
- **3**: Mid-level IC with some team influence
|
|
33
|
+
- **2**: Junior level with limited influence
|
|
34
|
+
- **1**: Entry level or unclear authority
|
|
35
|
+
|
|
36
|
+
### Urgency (Weight: 20%)
|
|
37
|
+
**Measures how actively the prospect is seeking solutions**
|
|
38
|
+
|
|
39
|
+
- **10**: Actively seeking solutions, mentions specific timeline or budget
|
|
40
|
+
- **9**: Frequently posts about the problem, shows clear frustration
|
|
41
|
+
- **8**: Recently started discussing the problem more often
|
|
42
|
+
- **7**: Regularly mentions challenges but no urgency indicators
|
|
43
|
+
- **6**: Occasionally discusses the problem
|
|
44
|
+
- **5**: Aware of the problem but not actively seeking solutions
|
|
45
|
+
- **4**: Problem exists but low priority
|
|
46
|
+
- **3**: Mentions problem infrequently
|
|
47
|
+
- **2**: Problem acknowledged but no action indicators
|
|
48
|
+
- **1**: No urgency signals detected
|
|
49
|
+
|
|
50
|
+
### Accessibility (Weight: 15%)
|
|
51
|
+
**Evaluates how easily you can reach and engage with the prospect**
|
|
52
|
+
|
|
53
|
+
- **10**: Direct email address or contact form available
|
|
54
|
+
- **9**: Active on LinkedIn with open messaging
|
|
55
|
+
- **8**: Mutual connections available for warm introduction
|
|
56
|
+
- **7**: Active on social media, responds to comments/mentions
|
|
57
|
+
- **6**: Public profile with some contact options
|
|
58
|
+
- **5**: Moderately active online, limited contact options
|
|
59
|
+
- **4**: Low online activity but reachable through platform messaging
|
|
60
|
+
- **3**: Private profiles but some engagement possible
|
|
61
|
+
- **2**: Very limited contact options
|
|
62
|
+
- **1**: No clear way to reach them
|
|
63
|
+
|
|
64
|
+
### Engagement Level (Weight: 15%)
|
|
65
|
+
**Assesses how active and responsive the prospect is online**
|
|
66
|
+
|
|
67
|
+
- **10**: Highly active, frequently posts and engages with others
|
|
68
|
+
- **9**: Regular posting and commenting, builds community
|
|
69
|
+
- **8**: Consistent activity, responds to others regularly
|
|
70
|
+
- **7**: Moderate activity, occasional engagement
|
|
71
|
+
- **6**: Posts regularly but limited interaction with others
|
|
72
|
+
- **5**: Sporadic activity, mostly consumption
|
|
73
|
+
- **4**: Low activity, occasional posts
|
|
74
|
+
- **3**: Minimal activity, mostly lurker behavior
|
|
75
|
+
- **2**: Very infrequent activity
|
|
76
|
+
- **1**: Inactive or dormant accounts
|
|
77
|
+
|
|
78
|
+
## Qualification Tiers
|
|
79
|
+
|
|
80
|
+
### Tier 1: High Priority (Score 35-50)
|
|
81
|
+
**Immediate Outreach Candidates**
|
|
82
|
+
- Strong pain point match (7+ score)
|
|
83
|
+
- High authority (7+ score) OR high urgency (8+ score)
|
|
84
|
+
- Accessible for outreach (6+ score)
|
|
85
|
+
|
|
86
|
+
**Recommended Actions:**
|
|
87
|
+
- Prioritize for immediate personalized outreach
|
|
88
|
+
- Craft highly customized messages referencing specific pain points
|
|
89
|
+
- Use warm introductions when available
|
|
90
|
+
- Follow up within 1 week if no response
|
|
91
|
+
|
|
92
|
+
### Tier 2: Medium Priority (Score 25-34)
|
|
93
|
+
**Nurture and Monitor**
|
|
94
|
+
- Good pain point match but missing authority or urgency
|
|
95
|
+
- High authority but unclear pain point urgency
|
|
96
|
+
- Accessible but need more qualification
|
|
97
|
+
|
|
98
|
+
**Recommended Actions:**
|
|
99
|
+
- Add to nurture campaign with relevant content
|
|
100
|
+
- Monitor for increased urgency signals
|
|
101
|
+
- Engage with their content to build familiarity
|
|
102
|
+
- Reach out when timing improves
|
|
103
|
+
|
|
104
|
+
### Tier 3: Low Priority (Score 15-24)
|
|
105
|
+
**Long-term Prospects**
|
|
106
|
+
- Weak pain point match or low authority
|
|
107
|
+
- Limited accessibility or engagement
|
|
108
|
+
- May become relevant in future
|
|
109
|
+
|
|
110
|
+
**Recommended Actions:**
|
|
111
|
+
- Add to long-term monitoring list
|
|
112
|
+
- Engage occasionally with their content
|
|
113
|
+
- Re-evaluate quarterly for status changes
|
|
114
|
+
- Consider for broader marketing campaigns
|
|
115
|
+
|
|
116
|
+
### Disqualified (Score <15)
|
|
117
|
+
**Not Worth Pursuing**
|
|
118
|
+
- Poor fit for target customer profile
|
|
119
|
+
- No clear pain point or authority
|
|
120
|
+
- Inaccessible or inactive
|
|
121
|
+
|
|
122
|
+
**Recommended Actions:**
|
|
123
|
+
- Remove from active prospect list
|
|
124
|
+
- Archive for potential future relevance
|
|
125
|
+
- Use data for persona refinement
|
|
126
|
+
|
|
127
|
+
## Qualification Process
|
|
128
|
+
|
|
129
|
+
### Step 1: Data Review
|
|
130
|
+
For each prospect from Phase 2:
|
|
131
|
+
1. **Review Discovery Context**: Re-read the post, comment, or profile section where they were found
|
|
132
|
+
2. **Analyze Pain Point Expression**: Look for specific language, urgency indicators, frustration levels
|
|
133
|
+
3. **Assess Authority Indicators**: Job title, company size, team size, budget responsibility clues
|
|
134
|
+
4. **Check Accessibility**: Available contact methods, social media activity, mutual connections
|
|
135
|
+
|
|
136
|
+
### Step 2: Scoring
|
|
137
|
+
1. **Score Each Criterion**: Use the 1-10 scale for all five criteria
|
|
138
|
+
2. **Calculate Weighted Score**:
|
|
139
|
+
- Pain Point Match × 0.25
|
|
140
|
+
- Authority/Influence × 0.25
|
|
141
|
+
- Urgency × 0.20
|
|
142
|
+
- Accessibility × 0.15
|
|
143
|
+
- Engagement Level × 0.15
|
|
144
|
+
3. **Assign Tier**: Based on total weighted score
|
|
145
|
+
4. **Document Rationale**: Note specific reasons for each score
|
|
146
|
+
|
|
147
|
+
### Step 3: Prioritization
|
|
148
|
+
1. **Rank Within Tiers**: Order prospects by total score within each tier
|
|
149
|
+
2. **Consider Strategic Factors**:
|
|
150
|
+
- Industry diversity
|
|
151
|
+
- Geographic distribution
|
|
152
|
+
- Company size mix
|
|
153
|
+
- Timing considerations
|
|
154
|
+
3. **Create Action Plan**: Specific next steps for each tier
|
|
155
|
+
|
|
156
|
+
## Common Pitfalls
|
|
157
|
+
|
|
158
|
+
### Over-Qualification
|
|
159
|
+
- **Problem**: Setting standards too high, eliminating good prospects
|
|
160
|
+
- **Solution**: Remember that 25+ score prospects are worth nurturing
|
|
161
|
+
- **Example**: Don't dismiss a VP (authority 8) just because pain point is implied (6) rather than explicit
|
|
162
|
+
|
|
163
|
+
### Under-Qualification
|
|
164
|
+
- **Problem**: Including prospects with poor fit to hit quantity targets
|
|
165
|
+
- **Solution**: Maintain minimum standards, quality over quantity
|
|
166
|
+
- **Example**: Don't include prospects with <15 total score just to reach target numbers
|
|
167
|
+
|
|
168
|
+
### Scoring Bias
|
|
169
|
+
- **Problem**: Favoring prospects from certain platforms or with specific characteristics
|
|
170
|
+
- **Solution**: Apply criteria consistently regardless of source platform
|
|
171
|
+
- **Example**: Don't automatically score LinkedIn prospects higher than Reddit prospects
|
|
172
|
+
|
|
173
|
+
### Incomplete Assessment
|
|
174
|
+
- **Problem**: Scoring without sufficient information
|
|
175
|
+
- **Solution**: Gather more data or mark as "insufficient information"
|
|
176
|
+
- **Example**: Don't guess at authority level without clear job title/company information
|
|
177
|
+
|
|
178
|
+
## Evidence Required
|
|
179
|
+
|
|
180
|
+
### Qualified Prospect Database
|
|
181
|
+
Create: `docs/customer-development/qualified-prospects-{timestamp}.csv`
|
|
182
|
+
|
|
183
|
+
**Required Columns:**
|
|
184
|
+
- Name, Platform Found, Profile URL
|
|
185
|
+
- Pain Point Match Score (1-10) + Rationale
|
|
186
|
+
- Authority/Influence Score (1-10) + Rationale
|
|
187
|
+
- Urgency Score (1-10) + Rationale
|
|
188
|
+
- Accessibility Score (1-10) + Rationale
|
|
189
|
+
- Engagement Level Score (1-10) + Rationale
|
|
190
|
+
- Total Weighted Score
|
|
191
|
+
- Qualification Tier (1, 2, 3, or Disqualified)
|
|
192
|
+
- Recommended Action
|
|
193
|
+
- Priority Rank within Tier
|
|
194
|
+
|
|
195
|
+
### Qualification Summary Report
|
|
196
|
+
Create: `docs/customer-development/qualification-summary-{timestamp}.md`
|
|
197
|
+
|
|
198
|
+
**Required Sections:**
|
|
199
|
+
- Total prospects evaluated
|
|
200
|
+
- Distribution across qualification tiers
|
|
201
|
+
- Average scores by criteria
|
|
202
|
+
- Top 20 prospects with detailed rationale
|
|
203
|
+
- Platform performance analysis
|
|
204
|
+
- Qualification insights and patterns
|
|
205
|
+
|
|
206
|
+
## Quality Assurance Checklist
|
|
207
|
+
|
|
208
|
+
### Scoring Consistency
|
|
209
|
+
- [ ] All prospects scored using same criteria
|
|
210
|
+
- [ ] Scores reflect actual evidence, not assumptions
|
|
211
|
+
- [ ] Rationale documented for scores 8+ and 2-
|
|
212
|
+
- [ ] Weighted calculations are correct
|
|
213
|
+
- [ ] Tier assignments match score ranges
|
|
214
|
+
|
|
215
|
+
### Data Completeness
|
|
216
|
+
- [ ] All required fields populated
|
|
217
|
+
- [ ] Contact information verified where available
|
|
218
|
+
- [ ] Pain point quotes are accurate and contextual
|
|
219
|
+
- [ ] Discovery context provides sufficient detail for outreach
|
|
220
|
+
- [ ] Priority rankings are logical and defensible
|
|
221
|
+
|
|
222
|
+
## Success Metrics
|
|
223
|
+
|
|
224
|
+
### Qualification Targets
|
|
225
|
+
- **Tier 1 (High Priority)**: 15-25 prospects
|
|
226
|
+
- **Tier 2 (Medium Priority)**: 25-40 prospects
|
|
227
|
+
- **Tier 3 (Low Priority)**: 15-30 prospects
|
|
228
|
+
- **Total Qualified**: 50-95 prospects (from 100-200 discovered)
|
|
229
|
+
|
|
230
|
+
### Quality Indicators
|
|
231
|
+
- Average pain point match score: 6.5+
|
|
232
|
+
- Average authority score: 6.0+
|
|
233
|
+
- 70%+ of Tier 1 prospects have contact information
|
|
234
|
+
- 80%+ of Tier 1 prospects have explicit pain point expressions
|
|
235
|
+
- Qualification rationale is clear and defensible for all Tier 1 prospects
|
|
236
|
+
|
|
237
|
+
## Next Steps
|
|
238
|
+
|
|
239
|
+
Once qualification is complete:
|
|
240
|
+
1. **Proceed to Phase 4**: Inventory Compilation
|
|
241
|
+
2. **Create final prospect database** with outreach recommendations
|
|
242
|
+
3. **Develop tier-specific outreach strategies**
|
|
243
|
+
4. **Prepare personalized messaging** for Tier 1 prospects
|