REIGN
Get Reign

For SaaS companies

Reign for SaaS companies. SaaS customer community and docs.

Put support where search can find it: a public Jetonomy forum with accepted answers, docs on the same domain, a BuddyNext space for customers who want to talk to each other and a public roadmap customers vote on. Measure ticket deflection, not member count. Reign gives docs, forum and roadmap one design and one login.

SaaS companies run a helpdesk, a forum, a docs tool and a chat community, so customers have no single login and the company has no clear view of engagement.

Reign + BuddyNext + Jetonomy for a unified customer community: forums, docs, tutorials and roadmap voting. All three of our plugins install free; bbPress is the alternative for teams already on it.

Customer forums, Q&A with accepted answers, and a public roadmap, free to install. You buy the Reign theme; BuddyNext, Jetonomy and Product Roadmap are ours and install free.

  • BuddyNext community engine
  • Jetonomy forums and q&a
  • Product Roadmap roadmap
Start with the free plugins Or the BuddyPress Community Bundle kit See the build recipe Have us set it up

Key takeaways for SaaS companies

  • A private support forum moves tickets. Public answers deflect them, and they keep deflecting for years.
  • Same domain, different sections: docs are authoritative, the forum is where edge cases live.
  • A public roadmap with voting turns feature requests into a visible conversation.
  • Jetonomy, BuddyNext and Product Roadmap install free. See pricing for the Reign licence.

What it looks like on Reign

Screens from the live demos, with sample content. Open any of them and click around.

  • Reign BuddyPress demo home with login, activity feed, members and groups
    The home screen: sign-in, the activity feed and who is active, on one page. Open the demo
  • Reign LearnDash demo course catalog with category and instructor filters
    The course catalog, filtered by category and instructor. Open the demo
  • Reign Dokan marketplace shop grid with product ratings
    The shop: products from every seller in one grid, with ratings. Open the demo

Three highlights for SaaS companies.

  • 01

    Free public docs alongside customer-only forums, using BuddyNext Pro gated spaces.

  • 02

    A public roadmap via our Product Roadmap plugin, free to install with voting, statuses and a changelog; multiple roadmaps and analytics are its Pro upgrade.

  • 03

    Customers sign in once if your app and the community share a login plugin.

What the site looks like on day one.

You launch with a customer community, public documentation, a forum for questions and a roadmap members can vote on. Support questions become indexed pages, docs sit alongside discussion, and the roadmap gives customers somewhere to put feature requests other than your inbox. For a SaaS the immediate win is deflection: the same question answered once, publicly, permanently.

What a member actually does.

A customer hits a problem, searches, and finds an answer written months ago for somebody else. If they do not find it they ask, and the answer becomes the next person's search result. Power users start answering before you do, which is the point at which the community begins paying for itself. The roadmap turns complaints into votes, which is a better conversation.

How this usually makes money.

The community is usually not a revenue line, it is a cost line that reduces another: fewer support tickets, better retention, and content that brings in trials. Where revenue appears it is a premium support tier or a certification course. The business case is normally deflection and organic traffic rather than subscriptions.

The mistake to avoid.

Making the community private. A members-only support forum moves tickets rather than deflecting them, because the answer helps one customer instead of every future one who searches. Public answers compound; private ones do not.

Which Reign setup fits a SaaS customer community

Reign is the WordPress theme for building a complete community site: social network, courses, member directory, marketplace and job board on one install. A SaaS company uses the forum, the community and the roadmap.

Jetonomy supplies spaces, threaded discussions, Q and A with accepted answers, voting, reputation and a moderation queue, all free. Its Pro plan adds private messaging, polls, email digests, auto-moderation and analytics. Our Product Roadmap plugin gives you a public roadmap with voting, suggestions, comments, custom statuses and a changelog for free, and Pro adds multiple roadmaps, extra layouts and a feedback widget. BuddyNext adds customer profiles and notifications, with gated spaces in its Pro plan for customer-only areas.

The BuddyPress Community Bundle kit is the packaged route for a BuddyPress stack, and the private community build guide covers access control. The forum picker helps you compare forum options, and the plugins page shows the split.

Launch steps for a SaaS community

Plan for deflection from day one. Every answer should be easy to find and easy to link.

  1. 01

    Install WordPress with Reign, Jetonomy and the Product Roadmap plugin. The start page lists the order.

  2. 02

    Create spaces that match your product areas and a Getting started space. Write the top twenty questions from your support inbox as seeded threads with accepted answers.

  3. 03

    Add your docs to the same domain with a search box that covers docs and forum together.

  4. 04

    Open the public roadmap with your real planned items and a few statuses. Invite customers to vote and suggest, and reply to every suggestion, even to say no.

  5. 05

    Agree who answers: support as part of their existing work, with a few hours a week set aside at the start.

  6. 06

    Link to the forum from the places where customers get stuck, such as the app help menu, the support email footer and the onboarding sequence.

