What is the difference between the knowledge base website, the app and the in-app help widget?
The website is publicly accessible, good for SEO and self-service from the browser. The app is for customers who need an answer on the go, with offline mode and push notifications. The context-aware help widget sits inside your existing SaaS product or mobile app and shows the relevant article straight away, based on the screen route and user role. The same content source feeds all three channels.
How exactly does a context-aware help widget work?
The widget is a lightweight SDK that you integrate into your own app or platform. On every screen change, your app sends a context signal (which route, which role, which object) and the widget shows matching articles, videos or an AI answer. Users don't have to search for anything, as the right answer is already waiting. It isn't a standalone pop-up, but a platform for context-aware help inside the app where your customer or end user already is. We connect the widget to the same headless knowledge base, so content updates flow through automatically without a new app release. The widget can be fully styled to match your brand identity and can be rendered as a slide-over, a modal or an inline embed.
Do you also build AI search on top of our own knowledge base content?
Yes. We set up a RAG (retrieval-augmented generation) architecture in which the LLM may only use your own articles as its source. No hallucinations from the wild web, and every answer includes a reference to the underlying article. For deeper AI functionality, such as an agent that carries out actions independently within your product, we combine this with our
AI agent development practice.
How do we migrate our existing content from Intercom, Zendesk or Notion?
We build a content importer for your source. For Intercom, Zendesk Guide, Freshdesk, Notion and Markdown repos we have standard converters; for more exotic sources we write a one-off import script via an
API integration. Images, videos and internal links come across too, and your editorial team can still tidy things up after migration before go-live. Importantly, we don't just map content but also metadata such as categories, tags, author attribution and article view stats, which gives the analytics dashboards a flying start from day one.
What is the difference between a knowledge base and a support portal or customer portal?
A customer or support portal focuses mainly on transactional matters: creating tickets, checking their status, viewing invoices or contracts. A knowledge base site or app is about answering questions before the user creates a ticket. The two often work together: you can link from the knowledge base to a ticket form, and empty search results can automatically start a support conversation. For broader customer portal projects, take a look at our page on customer portals and
document management systems.
Does this work in multiple languages too?
Yes, multi-language support is a first-class citizen in our approach. The CMS supports multiple language variants per article, with optional machine pre-translation (DeepL or similar) that your team then reviews. The site, app and widget automatically pick the right language based on locale or an explicit choice by the user.
What about accessibility and the accessibility scan?
We build to WCAG 2.1 AA as standard. That means keyboard navigation, readable contrast ratios, alt text on images, ARIA labels on interactive elements and screen reader compatibility. In the final sprint we run an accessibility scan (axe-core plus manual tests) and fix any findings before go-live. For public sites this is also legally relevant since the European Accessibility Act.
Can we connect the knowledge base to our ticketing system?
Yes. As standard, we integrate the knowledge base with Zendesk, Intercom, Freshdesk or HubSpot Service Hub. It works in both directions: articles can be suggested directly from the ticketing system, and empty search results or negative feedback can automatically create a ticket so support can follow up.
What does a knowledge base site with an app cost?
The range is wide: a compact knowledge base site with a basic app is a different project from a mission-critical knowledge base with context-aware in-app help and multi-tenant white-labelling for partners. That is why we work with fixed sprint budgets that you can steer. In the introductory meeting we outline the scope and give you an honest indication, based on what you really need in phase one.
How long until the first version can go live?
A first tier, for example the knowledge base site plus the editorial CMS, can be up and running publicly within a few sprints. The mobile app and the context-aware help widget follow in later sprints. A full project with site, app, widget, AI search and multi-language support spans several sprints, delivered in phases so you get value along the way.
Does the knowledge base also work multi-tenant for SaaS vendors with multiple customers?
Yes. For SaaS vendors we build a multi-tenant knowledge base layer: one codebase and one content platform, but a separate sub-environment for each customer or partner, with its own branding, its own articles and its own access rules. White-label setups for partners and resellers are a standard part of this: they get their own knowledge base on their own domain or subdomain, fed from central content where useful and their own content where needed.
How do we measure whether the knowledge base is working?
The analytics dashboard shows, per article: views, completion rate (did the visitor read it to the end), feedback score (was this useful), and click-through to related articles or ticket forms. At search level, you see which terms return no results, which is your content backlog. And combined with your ticketing system, we can see which articles actually prevent tickets and which are only consulted afterwards. It forms the basis for a continuous improvement process rather than a one-off content dump.