Service · App development

Custom knowledge base website and app development.

One set of knowledge base content, two faces: a searchable site and a mobile app where your customers or end users always find the right answer. Including a context-aware in-app help widget that travels with the user and shows the relevant article at the right moment.

Web + mobile appContext-aware helpAI searchOffline mode

A knowledge base that goes into the app.

Most knowledge bases are standalone websites with no idea what the user is doing in the product at that moment. As a result, the help stays generic and customers have to come up with the right search term themselves. It works better the other way round: the knowledge base is built into your own app or platform and knows which screen, which flow and which role the user has at that moment.

We build custom knowledge base sites and companion mobile apps for software vendors, healthcare, education and B2B SaaS. One content source, multiple channels: a public knowledge base site for SEO and self-service, a mobile app for customers who need a quick answer on the go, and a context-aware help widget that travels with the user inside your own app or platform.

The approach is fundamentally different from an internal knowledge portal for your own employees: here the audience is external, the traffic unpredictable, and the UX bar higher. Customers expect Notion-level search and Stripe-level documentation, whether they open it on desktop or on their phone.

What we see time and again with clients: there is already quite a lot of content ready in Intercom, Zendesk Guide or Notion, but nobody finds it at the right moment. A better search bar partly solves that. What really changes things is help that offers itself proactively, when the user gets stuck, not when they happen to go looking. Hence the focus on context-aware help as the core of the platform, with the site and app derived from the same content pipeline.

Three types of knowledge base.

Depending on where your end users need the knowledge and how deep the integration with your existing product needs to be. We'll discuss which type fits in the introductory call.

Compact project · fixed sprint budget

Knowledge base site

A public, searchable knowledge base on your own domain. Mobile-first and responsive, fast full-text search, category and tag navigation, and an editorial CMS in which your support team writes articles without developer involvement. Good for SEO and ticket deflection.

Editorial CMSFull-text searchSEO optimisationFeedback loops
Mid-sized project · fixed sprint budget

Knowledge base app (iOS & Android)

The same knowledge base content, delivered as a native mobile app for iOS and Android. Offline mode makes pre-downloaded articles available without a connection, push notifications flag important updates or release notes, and biometric login unlocks customer-specific content. Optionally available as a PWA for lighter use cases.

Offline modePush notificationsPWA optionMulti-language
Larger project · fixed sprint budget

Context-aware in-app help widget

An overlay widget that travels with the user inside your existing SaaS product or mobile app. Based on the screen route and the user's role, the widget recognises which article is relevant and shows it straight away, without the user having to search. An AI layer on top of the same content answers free-form questions based on your own knowledge base. Ideal for SaaS vendors who want a scalable self-service model: instead of expanding your support team with every new customer, the knowledge scales with you without adding ticket volume.

Route-aware overlayAI Q&A on your own contentRole-basedSDK integration

What you get at the end.

A production-ready knowledge base across all channels, plus the content pipeline and the measurement tools to make it worthwhile.

  • Public knowledge base siteMobile-first, responsive and SEO-optimised, with a sitemap and structured data so search engines index individual articles properly.
  • Mobile app or PWAiOS and Android (native or cross-platform, depending on your use case), with offline mode, push notifications and biometric login.
  • Editorial CMSOne place where your support team writes, translates and versions articles. Changes appear automatically on the site, app and widget.
  • Context-aware help widget SDKA JavaScript or mobile SDK your developers can add to your own product in ten minutes. It passes along route and role context so the widget shows the right articles.
  • AI search on your own contentA RAG-based answer engine that uses only your knowledge base articles as its source, with no hallucinations from the open web. Every answer includes source references.
  • Analytics dashboardInsight into which articles work, where users drop off, which searches return no results, and which ticket categories have declined since the knowledge base went live.
  • Maintenance contract (optional)Monitoring, dependency updates, security patches and ongoing development. Fixed monthly price, four response-time levels.

When a knowledge base works across all channels.

Six situations in which we often support clients with a knowledge base site and companion app. If you recognise one of them, we'd be happy to talk it through.

Software vendor

Support team drowning in basic questions

Customers keep asking the same questions because the documentation is buried. A searchable knowledge base plus context-aware help inside your own SaaS product takes these tickets off your support team's plate.

Hardware & IoT

Installation and troubleshooting flows

Customers install or repair your device themselves. A companion mobile app with step-by-step instructions, videos and a QR scan on the device itself saves a lot of call-outs.

Healthcare

Patient information in the app

After a consultation, patients look for information on their diagnosis, medication or lifestyle. A validated patient app with knowledge base content is safer and more reliable than Google.

Education

Student app with learning assignments

Assignments, reference material and explainer videos come together in a single app for students. Offline mode means it works on the train or without Wi-Fi.

Banking & insurance

Customer self-service and FAQ

Customers look for instructions, policy explanations or terms and conditions in the banking or insurance app. A context-aware help widget on top of your existing app lowers the barrier to self-service.

Retail

Product information via QR scan

QR codes on packaging or in store open the right article in your app straight away: a manual, video, warranty information or a ticket form. No detour via a generic homepage.

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 →

One content source, multiple channels.

The biggest risk in a knowledge base project is fragmentation. Three channels (website, app and in-product widget) invite three separate content streams that slowly drift apart. We prevent that with a headless content architecture. There is one place where your editorial team writes, and all three channels consume that content through an API. A change in the CMS appears within seconds on the website, in the app (online or after the next sync) and in the help widget.

The technical stack is deliberately modular: a headless CMS (Sanity, Strapi or Directus, depending on your editorial volume and existing tooling), a Next.js or Astro front end for the website, a React Native or native Swift/Kotlin app for mobile, and a lightweight JavaScript SDK for the widget. The AI search runs as a separate microservice that all channels can call through the same endpoint.

For integrations with your existing stack, we draw on our experience with API integrations: ticketing systems (Zendesk, Intercom, Freshdesk), product analytics (Mixpanel, Amplitude, PostHog), authentication (Auth0, Cognito, your own IdP) and CRM platforms (HubSpot, Salesforce) connect seamlessly, without your own team having to design that themselves.

How a knowledge base project works.

1

Introduction

A conversation in which we learn which questions your customers or end users ask most often, which channels you want to serve (website, app, in-product widget) and what content you already have in support tools or Notion pages.

2

Content audit and information architecture

We map your existing content, analyse ticket data and search logs (if you have them), and design a categorisation that works for both people and the AI search. The result: a concrete scope, screen flow and migration plan.

3

Building in sprints

A working build every two weeks. We start with the knowledge base website and the editorial CMS, then the mobile app, then the context-aware help widget. You test along the way, and so do end users. After a few sprints, the first tier is production-ready.

4

Content migration and release

We import existing articles from Intercom, Zendesk, Notion or Markdown files. Multilingual content is machine-translated first and then reviewed by your team. We coordinate the app store publication and SEO launch together with you.

5

Rollout and ongoing management

Analytics dashboards show which articles work and which searches return no results. Based on that, the knowledge base keeps evolving: we maintain the technology, your team writes the content.

Frequently asked questions.

What clients usually want to know before we start a knowledge base project.

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.

Talk to us about your knowledge base project.

A no-obligation introductory call of half an hour. We listen to where your customers or end users currently get stuck, look at your existing content and give you direction you can use straight away. Do you have other items on your list, such as a document management system or broader AI functionality? Then we'll map out the logical order.

Edit content