Website pre-launch checklist

Raw source preview

Raw, unprocessed file text shown below.

---
title: GTM Website - Pre-Launch Checklist
status: active
created: 2026-04-13
updated: 2026-04-17
purpose: Track operational and launch-readiness items that are intentionally deferred but must be resolved before broader sharing or launch.
---

# <un>peel Website - Pre-Launch Checklist

## Before broader buyer sharing

- [ ] Confirm the Showcase images are real product screenshots and the asset paths resolve correctly
- [ ] If real screenshots are not ready, temporarily remove the Showcase section rather than ship broken or placeholder visuals
- [ ] Confirm the hero screenshot is a real product image and not a generic placeholder
- [ ] Finalize whether the current anonymous pilot quotes are acceptable for limited sharing, or replace them with named or better-contextualized proof

## Before compliance-sensitive buyer conversations

- [ ] Replace the temporary contact-form route with a dedicated privacy email or named contact route on the privacy page
- [ ] Add data-controller details once available
- [ ] Confirm whether any analytics or non-essential cookies are running
- [ ] If analytics or non-essential cookies are active, add the required consent mechanism and update the privacy notice

## Before broader public launch

- [ ] Replace the lightweight company page with the fuller public company profile
- [ ] Publish final company/legal identity details in the public site where appropriate
- [ ] Replace the pilot-stage privacy notice with the production privacy policy
- [ ] Replace the pilot-stage terms page with the production site and service terms as needed
- [ ] Review whether the footer and company page still feel too lightweight for the intended audience
- [x] Fix nav dropdown ARIA: `aria-haspopup="true"` should be `aria-haspopup="menu"`, dropdown panel should carry `role="menu"`, and link items `role="menuitem"` - now implemented in the desktop nav
- [ ] Fix mobile nav ARIA: mobile hamburger button lacks `aria-expanded`, and the mobile Platform section carries no ARIA roles - desktop fix was scoped to desktop only

## Messaging and proof follow-up

- [ ] Review whether `Protect` remains the strongest middle-pillar label after initial buyer feedback
- [ ] Test whether `Trust layer` lands with buyers or needs a clearer label such as `Built-in trust` or `Research safeguards`
- [ ] Reassess when to expose the broader system-of-record / suite ambition publicly
- [x] Hero third clause revised - changed from `Build on what you know` to `Validate the answer` by internal decision (2026-04-17); alternatives preserved in decision register D-003 and one-line-description-options.md
- [ ] Reassess whether anonymous social proof is still acceptable once customer permissions become available