Most custom-work horror stories in this scene — the ghosted deposit, the half-finished heist script, the “my dev resold our signature system to three other cities” — were lost in the first week of the deal, not the last. A FiveM commission is won or lost before any Lua gets written: in the brief, the milestone plan and the payment terms you agree up front. This is the process experienced server owners actually use, from first Discord message to final handover.
The jobs that are genuinely commission-shaped
Custom work earns its price in three places. First, unique mechanics that define your city: a heist chain with your own progression, a gang territory system tuned to your map, a court-and-legal economy nobody else runs. Second, brand assets built to your identity — custom HUD, MLO of your city’s landmark business, liveries and EUP cut for your departments. Third, integration glue: making your dealership talk to your custom banking, or syncing Discord roles with in-city jobs.
What isn’t commission-shaped: anything three stores already sell for $40. You’re paying a developer for design work plus code, so spend that money where the design is yours.
Write a FiveM commission brief that gets accurate quotes
A usable FiveM commission brief names the framework and version, lists every resource the new script must touch, walks through the player-facing flow step by step, spells out the edge cases, and ends with a measurable definition of done. Vague briefs don’t produce cheaper quotes — they produce padded ones, or optimistic ones that collapse mid-project.
Get specific to the dependency level. “Qbox with ox_inventory, oxmysql and ox_lib on current artifacts, OneSync Infinity” tells a developer exactly what they’re building against; “QBCore-ish, we’ve modified some stuff” guarantees a rewrite argument in week three. Link reference videos of systems close to what you want and say precisely what you’d change. Then write down the ugly cases: what happens when a player disconnects mid-transaction, what survives a server restart, what admins can override.
The definition of done should be a checklist, not a vibe. Something like: territory capture works with three gangs of five in a live test, idle resmon stays under 0.05ms, all player-facing text lives in a locale file, every config option is documented. If you can’t test a requirement, it doesn’t belong in the brief.
Finding a developer you can actually verify
The Cfx.re forum’s Server Bazaar, established development Discords and referrals from server owners you trust are the honest sources. A portfolio should show finished systems running in-game — real gameplay video, not UI mockups and promises. Better still, ask which live servers run their work, then go play on one for an hour.
Vouches only count if you can check them. Message two past clients and ask one question: would you hire them again? Red flags worth walking away from: a Discord account created last month, no work you can see running anywhere, pressure to pay today because “the slot closes tonight”, and a quote sitting far under everyone else’s. Nobody builds a full custom banking system for $25 — they paste a leak, restyle it and vanish.
Pricing reality: hourly, fixed and why cheap is expensive
Fixed pricing fits a well-defined brief; hourly fits exploratory or ongoing work. As a 2026 ballpark: small standalone scripts land around $50–150, framework-integrated systems with custom UI run $200–600, and large persistent systems — economy overhauls, multi-stage heists, racing leagues with standings — start near $800 and pass $1,500 without being unreasonable. Custom MLO interiors range from roughly $150 to $800 depending on size and optimization work.
Competent FiveM developers charge in the $20–40 an hour range, specialists more. That math is the whole point: a system that genuinely takes forty hours cannot legitimately cost $60. Pay peanuts and you’re funding a copy-paste of leaked code you can no longer distinguish from stolen goods — with nobody answering when the next artifact update breaks it.
Milestones: structure the job so nobody has to trust anyone
The standard shape is a 25–30% deposit to book the slot, then payments tied to deliverables rather than dates. Three milestones cover most jobs: core logic working on a test server, the full feature set with UI, then polish, optimization and documentation. Each stage gets paid when it’s demonstrated, not when it’s promised.
Every milestone should arrive as a test build you run yourself on a staging server. Spinning up a second txAdmin instance with your real resource stack takes an evening, and it’s the only way to catch conflicts with your existing inventory, phone or job scripts — “works on my dev server” hides all of that. Final payment moves only after the definition-of-done checklist passes on your staging box, not the developer’s.
Payment protection without insulting anyone
Serious developers don’t resist protected payments — that’s part of what you vetted for. Invoiced PayPal goods-and-services gives both sides a paper trail and a dispute path. Platform commissions through Fiverr or Upwork cost more in fees but hold the money until delivery. Some development communities run vetted middlemen who hold payment until both parties confirm; that works when the middleman’s reputation is older than the deal.
What you never do is send friends-and-family or crypto to someone you met last week. There’s no recourse, and nearly every commission scam in this scene starts with exactly that request, dressed up as “avoiding fees.” Offer to eat the fee yourself — 3% is the cheapest insurance you’ll ever buy.
Owning the result: source code, exclusivity and resale
Settle ownership before work starts, in writing — half a page of plain English that both sides keep is enough, no lawyer required. Three questions decide everything. One: do you receive full source, or a locked build? For commissioned work, push hard for source. You paid for the asset, not a subscription to it, and source is the only thing that survives your developer quitting the scene.
Two: is the work exclusive? By default, assume the developer plans to resell a genericized version later. True exclusivity usually costs 1.5–2x the base quote because you’re buying out their resale rights — worth paying when the system is a core piece of your server’s identity, skippable when it’s plumbing. Three: can either side resell or redistribute it? Whatever you agree, write the sentence down. Unwritten assumptions are where every “he stole my script” thread starts.
Handover, retainers and when it all goes sideways
A real handover includes the source, any SQL files, a documented config and a walkthrough call where the developer shows you how to tune it. Agree the support window in advance: thirty days of bug fixes on delivered scope is a normal courtesy, while new feature requests are new paid work — pretending otherwise sours good relationships fast. Ask for a short changelog with any patch so you know what to retest.
If the developer is good, keep them. A modest monthly retainer — $50–150 depending on how much custom code you run — to keep your commissioned systems compatible with artifact and framework updates is cheaper than emergency fixes and puts you first in their queue.
When it goes wrong, the cause is usually visible in hindsight. Scope disputes trace back to gaps in the brief; resolve them with a priced change order instead of a shouting match. Ghosting hurts far less under milestones, because you hold working source for everything you’ve paid for. And half-finished work is salvageable, but expect the next developer to quote near full price to complete someone else’s undocumented code — that’s the honest cost of code archaeology, not a rip-off.
Commissioning is the expensive way to get exactly what you want, which is why it’s worth doing properly. Keep the custom budget for systems only your city will have, and cover the standard layer from catalog stores: script bundles at buy-tebex.io, framework resources at scripts-tebex.io and vehicle packs at cars-tebex.io.