Video summary

12 Przykazań Analizy Niszy Na Amazon KDP 😍

Main summary

Key takeaways

Business

Business-Focused Summary (Amazon KDP Niche Analysis + Execution Model)

Core Message: Stop “Blind Publishing” and Build Around Niche Demand + Positioning

The speaker argues that most Amazon KDP failures happen for one of two reasons:

  • Publishing because “I like the product”, ignoring market demand.
  • Publishing because “it should sell” despite weak market fit (described as a “lottery” approach).

Instead, success comes from a sequence:

  1. Niche analysis first
  2. Product creation for specific customer search intent
  3. Ongoing Amazon positioning via sales performance

“120 NIS” Program: Operational Playbook to Remove Niche Search Bottlenecks

Value Proposition (as framed by testimonials + course owner)

The program provides:

  • Monthly, pre-analyzed niche/product ideas including keywords, so users don’t have to interpret data from scratch.
  • Live recordings/webinars of niche searches (replayable for busy schedules).
  • Ongoing support via:
    • Email
    • Facebook group
    • Fast response expectations (often within a day).
  • A strong emphasis on:
    • Time savings
    • Reducing wasted spend on other subscriptions/courses

Frameworks / Processes / Playbooks Mentioned

1) Niche Definition Framework: What a “Niche” Actually Is

A niche is not a single keyword.

Instead, a niche is a cluster (bag) of related keywords such that:

  • Entering different keywords produces similar product results in Amazon search.

Example progression:

  • Broad: “planner”
  • More specific: “garden planner”
  • Even more specific: “garden journal for beginners”

Goal principle: move from broad niches toward more specific customer segments (don’t try to reach “everyone”).

2) Demand vs. Supply Logic for Niche Attractiveness

Niche strength is tied to:

  • High search demand (relative “volume”)
  • Relatively low supply (fewer strong competing products for that demand)

The better the demand/supply balance, the less you need to rely on PPC to rank.

3) “Positioning by Sales” (Algorithm Mechanics)

Amazon’s positioning is driven by sales performance, not only ad clicks:

  1. You publish a product → it gets indexed for multiple keywords
  2. If it sells, Amazon expands visibility to related keywords
  3. Over time, compounding continues:
    • better sales → more keyword coverage → stronger rankings

The speaker also describes ranking strength as improving over weeks/months, creating a “fortress” effect for earlier entrants.

4) Product Validation Checklist During Niche Analysis

When evaluating a candidate niche/keyword cluster, the speaker recommends checking:

  • Trademark risk: Is the term trademarked?
  • Competition relevance: Are all indexed products truly direct competitors (not just random matches that don’t fit customer intent)?
  • Differentiation potential: How will your product stand out?
  • Customer “missing features”: Use competitor feedback, especially negative reviews, to identify what must be improved/added.
  • Other keyword paths to the niche: How many related keywords exist?
  • Search trend direction: Growing or declining?
  • Seasonality vs. evergreen: Seasonal or year-round demand?
  • Promotion intensity: Are competitors heavily advertised/promoted?
  • Monopolization indicator: Does one author/product dominate?
    • The speaker references a “CIS indicator” concept: searches correlating to a small set of products may require extra checks in other marketplaces.

Key Metrics / KPIs Mentioned (and What They Imply)

Amazon Performance Indicators

  • BSR (Best Seller Rank)
    • Testimonials cite BSR ~50,000 to 30,000 (US market) for products from the program.
  • Keyword indexing/ranking behavior
    • The aim is higher ranking—ideally top positions (first page first).
  • “First-page sales” rationale
    • “First 10 products sell best” (used to justify ranking targets).
  • Product aging / lifetime effects
    • Earlier entrants can maintain rankings longer because Amazon lifetime is longer for existing listings.

Business Outcome Metrics from Testimonials

Examples mentioned (structure varies/unclear):

  • One user: PLN 43,000 net in December from one niche/product.
  • Another user: EUR 60,000 over ~6,000+ (yearly earnings implied; exact structure unclear).
  • Others: “a few thousand PLN” via one product.

Time-Based KPIs

Testimonials emphasize reducing time spent on:

  • Searching for niches
  • Analyzing them
  • Finding keywords
  • Waiting to publish

Note: No formal CAC/LTV/churn/retention metrics were discussed; the focus is mainly on Amazon-specific signals (BSR, demand/supply, ranking effects).

Concrete Recommendations / Execution Rules

Avoid “Reverse” Product Development

Core principle: find customers/market demand first, then build the solution.

The speaker warns against building based on personal preference without market validation.

Decide Whether PPC Is Needed (High-Level Guidance)

The speaker argues PPC is not universally required, and depends on competitiveness:

  • If a niche has high demand and relatively low supply (few products in results), organic ranking may be fast/immediate.
  • As niches become more crowded, competition increases → PPC becomes more necessary, especially for newer entrants.

Use Analysis Depth Before Investing Time/Money

The speaker discourages over-committing based on superficial signals such as:

  • “BSR looks okay” with too few visible competitors/products

Instead, the recommended deeper checklist includes:

  • trademark checks
  • competition relevance
  • differentiation potential
  • review-gap analysis
  • related keyword paths
  • trend direction
  • seasonality
  • promotion intensity
  • monopolization checks

Operational Rhythm: Publish According to “Marcin’s Schedule”

Testimonials describe following a cadence where the program:

  • supplies niche ideas + keyword sets
  • supports faster creation/publication cycles

An additional execution detail mentioned:

  • using time-blocking / Pomodoro-style work habits to maintain consistent production (described as testimonial behavior rather than a program feature).

Program Structure, Scale, and Timeline / Offer Constraints

What Users Receive (Monthly Cadence)

Participant descriptions indicate a monthly package including:

  • Selected niches
  • Keywords (sourced from a “Helium program” mentioned by name)
  • Materials designed to shorten niche/keyword work

From the course owner’s description (final/last edition claim):

  • 10 analyzed niches per month
  • Access to previously analyzed niches (claimed ~360 niches across earlier months/editions)
  • Plus additional content from live searches

Deadlines and Pricing Mechanics (Sales/Ops Side)

  • Registration window: until June 7 (midnight)
  • Sales close: June 8
  • “No joining after” the close date
  • Price behavior: increases by ~PLN 200 per week
  • Capacity constraint: 120 places
  • Payment options: 0% installments via payment gateways (e.g., PayU, and alternatives such as TubaPay)

Presenter / Sources Mentioned

  • Marcin
    • referred to as: “Marcin maup efektowy w sieci.pl”, “captain Marcin”
    • “Marcin Naomie” also appears in subtitles
  • Testimonials / participants:
    • Michalina
    • Przemek Kazanowski
    • Maciej
    • Józek
    • Wojciech (mentioned in an example about possible sales without ads)
    • Unclear name fragment: “Boek” (context suggests a background persona; full name not fully clear from subtitles)

Original video