How to hire a Discord bot developer without getting burned

To hire a Discord bot developer without getting burned, match where you look to the size of the job, then settle three things in writing before you pay: the bot runs on a Discord application you own, you receive the full source code, and "done" is a list of checks you can run yourself. Small jobs are fine on Fiverr or Upwork, where the platform holds your payment until you approve the delivery or a short review window runs out. Bigger builds need milestones and a developer who can show you working code.

Each of those three prevents a common failure: the bot lived on the developer's account and went with them, the code was never handed over, or the scope was a chat message both sides remembered differently. I build and sell custom Discord bots, so weigh my view with that in mind. The marketplace facts below are sourced and dated September 2026, and some of them argue for hiring someone other than me.

Where to hire a Discord bot developer

The Discord bot cost guide has the numbers behind each row. Here is what each channel is like to hire from.

Fiverr

Fiverr showed more than 1,400 gigs for "discord bot" in late September 2026. In a sample of 59 bot-development gigs, the median starting price was $30, and 80% of 121 sampled orders on top gigs were $200 or less. Most top sellers ask you to message them before ordering, so expect a custom offer rather than the listed package.

Fiverr's terms work in your favor on ownership: once the work is delivered and paid for, you get the intellectual property in it, unless the gig page or custom offer says otherwise. Read the gig for exactly that "otherwise", and make sure the source code is part of what gets delivered.

Watch the clock after delivery. Fiverr marks an order complete when you accept it, or automatically 3 days after delivery if you neither accept nor ask for changes; you can extend that by up to 5 days. Test the bot in your server inside that window.

For a reaction-role bot, a welcome message or a small utility, Fiverr is a sensible choice. The orders of $1,000 or more in my sample were bigger systems, such as a bot with a web dashboard or a minigame that also ran on Twitch, and that is where scoping matters most.

Upwork

Upwork's hire page puts a simple command bot at $300 to $1,200, a moderation, onboarding or ticketing bot at $1,000 to $4,000 and a custom integrated bot at $3,500 to $12,000 or more. Freelancer profiles on the same page ranged from $5 to $45 an hour when I checked.

Its own hiring advice is solid: post the bot's purpose, the permissions it needs, your security requirements "including token handling", and your success criteria, then interview for testing habits and least-privilege permissions. For fixed-price work, use funded milestones so money is released one approved phase at a time.

On ownership, Upwork's default contract terms give you the work product once the freelancer has been paid in full, except any "Background Technology" the freelancer brings in, which you get a license to instead. They have to disclose that, so ask for the list. You pay a client fee of up to 7.99% on the Basic plan (3% for eligible US clients paying by bank account) plus a one-time contract fee of $0.99 to $14.99.

Freelancer.com

The 54 fixed-price projects with "Discord" in the title posted between March and September 2026 had a median budget midpoint of about $133 and drew a median of about 45 bids. With that many bids, expect a lot of generic proposals. A simple filter: ask a question in your post that only someone who read it can answer, such as which permission the bot needs for your main workflow.

Toptal and Arc

Toptal says it accepts fewer than 3% of applicants, that you can typically hire in about 48 hours, and that it offers a trial of up to two weeks where you pay only if satisfied. Arc says its Discord bot developers "typically charge between $60-100+/hour" and that you can hire a freelancer in 72 hours. Both are priced for companies that need ongoing capacity rather than one small bot.

r/forhire and Discord hiring servers

The 25 newest r/forhire posts matching "discord bot" (August 31 to September 26, 2026) were all people offering their services, not buyers, and the hourly rates they quoted ran from about $15 to $35. Deals in Discord hiring servers have the same catch: nobody holds the money for either side, so everything in the checklist below matters twice as much.

Specialists and small studios

Look for developers who publish prices, write a spec before starting, test in a private server and hand over code and docs. Excalibur Interactive, for example, describes mapping your workflows, specifying the bot's behavior, testing in a controlled environment and handing over source code and documentation. Small studios publish rates of about $500 to $2,500 or more for a scoped bot. You sign a direct contract, so the protections are the ones you write into it.

