Pricing custom content: the math is older than this industry

Custom content — a fan pays you to make a specific video to their spec — is the closest thing this industry has to classic client work. And pricing client work is something I did for years in businesses before I ever pointed a camera at myself. The details here are new; the math is not. Creators keep reinventing pricing from scratch, badly, when the freelance world solved most of it decades ago.

So this is the operator's version: how to price a custom so it's worth making, without the "charge your worth ✨" hand-waving that passes for advice in creator spaces.

The core mistake: pricing the minutes

Almost every pricing guide and platform default anchors customs to runtime — a dollar amount per minute of finished video. That's backwards, and it's backwards in a way anyone who has priced client work will recognize instantly: you're pricing the deliverable's length instead of the work's cost.

A ten-minute custom isn't ten minutes of work. It's reading and clarifying the request, setting up lighting and framing, shooting (with retakes), editing, exporting, delivering, and handling the follow-up message asking for one small change. The runtime is the smallest number in that chain. Price per minute and the fan who wants "just a quick five-minute clip" gets your whole afternoon at a discount.

Every business I've run had a version of this trap — clients who wanted to pay for the deliverable, not the process. The fix is the same everywhere: know your floor, then multiply for what the request actually asks of you.

Step one: know your cost floor

The floor is the number below which the custom loses you money, and it has two parts.

Time cost. Count the whole chain honestly — request back-and- forth, setup, shoot, edit, delivery. For most solo customs that's 2–4 hours end to end, not the runtime. Multiply by what your working hour needs to earn. If you don't know that number, start with what your regular content earns per hour of production work and treat customs as needing to beat it — otherwise the custom is cannibalizing better work.

Platform cut and taxes. A custom sold through a platform loses the platform's percentage off the top, and what lands is pre-tax income, same as every payout. I've written about what actually reaches your bank — run customs through the same arithmetic. A $100 custom is not $100. If your floor math ignores the cut and the set-aside, your floor is fiction.

Floor in hand, everything above it is negotiation room. Everything below it is a no, delivered politely.

Step two: the three multipliers

Client-work pricing has always keyed off scope, not length. For customs, scope shows up as three questions — and each "yes" is a multiplier, not a small add-on.

1. Name use. Saying the buyer's name turns stock production into personalized production — it can never be resold, never join the catalogue, never earn again. Single-use work has always priced higher than reusable work, in every industry. If the custom is personalized, it needs to earn in one sale what catalogue content earns over its lifetime.

2. Exclusivity. Does the buyer want the clip to exist only for them, or can you release it to your catalogue later? A non-exclusive custom is a fan commissioning your next release — they pay, and the content keeps earning for you afterward. That's the cheapest tier, and it's genuinely fine to say so out loud: "non-exclusive is X, exclusive is three-times-X." Buyers respect a menu. The ones who don't were never going to pay the floor either.

3. Distance from your usual lane. A request inside what you already shoot costs you nothing extra. A request that needs new wardrobe, a location, a specific setup, or content at the edge of what you're comfortable making — that's scope creep wearing a costume, and it prices accordingly. And the edge case has a hard rule attached: if the request crosses a boundary rather than approaching one, no multiplier makes it a yes. Boundaries don't have a price; that's what makes them boundaries.

Step three: put it in writing before you shoot

The ask, the runtime, the deliverable, name use or not, exclusive or not, delivery window, and the no-refunds-after-delivery line — in the DM thread or an order form, agreed before anything is filmed. This isn't bureaucracy; it's the same reason collab money splits get agreed before the shoot. Every dispute I've ever seen in client work, in any business, traces back to scope that lived in someone's head instead of in writing. Custom requests are scope disputes waiting for a stage.

Half-up-front is standard client-work practice and translates cleanly here: deposit to lock the slot, balance on delivery, deposit non-refundable once you've shot. Fans who balk at a deposit are telling you something useful early, which is the cheapest time to learn it.

The lowball, and the script for it

You will get offers under your floor. Constantly. The freelancer's answer transfers word for word: don't argue the number, restate the menu. "My customs start at X — here's what that includes." No apology, no justification paragraph. People who've never priced their own work think the lowball is an insult; it's actually just the market asking whether your floor is real. The creators who fold under it teach their audience that the listed price is an opening bid.

And the corollary from running businesses before this one: the client who pays least asks for the most. It was true of bargain-hunting clients in every field I've worked, and the creators I've compared notes with say customs are no exception. Your floor isn't just economics — it's a filter.

The short version

Cost floor first — full time chain, minus platform cut, minus tax set-aside. Then three multipliers: name use, exclusivity, distance from your lane. Scope in writing before you shoot, deposit up front, menu instead of negotiation. None of this is new math; it's the oldest math there is, wearing new content. The industry part — what's in your lane, where your boundaries sit — only you can price. The business part was solved before either of us got here.

— Sly