Note for creators — pricing vs donations¶
This page is meta: it is for you publishing this course, not for students learning the bot.
Short recommendation¶
Use a hybrid, not a forced choice.
- Keep the core curriculum free and open (MIT or similar), hosted in GitHub + MkDocs—like Berta Chapters. That builds trust, SEO, and community.
- Add optional paid layers only when you have enough material to justify it:
- “Builder pack” — extra notebooks, solution PDFs, video walkthroughs (no face required: screen + voiceover).
- Office hours or cohort — if you ever want live revenue (optional).
- Turn on donations — this repo uses GitHub Sponsors only (see
.github/FUNDING.yml). For your own fork or brand, you can still add Ko-fi or similar if you want a non-GitHub tip jar.
Why not “donations only”? Sustainable maintenance (updates when Binance/APIs change) takes time; donations are uneven. Why not “paid only”? You shrink reach and compete with every other trading course; free core + paid depth is a proven pattern for technical education.
Messaging: The codebase is the tool as it ships—students should not expect you (or upstream) to rewrite the repo for every provider URL change. Point them at ADAPTING_WHEN_THINGS_CHANGE.md so they learn the process; you can still refresh chapter links when you have time.
Why not “everything paid”? For a repo-native course, buyers expect to see quality first; a free base is your proof.
Practical stack (examples, not endorsements)¶
| Model | Tooling ideas |
|---|---|
| Free core + paid PDF / Notion | Gumroad, Lemon Squeezy, Payhip |
| Recurring support | GitHub Sponsors (this repo), Patreon, Ko-fi memberships |
| Tip jar | GitHub Sponsors (this repo); else Ko-fi, Buy Me a Coffee |
| Enterprise / team license | Separate contract—outside this doc |
What to charge (rough guidance)¶
- Low-ticket PDF / checklist ($10–30): works if volume is the goal.
- Serious cohort or 1:1 (hundreds+): only if your time is limited and demand is proven.
Align price with support burden: paid tiers imply some expectation of updates or answers—state clearly what is included.
Legal and expectations¶
- Disclaimers (not financial advice) belong in the free layer too.
- If you sell access, clarify: software education, not guaranteed trading results.
Back to home or Chapter 0 — Beginners.