The wiki that refused to raise again - and still landed A24, Ramp and Asana

Somewhere in your company, right now, someone is typing "hey, quick question" into Slack. The answer exists. It was written down once, in a doc, in a thread, in a comment nobody bookmarked. Finding it will take four pings and twenty minutes. Slab was built for that exact moment - the small, daily, expensive act of asking a question that has already been answered.

Slab is a knowledge base and wiki. Companies use it to write down how they work - onboarding guides, engineering runbooks, sales playbooks, meeting notes, the reasoning behind decisions - and to find those things again later without a scavenger hunt. It is deliberately narrow. It does not want to be your project tracker, your database, or your second brain. It wants to be your company's memory, and it wants that memory to be trustworthy and fast to search.

The company was founded in San Francisco in 2016 by Jason Chen, Anvisha Pai, James Hsi and Chengyin Liu. That founding team had scaled coordination at hypergrowth companies - the kind of places where the org chart changes faster than the documentation - and had watched institutional knowledge quietly evaporate. Slab is, in a sense, a scar-tissue product: a tool built by people who kept losing the same knowledge and got tired of it.

01 / The founderThe person who already built the editor

Before Slab, Jason Chen made a thing you have probably used without knowing it. He created Quill, an open-source rich-text editor that quietly powers the writing surfaces of countless other apps. He also founded Stypi, a collaborative editor that Salesforce acquired. The pattern is hard to miss: Chen has spent much of his career on the deceptively hard problem of making text feel good to write on a screen.

That history matters, because Slab's core bet is not a feature list. It is that the writing experience itself is the product. A wiki nobody enjoys writing in becomes a wiki nobody writes in, which becomes a graveyard of stale pages. Slab's editor - built on Quill - is the answer to that failure mode. Formatting behaves. Collaboration is real-time. The page does not fight you.

02 / The productWrite it once, actually find it later

Two problems sink most internal wikis. The first is that writing in them is a chore, so people don't. The second is that even when things get written, nobody can find them - so the wiki becomes a place knowledge goes to be forgotten. Slab attacks both.

On the writing side, there is the clean editor, hierarchical topics so pages have a home, multi-topic labeling, and real-time collaboration. On the finding side, there is what Slab calls Unified Search: search that spans your Slab content and connected tools - Slack, Google Drive, GitHub - and ranks results by how much people actually read, link to, and mention them. Your knowledge does not live in one tool, and Slab is honest about that.

The feature that best captures Slab's temperament is verification. Any post can be verified by an owner, so a reader can tell at a glance whether a page is current or quietly rotting. It is a small thing. It is also the difference between a wiki you trust and one you second-guess.

03 / The customersA24, Ramp and a biotech walk into a wiki

Slab's customer list is a good party guest - eclectic and slightly surprising. More than 1,000 companies use it, and they don't share an industry so much as a symptom: too much knowledge, scattered across too many heads and tools.

The studio behind a run of indie films keeps its internal knowledge in the same tool as a fintech that moves corporate money and a biotech that runs experiments. Different worlds, one shared frustration - and that breadth is the tell. Knowledge loss is not a vertical problem. It's a company problem.

04 / The business$2.2M in 2018, and then silence

Here is the part that makes Slab unusual in a room full of venture-backed software companies. It raised $2.2M in early 2018 - from Matrix Partners, CRV and NEA - and then did not raise again. Eight years, no new round, while it grew to roughly $3M in annual recurring revenue and past a thousand customers. In an era of nine-figure war chests, Slab funded its growth mostly out of the register.

The model is straightforward B2B SaaS: per-user subscriptions with a free tier for up to 10 users, a Startup plan around $6.67 per user per month, a Business plan near $12, and enterprise options above that. No exotic monetization. The discipline is the story - fewer people to keep happy, so the roadmap stays about knowledge instead of chasing every adjacent category.

05 / The marketScalpel, not Swiss Army knife

Slab lives in a crowded neighborhood. Notion, Atlassian's Confluence, Coda, Guru, GitBook, Nuclino and Document360 all want a piece of the same job. Slab's positioning is restraint. Notion wants to be your everything - docs, databases, project boards, the works. Confluence carries the weight of enterprise history and setup burden. Slab decided to be one thing, a fast and trustworthy company knowledge base, and to be very good at it.

That choice shows up in who picks it. Teams migrating off Confluence because it felt heavy, or evaluating Notion but wanting something with a cleaner editor and lower setup cost, tend to land on Slab. Its AI features are intentionally narrow - a quiet autofix that catches typos as you write, rather than a bolted-on chatbot. In a market sprinting to stuff AI into every corner, that measuredness reads as a point of view.

06 / The timelineHow it got here

07 / QuestionsFrequently asked