Development Agency
Contact Sign in Get a project quote

Service

Forum development

For owners and administrators of interest forums, product support communities and brand communities who need categories, threads, moderation, reputation and search designed around how their members post and how their team keeps order, including a careful move from the forum software they run today.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A hobby forum with fifteen years of posts runs on software whose last update was long ago, on a shared host that falls over on Sunday evenings when the weekly meet-up thread fills up.

  • The administrator cannot upgrade because three plugins that hold the forum together no longer exist.
  • Spam registrations arrive in the hundreds overnight, so the only moderator with time works through them before breakfast and still misses the ones that post links at lunchtime.
  • Reports land in a queue nobody can sort; a member who has been warned four times by four different moderators has no record visible to any of them, so the fifth incident is treated as the first.

Where it gets harder

The search returns threads from 2009 before the one from last week, and new members ask questions that were answered well a hundred times because they cannot find the answers.

  • Thread URLs change whenever a title is edited, so the search engine traffic that kept the forum alive drains away.
  • A brand running a support community has the same problems with a different cost: a known fault has a workaround buried on page fourteen of a thread, and the support team answers it by email twenty times a week.
  • Members who have contributed for a decade have nothing that shows it, and the forum has no way of knowing who its most useful people are.
  • Moving to new software is the obvious answer and the thing everyone is afraid of, because the last migration lost the attachments.

Scope of the service

What the build covers

A custom forum build normally covers:

  • Categories and sub-categories with per-category permissions for viewing Posting and attaching
  • Threads and replies with rich text Quoting, mentions, attachments and image handling with size limits you set
  • Thread tools for moderators such as move Merge, split, lock, pin and mark as solved
  • A moderation queue that brings reports First posts from new accounts and flagged content into one sortable list with the member's full history alongside
  • Warnings with points and expiry Temporary and permanent bans, and a case note on every action
  • Reputation built from the signals you choose Such as accepted answers, likes from established members and longevity, with badges and trust levels that unlock features gradually
  • Private messages with limits for new accounts
  • Notifications and thread subscriptions by email and in the forum
  • Search that weights recent and solved threads and can be scoped to a category
  • Spam defence combining new-account limits Link rules, rate limits and a third-party check where you want one
  • Stable thread URLs with pagination Canonical tags and redirects from the old forum's addresses
  • An optional paid supporter tier with its own badge and benefits
  • An import that carries members Categories, threads, posts, attachments and private messages from the current software with the old URLs mapped

How discovery works

Discovery works through a week of the forum with the administrator and the moderators: which categories matter, what the posting rules are and how they are enforced, what signals mark a trusted member, how spam arrives, what the import must preserve and what the current URLs look like. Each becomes a named stage in the scope document: register, post, reply, report, moderate, earn reputation, migrate.

Deliberately out of scope

  • A vetted professional community with profiles and applications, a knowledge base authored by staff, a help desk with tickets, and the hosting of large video. Those are their own topics or stay in the tools that own them, connected where it earns its place

When the scope grows

Scoping scenario

A support community for a product range with two hundred thousand posts, a brand team that wants staff answers marked as official, a solved-thread workflow that feeds a public knowledge summary, trust levels that let established members edit titles and tags, and a migration from software with its own attachment format and URL scheme.

That needs

  • A staff role, solved workflows
  • A reputation model
  • An import tool
  • A redirect map of some size

That is a different build from a new forum for a club of two hundred, and the scope document says so plainly.

Deliverables

