Subscription vs Buying Salesforce Courses One by One: The Real Maths

Should you pay for a Salesforce course subscription or buy courses one at a time? Here's the short answer. If you need one narrow topic, buy that one course. It's almost always cheaper. If you need three or more topics over the next year (say Apex, LWC and Flows on the way from admin to developer), a subscription usually costs less. It also saves the hours you'd lose stitching courses from different instructors together. The rest of this post shows the maths, so you can check it against your own situation rather than take my word for it.

I run Salesforce Casts, which sells a subscription, so I have an obvious bias. That's why I'll also tell you when the subscription is the wrong call.

What you're really paying for (it isn't the videos)

Most people compare sticker prices: one course costs X, a subscription costs Y. That leaves out most of the real cost of learning Salesforce, which shows up in three places.

Overlap. Every standalone course has to assume you know nothing. So every course spends its first hour on org signup, what an object is and how to open the Developer Console. Buy five courses from five instructors and you'll sit through that first hour five times.

Gaps. The hardest topics live between courses. How should your LWC call the Apex you wrote? What happens when a record-triggered Flow and an Apex trigger both fire on the same object? How do you test an Apex class that makes a callout? A course on one topic stops at its own boundary, and nobody owns the seam.

Hunting time. Every gap sends you off searching. You find a video, check whether it's current, discover it uses a different trigger pattern, then try to reconcile the two. An hour here and there adds up across six months, and that time has a cost even if nobody bills you for it.

A sequenced curriculum fixes overlap and gaps by design. One instructor and one set of conventions also means one way of structuring triggers, from the admin course through to integrations. Hunting time drops because the next step is already the next course.

None of this shows up on a price tag. It's still the main reason I'd argue for a curriculum over a stack of individual courses, whoever sells it.

The three numbers that decide it

Before you compare any prices, write down three numbers.

1. How many distinct topics you need in the next 12 months. Be specific. "Become a developer" isn't a number. "Apex, SOQL, testing, LWC, JavaScript for LWC, Flows" is six.
2. How many months you'll actually study. Not how many months you hope to study. Look at your calendar. A working admin with a family typically manages five to eight hours a week, not twenty.
3. What an hour of your time is worth. If you freelance, use your rate. If you're salaried, use what your next role would pay per hour. That's the value of reaching it sooner.

With those three numbers, the decision mostly makes itself. One topic and a few weeks points to a single course. Several topics over several months points to a subscription. A career-long plan points to a one-time payment.

Salesforce Casts plans, side by side

Here are the current plans, pulled live from the pricing page:

What every plan includes:

• Every course in the catalogue, not a curated slice of it.
• New episodes as they're published. New episodes are added regularly, and Monthly and Yearly include everything published while your plan is active.
• A GitHub repo for each course, so you can diff your code against mine when something breaks.
• The discussion group for questions.
• Certificates of completion.

What only Lifetime adds:

• The Interview Questions Book, 700+ pages.
• The Real-Time Projects series.
• No renewal. You pay once.

And what no plan includes, because you should know before you pay: there are no refunds, videos stream only, there are no scheduled classes or 1:1 mentoring, and it isn't certification-exam drilling.

Cost per hour: useful, with the right denominator

Here's the catalogue as it stands today:

On the Lifetime plan that works out to about ₹111 / $2.13 per hour of video. The figure falls each time a new episode goes up, because the price stays the same while the hours grow.

I'll be honest about this number, though, because marketing pages often aren't. Cost per hour of catalogue is a flattering metric. You won't watch all 117 hours. Nobody needs CPQ, Aura, integrations and Flows all at once. The denominator that matters is the hours you will actually watch.

So redo the sum yourself. Add up the hours of the courses on your list (each course page shows its hours), then divide the plan price by that total. For example, an admin moving to development might take Apex (5.6 hours), LWC (7.9 hours) and Flows (16 hours). That's a far smaller denominator than the whole catalogue. It's also the honest one.

If the plan still wins on that smaller number, it really wins.

Four real scenarios

The focused sprint: an admin who needs Flows in six weeks

Priya is a working admin. Her company is retiring its old automation, and she's been told to rebuild it in Flow by the end of the quarter. She needs one topic, under a deadline, and she'll study every evening for six weeks.

Best fit: Monthly. She gets Learn lightning flows with me, including the HTTP callout and platform-event-triggered flows, plus anything adjacent she runs into. That might be the Sharing & Security module in the free admin course when a Flow runs in the wrong context. Two months of Monthly covers it. If she finishes and doesn't need more, she stops.

