Share the context
Start with the community details, the feature idea and the reason it matters for staff or members.
Contact
Let’s understand what your Discord community needs next.
Sidelight is built around managed communities with specific workflows, campaigns and fan activity to support. Share the context behind the server and we can look at whether a custom bot feature is the right fit.
Project context
The most useful enquiries explain the community, not just the command.
A good starting point is the background behind the request: who the server is for, what staff are trying to manage and what should feel smoother once the feature exists.
01
Community: who the server is for, who manages it and whether it supports an artist, fan community, partner project or campaign.
02
Workflow: the task, game, announcement, onboarding flow, moderation process or campaign activity you want the bot to support.
03
Current issue: what is manual, messy, repetitive, unclear for members or difficult for staff to keep on top of.
04
Ideal outcome: what should be easier, clearer or more reliable once the feature is in place.
05
Timing: any launch dates, tour dates, campaign windows, approvals or deadlines that affect the build.
How it works
From first context to a practical next step.
Review the fit
We look at whether the request needs a custom Sidelight build, a simpler setup or more detailed scoping.
Set the direction
If it is a good fit, we suggest the clearest next step based on the workflow, timing and level of custom work involved.
Best fit
Purpose-built for artist communities, not adapted from a generic bot.
Good fit
- Artist, fan or partner-led Discord communities
- Custom games, campaigns or staff workflows
- Servers with a clear management team
- Features that need to fit a specific community
- Launches, tours or events that need planned activity
- Teams managing more than one recurring community task
Less suited for
- Standard public bots with no custom setup
- One-off moderation without a wider workflow
- Servers with no clear owner or staff process
- Requests that existing public bots already cover well
- Communities needing only basic commands or utilities
- Projects without a clear use case or launch context