Limit custom orders with one formula: weekly hours you can give custom work รท average hours per order = orders per week, multiplied by four for a monthly figure, rounded down, minus a buffer for sick days and orders that run long. Publish that number on your page, close new requests once you hit it, and route overflow to a waitlist or a temporary price increase.
FanBell is free to start with no monthly fee and applies a 12% platform fee only when a fan pays (pricing).
A standing cap is different from reacting to a bad week. It's a number you decide on a slow day โ when you can think clearly about how many hours a custom order actually takes โ and then hold yourself to it even when requests are easy to say yes to individually. Gallup reports that 76% of employees experience burnout on the job at least sometimes, and 28% say they are burned out "very often" or "always" at work (Gallup, "Employee Burnout: The Biggest Myth"). Gallup's research on the causes names an unmanageable workload among the strongest predictors:
"When their workload is out of control, employees look to their managers to be their advocates for what they can and can't accomplish." โ Gallup, "Employee Burnout, Part 1: The 5 Main Causes"
A solo creator selling custom orders has no manager to set that boundary โ the monthly cap is how you set it yourself.
How many custom orders should you take per month?
Divide the hours you can realistically give custom work each week by the average hours one order takes end to end, multiply by four, round down, then subtract a buffer of roughly 15โ20% for sick days and orders that overrun. There is no universal number: a 20-minute shoutout and an 8-hour commission produce very different monthly caps from identical working hours.
Count the real hours per order, including intake questions, revisions, and back-and-forth โ not just the recording or rendering time. Round down on your first pass. Raising a cap after you've proven you can hit it is easy; lowering one after fans are already waiting is not.
Four worked examples, each using the same formula:
| Offer | Avg hours per order | Weekly hours you give it | Raw monthly cap (hrs/wk รท hrs/order ร 4) | Published cap after buffer |
|---|---|---|---|---|
| Personalized Shoutout, 60-second video | 0.33 (about 20 minutes) | 2 | 24 | 20 |
| Creator Service, standard edit or custom asset | 3 | 9 | 12 | 10 |
| High-effort custom service, full illustration or long-form edit | 8 | 12 | 6 | 5 |
| Mixed page: shoutouts plus one service tier | 0.33 and 3 | 2 for shoutouts, 6 for services | 24 and 8 | 20 and 6 |
Read one row at a time. A creator who spends about 20 minutes on a 60-second Personalized Shoutout and gives it 2 hours a week can deliver 6 a week, or 24 a month, and should publish 20 to leave room for a bad week. A Creator Service that takes 3 hours end-to-end with 9 hours a week available yields 3 a week, 12 a month, published as 10. An 8-hour custom illustration with 12 hours a week available yields 1.5 a week, 6 a month, published as 5 โ the same working hours, a cap four times smaller, because effort per order is what the formula divides by. If you sell more than one offer, run the formula separately for each and split your weekly hours between them rather than publishing a single blended number.
Why set a hard number instead of just working harder?
A published cap protects the turnaround time you promised, which is the part of the offer a fan is actually paying for. Without a cap, every extra "yes" quietly extends the wait for fans who already paid, and a missed delivery date becomes a refund conversation rather than a scheduling one. The cap is what keeps the deadline true.
On FanBell, Creator Services and Personalized Shoutouts let you set your own delivery time, and the product accepts a delivery promise of 1 to 120 hours โ a maximum of five days (how it works). That deadline is only meaningful if your total order volume stays inside what you can deliver within it.
Stated delivery windows are treated as binding commitments, not marketing copy. The U.S. Federal Trade Commission's Mail, Internet, or Telephone Order Merchandise Rule requires a seller to ship within the time it clearly and conspicuously states, or within 30 days if no time is stated, and to get the buyer's consent to any delay or issue a prompt refund (16 CFR 435.2; FTC rule page). The Rule governs merchandise orders and does not cover every digital service, but it shows the standard a regulator applies to a promised turnaround.
Large marketplaces cap the same variable rather than leaving queues open-ended. Etsy โ which reported 89.6 million active buyers and 5.6 million active sellers as of December 31, 2024, in its Form 10-K filed with the U.S. Securities and Exchange Commission โ sets a ceiling on custom-order timelines:
"The maximum processing time you can place on a custom order is 6-8 weeks." โ Etsy Help, "How to Offer Custom Items"
Fiverr caps intake volume directly: its Help Center documents a "Limit orders in queue" toggle and a "Max orders in queue" field that stops new orders once a freelancer's queue reaches the number they chose (Fiverr Help Center, "Managing your Gigs"). Two marketplaces at very different scales both build the same constraint into the product; on a page where the cap isn't automated, you publish it yourself.
What's the difference between a monthly cap and pausing orders?
A monthly cap is a standing policy โ a fixed intake number you reset at the start of every month, whether demand is high or low. Pausing is a temporary toggle you flip on when you're already overloaded, sick, or between other commitments, then flip off when you're ready again. A cap prevents overload; a pause responds to overload that has already arrived.
Both marketplaces above ship a pause switch alongside their volume controls. Fiverr's Availability feature "lets you set a time frame when you cannot receive new orders or messages" (Fiverr Help Center, "Setting Availability for freelancers"), and Etsy's Vacation Mode stays on indefinitely until the seller turns it off (Etsy Help, "How to Manage Vacation Mode for Your Shop"). Neither is a cap: they stop everything rather than metering intake. You can run both โ a standing monthly number, plus the ability to pause entirely if that number turns out to be wrong for a given month. For the on/off mechanism itself, see how to pause taking orders when you're overwhelmed.
Where should the extra demand go once you're capped?
Once you hit your number, the two standard overflow routes are a waitlist or a temporary price increase. A waitlist defers demand to next cycle and leaves you a list of already-interested fans to open to first. A temporary price increase lets fans who need the work now self-select and pays you for the extra effort of squeezing them in.
Neither route guarantees the fan comes back, and we have no data showing one converts better than a hard close โ the defensible difference is that a waitlist leaves you a contact you can follow up with next cycle, while closing with no list leaves you nothing. See how to manage a waitlist for custom requests for the mechanics. A temporary price increase โ sometimes called surge or rush pricing โ is the better fit for one-off spikes you can absorb with effort rather than steady demand you'd rather serve at your normal rate. Both routes beat quietly accepting orders you can't deliver on time, which trades a short-term "yes" for a request you'll eventually have to explain, delay, or refund.
| Overflow option | What it signals to the fan | Best for |
|---|---|---|
| Waitlist (no price change) | "I'll get to you next cycle" | Steady, predictable monthly demand |
| Temporary price increase | "I can fit you in, at a premium" | Occasional spikes you can absorb with effort |
| Close with no waitlist | "Not available right now" | Short breaks, or offers you're phasing out |
| Redirect to a lower-effort offer | "Here's something I can do today" | Fans who'd accept a smaller deliverable |
How do you communicate a monthly cap to fans?
State the cap in plain terms on your page or in the offer description, and update it the moment you're full. A fan should be able to tell, before paying, whether you're currently taking new orders and roughly when a new order would be delivered. Vague availability language creates more support questions than a specific number does.
Something like "Taking 15 Creator Service orders this month โ 4 spots left" is more useful to a fan deciding whether to pay than no visibility at all. If you're full, say so plainly rather than leaving an offer open you don't intend to fulfill on schedule. On FanBell, a fan pays and submits their request through your page, so the moment before checkout is the only real chance to set that expectation โ there's no separate booking step where availability gets clarified later.
Does a monthly cap mean turning down money?
A cap does mean declining some orders in a given month, but it caps unsustainable order volume rather than your income ceiling. Revenue is price multiplied by orders delivered, so fixing the order count leaves price and per-order efficiency free to move โ and an order delivered late or refunded was never revenue in the first place.
You can raise capacity over time by improving your process (templates, batching similar orders, clearer intake questions that cut down on revision rounds) โ see how to take on more paid requests without burning out โ or by raising your price so each order pays proportionally more without adding hours. In the worked examples above, cutting a 3-hour Creator Service to 2 hours raises the same 9 weekly hours from 12 orders a month to 18; doubling the price raises revenue with the cap untouched. Neither path requires abandoning the number.
What happens if you don't cap orders at all?
Without a cap, turnaround slips for everyone in the queue, including fans who paid early expecting a fast reply, and each week's overflow becomes next week's backlog. A missed deadline is harder to fix after the fact โ it usually ends in refunds or a full pause โ than a published "not this month" ever was.
The health data on sustained overwork is specific. A joint WHO and ILO global study found that working 55 or more hours per week is associated with an estimated 35% higher risk of stroke and a 17% higher risk of dying from ischaemic heart disease, compared with working 35โ40 hours per week (WHO, "Long working hours increasing deaths from heart disease and stroke", 17 May 2021). The American Psychological Association's 2023 Work in America survey found that 77% of U.S. workers reported experiencing work-related stress in the month before the survey (APA, "2023 Work in America Survey"). Gallup reports that employees who frequently experience burnout are 63% more likely to take a sick day and 2.6 times as likely to be actively seeking a different job. Those figures were measured on employees rather than solo creators, so read them as evidence about workload generally, not as a measurement of custom-order sellers โ but a creator who burns out has no colleague to cover the queue. Related: how to organize incoming paid fan requests covers the triage system that makes a cap easy to track in the first place.
Frequently asked questions
How do I pick my first monthly cap number?
Divide the hours per week you can dedicate to custom work by the real hours one order takes you including revisions, multiply by four, round down, and cut another 15โ20% as a buffer. Nine weekly hours against a 3-hour order gives 12 a month, published as 10. It's easier to raise a conservative first cap once you've proven you can hit it than to lower one after fans are already waiting past your stated turnaround.
Should the cap apply per offer or across my whole page?
Per offer is usually clearer if you sell more than one type of custom work โ a separate limit for Creator Services versus Personalized Shoutouts โ because the hours per order differ enough to change the answer. A 20-minute shoutout and an 8-hour commission drawn from the same weekly hours produce caps that differ by a factor of four or more.
What if I hit my cap in the first week of the month?
That's a signal your cap is set too low for current demand, not a problem to solve by quietly ignoring it. Open a waitlist for the rest of the month, and raise the number (or your price) next cycle once you've confirmed the higher volume is repeatable rather than a one-off spike.
Does FanBell enforce order caps automatically?
No. FanBell lets a creator set price and delivery time on Creator Services and Personalized Shoutouts โ a delivery promise of 1 to 120 hours, five days at most โ and decline and refund any request outside scope or capacity. The monthly number itself is a policy you publish and manage yourself, not an automated intake limit like Fiverr's "Max orders in queue" field.
Is a monthly cap the same as a paid queue length?
No โ a cap limits how many new orders you'll accept in a given month, while a queue is simply the orders you've already accepted, waiting to be delivered. A well-managed cap keeps the queue short enough that your published turnaround time stays accurate.
Keep reading
Ready to get paid for the interactions you already get?
Create your free FanBell link