Built by people who got tired of asking the same questions.
Every team has a version of the same story. We had it too, at three different companies, before we decided to build the tool that should already exist.
Eliminate the new hire Slack question.
The pattern is universal: someone joins a team, hits a decision that needs context, asks in Slack, waits for three engineers to provide three different documents, and eventually pieces together an answer that will need to be re-derived when the next person joins.
That answer was already written down. It was in the incident retro, the architecture decision record, the ticket comment from eight months ago. The problem was never that the knowledge didn't exist. The problem was that retrieving and synthesizing it took more time than just asking someone.
Corpussage changes the equation. Ask once, get one sourced answer. Stop re-deriving what your team already knows.
Three prior jobs. The same problem at each one.
Aisha was an engineering lead at two fintech companies. Marcus built data infrastructure at a logistics startup. At every job, the same friction: knowledge existed but wasn't findable when you needed it.
The tools they tried were designed around search, which assumes you know what document to look for. But most questions are about context, decisions, and reasoning, not documents. The answer to "why did we pick gRPC here?" doesn't live in one file.
They co-founded Corpussage in Palo Alto in 2024 with a specific thesis: synthesis over search. The product returns an answer, not a list of links.
Founded 2024, Palo Alto, CA
The team
Four people, two time zones, one shared obsession with making institutional knowledge accessible.
Aisha Rahman
Previously engineering lead at two fintech companies. Built and scaled knowledge processes from 8 to 120 engineers. She ships the roadmap and talks to every customer.
Marcus Delacroix
ML infrastructure background from a logistics data startup. Designed the retrieval and synthesis pipeline. Obsessed with answer quality measurement and reducing hallucination surface.
Priya Okonkwo
Ran product at a B2B collaboration tool. Knows what makes knowledge tools succeed or fail with real teams. She turns user feedback into precise design decisions, fast.
Theo Bergmann
Previously embedded with engineering teams at a developer tools company. Guides beta customers from first connection to measurable knowledge improvement. Knows every integration quirk.