You're seeing the preview. Pro unlocks the full Niles teardown, the rebuild plan, every technical spec in the database, and 5 fresh report requests each month.
This report was generated by our Deep Research agent and may contain mistakes.
Did we get something wrong? DM @oscrhong and we'll fix it ASAP!
Niles was a Y Combinator Winter 2017 company that built a Slack-native knowledge bot designed to replace the internal wikis that companies create but never use.Founded in late 2016 by Mack Lu and Andy Kim in San Francisco, the product allowed employees to ask questions directly in Slack and receive answers drawn from a continuously updated knowledge base built from existing chat conversations and documents.
The core thesis was sound—institutional knowledge decay is a universal, costly problem—but the company shut down around early 2020 after approximately three years of operation, having raised only $120K in total funding and never growing beyond a two-person team.The most likely cause of failure was a combination of technical premature arrival and severe capital constraint: the natural language processing tools available between 2017 and 2020 were not reliable enough to deliver the seamless, accurate knowledge retrieval the product promised, and the team lacked the runway to iterate toward a solution.
Niles' story is a case study in correct problem identification paired with insufficient resources and technology to execute the vision.
Niles was founded in November 2016 by Mack Lu and Andy Kim, operating out of San Francisco. [1]
Mack Lu brought a strong product management pedigree to the company. Before Niles, he had completed Google's Associate Product Manager program—one of the most competitive product training pipelines in the industry—and had risen to Director of Product at Apartment List, a venture-backed rental marketplace. He studied Computer Engineering at Columbia University. [2] This background gave Niles immediate credibility in enterprise productivity tooling and likely opened early doors with potential customers.
The founding insight was personal. Lu described the problem in direct terms on Product Hunt: "I've personally felt the pain of creating wikis that nobody used and struggling to find information across multiple tools, and wanted something better." [3] This was not a problem discovered through market research—it was a frustration Lu had lived through at scale, managing product teams at companies where institutional knowledge was constantly being lost to Slack threads, buried Google Docs, and outdated Confluence pages.
The founding insight was also structurally sound. The failure mode of internal wikis is well-documented: they require deliberate, sustained effort to maintain, and that effort competes with the immediate demands of daily work. The result is that most wikis become stale within months of creation. Lu's bet was that a tool embedded directly in Slack—where knowledge was already being created organically through conversation—could capture and surface that knowledge without requiring any additional behavioral change from employees.
Y Combinator accepted Niles into its Winter 2017 batch, providing early institutional validation of the thesis and $120K in seed funding alongside Eudaimonia Capital. [4] [5]
Andy Kim's specific background, technical role, and eventual departure from the company are not documented in available sources. The YC company profile lists only Mack Lu as founder, and Lu was the sole public-facing representative of the company across press coverage and Product Hunt. [6] Whether Kim departed early or remained through the shutdown is unknown.
November 2016 — Niles AI founded by Mack Lu and Andy Kim in San Francisco, CA. [1]
Early 2017 — Niles accepted into Y Combinator Winter 2017 batch; raises $120K seed round from YC and Eudaimonia Capital. [5]
March 17, 2017 — TechCrunch publishes a dedicated article on Niles, describing it as "an alternative to that internal wiki that every company has and no one uses." [7]
March 21, 2017 — Niles presents at YC W17 Demo Day 2; TechCrunch covers it as "a wiki you can talk to in Slack." [8]
Read the complete post-mortem, the rebuild playbook, and the exact reasons Niles is still worth studying now.