Creator workflow
Commission workflow for creators
A commission workflow is the path from a casual buyer message to a finished, approved order. It should feel clear and human, not corporate. The point is to protect your time while helping the buyer understand what happens next.
Quick answer
commission workflow for creators
A strong commission workflow has nine basic stages: inquiry, intake, quote, approval, payment status, production, revisions, delivery, and final approval.
The workflow does not need to remove DMs. Let DMs start the relationship, then move the important details into one shared order record before work begins.
The best workflow is simple enough for buyers to follow and specific enough that you can point back to what was approved when edits, file requests, or usage questions come up later.
Guide
How to make the process clearer without making it colder.
- Move serious requests out of messy message threads before quoting.
- Make the quote describe scope, not just price.
- Track payment status separately from creative progress.
- Attach revisions, files, approval, and usage rights to the same order.
Start with the inquiry, but do not keep the whole job there
A buyer might start with a quick message like, "Are you open for commissions?" or "Can you make something like this for my debut?" That first message is useful because it shows interest and gives you a chance to decide whether the request is a fit.
The problem starts when the whole commission stays in that same thread. References arrive in one place, the price is discussed somewhere else, usage is implied but not confirmed, and revision notes get mixed with casual chat. A good workflow lets the conversation stay friendly while moving the actual order details somewhere stable.
- Buyer name and contact
- Source channel such as Discord, X, Twitch, referral, or email
- What the buyer wants made
- References, deadline, and budget context
- Whether the request is ready for a quote or needs clarification
Use the first message to qualify interest. Use the order record to preserve decisions.
Collect quote-changing details before you name a final price
The fastest way to underquote is to price the commission before you know what actually changes the work. For creator commissions, the big quote-changing details are usually complexity, deadline, file package, revision expectations, and usage.
A buyer may not know which details matter. That is why intake should ask simple questions in buyer language: where will this be used, when do you need it, do you need editable files, and are you planning to sell it or use it in paid work?
- Commission type and final files
- Reference files and style direction
- Deadline or event date
- File formats, sizes, and editable source files
- Where the work can be used, including paid channels, merch, or credit expectations
Turn the quote into a clear scope, not just a price
A quote should make the buyer feel confident about what they are getting. It should also make it easy for you to tell the difference between an included edit and new paid work.
Instead of sending only "That will be $120," write the quote as a compact agreement: six emotes, two sizes, one sketch revision, one cleanup revision, stream and social use included, delivery by Friday, editable source files not included.
- Price
- Deliverables
- Timeline
- Included revision rounds
- What is not included
- Payment needed before work starts
If a buyer cannot tell what the price includes, the quote is not finished yet.
Track payment status separately from creative progress
A commission can be creatively approved but not paid. It can be paid but waiting on references. It can be delivered but waiting on final acceptance. Treating all of those as one status makes it hard to know what should happen next.
A clearer workflow separates payment from production. You can then decide your own rule, such as no work before deposit, no final files before balance, or no merch or business-use upgrade before the added fee is approved.
- Quote sent
- Buyer approved
- Deposit or full payment received
- Work started
- Balance due
- Final files delivered
Close the order with delivery, rights, and final approval
Delivery is more than sending a zip file. A clean close should show what files were delivered, what use is allowed, whether the buyer approved the final work, and whether any follow-up support is included.
This is especially helpful when buyers return weeks later asking for another crop, source file, merch permission, or a small change. You can answer from the order record instead of guessing from memory.
- Final file package
- Delivery date
- Approval or acceptance note
- Usage rights included
- What future changes require a new quote
Practical use
Examples creators can recognize.
These examples show how the same guidance applies to real commission moments, from first request to final decision.
Emote pack workflow
A streamer asks for six animated emotes before a subathon and sends references across Discord.
- Move the request into intake and collect emote count, expressions, animation needs, reference files, deadline, and usage.
- Quote the exact package: six animated emotes, Twitch sizes, one sketch revision, one cleanup revision, stream and social use included.
- Wait for buyer approval and payment status before starting.
- Send draft previews in the order record so feedback stays attached to the right version.
- Deliver final files, record approval, and note whether merch or editable source files are excluded.
Stream overlay workflow
A buyer wants starting soon, BRB, panels, alerts, and maybe a few extras if there is time.
- List every included screen and asset before quoting.
- Separate optional add-ons from the base package.
- Confirm the revision stage for layout changes versus final polish.
- Track payment status before starting production.
- Treat extra screens as add-ons instead of silently expanding the original scope.
Character art workflow
A buyer asks for a half-body character piece and later mentions possible merch use.
- Collect pose, expression, outfit, references, deadline, and intended use.
- Quote personal or stream use as the base scope.
- List merch rights as a separate upgrade if needed.
- Use sketch approval before moving into color and polish.
- Deliver the agreed files and keep the rights language attached to the order.
Details
Practical details to decide before the work moves.
Suggested workflow statuses
Use statuses that tell you what the next action is, not vague labels that hide the blocker.
- New request
- The buyer has reached out, but details are not ready for a quote.
- Needs details
- You are waiting on references, usage, deadline, budget, or file requirements.
- Quoted
- You sent price, scope, timeline, revisions, and payment expectations.
- Approved
- The buyer accepted the quote, but payment may still be pending.
- Paid or funded
- Your payment condition for starting has been met.
- In revision
- A draft is under review or feedback is being applied.
- Delivered
- Final files were sent, with usage rights and approval status recorded.
Client language
Wording you can adapt.
Use these as starting points. Keep the tone yours, but make the boundary or next step visible.
This sounds doable. Can you put the details in my commission form so I can quote it properly and keep everything in one place?
I can start once the scope and payment are confirmed. That way we both know what is included before I begin work.
That is a new addition beyond the approved scope. I can quote it separately if you want to include it.
Here are the final files for the approved scope. This includes the usage we agreed on in the order. Let me know if you need a separate quote for additional formats or rights.
Fit check
When a commission workflow helps most
Use this when
- You handle more than one commission at a time.
- Buyers come from several channels and details get scattered.
- You include revision rounds or approval checkpoints.
- Usage rights, editable files, merch, or business use affect price.
- You want a record both sides can point back to later.
Skip or simplify when
- A one-off free request with no files, payment, deadline, revisions, or rights attached.
- A tiny fixed-price product where buyers cannot customize scope.
- A casual favor where creating a full order would add more friction than clarity.
Checklist
Commission workflow checklist
Slatero is being built for this handoff: creators bring their own buyers, then use one shared order record for intake, scope, payment status, revisions, rights, and delivery.
- Original request and source channel
- Buyer contact and communication preference
- References, files, and required context
- Approved price and final files
- Payment status and start condition
- Included edits and extra-work rules
- Drafts, feedback, and approval history
- Final file package
- Usage rights and attribution terms
Workflow mistakes that create extra stress
- Quoting before you know deadline, usage, and file needs.
- Letting payment status live in one app and revision notes in another.
- Treating every small buyer message as approved scope.
- Delivering files before usage rights and final approval are clear.
- Using vague statuses that do not show who needs to act next.
- Relying on memory when several commissions are active at once.
FAQ
Common questions about commission workflow for creators.
Do creators need a formal commission workflow?
A workflow does not have to feel formal. It can be simple, friendly, and lightweight. The purpose is to keep important decisions visible once money, deadlines, edits, and files are involved.
Can commissions still start in DMs?
Yes. DMs are often where trust starts. The workflow is for the next step, when the request needs details, approval, payment status, revision history, or final delivery.
What should happen before a creator starts work?
The buyer should approve what you will make, the price, timeline, included revision rounds, payment expectations, and allowed use. If those are vague, the commission is not really ready to start.
How detailed should the workflow be?
Detailed enough that a buyer understands what they are getting and you can defend your time later. It should not ask for information that does not affect the quote, timing, rights, or delivery.
What is the difference between a workflow and a tracker?
The workflow is the process from request to approval. The tracker is the view that shows where each commission sits inside that process.