The second job from the same buyer is the cheapest one to win

A discount needs a source, and on repeat work the source is obvious: you did not have to win the buyer twice. Everything a bundle gives away should come out of that saving and nowhere else.

Get the arithmetic the wrong way round and a bundle is just a price cut with extra admin attached.

What winning a buyer actually costs

Nothing on your invoice, which is why it goes unnoticed.

A first booking costs you the enquiries that did not convert, the messages answering questions the listing had already answered, the clarifying exchange on a thin brief, and the elevated care you take on a first job with someone whose review you cannot afford. Add it up honestly across a month and the acquisition overhead on a new buyer is frequently a fifth to a third of the job's billable time. Whether it is a fifth or a third for you is a thing your own records answer, and it is one of the better reasons to be tracking the enquiries that did not convert.

A second booking from the same person costs almost none of that. They know the format, they brief you correctly, they do not need reassurance, and the delivery is a message rather than an introduction.

So the same fee is worth more from a repeat buyer than from a new one. That difference is real money, and sharing part of it is a discount you can afford permanently, unlike one granted because somebody asked.

Structuring a bundle so it holds

The failure mode of a bundle is that the buyer takes the discount and then uses the jobs in a way that costs you the saving back.

Four terms prevent that, and they fit in a listing.

A fixed count, priced as one transaction. Four jobs at a stated total, not "ten percent off future work", which is an open-ended concession with no end in it.

An expiry. Six months is generous and three is normal. Without one you are holding an obligation at an old price indefinitely, and prices move.

A defined job. The bundle covers the same format at the same length as the tier it was bought from. Otherwise the fourth job arrives as a much larger request that has technically been paid for.

A stated turnaround per job, not for the set. Buyers who bundle occasionally assume the whole set can arrive in a week, and it is easier to have said otherwise than to explain it later.

Keep the discount modest. Ten to fifteen percent across a small bundle is enough to be worth taking and small enough that you have not undercut your own single-job price for anyone watching. Thirty percent is not a bundle; it is a second, cheaper rate card that you now have to defend, which is the outcome the piece on discounting properly exists to prevent.

Prepayment, and what it is actually for

A bundle paid up front is the whole point of a bundle from your side, and it carries two risks that pull in opposite directions.

The first is that you are holding money for work you have not done. If the buyer disappears halfway through, the unearned portion is not comfortably yours, and if they dispute it months later the platform will look at what was delivered rather than what was paid for. Months is literal: Stripe's documentation of how disputes work says card networks typically allow disputes within 120 days of payment, and for a service paid in advance the window can start from the service date instead.

The second is that a prepaid buyer has already spent the money, which makes them relaxed about deadlines and then abruptly urgent when they remember.

Both are manageable with the same discipline. Treat each job in the bundle as a separate delivery with its own confirmation and its own record, and never let the accounting exist only as a running total in your head. Recognise the money as earned job by job rather than on the day it arrived, because a prepaid balance spent as income is the fastest way to owe work you no longer have the budgeted hours for.

Where prepayment is genuinely uncomfortable, half up front and half at the midpoint keeps most of the commitment benefit with much less exposure. That is the same logic as asking for a deposit at all, applied to a longer arrangement.

When a retainer makes sense

A retainer is a bundle without a fixed count: a monthly fee for guaranteed availability, usually up to some cap.

It is the right shape in exactly one situation. The buyer's need is recurring and roughly predictable, and what they are actually buying is a slot rather than a volume.

It is the wrong shape when the buyer's real need is occasional and they want the option of frequency without the cost of it, which is most of the time. A retainer priced as "as much as you want" is an unbounded obligation sold at a fixed price, and the buyer who uses it heavily is the one who keeps renewing.

If you offer one, cap it in units, price it above the equivalent bundle rather than below, and review it every quarter. The premium is for the reserved capacity, and reserved capacity is genuinely expensive: a slot held for someone who does not use it is a slot you turned other work away from.

What repeat buyers are really buying

Worth being clear about, because it changes what the discount should protect.

People return to the person who noticed something, not the person who was fastest or cheapest. The specificity is the product, and a bundle that quietly makes each job more perfunctory kills the thing that generated the repeat business in the first place.

That is also why bundles work better across formats than within one. Pairing a written and a recorded piece gives the buyer two genuinely different things off one act of judgement, which is a better deal for both sides than four of the same thing at a discount.

The buyer-side convention around returning to the same judge is more established than most earners realise, and the account of how repeat commissions are normally handled is a useful corrective to the assumption that every job is a fresh sale. It also helps to know what the free alternatives already do well, since a bundle is competing against the buyer simply running an automated score again for nothing. Where a buyer wants to track something across several submissions over time, consistency of method matters more than any individual assessment, and the conventions for comparable measurements are what make a series of jobs add up to more than the sum of them.

Rate Cock's rewards and payout mechanics for multi-job and repeat arrangements are documented on its rewards page, which is the platform-specific layer under all of this.