We build Kipwise to help teams learn better

Teams skip documentation because it costs time on top of the work, so we built Kipwise to capture knowledge where it is already shared: in Slack. Company growth gets stuck when knowledge stops flowing among teammates. The same question gets asked again, and the same mistake repeats because earlier learnings were never shared. Reid Hoffman, founder of LinkedIn, argues on his podcast Masters of Scale that no one can truly claim to be a master of scale and that the most successful scalers are infinite learners.

We had the same problem in our previous company. We tried to set up a knowledge base, but teammates were reluctant to document team knowledge because it took too much time.

We then asked ourselves: most of the knowledge we want to document is already communicated somewhere, for example in shared articles, custom videos and chat conversations. Why isn’t there a tool that converts them into saved knowledge easily?

So we started Kipwise, a tool that turns daily communication in Slack into saved team knowledge. For example, when you share an article in Slack, Kipwise turns it into a collaborative version where your team can add highlights and notes.

These annotations help teammates digest the content faster. To get a specific teammate to notice a point in the article, mention them in a note, and the annotation syncs to Slack so they get notified. Our reasoning is that a highlight with a one-line note takes seconds and keeps the context on screen, while a separate page takes long enough that people skip it.

All shared articles are saved automatically, and you can search them directly in Slack with the command /kipwise search [keyword].

Our next step is to support more knowledge formats, such as clipping Slack conversations and video annotations, to help teams share knowledge more smoothly.

Have a suggestion for the next knowledge format we should support? Email us at support@kipwise.com.

The first three letters of our name, Kipwise, stand for Knowledge Is Power.