When she should buy elsewhere instead: if a single Flow course on a marketplace is on sale and covers exactly her use case, and she knows she won't need anything else this year, that's cheaper. I'd still tell her to watch a free lecture first and check whether the instructor builds in a real org.

The career switch: admin to developer over nine months

Arjun has three years as an admin and wants a developer role. His list is Apex, SOQL, triggers, testing, JavaScript, LWC, then integrations. That's six or seven topics, and they depend on each other in a specific order.

Best fit: Yearly or Lifetime. Nine months on Monthly almost always costs more than one Yearly payment. Compare ₹ 1,999 / $ 19 per month with ₹ 7,499 / $ 149 per year and find your own break-even month. Buying the same seven topics individually also brings back the overlap-and-gaps problem at exactly the point where he can least afford confusion.

Yearly vs Lifetime comes down to one question: will he keep learning after he lands the role? Most developers do. Integration, async patterns, CPQ or DevOps usually come next. At the time of writing, Lifetime costs less than two years of Yearly, and it includes the Interview Book he'll want around month eight. If he's even moderately sure he'll stay in the ecosystem, Lifetime is the better maths.

The long game: a developer heading towards integration and architecture

Meera is already a mid-level developer. Her next two years look like integrations (Named Credentials, Platform Events, Bulk API 2.0, JWT flows), then broader architecture work, with an interview or two along the way.

Best fit: Lifetime. She'll use Salesforce Integration Master Course (Advanced Apex) heavily and dip into everything else as projects demand. The Real-Time Projects series and the Interview Questions Book are only on Lifetime, and they're aimed squarely at someone at her stage. For career-long learning, a one-time payment that keeps picking up new episodes is the cleanest model there is.

The one-off: a developer who needs one narrow thing by Friday

Sam is an experienced Java developer, newly on a Salesforce project. He needs to understand one specific thing this week, then he'll learn the rest on the job.

Best fit: probably not a subscription. If the free courses cover it (JavaScript for LWC, Apex Triggers Framework 101 or the admin course), he should pay nothing. If not, a single targeted course or the official documentation is the efficient choice. One month of Monthly is reasonable if he wants a guided path through the basics, but I wouldn't push him to a bigger plan.

When buying one course is the smarter move

I said I'd be honest about this. Salesforce Casts courses can also be bought one at a time — each course page shows its own price — so "one course" doesn't have to mean leaving the curriculum. Buy a single course, from me or anyone else, when:

• You need exactly one topic and nothing on your 12-month horizon follows from it.
• You need a refund safety net. Marketplaces such as Udemy offer a refund window. I don't offer refunds, so if that matters to you, it's a legitimate reason to buy elsewhere.
• You need to watch without a connection. My videos stream only.
• You're drilling a certification exam. Practice-test courses and Trailhead are built for that. I teach you to build, which helps in interviews and real projects, but it isn't exam drilling.
• A free resource already covers it. Trailhead, the free courses here, and good YouTube explanations cost nothing. Use them first.

If none of those apply, and your list has three or more topics on it, the subscription maths usually comes out ahead.

Run your own numbers

The defaults below are placeholders. Replace them with the real prices you'd pay for individual courses, the months you'll study and the value of your time:

Two things to watch when you fill it in. First, be honest about the hours you spend hunting for tutorials. Most people underestimate it, because it happens in ten-minute chunks. Second, count the courses you'd actually need. If the answer is one, the calculator will tell you a subscription doesn't pay off, and you should believe it.

The calculator also lives on its own page at the learning cost calculator if you want to share it with a manager.

Before you pay anything

Because there are no refunds, I'd rather you judged the teaching for free first:

Watch one of them end to end. If you like the way I build things live, with real errors and real debug logs, the paid courses work the same way. If you don't, you've lost nothing, and you'll have learned something useful anyway.

My recommendation, plan by plan

• Monthly: a focused sprint with a clear end date. One topic, one deadline, a few weeks.
• Yearly: a structured switch, such as admin to developer, that you'll finish within a year and won't extend.
• Lifetime: you're building a Salesforce career and plan to keep learning. It's the only plan with the Interview Questions Book and the Real-Time Projects series, and it never renews.
• Nothing at all: you need one narrow topic, or a free resource already covers it. Buy that one course, or use the free one, and come back when your list gets longer.