Service · Web development

Custom knowledge portal development.

Your own knowledge base where employees, customers or partners find the answer without having to ask someone. Smart search, your own branding, and integrated with the systems the information comes from. Not a generic Confluence tick-box, but an environment that fits your workflow and audience.

AI searchMulti-tenantVersion controlBranded UX

A knowledge portal is not a DMS and not an LMS.

A document management system is organised around files and records: who has which PDF, in which version, with which signature. A learning management system is organised around modules, progress and certification. A knowledge portal sits between the two: it is organised around questions. Whoever opens the portal has a specific question and wants an answer, not a folder structure or a course.

That difference determines everything. Search is not a feature, it is the main entrance. Content has to be split into articles that can be read independently of one another. Categories are navigation, not an archive. And analytics on which questions go unanswered are more valuable than page views. We build document management systems separately from knowledge portals precisely because the two need to be designed so differently.

The target groups differ more than you might expect. HR departments that want to make internal procedures, policies and onboarding flows accessible. Customer service teams that want to deflect repetitive questions. Professional services firms (law, accountancy, consultancy) that want to unlock client-specific knowledge without juniors having to disturb their seniors every time. Franchise organisations that want to distribute manuals, marketing templates and compliance documents to hundreds of franchisees. And software vendors that help their customers with self-service documentation before a support ticket is raised. For each audience, the portal looks fundamentally different.

Three kinds of knowledge portal.

The form depends on who you serve and how sensitive the content is. In the first conversation we'll advise which direction suits your situation, and whether an off-the-shelf package would actually be enough.

Compact project · fixed sprint budget

Internal knowledge base for your team

A central place where employees find procedures, manuals, policies and internal FAQs. Single sign-on via your existing identity provider, role-based permissions per department, and analytics showing which topics are searched often but rarely found, so the knowledge base keeps feeding itself.

SSORole managementSearch analyticsMobile-friendly
Mid-sized project · fixed sprint budget

Customer portal with FAQ and support docs

A branded environment where your customers or end users find answers without opening a ticket. Semantic search that understands intent rather than matching literal words, deflection statistics for your support team, and hooks into your ticketing system so an unanswered search automatically becomes an improvement point.

Branded UXSemantic searchTicketing integrationFeedback flow
Larger project · fixed sprint budget

Multi-tenant knowledge platform with AI Q&A

For organisations that need to serve a separate knowledge set per customer, franchise or label. Each tenant sees the content that is relevant to them, with their own branding and their own permissions. On top sits an AI assistant that summarises answers from your own content, not from the wider internet.

Multi-tenantAI Q&A (RAG)White-labelAPI integrations

What you get at the end.

A working knowledge portal, plus everything your team needs to manage and extend it independently.

  • The knowledge portal in productionProduction and staging environments, running in your cloud (AWS, Azure or GCP) or hosted by us, with SSL, backups and monitoring set up.
  • Editor environment for content ownersA rich editor so your experts can write, revise and publish articles themselves, without IT having to be involved.
  • Import script from your old systemMigration of existing content from Confluence, Notion, SharePoint or any CMS, preserving the structure wherever possible.
  • Full codebase plus documentationSource code in your own repository, an architecture overview, ADRs for the key decisions, and a runbook for your operations team.
  • Training sessions for editors and administratorsTwo hands-on sessions for content owners, plus a short guide for end users who don't know where to start.
  • Ongoing support (optional)Monitoring, security updates, user support and further feature development for a fixed monthly fee.

When custom pays off and when an off-the-shelf package is enough.

For most teams, Notion, Confluence, Zendesk Guide, Helpjuice, Document360, Slab or GitBook will do just fine. We won't simply replace those. Custom pays off when you recognise one of these patterns.

Compliance

Your sector requires an audit trail

In healthcare, finance or government, it must be demonstrable who saw or changed which version. NEN 7510, GDPR and internal governance call for logging that standard packages don't provide. The same applies to peer-review workflows for medical or legal content.

Multi-tenant

Different customers see different content

You serve multiple customers, franchisees or brands, and each tenant has its own articles, permissions and branding. Standard knowledge base software almost always works as single-tenant, or forces you into separate subdomains, which becomes unmanageable as the number of tenants grows.

Brand experience

No subdomain.zendesk.com

Your customers should land in your knowledge portal, not in a generic support environment with a different logo stuck on. Your own domain, your own UX, your own typography, and a low-friction path to paid support or contact when a search goes unanswered.

Integration

Deep integration with your core systems

When the content isn't static but comes live from your CRM, HR system, product catalogue or ticketing platform, an off-the-shelf package can't cope. We connect the portal to the source systems through smart API integrations, so content never has to be maintained twice.

AI

You want AI Q&A on your own content

A chat interface that compiles answers from your own knowledge base, not a general-purpose LLM that hallucinates about your products. This calls for retrieval-augmented generation (RAG) on your own vector index, with source citations for every answer and logging for continuous improvement.

Scale

Hundreds to thousands of articles

At a small scale, any tool will do. Once you pass a few hundred articles, findability becomes the problem: the same questions keep coming back, content goes stale unnoticed, and search results force users to type exactly the right term. Custom search solves that.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Which modules make up a knowledge portal.

A knowledge portal is not a monolith — it's a set of building blocks that we combine to fit your use case. Here are a few building blocks we almost always put on the table in the first conversation.

Search

AI and semantic search

Standard full-text search with fuzzy matching for typos, plus optional vector search that understands what a user means — not just which words they type. A question like "how do I extend my subscription" finds articles on renewal, cancellation and upgrades, even if those terms don't appear in them verbatim.

Structure

Categories, tags and collections

