Slab, Helpjuice, and the War Over Where Company Knowledge Lives

Somewhere in your company right now, someone is asking a question that has already been answered. Twice, probably. The answer exists. It was typed into a Slack thread in March, or buried in a Google Doc named "FINAL_v3," or lodged in the head of a colleague who is on vacation. The cost of not finding it looks like nothing on any spreadsheet, which is exactly why it is so large. That invisible tax - the re-asked question, the interrupted expert, the customer who emails support instead of reading the page that would have helped - is the entire market that Slab and Helpjuice are selling into.

They sell software in the same category, "knowledge base," and if you glanced at screenshots you might not tell them apart. Both give you a clean editor, organized articles, and a search box. But they arrive from opposite directions, and the difference is more interesting than the similarity. Slab is a venture-backed company out of San Francisco, founded in 2017, built for teams who want to write things down for each other. Helpjuice was started in 2011 by Emil Hajric, has never raised a funding round, and points its knowledge base outward - at your customers. Same problem. Two very different answers.

01The boring, expensive problem

Every growing company rediscovers the same truth on roughly the same timeline. At ten people, knowledge lives in everyone's head and that is fine. At fifty, the person who knows how deploys work becomes a bottleneck. At two hundred, the same onboarding question gets asked so many times that answering it becomes someone's unofficial part-time job. Tribal knowledge does not scale, and neither does a human repeating themselves.

The instinct is to blame storage. We need a place to put things. But the companies that have been doing this a while will tell you storage was never the hard part. The hard part is that a wiki nobody updates becomes worse than useless - a stale answer is more dangerous than no answer, because someone trusts it. The real product here is not a database. It is the design work that makes people want to keep the thing alive, and makes the next person actually find what got written.

A wiki nobody reads is a graveyard with a search bar. The work isn't storing knowledge - it's making the answer findable on the day someone needs it.

02Who are you writing for?

The cleanest way to tell these two apart is to ask a single question: who is the reader? A knowledge base written by insiders for insiders is a different object than one written for a stranger who is frustrated and one click away from emailing support. The vocabulary is different. The tone is different. The definition of "done" is different.

Slab leans internal. It is the team wiki - the place engineers document how the system works, where operations writes down the process, where a new hire goes to learn what everyone else already assumes. Reviewers consistently praise its editor and its search, and its scope is deliberately narrower than an everything-app like Notion or Confluence. It puts weight on reading and finding rather than on turning your workspace into a project-management suite. That focus is the pitch: do the wiki part extremely well.

Helpjuice leans external. It is most at home as a public help center - the searchable FAQ and documentation site that deflects support tickets before they are filed. The writing is for a customer, not a colleague, which changes everything downstream: how articles are structured, how search has to behave, how much polish the public-facing pages need. Helpjuice's own framing positions it against feature-heavy rivals as the clean, uncluttered customer knowledge base.

03The pricing page is the strategy

If you want to know who a software company thinks you are, skip the homepage and read the pricing page. It is the most honest document a startup writes, because it encodes an actual bet about how you will grow and what you will tolerate paying.

Slab charges per user. There is a free tier for up to ten people, then paid plans that start around $6.67 per user per month billed annually and climb from there, bundling an AI suite into the higher tiers. Per-seat pricing is a growth-friendly on-ramp and a quiet growth tax at the same time: cheap when you are small, and a line item that grows with every hire. It rewards teams that are careful about who gets a seat.

Helpjuice charges a flat fee. No free plan, a trial instead, and tiers that start around $120 per month for a small team and scale by bands of users rather than by the head. Flat pricing punishes the tiny team and rewards the large one: your two-hundredth employee reads the docs for the same price as your second. For a public help center - where the "users" are really your customers, and there could be millions of them - charging per reader would be absurd. The pricing model follows the reader.

There is a psychological wrinkle here too. Per-seat pricing quietly discourages the exact behavior you want from a wiki, which is for everyone to be in it. When adding a person costs money, someone starts rationing invites, and the knowledge base becomes a smaller room than it should be. Flat pricing removes that friction and says, in effect, invite the whole company. Neither is wrong. They are just optimizing for different rooms - a working team on one side, an open door to customers on the other.

04Two ways to build a company

Underneath the product story is a business story, and it may be the more instructive one. There are broadly two ways to build a software company. You can raise money, hire ahead of revenue, and try to grow into a large market before someone else does. Or you can charge from day one, stay small, and compound quietly for a decade. Slab took the first road. Helpjuice took the second, and has been on it since 2011.

The bootstrapped path is unfashionable and, in Helpjuice's case, a genuine moat. A founder who has run the same company for fourteen years without an exit or a round is not going anywhere, is not beholden to a board's timeline, and has survived a parade of better-funded competitors simply by charging money and continuing to ship. In a market obsessed with valuations, "we are still here, still profitable, still improving" is a stronger pitch than it sounds.

Slow software companies have a quiet advantage: they are still around to answer the phone in year fourteen.On Helpjuice's bootstrapped longevity

This is not to romanticize bootstrapping or dismiss venture capital. Slab's funding let it invest in the parts of a wiki that are genuinely hard - fast search across a large corpus, a good editing experience, integrations that meet teams where they already work. Those things cost money to build well, and buyers can feel the difference. The point is not that one path is virtuous and the other reckless. It is that the same category can support both, and that a founder gets to choose which set of trade-offs to live with for the next decade.

05What AI did and didn't change

You might expect large language models to have flattened this whole category. Why maintain a knowledge base when you can ask a chatbot? The opposite happened. A model can only answer from what your company actually wrote down. Point one at an empty or stale wiki and it will confidently make things up. The boring discipline of documentation did not become obsolete - it became the raw material for everything built on top of it.

Both companies read the moment the same way. Slab folds AI search and writing help into its paid tiers, treating assistance as core rather than a bolt-on. Helpjuice layers lighter AI search onto its help center. The framing has shifted from "store your knowledge" to "make your knowledge answer questions on its own," but the prerequisite is unchanged: someone still has to write the good answer once. The tools just raise the return on doing it.

06So which one

The honest answer is that they mostly do not compete for the same buyer, and choosing between them is really a question about your reader. If you are documenting for your own team - runbooks, processes, the institutional memory you do not want walking out the door - an internal wiki like Slab fits the job, and its per-seat pricing is friendly while you are small. If you are trying to deflect support tickets and give customers a place to help themselves, a customer help center like Helpjuice fits, and its flat fee gets cheaper per reader as you grow.

The larger takeaway sits above either product. Company knowledge tends to live in three places: someone's head, a Slack thread, and a document no one can find. Both of these companies are competing to be the fourth place - the one you actually check first. Whether you get there by raising venture money or by bootstrapping for a decade turns out to matter less than whether the answer is there when you look for it.