Welcomes and roles
A message when someone joins, and roles they can pick. The copy is yours.
Discord bots
A bot for the server you already run.
Custom commands, roles, and tools, written for one Discord server. A web panel can sit beside the bot when you want one. The scope is written first, the price is agreed before we build, and the finished bot is yours.
- Built for
- One server, or a small set of servers named in the quote
- Commands
- Slash commands, and only the jobs the server actually needs
- Records
- MySQL when the bot has to remember a ticket, a member, or a decision
- With a site
- Orders, bookings, or a member check, when that link is in the scope
- Web panel
- A private page beside the bot, when you want one
- Testing
- Our own Discord bot tokens and secrets
- Review
- A Discord server built for your bot, where you see it working
- Agreement
- Scope and price in writing before the build
- Ownership
- The code is yours when the quoted price is paid. After that, we do not ask for your token or any other secret
01
Server
The everyday jobs a community asks for, built as commands rather than a pile of switches.
Custom commands
Answers your members already ask for: hours, rules, a price, a link, a fixture.
02
Moderation
A quieter way for staff to see a problem and keep a record of what they did.
Reports
A member flags a message. Staff see it in a channel you choose.
Tickets
A private thread with the team, for a shop question, a membership, or a complaint.
03
Tied to a website
Useful when the Discord server and the site are meant to be the same organisation.
Orders and bookings
A note in a staff channel when an order is paid or a time is booked.
Members
A role, or a refusal, based on a list the website already keeps.
04
Private tools
A company, a club, or a family server. The bot is not listed in a public directory unless you ask for that.
Internal commands
A status, a rota, a stock note, or a reminder that only staff should see.
Your server
After you have seen it working, you add it to the server you already run.
05
Web panel
A private page beside the bot, for the people who run it. It is available with the bot, and named in the quote when you want it.
Settings
Change the parts that should change: a welcome, a role list, a channel, a message.
Records
Tickets, reports, or a log of what the bot has done, read in a browser.
06 — Tokens
Testing uses our tokens.
During the build
Testing uses our own Discord bot tokens and our own secrets. You see the working bot in a Discord server built for that bot.
When it is finished
We do not ask for your bot token, or for any other secret. The project ends without a request for them.
How you run it
We show you how to manage the bot, so you know the steps yourself.
07 — Process
Same shape as a website job.
- 01
Listen
What the server needs the bot to do, and whether you want a web panel.
- 02
Scope
Commands, the panel, price, and timing, written down before we build.
- 03
Build
You see the working bot in a Discord server built for it. Testing uses our tokens.
- 04
Hand over
We show you how to manage the bot. After that, we do not ask for your token or any other secret.
There is no package price on this page. Two servers rarely need the same bot, so the quote follows the scope. Discord’s own costs, if any, are named before you agree. Looking after the bot after launch is optional and quoted on its own.
Questions
Is this a bot I rent from a dashboard?
No. The bot is written for your server. If a free bot already does the job, we will say so before you spend the money.
Can it talk to a website?
Yes, when that connection is in the scope. An order, a booking, or a member check can post into Discord. It can sit beside a site we build, or a site you already have if the connection is straightforward.
Where does the bot run?
A bot has to run somewhere. That place, and who pays for it, is named in the quote before you agree. It is not hidden in the build.
Who owns the bot?
You do, once the price in the quote has been paid. You own the code written for the project, and the web panel if the quote includes one. Discord’s own service stays on Discord’s terms.
Will you need my bot token?
Testing uses our own Discord bot tokens and our own secrets. You see the working bot in a Discord server built for that bot. When the project is finished, we do not ask for your bot token, or for any other secret. We show you how to manage the bot yourself.
Can I have a web panel?
Yes. A private page can sit beside the bot, for settings, tickets, or a record of what the bot has done. It is named in the quote when you want it.
What will you not build?
A bot whose job is to spam, scrape private messages, raid, or evade a ban. The bot uses Discord’s API and has to follow Discord’s rules.