A multi-level category tree plus free tagging plus personal collections. More important than the structure itself is that your editorial team can maintain it easily, without every article losing its natural place whenever you restructure.

Editorial

Editor with version control and workflow

A pleasant editor for your content owners, with draft versions, a peer-review flow, sign-off for regulated content, and full version history. For medical or legal knowledge this often includes a four-eyes principle: an article only goes live after explicit approval.

Feedback

Comments, ratings and gap analytics

Users can rate an article, leave a comment or suggest an improvement. The portal logs which searches lead to no click, which articles are most often closed without being read, and which articles draw traffic away from others — three signals that give your editorial team fresh direction every month.

Access

Roles, permissions and single sign-on

Fine-grained permissions: per space, per category, per article tag, per tenant. Authentication via SAML, OIDC or magic links for external users. An audit log that records who saw or changed what, and when — relevant for sectors where that is a compliance requirement.

Distribution

Multilingual, intranet/extranet and mobile

Multiple languages with a fallback mechanism, a mobile reading view for engineers and field staff, and a choice between fully internal (behind SSO only), fully public (discoverable by Google) or hybrid: a public layer with deeper articles behind a login.

How a knowledge portal project works.

1

Introduction and intent

A conversation in which we sharpen the target audience, the scope and the type of content. Who will use the portal, which questions need answering, and which systems supply the content or need to be connected.

2

Content audit and architecture

An inventory of your existing knowledge — scattered across wikis, drives, emails and people's heads. Together with a few content owners we work through the top topics, design the information structure and determine which roles are needed.

3

Building in sprints

Working builds every two weeks. The first sprint already delivers a readable portal with a handful of test articles. After that we layer on search, roles, the editor, integrations and, if needed, the AI layer. You test along with us, and so do end users.

4

Content migration and go-live

Migration of your existing articles via an import script, cleaned up where it makes sense, with a final check by your editors. A phased go-live to a first user group, then more widely. Training sessions for editors and administrators are scheduled.

5

Management and further development

Ongoing monitoring, security patches and feature extensions. Every month we review the search analytics: which questions remain unanswered, which articles are going stale, and which functionality the portal needs next quarter.

Frequently asked questions.

What clients almost always ask before we begin.

What exactly is a knowledge portal and how does it differ from a wiki?
A knowledge portal is a searchable environment designed to answer questions. It is not just a collection of pages like a wiki, but a structured system with categories, tags, search and permission management. The content is broken down into standalone articles that can each be read on their own, and there is always an editorial layer to safeguard quality and keep content up to date. For a large audience, that is a fundamentally different design from an internal wiki where anyone can paste in whatever they like.
Do you replace Notion, Confluence or Zendesk Guide?
Almost never, for small, simple use cases. Notion, Confluence, Helpjuice, Document360, Slab and GitBook are excellent for teams that want to get started quickly with an internal knowledge base and have no exotic requirements. We will honestly advise you to stay with those packages if they fit. Custom development comes into play as soon as you run into multi-tenancy, brand experience, sector-specific compliance or deep integration with your core systems, areas where the standard packages structurally fall short.
Can we get AI-powered search on our own content?
Yes. We build a retrieval-augmented generation (RAG) layer on top of your knowledge base: your articles are indexed as vector embeddings, and a language model answers questions by drawing only on that index. Answers include references to the underlying articles, and we log which questions go unanswered so the knowledge base improves itself. We only use this when there is enough content, as below a certain volume AI adds little.
Can you import our existing content from Confluence or SharePoint?
Yes. We write a migration script that connects to the exports or APIs of your current system (Confluence, Notion, SharePoint, Zendesk Guide or any database) and transfers the content while preserving structure, metadata and, as far as possible, the original links. For large migrations, we first run a trial batch to agree on what is and isn't carried over. A migration is often also the moment to clear out old content.
How do you handle access and permissions for internal and external users?
For internal users, this goes through your existing identity provider: Microsoft Entra ID (formerly Azure AD), Google Workspace, Okta or any other solution that supports SAML or OIDC. For external users, such as customers or partners, we usually use email with magic links or a separate account structure per organisation. Roles can be configured in fine detail: per space, per category, per article tag, or per tenant in a multi-tenant setup. We often set up a knowledge portal alongside a vendor portal or employee environment, with shared authentication so that a single login gives access to both.
What about branding: will we get a portal that is truly our own?
Fully branded. Your own domain (kennis.yourcompany.com or support.yourcompany.com), your colour palette, your typography, your illustrations, your tone of voice. Not a logo stuck onto a standard environment, but a UX we design together with your brand team. We work with design tokens so that brand updates can easily be rolled out later, without having to rebuild the portal.
What determines the cost of a knowledge portal?
The biggest factors are the scope of search functionality (simple text search versus semantic AI search), the number of roles and permission levels, the complexity of integrations with your core systems, whether multi-tenancy is needed, and whether content migration is involved. An internal knowledge base for one team is a fundamentally different build from a multi-tenant customer portal with AI Q&A. After the first conversation we give you a direction; a quote follows after the short intake workshop in which the scope becomes concrete.
How long until we can go live?
A first working version is usually ready within a few sprints: readable, searchable, with a handful of articles to test with. A broader rollout with content migration, all roles, all integrations and a possible AI layer takes several sprints. What makes the project longer is usually not the build itself but the content: gathering, cleaning up and rewriting existing knowledge is more laborious at larger organisations than developing the portal.

Talk to us about your knowledge portal.

A no-obligation introduction of half an hour. We listen to who the portal needs to serve and what knowledge it should hold, and give you a direction, even if it turns out an off-the-shelf package is perfectly adequate. We work on standalone knowledge portals as well as on broader custom software projects of which the portal is a part.

Edit content