Know what you are buying before you post

First check whether a ready-made bot already does the job. Ticket Tool, Tickets, MEE6 and BotGhost cover tickets, levels, reaction roles and simple custom commands for free or up to about $12 a month, and no developer can beat that price. BotGhost alternatives covers where no-code stops being enough.

If you still need a custom bot, write a one-page brief. It gets you comparable quotes and becomes the contract's scope. How to write a Discord bot spec has a template. Put these in it:

1. The problem. Who uses the bot, and what it replaces: a spreadsheet, a staff task, three other bots.
2. Each workflow, step by step, from the member's side and the staff side.
3. The commands, buttons and forms you picture. A good developer will suggest better ones.
4. The data. What the bot stores, where, and for how long.
5. Outside systems. Every service it talks to (Stripe, Google Sheets, start.gg, your own API), and whether you already have API access.
6. Whether it reads message text. Message Content is one of three privileged intents in Discord's API, with server members and presence. You switch it on in the Developer Portal, and since June 10, 2026 Discord reviews the bot's use of it once more than 10,000 users can see the bot. Separately, a bot needs verification to grow past 100 servers.
7. Scale. One server or many, and roughly how many members.
8. Hosting. Where the bot will run and who pays for it.
9. What "done" means. Checks you can run yourself (see the next section).
10. Budget range and deadline. A range gets you honest quotes; "what's your best price" gets you the cheapest guess.

The vetting checklist

1. Working code you can see

Ask for a GitHub profile, a demo bot in a test server, or a screen share of a bot they built. Client bots are often private, so a walkthrough of one is a fair answer. Having nothing at all to show is not.

2. The bot runs on your Discord application

This is the one that protects you most. Do it before the developer starts:

1. Create the application yourself in the Discord Developer Portal.
2. Create a developer team, which makes you its owner (Discord requires two-factor authentication for everyone on a team), and move the application into it with Transfer App to Team. Discord warns that the transfer can't be undone, which is fine when the team is yours.
3. Invite the developer to the team with the Developer role. Discord's docs say Developers can see the client secret and reset the bot token, but can't manage the team or take destructive actions such as deleting the app.
4. When the job is done, remove them from the team and reset the token.

Discord's own docs say never to share the token or commit it to version control. If the bot ever needs verification, which it does to grow past 100 servers, the team owner has to verify their identity through Stripe. That should be you, not a freelancer you hired once.

3. Source code ownership in writing

Fiverr's and Upwork's default terms give you the work once it is delivered and paid for, but only the work that is actually delivered. Some sellers price code separately; Aviantly, for example, sells source code as a $10 to $35 add-on. That's fine if you know up front. Ask for:

• a repository in your own GitHub account or organization,
• a README that explains setup and every environment variable, with an example .env file and no real secrets,
• a list of any templates or earlier code they reuse, and its license.

4. Fixed scope and acceptance criteria

Write down what "done" means as checks you can run. For a map veto bot, for example:

• A best-of-3 veto between two assigned captains follows the order we agreed (for example ban, ban, pick, pick, ban, ban), and the last remaining map becomes the decider.
• Only the captain whose turn it is can press the buttons; anyone else gets a private error.
• The final maps and sides are posted in one summary message.

The map veto simulator lets you click through a veto in the browser if you want to see what such a flow looks like before you write it down. Anything outside the list is a change request with its own price, agreed before it is built.

5. Milestones and a deposit

On Upwork and Freelancer.com, use their milestone payments. For a direct contract, a common structure is a deposit to book the work and the rest on delivery against the checklist; mine is 50% and 50%, and Platform builds are billed per milestone. Paying the full price up front for a multi-week build leaves you nothing to hold back if it stalls.

6. A hosting plan