What customers and your team do week to week

A customer hits a problem, searches and finds an answer written months ago for someone else. If they do not find one, they ask a question in the space. Within a day the thread has a reply, and once accepted it becomes the next person's search result.

Power users start answering before you do. Recognise them with reputation and badges, and make them known to the team. They also vote on the roadmap, so you can see which features matter most to those who use the product daily.

Your team's week includes a short community check: unanswered threads, new suggestions, anything that suggests a bug and a note for the product team. Close the loop by moving roadmap items through statuses and posting changelog entries as things ship.

How a SaaS community grows

The community grows through usefulness, not promotion. As the answer set grows, more searches land on your forum, and more customers solve problems without raising a ticket. That inflow also brings in prospects who see an active product.

Roadmap transparency builds trust. Customers who can see what you are working on, what you decided against and why, tend to stay. Say no publicly and explain it; people accept that far better than silence.

Premium support tiers or a certification course are possible revenue lines later. For most companies, the business case is retention and organic traffic rather than direct subscriptions.

How to run the roadmap so customers trust it

A public roadmap helps only if customers believe it. A board of requests nobody answers is worse than none, because it shows customers that asking is pointless. The discipline is to keep it current and to be honest when the answer is no.

Use the statuses to tell the truth. Product Roadmap supports custom statuses, so you can mark ideas as under review, planned, in progress, shipped or not planned. Move items when the facts change, and write a sentence about why. A status that is never updated tells customers you are not looking.

Reply to every suggestion. A short note that thanks the author, says whether it fits the direction and explains the reasoning is enough. Merge duplicates and point to the combined item so votes are not split.

Close the loop on shipped work. Use the changelog to announce what shipped and link back to the original request. Customers who asked for something and see it delivered become your advocates.

Be clear that votes inform you, not decide for you. Say what else guides priorities, such as security, reliability and the direction of the product, so nobody feels misled when a popular request waits.

Mistakes specific to SaaS communities

Making the community private is the main one. A members-only support forum moves tickets rather than deflecting them, because the answer helps one customer instead of every future one who searches.

Leaving unanswered threads is the second. A community that nobody from the company answers reads as abandoned within a month. Budget the time.

Third, do not measure success by member count. Five hundred members and no searchable answers is doing nothing for the business. Track deflection and traffic to answer pages.

When a different setup fits better

If you want a pure forum with deep moderation features and nothing else, a dedicated forum product may suit you better than a WordPress community. If your project is open source rather than commercial, see the open source community page.

If you only need a help centre with articles and no discussion, a documentation site is simpler.

SaaS company-specific questions.

Why not Discourse?

Discourse is the better standalone forum. Jetonomy plus Reign wins when forums, docs and courses have to share one login and one design. If a pure forum is all you need, use Discourse.

Will this reduce support tickets?

Over time, and only if the answers are public and findable. A private community moves tickets rather than deflecting them. The compounding comes from search: the answer you write today is deflecting tickets in two years, which is not true of anything in your helpdesk.

Should docs and community be separate?

Same site, different sections. Docs are authoritative and written by you; the forum is where the edge cases live. Keeping them on one domain means one search box and one place customers learn to look, which is worth more than tidy separation.

How do I handle feature requests?

A public roadmap with voting, so requests become visible and comparable instead of arriving one at a time in support. It also lets you say no publicly and explain why, which customers accept far better than silence.

Who moderates the community?

Support, usually, as part of their existing work rather than a new role. Budget a few hours a week at the start. A community nobody from the company answers in reads as abandoned within a month.

How do we measure whether it works?

Ticket deflection and organic traffic to answer pages, not member count. A community with five hundred members and no searchable answers is doing nothing for the business.

Buy the theme. Add the plugins free.

BuddyNext, Jetonomy and Product Roadmap cost nothing to install, and each has its own Pro plan for later. Running the third-party stack instead? The BuddyPress Community Bundle kit is the packaged route. Or have the Wbcom team set either one up for you.

See the free plugins See the BuddyPress Community Bundle kit Have us set it up

One theme, the whole site

See what you can build with Reign, then try it.

Reign is the WordPress theme for building a complete community site: social network, courses, member directory, marketplace and job board on one install. Start with one, add the others when you need them, and keep one login for every member. Open a live demo, or launch a sandbox and get a fresh WordPress site to click through in about a minute.

Add more when you need it

Not sure which setup fits your site?

Tell us what you want members to do on your site. We will tell you which Reign setup, plugins and kit fit, before you buy anything.

Ask us before you buy Email support@wbcomdesigns.com

What customers say on Trustpilot

Love this company

Love this company. Loved the REIGN product. They were there the entire time helping me set things up; and when things went wrong? They were quick to take action and help find a solution.

Fable FortitudeCA