Where KAAS sits, and why each adjacent category falls short.

Knowledge as a Service sits at a four-axis intersection none of the existing categories occupy. The axes are: capture method (structured AI-guided interview with a trained worker), output form (a continuous intelligence layer refreshed weekly), buyer (the COO, CFO, or CSO building a new revenue line), and monetization model (three-endpoint distribution priced as infrastructure). The empty cell is the combination. Outset has the first axis in close form and loses the last two. Interloom has axes two and four in partial form and loses axis one. Nielsen has axis two and partial four. Nobody has all four. That is the category.

Below, each adjacent category is described against the same three stages we use to talk about KAAS: Gather (do they originate net-new structured knowledge from humans?), Codify (do they turn raw input into a continuously refreshed structured layer with comparability and time-series?), and Monetize (do they distribute the layer to multiple revenue endpoints, including downstream third parties and AI agents?). For each category, the specific structural reason the configuration is incompatible with KAAS.

[ 01 ]  ·  VOICE OF CUSTOMER

Examples: Qualtrics, Medallia, InMoment, SurveyMonkey Enterprise.

GATHER

Partial

CODIFY

Partial

MONETIZE

No

The subject is the customer. The respondent base is anonymous and untrained. Fidelity per response is low because the respondent has thirty seconds of attention and no domain context. KAAS interviews a trained worker who has spent years in front of the customer and carries structured, accumulated understanding the customer themselves does not have access to.

Architectural blocker for VoC platforms: the entire stack assumes pre-defined questions. Probing is an anti-pattern in their schema. The capture instrument caps at the survey ceiling. Wrong respondent, wrong instrument, wrong economics.

[ 02 ]  ·  EMPLOYEE EXPERIENCE AND ENGAGEMENT

Examples: Glint (Microsoft), Culture Amp, Lattice, Medallia EX, Qualtrics EX.

GATHER

Partial

CODIFY

Partial

MONETIZE

No

The question these platforms answer is “how do your employees feel about working here.” The question KAAS answers is “what do your employees know about the market, the customer, the product, the operation.” Different output, different buyer (CHRO versus CFO/COO/CSO), different price point, different consumer. An engagement score is a thermometer. The KAAS layer is a sensor network.

Architectural blocker: these platforms optimize for participation rate and anonymity. KAAS optimizes for fidelity per interview, which requires structured probing and time. The instruments are incompatible.

[ 03 ]  ·  KNOWLEDGE MANAGEMENT

Examples: Notion, Guru, Glean, Bloomfire, Confluence.

GATHER

No

CODIFY

Partial

MONETIZE

No

These tools assume the knowledge is already articulated and just needs to be findable. The hard problem in KAAS is the opposite: the knowledge is in the human's head and has never been written down. A KM tool serves the thirty percent that was already documented. KAAS captures the seventy percent that was not.

Architectural blocker: monetization is seat-based SaaS with no downstream distribution. Even if a KM tool shipped an AI-interview module, the buyer (head of knowledge management, IT) does not have authority over a brand-partner API.

[ 04 ]  ·  SYNTHETIC USERS AND AI RESPONDENTS

Examples: Synthetic Users, Evidenza, parts of Outset's offering.

GATHER

No (by definition)

CODIFY

Partial

MONETIZE

No

The respondent is an LLM persona. This category is the direct philosophical opposite of KAAS. They simulate humans because humans are expensive. We interview humans because the human is the only place this knowledge lives. If KAAS is correct, this category is selling fiction at scale. Both can exist commercially; only one of them produces proprietary data.

Architectural blocker: a synthetic respondent cannot surface anything the model did not already know. The output is statistically aligned to the model's priors. The proprietary signal that comes from the actual worker observing an actual customer never enters the dataset.

[ 05 ]  ·  SALES AND FIRMOGRAPHIC INTELLIGENCE

Examples: Dun & Bradstreet, ZoomInfo, LiveRamp, Acxiom (IPG).

GATHER

Yes

CODIFY

Yes

MONETIZE

Yes

The monetization model is the closest match in the entire landscape. Multi-tenant API distribution priced as infrastructure. The difference is what is being captured. Data brokers harvest digital exhaust, transactions, and firmographics. KAAS harvests intent and knowledge. Acxiom can tell you what someone bought. Only KAAS can tell you why the customer almost bought something else, because only the beauty advisor who stood next to her knows.

Architectural blocker: their capture engine is built for exhaust ingestion. Building the AI-interview muscle requires research methodologists and a protocol library. The market for senior qualitative methodologists is small, and KAAS-first players will pay more. Retrofitting produces panel-buy data of the lowest fidelity in the landscape.

[ 06 ]  ·  CUSTOMER AND SALES CONVERSATION INTELLIGENCE

Examples: Gong, Chorus, Cresta, Sierra, Forethought, Decagon.

GATHER

Yes (in support and sales contexts)

CODIFY

Partial

MONETIZE

No

