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

# Getting started checklist

> The fastest way to kick off an Oratory sprint (assets, access, and owners).

This checklist is designed to **remove friction** before we start designing.

## 1) People (owners + reviewers)

* **Project owner (required):** one person who consolidates feedback
* **Decision maker (required):** who gives final approval (and is available)
* **Reviewer list:** who should comment in Figma vs. who’s FYI

<Tip>
  If too many people give feedback directly, the sprint slows down. One owner = faster outcomes.
</Tip>

## 2) Access (so we can see the real product)

* A **recorded product walkthrough** (Loom is perfect) or a live demo
* Access to a **staging environment** if available (optional but helpful)
* Any existing **analytics** context (what matters to you)

## 3) Assets (what to send)

* Logo files: **SVG preferred**, plus PNGs
* Brand guidelines (if you have them)
* Product screenshots (or we’ll capture during walkthrough)
* Team photos (optional; only if you want team/testimonial sections)

## 4) Content inputs (even if copy isn’t final)

* A short description of your product (1–3 sentences)
* 3–5 key features / use cases
* Your top 3 differentiators (why you win)
* Your top objections (why people hesitate)

## 5) Logistics

* Confirm platform: **Framer** or **Webflow**
* Confirm launch needs:
  * Are we doing **DNS changes**?
  * Any existing pages that need **redirects**?

## What we need from you (TL;DR)

* A single project owner + decision maker
* A product walkthrough
* Logos + any brand guidelines
* A rough feature list + differentiators (doesn’t need to be polished)

***

<Card title="Book a free intro call" icon="calendar" href="https://oratory.co/meeting" horizontal>
  Schedule a call to talk through your project.
</Card>