This capstone has one goal: get an automated workflow running live on your Amazon business before you close this tab.

Not planned. Not “I’ll do it later.” Running. Scheduled. Delivering output without you initiating it.

Step 1: Choose Your Workflow

Pick one use case from Module 6. The recommended starting point for most sellers is the Weekly PPC Digest — it is the highest-frequency, highest-value workflow and the one that makes automation feel most real once it starts arriving in your Slack.

• Weekly PPC Performance Digest (recommended first workflow)
• Inventory Reorder Alert
• Listing Quality Audit
• Monthly Profit Summary
• Competitor Price Monitoring

Your choice: ___________________________

Step 2: Confirm Prerequisites

• Seller Labs Amazon MCP is connected and tested (Module 4)
• You verified the MCP works by running a test query
• Your Slack channel is configured for output delivery (if using Slack)
• Your CLAUDE.md has the context needed for the workflow (ASINs, thresholds, supplier lead times)

Step 3: Write the Prompt

Use the prompt template from your chosen use case in Module 6 as a starting point. Customize it with your actual:

• ACoS threshold (or whatever the relevant threshold is for your workflow)
• Output file path (e.g., analysis/ppc-digest-[date].md)
• Slack channel name
• Any ASIN-specific details not already in CLAUDE.md

Test the prompt manually first: copy it into Claude Code and run it by hand. Review the output. Does it do what you expected? Are the numbers right? Is the format useful?

Refine the prompt until the manual run produces good output. Only then schedule it.

Step 4: Run It Manually 2-3 Times

Before scheduling, run the workflow manually 2-3 times across different days. This is the supervised phase from Module 5. You are building confidence in the output before handing it off to automation.

• Manual run 1: Output reviewed and looks correct
• Manual run 2: Output reviewed — consistent with run 1
• Manual run 3 (optional): If any issues found, address them first

Note any corrections you made. Update your prompt to account for them.

Step 5: Schedule the Workflow

In Claude Code, use the /schedule command to create the scheduled task:

1. Paste your refined prompt
2. Set the schedule (e.g., “Every Sunday at 6pm” or the equivalent cron expression)
3. Confirm the output destination (file path and/or Slack channel)
4. Activate the schedule

Verify the task appears in your scheduled tasks list (/schedule list).

Step 6: Verify the First Automated Run

Wait for the first scheduled run. When it triggers:

• Output was delivered to the expected location (Slack and/or file)
• Content is accurate and useful — no hallucinations, no missing data
• No errors were thrown
• The format is what you expected

If anything is off, refine the prompt and run it manually once more before re-scheduling. If it runs correctly, you are done with this workflow — and it will run every week without any further input from you.

You Are Now Operating at Level 3 (or 4)

If you completed all six steps, you have:

• Live Amazon data access via the Seller Labs Amazon MCP
• A working scheduled workflow delivering automated output
• A tested, reliable prompt that produces consistent results
• The skills to build additional workflows using the same pattern

The first workflow is the hardest. The second one takes half the time. The third is routine. Build incrementally.

What to Build Next

Once your first workflow has run reliably for 3-4 weeks, add a second. Then a third. Over time you will have a small portfolio of automated workflows that collectively give you better business intelligence — faster and more consistently — than you could get manually.

A realistic 90-day progression:

• Month 1: Weekly PPC Digest running live
• Month 2: Add Inventory Reorder Alert
• Month 3: Add Monthly Profit Summary

By month 3, you have three automated intelligence workflows running every week — and you spent less than an hour total setting them up.