These platforms listen to live conversations to coach the worker or deflect the customer. The capture volume is high. The domain is wrong (support resolution, sales compliance), the buyer is wrong (VP Support, VP Sales Operations), the monetization model is wrong (per-seat SaaS). They extract compliance from the worker. KAAS extracts strategic understanding from the worker.

Architectural blocker: the worker is performing under evaluation when these tools listen. The transcript is rich and the content is reactive, defensive, and shallow on the dimensions KAAS cares about. The same advisor producing one-word answers on a call would answer with three minutes of detail under the KAAS interview protocol.

[ 07 ]  ·  TALENT INTELLIGENCE AND WORKFORCE DATA

Examples: Eightfold, Gloat, Revelio Labs, LinkedIn Talent Insights.

GATHER

Yes

CODIFY

Yes

MONETIZE

Partial

They describe the worker. KAAS interviews the worker. They model who the worker is on paper. We extract what is in the worker's head. Eightfold can tell L'Oréal which beauty advisor has the strongest skill profile. KAAS can tell L'Oréal what that advisor saw last Tuesday when a customer rejected a foundation.

Architectural blocker: skills ontologies come from resume parsing and public profile scraping. The signal ceiling is whatever the worker chose to put on their LinkedIn. The tacit observation never made it onto a public profile.

[ 08 ]  ·  MARKET RESEARCH FIRMS

Examples: Nielsen, Kantar, NIQ (formerly NPD), Ipsos, Forrester, Gartner.

GATHER

Yes

CODIFY

Partial

MONETIZE

Partial

The closest adjacent in spirit. The difference is structural. Their output is a document; ours is a live API endpoint and an agent feed. Their refresh cycle is quarterly or annual; ours is weekly. Their unit economics assume one finished study sold many times. Ours assume one client owns the proprietary layer and resells it to its own ecosystem.

Architectural blocker: their billable model is incompatible with productized infrastructure. Pivoting destroys their existing P&L. The buyer they have spent decades selling to (marketing and strategy at a single firm) is not the buyer of a KAAS deal (the COO building a revenue line).

[ 09 ]  ·  CONVERSATIONAL AND QUALITATIVE RESEARCH AT SCALE

Examples: Outset.ai, Listen Labs, User Interviews, Discuss.io, dscout.

GATHER

Yes

CODIFY

Partial

MONETIZE

No

This is the closest mechanical match to the Gather stage. Outset.ai ($51M total funding through December 2025, Series B led by Radical Ventures) and Listen Labs ($69M raised) both run AI-moderated interviews at scale. The structural difference is downstream. They sell a better research project. We sell a new business unit. Outset is KAAS-shaped at the input and SaaS-shaped at the output. The Series B language already signals a rotation into customer experience management (Qualtrics/Medallia territory) rather than workforce intelligence.

Architectural blocker: the buyer they sell to (VP Research, head of insights) does not have the authority or appetite to convert the layer into a brand-partner API. The third endpoint is structurally unreachable from that buyer relationship.

[ 10 ]  ·  WORKFORCE KNOWLEDGE CAPTURE FOR AI AGENTS

Examples: Interloom (Munich), Tacit AI, and a tail of YC W25 / S25 entries.

GATHER

Partial

CODIFY

Yes

MONETIZE

Partial

Interloom (€14.2M / $16.5M seed, March 2026, DN Capital lead, Bek Ventures and Air Street Capital co-investing) is the closest competitor in the entire landscape. They believe in tacit knowledge. They believe in productization. They explicitly position as infrastructure for AI agents.

The structural gaps versus KAAS are three. First, their capture is reactive: they capture the moment of expert resolution alongside an AI agent, opportunistic rather than scheduled. Ours is proactive: we interview the whole workforce on a cadence. Second, their domain is operations (how problems get resolved). Ours is strategy (what the worker knows about the market, the brand, the customer). Third, their monetization is single-tenant agent memory. Ours is multi-endpoint with downstream third-party revenue.

What would move them toward us: hiring a vertical head in retail, beauty, or restaurants, and shipping a multi-tenant knowledge marketplace API. If they do either, the gap closes. Until then they are operations memory infrastructure, sold to IT and automation buyers.

THE FOUR-AXIS INTERSECTION

One configuration, no incumbents.

The KAAS configuration is the simultaneous occupation of four axes:

  1. Capture method. Structured AI-guided interview with a trained worker. Net-new knowledge originated from the human who holds it.
  2. Output form. A continuous intelligence layer with comparability across markets and time, refreshed weekly. A queryable layer rather than a finished study.
  3. Buyer. The COO, CFO, or Chief Strategy Officer building a new revenue line. The operator with authority over brand-partner distribution.
  4. Monetization model. Three-endpoint distribution: internal dashboard, brand-partner API, AI-agent retrieval feed. Priced as infrastructure with a percentage-of-downstream logic, capped by an enterprise floor.

No category currently sits in all four cells. Most players have one or two axes in close form and lose the others to structural constraints (wrong buyer relationship, wrong instrument architecture, wrong billing model, wrong consent posture). That four-cell configuration is the category KAAS occupies.