6 ms·
Why not offer both? Paying $10/m for as long as you like and get all new and old courses. A basic streaming subscription essentially. But for $100 get lifetime
by TrueSlacker0 4y ago
Why not offer both? Paying $10/m for as long as you like and get all new and old courses. A basic streaming subscription essentially.
But for $100 get lifetime access to only that one purchased course?
Then if the consumer wants more they have the option to spend another $100 for a different course or add the $10/m subscription for other/new content.
I personally would benefit from this immensely in course style learning. I tend to browse lots of content until I find the right info. Then deeply consume the single topic slowly as I teach it to my team. I'm usually stuck paying monthly for something I use for a month then don't use until I begin the training a few months later then dormant again until the next training x months later.
An example.. pay for a Spotify/Netflix/etc monthly subscription but have the ability to purchase a cd/series/movie/book so that if you end your subscription you still have access to the purchased items. Essentially paying a monthly rate to peruse through material then purchasing to deeper dive/repeatedly use an item. The service might even make more money this way.
- nickjj 4y agoThanks, that's a good idea -- especially for standalone courses that are kind of pre-made and done. I guess it's a bit tricky to balance with "screencasts vs courses" which I suppose is a different conversation than a SAAS model or not, although these 2 are pretty tightly coupled. For example, you could have 100 isolated 5-15min screencast videos released once a week about let's say Flask or Rails or whatever topic you're interested in or a 5-10 hour course that covers a cohesive project from beginning to end using a specific tech. The appeal of screencasts to me is you can make a video about anything around that topic, it's completely standalone where as a course is more like you pick the material, record it and that's it but then 8 months later something changes and you'd like to refactor something which could mean re-doing half the course because now you want to use esbuild instead of Webpack for your assets. Full courses tend to be better at taking someone who is a beginner and guiding them to a finished solution and screencasts are good for anyone who wants to solve a very specific problem like "how do I do pagination with Flask". In theory you could have screencasts grouped together as a learning path to solve bigger problems tho so you can technically maybe get the best of both worlds with screencasts which is something I've always wondered about as someone who has made a couple of one time standalone courses.