School of Bots — Content to Cashflow

Course Sales PageVisit sitelearn.schoolofbots.co

A course funnel organized around a large digital bundle, a clear method, and prominent access buttons.

School of Bots — Content to Cashflow — captured interface — Full page · scroll inside to explore

Source capture · 2026-09-07Open full image ↗

Why this pattern works

Study the public sales page and its section order, offer presentation, and calls to action. This reference captures one page; checkout steps and conversion results are not verified.

Design notes

Mood: Product-led and emphatic
Colors: White, deep indigo, violet gradients, and gold access buttons.
Type: Bold sans-serif headlines, compact labels, and scannable benefit lists create a clear hierarchy through the long page.
Layout: Course bundle and outcome headline → brand proof → method and included resources → instructor and student proof → repeated access offer.
Motion: The capture records a static page state. Preserve readable scrolling and clear action feedback; video playback, counters, and hidden form behavior are not demonstrated.
Texture: Photographic or product imagery, contrasting section backgrounds, grouped benefits, and visual proof panels.
Don't: Use your own offer, brand, and assets. Do not invent testimonials, results, scarcity, guarantees, or pricing.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: School of Bots — Content to Cashflow
Source: https://learn.schoolofbots.co/ctc-level1-organic-yt
Swipefile reference: https://swipefile.design/ref/funnel-natasha-willis-the-content-to-cashflow-system/
Captured: 2026-09-07. This is a dated reference, not a claim about the current live product.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- mood: Product-led and emphatic
- colors: White, deep indigo, violet gradients, and gold access buttons.
- typography: Bold sans-serif headlines, compact labels, and scannable benefit lists create a clear hierarchy through the long page.
- layout: Course bundle and outcome headline → brand proof → method and included resources → instructor and student proof → repeated access offer.
- motion: The capture records a static page state. Preserve readable scrolling and clear action feedback; video playback, counters, and hidden form behavior are not demonstrated.
- texture: Photographic or product imagery, contrasting section backgrounds, grouped benefits, and visual proof panels.
- dont: Use your own offer, brand, and assets. Do not invent testimonials, results, scarcity, guarantees, or pricing.

Useful for: Study the public sales page and its section order, offer presentation, and calls to action. This reference captures one page; checkout steps and conversion results are not verified.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Study the public sales page and its section order, offer presentation, and calls to action. This reference captures one page; checkout steps and conversion results are not verified.

School of Bots — Content to Cashflow

Make it your own

Keep exploring