The Netorigo Community module is currently in pre-launch, but the problem it addresses is already a real pain point for our B2B SaaS tenants. Below is why we built it ourselves rather than reselling three external services.
The pre-Community stack
A typical mid-sized Netorigo tenant today uses three separate vendors to cover what a single Community module will deliver: a community forum (e.g. hosted Discourse, ~€4,800/year), a help center (e.g. Intercom Help Center, ~€7,200/year), and a customer Slack workspace (Slack Connect, ~€6,000/year for B2B channels). Total: ~€18,000/year per tenant.
And that's only the license side. Four SSO integrations to maintain (admin app + three vendors), three separate user identities to manage (a customer registers three times, forgets their password three times), and three separate audit trails to cross-reference when reconciling who said what in a contractual dispute.
Why we built it ourselves
Two reasons: data sovereignty and deep integration.
Data sovereignty. A B2B audience is more sensitive about what happens to discussions on a public Discourse instance than a consumer audience would be. A logistics tenant does not want a competitor surfacing in a SEO search which warehouse integration they're struggling with. A self-hosted, tenant-scoped module is default-private and only crawlable when the tenant admin explicitly opens it.
Deep integration. When a customer asks "why did the NAV integration post the wrong line on December 14th", the chat agent can see the tenant's Finance module audit log, see the NAV sync job status, and reply with a concrete incident permalink. An external help center cannot do that without you building three sides of API plumbing between them.
The first launch tenant
Our first design-partner tenant is an ~80-person multi-warehouse logistics operator that has been using the Netorigo platform for two years and worked with us on every feature iteration. They get the Community module first, in a three-month closed beta, before we open it to a wider tenant pool.
Starting with an existing partner is deliberate: the Community module only has value when there's content. The first three months of an empty forum is where every community project dies. The design partner brings ~400 resolved support tickets that seed the KB + auto-FAQ before launch.
The four post-launch metrics
What we measure for three months after launch:
- Time-to-first-answer. How long a new question takes to get any reply within the tenant. Target: median <4h business-hours.
- Deflection rate. How many support tickets don't arrive because community + KB answers them. Target: 30% by end of month three.
- Cross-tenant participation. How many comments come from peer tenants (not the tenant's own team, not Netorigo staff). Target: 25%.
- Auto-FAQ approval rate. What share of the weekly LLM-generated FAQ ships through the human approver without edits. Target: >70%.
What it does NOT solve
The Community module is not a replacement for the paid support contract. SLA-bound tickets continue through the support channel, and community questions get best-effort Netorigo-staff replies, not contractually guaranteed ones. We surface that on the first onboarding screen so the expectation mismatch never happens.
Similarly, it does not replace the sales channel: you can't close a new contract in the community, you can't get a quote, and pricing questions are routed to the sales team automatically and excluded from the auto-FAQ (see the next post on the KB).