There is no magic number that works for everyone, and anyone who gives you one without knowing your offer is guessing. The smarter question is not how much should I spend, but how much do I need to spend to learn whether this works.
Start small enough to learn, big enough to matter
When you are testing, your budget is tuition. You are paying for data. Spend an amount you are genuinely comfortable losing while you learn what your audience responds to. Too little and you never gather enough information to make a decision. Too much and you panic and turn it off before it can work.
Think in cost per result, not total spend
The headline number matters far less than what each result costs. What does a lead cost you? What does a sale cost you? Once you know that a sale reliably costs less than your course price, spending more becomes an easy decision rather than a scary one.
Separate testing budget from scaling budget
Early spend is for finding what works: which audience, which creative, which message. That is your testing budget. Only once you have a combination that returns more than it costs do you move into scaling budget, where you steadily increase spend on the winners.
Never scale a broken funnel
If your sales page does not convert warm traffic, more ad spend just means losing money faster. Prove the funnel works on a small budget first. Spending more cannot fix a leak, it only makes it more expensive.
A bigger budget makes a working funnel grow and a broken funnel fail faster. Fix it small before you scale it.
A simple way to think about it
If a sale costs you a fraction of your course price in ad spend, every extra dollar you put in comes back multiplied. At that point the only sensible question is how quickly you want to grow. Until you reach that point, keep spend modest and focus on improving the offer and the funnel.
Want help turning ads into course sales?
Inside Beauty CEO Society, Luke shares the exact ad systems we use to sell courses on repeat, plus 50% off our Meta Ads Mastery training and live coaching whenever you get stuck.
See What's Inside →