amazon-bestseller-launch▌
breverdbidder/life-os · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Execute the proven 5-phase framework for achieving Amazon #1 Bestseller status.
Amazon #1 Bestseller Launch System
Execute the proven 5-phase framework for achieving Amazon #1 Bestseller status.
Success Metrics That Drive #1 Rankings
Amazon's A10 algorithm ranks books based on:
| Metric | Weight | Target for #1 |
|---|---|---|
| Sales Velocity | 40% | 50-200+ sales in 24-48 hours |
| Conversion Rate | 25% | >15% page visitors → buyers |
| Reviews | 20% | 25+ reviews in first 30 days |
| Read-Through | 10% | >70% Kindle Unlimited pages read |
| Keywords/Categories | 5% | Rank top 3 in 3+ categories |
Phase 1: Pre-Launch Foundation (T-90 to T-30 days)
Category Selection Strategy
Select 3 categories using the "Low Competition, High Demand" formula:
CATEGORY_SCORE = (Monthly_Sales / #Books_in_Category) × Avg_Review_Count
Target: CATEGORY_SCORE > 500
Winning Category Criteria:
- #1 book has <50 reviews (beatable)
- Top 10 average <1,000 BSR (active buyers)
- At least 3 books selling 300+/month (proven demand)
7-Keyword Optimization
Amazon allows 7 backend keywords (50 chars each). Optimize using:
PRIMARY: [main topic] + [audience] + [benefit]
SECONDARY: [problem] + [solution] + [format]
LONG-TAIL: [specific niche] + [unique angle]
Keyword Research Tools:
- Publisher Rocket ($97 one-time)
- KDP Rocket alternatives: Helium 10, Jungle Scout
Listing Optimization Checklist
□ Title: Primary keyword + benefit (≤200 chars)
□ Subtitle: Secondary keywords + specific outcome
□ Description: 4,000 chars, HTML formatting, 3 CTAs
□ Author Bio: Credibility + related books + social proof
□ A+ Content: 5 modules minimum (if Brand Registered)
□ Editorial Reviews: 3-5 pre-launch endorsements
Phase 2: ARC Campaign (T-60 to T-14 days)
ARC (Advance Review Copy) System
Target: 50 ARC readers → 25+ reviews by launch day
ARC Recruitment Sources:
- Email list (highest conversion: 40-60%)
- BookFunnel/StoryOrigin (10-20% conversion)
- Goodreads groups (5-10% conversion)
- Facebook reader groups (5-15% conversion)
- NetGalley ($450/listing, professional reviewers)
ARC Email Sequence
Email 1 (T-60): Announce book, recruit reviewers
Email 2 (T-45): Send ARC via BookFunnel
Email 3 (T-30): Check-in, ask for feedback
Email 4 (T-14): Reminder to prepare review
Email 5 (T-1): "Review goes live tomorrow!"
Email 6 (Launch): Direct link to leave review
Review Velocity Target
| Day | Cumulative Reviews | BSR Impact |
|---|---|---|
| 1 | 5-10 | Enter top 10,000 |
| 7 | 15-20 | Enter top 1,000 |
| 14 | 20-25 | Stabilize ranking |
| 30 | 25-50 | Long-term visibility |
Phase 3: Pre-Launch Momentum (T-14 to T-1 days)
Price Strategy for Launch
| Phase | eBook Price | Goal |
|---|---|---|
| Pre-order | $0.99 | Maximize pre-orders |
| Launch (Day 1-3) | $0.99 | Sales velocity |
| Post-launch (Day 4-7) | $2.99 | Revenue + ranking |
| Steady state | $4.99-9.99 | Profit margin |
Pre-Order Stacking
Pre-orders count as Day 1 sales. Strategy:
- Open pre-orders 90 days before launch (max allowed)
- Stack all pre-order sales for launch day impact
- Coordinate with email list for pre-order push T-7
Launch Team Assembly
Minimum viable launch team:
- 50 email subscribers committed to buy Day 1
- 25 ARC reviewers ready to post reviews
- 10 social media amplifiers (shares/posts)
- 5 podcast/blog appearances scheduled
Phase 4: Launch Day Execution (T-0)
Hour-by-Hour Launch Protocol
6:00 AM EST - Verify listing is live, price correct
7:00 AM - Email blast #1 to full list
8:00 AM - Social media announcement (all platforms)
10:00 AM - Notify ARC team: "POST REVIEWS NOW"
12:00 PM - Email blast #2 (non-openers)
2:00 PM - Check BSR, adjust if needed
4:00 PM - Social media push #2
6:00 PM - Email blast #3 (last chance $0.99)
9:00 PM - Track final Day 1 metrics
Sales Velocity Targets
| Category Competitiveness | Day 1 Sales Needed |
|---|---|
| Low (<1,000 books) | 25-50 |
| Medium (1,000-10,000) | 50-100 |
| High (10,000+) | 100-200+ |
Real-Time Monitoring
Track every 2 hours on launch day:
# Key metrics to monitor
metrics = {
"bsr": "Best Seller Rank (lower = better)",
"category_rank": "Position in chosen categories",
"review_count": "Total reviews posted",
"review_avg": "Average star rating",
"also_bought": "Appearing in 'also bought' carousels"
}
Phase 5: Post-Launch Optimization (T+1 to T+30)
Week 1: Maintain Momentum
□ Day 2-3: Continue $0.99 pricing
□ Day 3: Raise to $2.99 if BSR stable
□ Day 4-7: Amazon Ads campaign (ACoS target <50%)
□ Daily: Monitor reviews, respond to questions
Amazon Ads Strategy
Sponsored Products Campaign Setup:
Campaign Type: Manual targeting
Daily Budget: $20-50
Bid Strategy: Dynamic bids (down only)
Keywords: 50-100 from research
Match Types: Exact (60%), Phrase (30%), Broad (10%)
Target ACoS by Phase:
| Phase | Target ACoS | Goal |
|---|---|---|
| Launch (Week 1) | 100%+ OK | Visibility |
| Growth (Week 2-4) | 50-70% | Ranking |
| Profit (Month 2+) | 30-50% | Sustainable |
KDP Select Strategy
Enroll in KDP Select for 90-day exclusivity benefits:
- Kindle Unlimited: Earn per page read (KENP)
- Kindle Countdown Deals: 7-day promo pricing
- Free Book Promotion: 5 free days per 90-day period
Countdown Deal Timing:
- Schedule for T+21 (post-launch dip)
- Promote 48-hour $0.99 deal
- Stack with email + social push
Quick Reference: #1 Bestseller Checklist
PRE-LAUNCH (T-90 to T-0)
□ Category research: 3 low-competition categories selected
□ Keywords: 7 backend keywords optimized
□ Listing: Title, description, A+ content complete
□ ARC campaign: 50 readers recruited, ARCs distributed
□ Launch team: 50+ committed Day 1 buyers
□ Pre-orders: Open and promoted
□ Price: Set to $0.99 for launch
LAUNCH DAY (T-0)
□ Email sequence: 3 blasts scheduled
□ Social media: Posts scheduled all platforms
□ ARC team: Notified to post reviews
□ Monitoring: BSR tracked every 2 hours
POST-LAUNCH (T+1 to T+30)
□ Price increase: $0.99 → $2.99 → $4.99
□ Amazon Ads: Campaigns live
□ Reviews: 25+ posted
□ Countdown deal: Scheduled for T+21
References
- Detailed category research: See
references/category-research.md - Email templates: See
references/email-templates.md - Amazon Ads playbook: See
references/amazon-ads.md - Launch day scripts: See
scripts/launch-tracker.py
How to use amazon-bestseller-launch on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add amazon-bestseller-launch
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches amazon-bestseller-launch from GitHub repository breverdbidder/life-os and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate amazon-bestseller-launch. Access the skill through slash commands (e.g., /amazon-bestseller-launch) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★33 reviews- ★★★★★Pratham Ware· Dec 16, 2024
amazon-bestseller-launch has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Yuki Abbas· Dec 12, 2024
Solid pick for teams standardizing on skills: amazon-bestseller-launch is focused, and the summary matches what you get after install.
- ★★★★★Olivia Reddy· Dec 8, 2024
I recommend amazon-bestseller-launch for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Evelyn Mehta· Nov 27, 2024
amazon-bestseller-launch fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Yash Thakker· Nov 7, 2024
Solid pick for teams standardizing on skills: amazon-bestseller-launch is focused, and the summary matches what you get after install.
- ★★★★★Hassan Kapoor· Nov 3, 2024
amazon-bestseller-launch has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Dhruvi Jain· Oct 26, 2024
We added amazon-bestseller-launch from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Aisha Ramirez· Oct 22, 2024
Keeps context tight: amazon-bestseller-launch is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Anaya Gupta· Oct 18, 2024
Registry listing for amazon-bestseller-launch matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Yusuf Khan· Sep 25, 2024
Solid pick for teams standardizing on skills: amazon-bestseller-launch is focused, and the summary matches what you get after install.
showing 1-10 of 33