English
Request a call Open the demo
Internal system for SMEs

Knowledge base

Your company's know-how and process descriptions are kept in one shared collection, linked directly to the projects, the customers and the daily tasks. Your colleagues find the guides where they already work. The built-in search looks through the full text of every article, not just the titles.

Why this page exists

What does it actually fix?

The search nobody puts in the calendar

You need a contract signed two years ago, and nobody knows who saved it or where. Three colleagues go through their mailboxes, and what turns up is a version nobody is sure is the final one. It happens several times a week, and it always takes time from whoever is busiest.

The question answered for the tenth time

How do we request leave? Who approves overtime? Which subcontractor do we have a framework agreement with? The answers exist, but they are not written down, so the same key people are interrupted again and again.

Versions you cannot vouch for

The same document sits in a shared folder, in an email attachment and on someone's laptop, and each copy is slightly different. Nobody knows for certain which one is the current, official version.

The knowledge that resigns

When a key person leaves, what they knew about customers and processes leaves with them, because nobody ever asked them to write it down.
Our approach

A wiki lives by being opened

Internal wikis are rarely abandoned because of their content. They are abandoned because they sit somewhere else, behind another login, and after a fortnight nobody opens them. That is why, in IntrApp, the write-up is where the work is, and the search reads the body of each article rather than only its title.

1 place the process is written down
~30 min automated setup
0 implementation fee
Knowledge base

Write it down once, so you do not explain it again

The knowledge base is your company's internal wiki, a shared collection of articles for policies, process descriptions, how-to guides and answers to the questions that keep coming back. Instead of asking you, your colleagues search for the answer and find it in seconds.

Categories in your own words

There is no fixed structure you have to adopt. You organise the articles the way your company actually works, from internal policies and supplier processes to a new colleague's first week.

Formatted, with files attached

You can use subheadings, lists and emphasis, and attach files directly to the article. That way a process description is easy to read and to follow step by step.

Onboarding from day one

The answers to new colleagues' most common questions are already in the system, so learning the ropes does not take up everyone else's working time.
The knowledge base in IntrApp, listing the articles with their category and creation date, from policies to onboarding.
How it fits together

The write-up is where the work is

The knowledge base is useful because it is connected to everything else:

Who sees what

The knowledge base is deliberately flat

Anyone with access to the knowledge base sees every article, and that is a deliberate decision. An internal wiki is only worth something if nobody has to wonder whether they are allowed to read a process description, and nobody should have to maintain a permission table so that a colleague can find out how to request leave. Files and notes work differently, because they do a different job, and each has its own page.

What you will not find here

An internal wiki, not a compliance archive

There are no multi-step approvals, no retention policies and no regulatory archive. If you work in a regulated industry and have to prepare for official audits, a dedicated system will serve you better.

The knowledge base is for people inside the company, not a public customer portal. Having somewhere to put your knowledge does not fill it by itself. What realistically happens is that over the next six months you write down the things you currently explain every week, and after that you only need to keep them up to date.

Frequently asked

What most people ask at this point

We did not make these questions up; they are the ones prospective customers ask us most often. None of the answers is that you will get used to it.

What makes sure the team will actually use it?

Knowledge bases in a separate application often go unused, because nobody wants to log in to yet another place. In IntrApp the guides and how-tos sit right next to the daily work, so nobody has to go and look for them elsewhere.

Do we need training?

No. IntrApp has a built-in manual and a step-by-step walkthrough, so people find their own way in. There are no training days, and nobody has to become the in-house expert.

What does it cost to start?

The automated setup takes about half an hour. There is no implementation fee and no compulsory consulting day.

How flexible is the trial?

During the trial you work in your own system with your own data, and if it turns out not to be right for you, you can cancel at any time.
If something is missing

Ask, and you may not have to pay for it

If a template or a way of categorising is missing, tell us. If roughly three quarters of our customer base would use it, we build it for free, and every customer gets it. We decide whether a request falls into that group, because we can see the whole customer base. We do not promise a delivery date, but we do promise that the request goes into development. Anything specific to your company is built under a separate agreement.

Take a look inside

The demo shows the whole system with sample projects, sample customers and sample documents, with no sign-up and no card, and you cannot break anything because it resets every night. To try it with your own data, that is what the trial is for.

Want to see how this would work for you? We will call you back.

Got a question? Rather talk to someone?

One of our team will get in touch within one working day.

When can we call?

If you add it, we send you a summary of our call.