Skip to main content

How Paid Tasks Work ✅🐷

Custom content, made to order. Here's how Paid Tasks work, how to price them, and how to keep them manageable.

Written by 🐽 Support Piggy 🐽

Sometimes a supporter doesn't want what you've already made. They want something made for them.

Paid Tasks is custom content, commissioned and paid upfront. They tell you what they want, you agree to it, you make it, you deliver it. Simple, and usually the highest-value thing on your profile.


The 30-second version ⏱️

✅ Supporters request custom content from you

✅ You review each request and accept or decline — nothing is automatic

✅ Payment is taken upfront

✅ You create it and deliver through the platform

✅ Supporters need an account for this one

✅ You keep 100% of your listed price


Setting them up 📝

1. Decide what you'll take on. Be specific about what a Paid Task from you actually is — a custom photo set, a personalised video message, a made-to-order edit, a voice note, a bespoke design. Vague offers attract vague requests.

2. Set your price. Custom work takes longer than something you've already made and sold twenty times. Price it accordingly — this should be one of your higher rates, not one of your lower ones.

3. Set your terms. Turnaround time, what you will and won't do, how many revisions (if any). Writing this down once saves you every awkward conversation afterwards.

4. Publish. It appears on your profile with a request button.


How a task actually runs 🔄

1. Supporter submits a request with the details of what they want.

2. You review it. Accept if it works. Decline if it doesn't — you're never obliged to take anything on. ✅

3. Payment is taken once you accept.

4. You create it.

5. You deliver it through the platform. ⚠️ Always through the platform. Never by DM, email, or anywhere else — the delivery record is what protects you if the payment is ever disputed.

6. Done. Money's in your Stripe account.


Declining is a feature, not a failure 🚫

Say no to:

❌ Anything outside our content rules
❌ Anything you're not comfortable making
❌ Anything you haven't got time to do properly
❌ Anything where the request is so vague you'd be guessing

A declined request costs you nothing. A badly delivered one costs you a chargeback and a bad review. Decline freely. 🐷


Making them work for you 💡

Price for your time, not the file. A one-minute video that took an hour to make and edit isn't a £5 product.

Cap how many you take. Six open commissions is how creators end up hating a feature that should be their best earner. Close requests when you're full.

Set a realistic turnaround and beat it. Promise a week, deliver in four days, and watch them come back.

Be specific about what you don't do. Upfront, in your description. It filters out the requests you'd have declined anyway.

Deliver exactly what was agreed. Not "close enough". Custom work is where disputes happen, and the agreed brief is your evidence. 🛡️


Common questions 🤔

"Can I decline after accepting?"
Talk to us through the chat if something's gone wrong. Best practice is to review properly before accepting.

"What if the supporter isn't happy?"
Deliver what was agreed and you're on solid ground. If the request was ambiguous, that's a lesson for the description — tighten it and move on.

"Can I take unlimited requests?"
You can, but you shouldn't. Manage your queue.

"Do supporters need an account?"
Yes — there's a back-and-forth involved, so it needs somewhere to live.

"When do I get paid?"
Into your Stripe account after delivery, on Stripe's usual payout schedule.


TL;DR 🎯

  1. Supporters request → you accept or decline → paid upfront → you deliver

  2. You are never obliged to accept anything

  3. Deliver through the platform, always — that record protects you

  4. Price for your time; cap your queue

  5. 100% of your listed price

Custom work, properly paid. ✅🐷

Did this answer your question?