Agree where the bot runs, whose account pays for it, and what it costs each month; a small bot costs $2 to $5 a month on a managed host. Hosting can sit with you or with the developer, as long as you hold the Discord application and the code, so the bot can move if the arrangement ends.

7. Who maintains it

Discord and its libraries change, so bots need occasional fixes. Ask for a bug-fix window after launch and a price for ongoing care. Published windows range from 14 to 60 days of defect support at Aviantly's three tiers to 30 days of corrections at Custom Bots. Fiverr's cost guide puts basic maintenance at $50 to $150 a month, and my own hosting and Care plans start at $49 a month.

8. A test server before your live server

The bot should be built and demonstrated in a private test server. Upwork's hiring guide recommends asking about "testing methodology before adding the bot to your production server", and it's a good interview question.

9. Permissions they can explain

Ask which permissions the bot needs and why. A ticket bot needs to manage channels and roles; it has no reason to ask for Administrator. A developer who requests only what the bot uses is the kind who thinks about security elsewhere too.

Red flags

• They ask for your Discord login, password, 2FA code or account token. A bot developer never needs these; the team role above gives them everything the build requires. Discord's Developer Policy says that under no circumstances may a developer or their app try to obtain Discord users' login credentials, including "passwords or account access or login tokens".
• They offer a selfbot, message forwarding from servers you don't own, or member growth. Automating a normal user account "is forbidden, and can result in an account termination", per Discord. The Developer Policy also bans inflating member counts, faking activity and scraping. Upwork's own guide tells clients to avoid developers who suggest inflating engagement, faking activity or scraping data. I decline all of these.
• "Unlimited features" for a flat $10. At that price it is almost certainly a template with settings. That can be exactly what you need for standard features, but custom logic has to be designed, built and tested, so ask what happens when your request isn't in their template.
• The bot only runs on their Discord application, or on hosting you can't move away from. Then it's their bot, and it leaves when they do.
• No source code, or code only for a fee you first hear about at delivery.
• They won't write down the scope, or want the full price up front for a multi-week build.
• Your token shows up in a chat message or in the code.
• They can't explain which permissions or intents the bot needs.

How long it takes

Timelines published by marketplaces and studios, as of September 2026:

Add your own time. You will answer questions, test in the staging server and sign off each milestone, and a slow reply on your side moves the delivery date as much as anything the developer does.

Marketplace or specialist?

Use a marketplace when the job is small, standard and easy to check: one server, one feature, a budget under a few hundred dollars. Fiverr and Upwork handle the payment, and a bad result costs you little.

Use a specialist when the bot touches your own data, payments or league, when several systems have to work together, or when you want someone to keep it running afterward. That is where a written spec, a test server and a proper handover pay for themselves.

If you're a company that needs a developer for months rather than a single bot, Toptal and Arc are built for that kind of hire. If you need one bot connected to your product, such as roles by customer plan or tickets with account details, see Discord bots for business.

If you've already been burned

1. Check who owns the application. Open the Developer Portal. If the app isn't under your account or a team you own, ask the developer to hand it over, for example by moving it into a team you own. If they won't or can't, you'll need a new application, and every server has to invite the new bot.
2. Reset the bot token once you control the app, so nobody else can run the bot.
3. Get the code and check it matches what is running. Without the code, the realistic option is a rebuild.
4. Get it running again. If the bot is broken, offline or stuck on an old library version, Bot Rescue is a fixed $149 with no fee if I can't fix it.

Hiring me instead

I've built Discord bots since 2019, including a registration bot I co-built for a 131-team esports league and the Discord operations for Rivals League, a 154-team league; the details are on the work page. Every build runs on your own application, comes with full source code in a repository you own, and is accepted against a written checklist before the final payment. Prices are on the pricing page.

If you're not sure what you need yet, the Bot Blueprint is a call and a written spec with a fixed quote for $249, credited in full if you order the build within 30 days. You can take that spec to any developer.