> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getwhys.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Key concepts

> The building blocks that show up across GetWhys.

A short glossary so the rest of the documentation makes sense.

<AccordionGroup>
  <Accordion title="Buyer Validation Platform">
    How GetWhys describes the category it occupies. The validation layer that sits across the tools your team uses to write and ship, ensuring everything that goes to market reflects what buyers actually think.
  </Accordion>

  <Accordion title="Validation Layer">
    GetWhys' primary role in your stack. Not a research tool you visit once a quarter. A continuous validation layer that touches every piece of content, every campaign, every sales conversation before it leaves the building.
  </Accordion>

  <Accordion title="Buyer Signal Database (GetWhys Data)">
    The proprietary corpus of research interviews that powers the platform. Every interview is a 45 to 60 minute conversation with a real B2B buyer, user, or implementer, conducted and moderated by the GetWhys research team. The depth and specificity of this data is what makes the validation meaningful instead of automated.
  </Accordion>

  <Accordion title="Organization Data">
    Your team's first-party knowledge: sales calls, win/loss interviews, customer research, internal docs. Once it's uploaded, it's searchable alongside the buyer signal database. See [Organization Data](/features/organization-data).
  </Accordion>

  <Accordion title="Inside-Out vs Outside-In Data">
    **Inside-out data** is gathered from inside your organization: call recorders, CRM, internal research. **Outside-in data** is everything else: research interviews from outside your customer base, the open web. GetWhys searches both kinds in parallel so answers reflect what your team has heard *and* what the broader market is saying.
  </Accordion>

  <Accordion title="Chat">
    The conversational research interface. Ask a question, get a source-linked answer drawn from the buyer signal database, your Organization Data, and (when useful) the open web. See [Chat](/features/chat).
  </Accordion>

  <Accordion title="Personas">
    The buyers your team writes for, encoded so GetWhys can apply them. Each persona captures titles, challenges, motivations, KPIs, and where the buyer gets their information. Required for [Message Testing](/features/message-testing) and used as context across Chat. See [Personas](/features/personas).
  </Accordion>

  <Accordion title="Brand Voice">
    A structured description of how your company writes. Each Brand Voice Characteristic has a description, do's, and don'ts. Message Testing uses Brand Voice to flag drafts that drift off-brand. See [Brand Voice](/features/brand-voice).
  </Accordion>

  <Accordion title="Messaging Frameworks">
    The positioning, value props, and key messages your GTM team builds around. Codify them once in GetWhys and they get applied automatically when you ask Chat to draft or evaluate content. Frameworks can be org-wide or scoped to a specific Project. See [Messaging Frameworks](/features/messaging-frameworks).
  </Accordion>

  <Accordion title="Message Testing">
    The tool that evaluates a draft against your Personas and Brand Voice. You see what's landing, what's not, and why, tied back to research. Use it to validate before you ship. See [Message Testing](/features/message-testing).
  </Accordion>

  <Accordion title="Projects">
    A container for a body of work: a launch, a campaign, a competitive review, a persona refresh. Each Project gets its own chat history, artifacts, research requests, and (optionally) Project-level messaging frameworks. See [Projects](/features/projects).
  </Accordion>

  <Accordion title="Artifacts">
    Anything you produce inside GetWhys that you've decided to save: drafted content, frameworks, generated personas, competitive teardowns. Edit, share, revisit. See [Artifacts](/features/artifacts).
  </Accordion>

  <Accordion title="Research Requests">
    A way to commission new research interviews when the buyer signal database doesn't already have what you need. Unlimited for Pro users. No per-project fee. The GetWhys research team handles recruiting and moderation. See [Research Requests](/features/research-requests).
  </Accordion>

  <Accordion title="AnswerSLA">
    The guaranteed turnaround time for a Research Request, in business days. Default is 10 business days; Scale customers can accelerate to 5. See [Research Requests](/features/research-requests) for the holiday schedule.
  </Accordion>

  <Accordion title="Source-Linked Insights (Citations)">
    Every claim in a GetWhys answer links to its source: a research interview, an uploaded document, or a web result. Click any citation to see the underlying material. The "how do we know?" answer is built into the product. See [Citations](/features/citations).
  </Accordion>

  <Accordion title="MCP (Model Context Protocol)">
    The protocol that lets GetWhys plug into Claude, Cursor, Typeface, custom agents, and other AI tools. Your team already lives in those tools — through MCP, GetWhys becomes the buyer intelligence layer behind every AI workflow they run. See [MCP integration](/integrations/mcp).
  </Accordion>
</AccordionGroup>