Public site architecture

Raw source preview

Raw, unprocessed file text shown below.

---
title: GTM Website - Site Architecture
status: active
created: 2026-04-09
updated: 2026-04-13
notes: Canonical site architecture aligned to the live marketing site and the current proposition.
---

# <un>peel Website - Site Architecture

## Site goal

The site is built as one coherent messaging system for enterprise insight teams.

- Core outcome: help insight teams answer faster, defend the work, and validate the answer against connected evidence
- Mechanism: sharpen research before launch, protect data quality during fieldwork, and connect evidence across studies so teams can validate later answers against corroborating evidence
- Proof posture: Research Guard and Trust Centre earn trust early; Insight Navigator helps teams validate answers through connected evidence
- Secondary framework: Design -> Protect -> Validate

---

## Live pages

| Page | URL | Purpose |
|---|---|---|
| Homepage | `/` | Top-funnel strategic page. Frames the business-speed problem, the team outcome, and the trust-led proposition. |
| Pricing | `/pricing` | Commercial expression of the same proposition. Explains how pricing scales with workflow scope, trust infrastructure, and organizational reach. |
| Company | `/company` | Minimal company-context page for pilot-stage credibility. |
| Privacy | `/privacy` | Pilot-stage privacy notice. |
| Terms | `/terms` | Pilot-stage site terms. |
| Platform overview | `/platform` | Stub page. Content to be defined. Explains what sits inside <un>peel and how the confidence framework applies across all tools. |
| Surveys | `/platform/surveys` | Tool page for quantitative research workflow. |
| Discussion Groups | `/platform/discussion-groups` | Tool page for async qualitative discussion workflow. |
| Guided Interviews | `/platform/guided-interviews` | Tool page for faster qualitative depth at scale. |
| Insight Navigator | `/platform/insight-navigator` | Tool page for connected evidence, source-traceable retrieval, and cross-study corroboration that help teams validate answers. |
| Research Guard | `/capability/research-guard` | Capability page explaining the pre-launch methodological review layer. |
| Trust Centre | `/capability/trust-centre` | Capability page explaining the live respondent-quality layer. |

---

## Retired pages

Audience pages are no longer part of the public architecture.

- `/enterprise` -> redirects to `/`
- `/agencies` -> redirects to `/`

Reason: the homepage now speaks directly to enterprise insight buyers without needing separate audience positioning pages.

---

## Navigation structure

```
Logo (top left)   |   Platform   Pricing   Company   [Book a demo]
```

- `Platform` -> dropdown with:
  - Platform overview (link to `/platform`)
  - Tools in <un>peel
  - Trust layer
- `Pricing` -> `/pricing`
- `Company` -> `/company`
- `Book a demo` -> `/#contact`

Footer links:

- `Company`
- `Pricing`
- `Contact`
- `Privacy`
- `Terms`

---

## Homepage section map

| Section | Role | CTA |
|---|---|---|
| Nav | Top-level orientation plus product browse paths | `Book a demo` -> `#contact` |
| Hero | Lead with a more concrete promise than the old relevance-only framing | `Book a demo` and `See how it works` |
| Problem | Name the business-speed threat and loss-of-relevance risk | - |
| Solution | Explain the system through Design -> Protect -> Validate | - |
| Features | Show the research tools teams buy and the trust layer that comes with them | Feature-level `Learn more` links |
| Showcase | Make the trust layer visible through product screenshots | Capability detail links |
| Proof | Back the proposition with evidence-led claims | - |
| Social proof | Reinforce traction with pilot-customer signal without overclaiming the proof level | - |
| Pricing bridge | Connect the homepage story to the standalone pricing page | `See pricing` |
| Contact | Capture demo interest inline | `Send message` |
| Footer | Add company/legal scaffolding and pilot footprint signal | - |

---

## Product pages

Product pages are mid-funnel evaluator pages. Their job is to answer:

- what the tool does
- when a team uses it
- why it matters inside this platform rather than as a standalone workflow

Each product page should stay product-led, then connect back to the wider trust system through capability links.

Detail pages also include:

- breadcrumb orientation
- sibling links to other product or capability pages

| Page | URL | Source doc |
|---|---|---|
| Surveys | `/platform/surveys` | `website/product-pages/survey-platform.md` |
| Discussion Groups | `/platform/discussion-groups` | `website/product-pages/discussion-platform.md` |
| Guided Interviews | `/platform/guided-interviews` | `website/product-pages/ai-interviews.md` |
| Insight Navigator | `/platform/insight-navigator` | `website/product-pages/insight-navigator.md` |

Legacy `/product/*` routes redirect to corresponding `/platform/*` routes. Old slugs (survey-platform, discussion-platform, ai-interviewer) also redirect to new slugs.

---

## Capability pages

Capability pages are mid-funnel proof pages. Their job is to answer:

- why this approach is credible
- what is actually different under the hood
- why that difference helps the team produce work it can stand behind

| Page | URL | Source doc |
|---|---|---|
| Research Guard | `/capability/research-guard` | `website/capability-pages/research-guard.md` |
| Trust Centre | `/capability/trust-centre` | `website/capability-pages/trust-centre.md` |

---

## Content guardrails

- Do not lead with `Research OS`
- Do not imply AI replaces the researcher
- Do not open with breadth before proof
- Do not reintroduce separate audience-page messaging
- Do not make pricing feel detached from the proposition
- Do not invent company facts that are not ready to publish