Guides · Payments

Paying for Revisions and Milestones

Two payment ideas decide whether a commission feels fair on both sides: revisions, the agreed rounds of correction after a delivery, and milestones, the splitting of a large job into staged payments. Used well they make big work safe and small work smooth. Used vaguely they become the two arguments every freelancer and client eventually has. Here is how each actually works.

BLOXWORK, the most trusted Roblox developer marketplace in the world.

Escrow on every order

Your money stays held until you approve the finished work. Only then does the dev get paid.

How escrow works
Devs verified with real ID

Every dev shows ID to earn the Verified badge. The document stays private. Only the badge is public.

About the badge
One fair fee

10% of the job, never more than $1,000. No buyer fees. Nothing stacked on top.

The fee rule

Revisions: what they are and are not

A revision is a correction pass against the agreed scope: the delivered work adjusted where it misses the brief, the references or the promised standard. Packages state how many rounds are included, and professionals plan their process around them, expecting your reaction to real work to teach both of you something the brief could not. A revision round works best as one collected list, everything you found in the test, sent once, rather than a drip of single notes that burns rounds on postage.

New scope is not a revision: features the brief never named, directions reversed after approval of the direction, a second version to compare against the first. The distinction is not pedantry; it is the boundary that keeps prices honest. Devs who cannot tell revisions from additions either pad every quote against the risk or bleed on every job, and both outcomes eventually bill the client.

Spending revisions well

Test before you write the list: play the delivery the way players will, check it against the scope line by line, and gather every gap into one round. Prioritise inside the list, the functional gaps first, the feel items next, the taste items last, because rounds are finite and a delivery that works correctly but feels slightly off is a better position than the reverse. Give references in your notes, a clip of the motion, a screenshot of the layout, because "make it better" is not a revision note, it is a wish.

Know when to stop: revisions converge, and each round should visibly shrink the list. If round three is producing new categories of complaint, the problem is not revision discipline, it is scope, and the honest move is a conversation about a new order for the new direction rather than a fourth round spent pretending otherwise. Good clients and good devs both recognise that moment and name it kindly.

Milestones: splitting the big jobs

Above a certain size, a single payment at the end of a long build serves nobody: the client’s risk concentrates, the dev’s cash flow starves, and one misunderstanding can grow for weeks before a delivery exposes it. Milestones divide the job into stages, each with its own deliverable, test and payment release. The natural seams are the build’s own: core system working, content integrated, polish pass, launch. Each stage approved before the next begins converts one giant act of faith into a series of small verified facts.

On BLOXWORK the clean way to run milestones is staged orders: each stage its own order with its own scope and escrow, approved in sequence. That keeps every stage’s record, review logic and dispute rights self contained, and it lets either side stop cleanly at a seam, the client with working stages in hand, the dev paid for everything delivered. Compare that to the off platform alternative, a percentage up front and hope, and the structural difference is the whole story.

How the fee and escrow treat each shape

Revisions cost nothing extra inside their included rounds, because they are part of the order’s price, and escrow simply stays held while they run: approval, and only approval, releases the payment. Additions agreed mid job become a follow on order with its own escrow, which keeps the original order’s scope, the thing disputes and reviews are judged against, clean and readable.

Milestones multiply orders, and the fee math stays plain across them: 10% of each order, capped at $1,000 per order, taken from the release, nothing added on top for the buyer. Stage sizes are yours to choose; the structure does not care whether a build runs as two stages or six, only that each stage is scoped, testable and approved on evidence. That indifference is the point. Payment structure should follow the work’s shape, not the platform’s convenience.

Where BLOXWORK stands today

BLOXWORK packages state their revision counts in the open, and escrow holds each order’s payment until approval. The marketplace is new, but these mechanics are the product: structure first, trust earned inside it.

How hiring works here

1
Agree the scope & pay into escrow

The scope is in writing before you pay. BLOXWORK holds your money. It does not go to the dev yet.

2
The dev builds

Work runs against the agreed scope and delivery time. Revisions in the package are tracked on the order.

3
You approve, money releases

Check the work. Only your approval releases the pay, minus the 10% fee capped at $1,000.

Are you a Roblox developer?

Keep 90% of every job. The fee never takes more than $1,000, even on a $25,000 job where a 20% platform takes $5,000. Your pay sits in escrow before you start and lands in USD when the client approves. Show your ID once, wear the Verified badge, and let clients trust you on sight.

Questions, answered

How many revision rounds should a package include?

One to three is the healthy band for most work: enough to converge on the brief, few enough to keep both sides decisive. Zero included revisions is a warning sign about the dev’s confidence or process. Unlimited revisions sounds generous and usually signals a dev who has not yet learned what it costs them, which you will pay for in schedule instead.

A dev says my change is new scope. How do I judge?

Hold it against the written scope. If the brief names it, implies it through a stated test, or the delivery cannot meet the brief without it, it is correction. If the brief is silent and the delivery meets everything written, it is an addition, fairly quoted as one. The scope you wrote at the start is the referee, which is why writing it mattered.

When is a job big enough for milestones?

When its build time stretches past a couple of weeks, when it has natural seams with testable states, or when the price would hurt to lose in one piece. Small package work gains nothing from staging; the escrow already covers it. Whole games and large systems gain everything, and staging them is the professional default, not a sign of distrust.

Can milestones protect me if a dev quits mid job?

They limit the blast radius to one stage: completed stages are yours, approved and paid; the current stage’s money never released, so a dispute or refund path covers it; and the next dev inherits working, documented stages instead of a half built mystery. Quitting still costs you calendar. It should never cost you the whole budget and the whole build.

Should I ever pay outside the order to speed things up?

No. The moment money moves off the order, escrow, the record and your dispute rights stop covering it, and the monitored chat here will block the attempt to arrange it for exactly that reason. Speed bought by abandoning the structure is the most expensive speed in this market.

Keep going

Ready when you are

Browse the marketplace with escrow on every order, or put your own work in front of the clients arriving here.