The Company Wiki Nobody Reads, and Four Bets to Change That

Somewhere in your company there is a page that answers the question you are about to Slack a colleague. It explains the deploy process, or the refund policy, or why the thing that broke last March broke. Someone wrote it. It is thorough. And you will never find it - so you will ask the colleague, who will re-explain it, and the page will sink another inch into the archive. This is the quiet failure that an entire software market exists to fix.

The market has a name that makes eyes glaze over: knowledge management. Strip the jargon and the job is simple. Take what a team already knows, put it somewhere, and make it findable again on a random Tuesday when the person who wrote it down is in a meeting or has left the company. Four companies attack that job from wildly different angles. Nuclino wants to be fast. Tettra wants to live in your chat. Notion wants to be everything. SAP wants to be the system of record for a global enterprise. Put them on one line and you can see the whole category.

The real enemy isn't a competitor

Ask anyone who has rolled out an internal wiki what killed the last one and you will not hear a rival product's name. You will hear two words: stale and buried. A knowledge base rots the moment the world moves and the page does not. Worse than an empty wiki is a wiki that answers confidently and wrongly, because a confident wrong answer costs more than no answer at all. That is the shared enemy. Every company here is really selling a defense against their own product becoming a graveyard.

Tettra took that threat most literally. Founded in Boston in 2015 by Andy Cook and Nelson Joyce, it built content verification into the core: a page gets an owner, an owner gets a nudge, and readers can see whether an answer is trusted or overdue for a check. The pitch is not "store more." It is "let people trust what they find." That is a different bet than a bigger editor, and it is the more honest one.

Tettra's other founding insight was about location. It launched on Slack and grew by answering the one question every team keeps typing: where is that doc? Instead of asking people to leave their conversation, open a separate app, and search, it put capture and answers inside the place the question was already being asked. That is not a feature list. That is a read on human behavior - people will not go where the knowledge is, so the knowledge has to come to where the people are.

Speed is a feature people underrate

Nuclino, launched the same year, made the opposite kind of bet - not about location but about friction. Its whole personality is speed and simplicity. Pages open instantly, editing is real-time, and you can arrange documents as nested lists, boards, tables, or a mind-map style graph. There is no configuration ceremony. The wager is that a wiki people find pleasant and quick to use will get used, and a powerful one that feels like homework will not.

This sounds minor until you have watched a team abandon a heavier tool. Every second of load time and every extra menu is a small tax, and taxes compound. Nuclino's teams tend to pick it precisely because it does less. That is a genuine strategy, not a shortfall. In a category where the failure mode is abandonment, "fast and few features" is a defensible moat.

Flexibility is a gift until it isn't

Notion is the tool most people in this conversation have actually used. Founded in 2013 by Ivan Zhao and Simon Last, it reached a reported $10 billion valuation in a 2021 round by turning documents into building blocks. Notes, databases, tasks, wikis - you assemble your own workspace out of components. It is genuinely delightful, and that delight is why it spread through startups the way it did.

The catch is baked into the strength. When a tool lets you structure anything, teams structure things inconsistently, and pages get created faster than anyone imposes an order on them. Six months in, a Notion workspace can hold every answer you need and still fail the Tuesday test, because there are four pages about onboarding and no one knows which is current. This is the recurring critique in comparisons with focused tools like Tettra and Nuclino: freedom to build your own system is also freedom to build a mess. Notion is a fantastic default. It is not automatically a knowledge base, and treating it as one without discipline is how the graveyard fills.

The one that has done this since 1972

SAP sits at the far, unfashionable end of the line, and it is easy to leave it out of a startup comparison - which is exactly why it belongs in one. Founded in 1972 by five former IBM engineers to build real-time enterprise software, SAP has spent five decades organizing the knowledge that runs large companies. Its knowledge tools are not there to look nice in a demo. They exist to tie documentation to ERP and core business processes at a scale where a wrong answer has compliance and money attached to it.

Compared to Notion, SAP is heavy, and the setup is not a weekend project. But the two are not really solving the same problem. A startup wiki treats knowledge as culture - a way to onboard fast and stop repeating yourself. An enterprise treats it as infrastructure - a governed, integrated part of how the business runs. SAP versus Notion is less a product fight than a disagreement about what a company's knowledge is for.

What to actually take from this

The useful lesson is not "pick the winner." There is no single winner, because the four are aimed at different teams. The lesson is to buy for the workflow you already have, not the one you wish you had. If your team lives in Slack and wants answers it can trust, Tettra's model fits. If you want a quick, low-friction wiki, Nuclino's speed is the point. If you have builders who enjoy designing their own system and will maintain it, Notion rewards that energy. If you are a global enterprise that needs knowledge wired into core processes, SAP is playing a game the others are not.

Underneath all four is the same quiet truth, and it is worth stealing for whatever you are building. Your team almost always already knows the answer. The entire category exists to shorten the distance between the question and the page - to win the search box, not the editor. Store everything and you have a warehouse. Make the right page appear in ten seconds and you have a knowledge base. That gap is where these companies compete, and it is the only part that ever mattered.