Video summary

Zarabianie na Amazon KDP - Emilia i jej sekrety sukcesu

Main summary

Key takeaways

Business

Business-focused summary (Amazon KDP work organization & planning playbook)

Core thesis

  • Results on Amazon KDP don’t come from publishing “whatever you feel like”—they come from structured planning that reduces chaos, stress, and decision fatigue.
  • Because KDP is often a side activity (full-time job/family), planning is mainly used to reconcile multiple responsibilities and keep execution consistent.

Planning framework (their “operating system”)

They describe a recurring hierarchy of goals and execution:

  • Main Vision → Year → Quarter → Month → Week → Day
  • Each layer breaks the previous one into actionable “small steps” so complex work becomes manageable.

Process as described:

  1. Set annual goals based on a longer-term vision (2–3+ years).
  2. Translate annual goals into quarterly goals (“mini-years”).
  3. For each quarter, define monthly milestones for a specific product/workstream.
  4. Break monthly milestones into weekly tasks, then into daily tasks.
  5. Daily execution focuses only on what must be completed that day; everything else stays “in the background.”

Goal-setting guidelines (how they structure targets)

Goals must be:

  • Ambitious but achievable
  • Measurable
  • More actionable than vague outcomes like “earn more”

Early mistake example:

  • Setting overly aggressive revenue targets without accounting for the learning curve (e.g., in 2019, a goal like “thousands of zlotys in a year” was poorly calibrated).

Alternative to “revenue-only goals”:

  • Since revenue is not fully controllable (market/niche factors), they set goals like:
    • number of products to publish
    • list of specific niches/products to test
  • Revenue targets become indirect—driven by execution (product creation + promotion).

Example product execution timeline (quarter → month)

For a very complex product planned for the first quarter, the steps include:

  • January: niche re-analysis; check what competitors released; design cover; prepare interior
  • February: publish product + create content
  • Following month: start promotions

This illustrates their method: assign each production step to a time box, then break it into smaller tasks.

Operational tools (“systems” / second brain)

Paper + apps hybrid

  • They still keep a handwritten paper plan (for motivation/psychological effect).
  • They use digital tools to store workflow artifacts and coordinate stages.

App recommendations and purpose

They tried multiple systems:

  • Google Drive (ended messy due to document fragmentation)
  • Evernote (good notes, but they felt it lacked some needed functionality)

Recommended task/workspace tools:

  • Asana (mentioned as one of the most popular options)
  • Notion (their main recommendation)

What Notion is used for (concrete):

  • A centralized “second brain” / workspace for:
    • business stages
    • production workflow per product
    • notes + tables + embedded links
    • keeping everything in one place even if they pause work and resume later
  • They also manage non-KDP admin there, e.g.:
    • expense tracking spreadsheet
    • projects status
    • personal inspirations/hobbies

Case scale example (workflow complexity)

  • They reference having ~500 products at one time, which caused forgetting authors/videos and fragmentation with spreadsheets.
  • Their motivation for a centralized system increases with scale (dozens of products, many authors, many steps per product).

Management principles they emphasize

  • Don’t be strict with deadlines if life interrupts: plans set direction, but reality changes (illness/personal events).
  • Avoid self-punishment cycles: discipline is necessary, but abusing strictness is harmful.
  • Perseverance: don’t “jump for the first $100”—treat KDP like a job and plan for the long term.
  • Consistency over novelty: the best results come from staying with one income stream for a long time (marathon mentality).

Key performance & target signals mentioned (lightly, no formal KPIs)

No explicit CAC/LTV/churn metrics are provided (KDP-focused). However, they do mention:

  • Revenue targets in złotys
    • e.g., “in a year at this time I would earn thousands of zlotys” (later described as unrealistic)
  • Product quantity planning:
    • “spend/time horizon to publish 5 or 50 products” (deadline + quantity framing)
  • Operational volume:
    • “several dozen” early tests
    • up to “~1000” cases mentioned generally
    • their personal anecdote of “~500 products” at one point

Most actionable “targets” are operational rather than financial:

  • Set the number of products and deadlines, then execute reliably.

Actionable recommendations (what viewers should do)

  • Write goals down (paper or system) and share them as part of accountability.
  • Set annual goals, but break them into:
    • quarters → months → weeks → days
  • Use “small steps” to reduce anxiety and improve focus.
  • Use a centralized workflow tool (they strongly recommend Notion) when product count grows.
  • Treat KDP as a long-term job:
    • plan like a marathon
    • expect motivation dips and rely on written plans to persist

Presenters / sources

  • Emilia Fade
  • Tomek (host/initiator; mentioned as “Tomek from … waiter to millionaire.pl” and as the person with whom she previously discussed her experience)

Original video