Pay yourself a flat monthly wage when the income arrives in lumps

March was extraordinary. You launched, the money landed in your Stripe account over about nine days, and for a fortnight you felt like someone who had cracked it. Then April did roughly a fifth of March, and by the middle of the month you were considering a discount you did not want to run, on a product you had not planned to discount, for reasons that had nothing to do with the market and everything to do with your bank balance.

The problem is not the total, it is the timing

Two creators earn the same amount over a year. One takes it in twelve even instalments and the other takes it in three launches. They pay the same tax and buy the same groceries, but they make completely different decisions, because the second one spends four months of the year mildly frightened and two months mildly reckless.

Fear and elation are both expensive. Frightened creators discount early, take work they should decline and price the next thing too low. Elated creators buy the software, book the retreat and hire the editor in the same fortnight. Neither state is a good place to decide anything, and lumpy income guarantees you will spend most of the year in one or the other.

The genuinely hard part is that you cannot smooth the income itself. Launches are lumpy because attention is lumpy. What you can smooth is what leaves the business and reaches you, and that is a decision rather than a market outcome.

Two ways to take money out

Most creators run the first column without ever choosing it. Because payments go directly to your own Stripe account and store.fan never holds your funds, moving to the second column is a habit rather than a feature request.

Setting the number

This takes an evening and a spreadsheet. You need three months of history at minimum, and twelve if you have them, because seasonality is real and one launch will flatter you badly.

A year with the wage running

Imagine a year where two launch months bring in the bulk of the revenue and the other ten tick along on evergreen sales and a small membership. Under the old approach, those two months feel like success and the other ten feel like decline, even though the annual total is fine. With a wage, the launch months simply fill the buffer, and the quiet months draw it down without anybody panicking.

The second effect is slower and more useful. Because your personal finances stop reacting to weekly sales, you can leave a price alone long enough to learn something from it. You can let a product sit for a quarter instead of discounting it in week three. You can turn down a badly fitting client. None of that is available to someone checking their balance before deciding whether to hold their nerve. Your figures will differ, and a business that cannot yet cover a wage of any size is telling you something worth hearing rather than failing a test.

The mistake most people make

They set the wage from their best month. It feels reasonable at the time, because that month proved what is possible, and possible quietly becomes expected. Three months later the buffer is empty and the wage has become another bill the business has to service. Set it from a bad month instead and let the good months be pleasant surprises. The related error is treating a Stripe balance as profit. It is not: tax, refunds, chargebacks and Stripe's own card processing fees all come out of it, and the 0% platform fee on every store.fan plan does not change that arithmetic. What it does mean is that nothing else is taking a cut on the way through.

You cannot make the sales arrive evenly. You can decide, once, what leaves the business each month, and then stop renegotiating it every time a good week or a bad week turns up. Almost every expensive decision creators make is really a decision about how their bank balance felt that morning.