What you receive

  • Discovery notes from a week of the forum: categories, posting rules, moderator actions, spam patterns and the current URL and attachment structure
  • A written scope document naming each stage from registration to migration, with what is out of scope
  • Design of the category and thread views, the composer, the moderation queue and the member profile with reputation, checked on phones and desktop
  • The build, deployed to your hosting or ours
  • Import of members, categories, threads, posts, attachments and private messages from the current forum software, with a redirect map from old URLs
  • Training for the administrator and moderators, with a short written guide and a moderation handbook template for your rules
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access, contacts and a look at the current forum software, its database and attachments, the moderator logs, the spam patterns and the search engine traffic the forum relies on.

    Project stage: Onboarding

  2. Planning

    Discovery with the administrator and moderators; categories, rules, reputation signals, spam defences and the import scope are agreed in the scope document with a milestone plan.

    Project stage: Planning

  3. Design

    Clickable designs of the category index, the thread view, the composer, the moderation queue and the profile with badges, reviewed with moderators and a few long-standing members.

    Project stage: Design

  4. Development

    Built in stages: categories, threads, replies and search first, then moderation, warnings and spam defence, then reputation, badges and messages, then the import tool and redirect map.

    Project stage: Development

  5. Client review

    Moderators run a test week on a full trial import of the real forum, work the queue on real reports and tell us where it does not match how the forum behaves.

    Project stage: Client review

  6. Revisions

    Permissions, queue sorting, reputation weights, spam thresholds and import mappings are adjusted from the review and re-checked against the scope document.

    Project stage: Revisions

  7. Ready for launch

    Final import run with the old forum in read-only mode, redirects verified against a sample of old URLs, notifications tested on addresses you control, checklist signed off.

    Project stage: Ready for launch

  8. Delivered

    The forum runs on the new software and the old one is retired; optional maintenance and hosting continue under their own agreement.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Email providers for notifications, digests and verification
  • Spam and abuse checking services for registrations and posts
  • Card payment providers for the supporter tier
  • Single sign-on with a brand account, shop or membership platform
  • Media storage and image processing for attachments
  • Search engine tools for sitemaps and indexing of thread pages
  • Help desk or knowledge base systems where solved threads should surface

How we would approach it

Worked example

Concept demo

A product support community with two hundred thousand posts moving off legacy forum software

The situation

A brand ran a support community of two hundred thousand posts on forum software that could no longer be upgraded. Known workarounds were buried deep in threads, staff replies were indistinguishable from member replies, trusted members had no more power than newcomers, and a previous migration attempt had lost attachments.

Why it is a custom build

This needs a custom build because the staff and solved workflows, the trust model and the import from a specific legacy schema are particular to this forum, which off-the-shelf forum software does not provide without the same plugins that caused the problem.

The scope we would propose

  • Categories by product range with a staff role whose answers are marked official
  • A solved workflow where the asker or a moderator marks the answer and solved threads are weighted in search and summarised on a public page
  • Trust levels earned from accepted answers and longevity that unlock title and tag editing
  • A moderation queue with the member's history beside each report and warning points that expire
  • Spam defence with new-account limits and a third-party check
  • An import tool run first as a trial, then for real with the old forum read-only, carrying attachments and mapping every old URL to its new address

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of categories and the permission model across them
  • Moderation tooling: queue design, warning points, bans and case notes
  • Reputation model, badges and trust levels and what they unlock
  • Spam defences and any third-party checking service
  • Size and format of the existing forum to import, including attachments and private messages
  • Redirect mapping from the old URL scheme and search engine considerations
  • Supporter tier, staff roles and single sign-on with other systems
  • Hosting choice: your own hosting or ours, and the traffic the forum carries

Start from a package

Community forum package

Categories, threads and replies, a moderation queue with warnings and bans, reputation and badges, private messages, search, spam defence, stable thread URLs and import from an existing forum for interest, support and brand communities.

Custom build
View the package

FAQ

Frequently asked questions

When is the package enough and when do we need a custom build?

The community forum package covers categories, threads, a moderation queue, warnings and bans, reputation and badges, messages, search, spam defence, stable URLs and an import from common forum software with configuration. A custom build is the honest answer for staff and solved workflows feeding a knowledge base, trust levels with unusual rules, sign-on with a brand account or an import from software with its own schema. Discovery tells you which before anything is quoted.

Will we lose our search engine traffic when we move?

The migration keeps thread URLs stable on the new forum and maps every old address to its new one with permanent redirects, verified against a sample before launch. The scope document states what is mapped and how, and we work from the actual traffic to the old forum rather than from assumptions.

Can the import bring attachments and private messages?

Usually yes. The import is run first as a trial on a copy of the old forum so moderators can check threads, attachments and messages before the real run. What can and cannot be carried over from your specific software is stated once we have seen the data.

How does reputation work and can we switch parts of it off?

Reputation is built from signals you choose and weight, such as accepted answers, likes from established members and account age, and feeds badges and trust levels that unlock features. Any signal or unlock can be turned off; some forums want badges only and no scores, and that is a configuration, not a change request.

Who owns the system afterwards?

You do. Source code and data are handed over at delivery; hosting and maintenance are optional and separately agreed, and the forum can move to another provider.

Get a project quote for forum software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences