# GPT Agent — Homepage Master Specification

**Document type:** Implementation specification (planning only — no code)
**Audience:** Coding agent / developer implementing the homepage
**Product:** GPT Agent — AI Sales Agent for any website
**Status:** Ready for implementation

---

## 0. How to use this document

This file is the single source of truth for the GPT Agent homepage. Before writing any code, the implementing agent must:

1. Read this entire document.
2. Inspect the existing GPT Agent repository/codebase (app, dashboard, existing components).
3. Extract and reuse the existing design system (see Section 1).
4. Implement the homepage using only existing routes, existing auth entry points, and existing components where possible.
5. Not introduce a new visual identity, new color palette, new typography scale, or a second design system.

If something in this spec is ambiguous, default to **restraint**: fewer visual effects, more whitespace, more product clarity.

---

## 1. Non-negotiable constraints

These rules override any stylistic preference implied elsewhere in this document.

- **Theme:** Light theme only. GPT Agent is a light-theme product. Do not create a dark mode variant of this page. Do not design a homepage that only works on dark backgrounds.
- **Design system reuse:** Before styling anything, inspect the existing codebase and extract:
  - Existing color tokens (primary, neutral/gray scale, background, border, success/error states)
  - Existing typography (font family, weight scale, heading sizes, line-height, letter-spacing)
  - Existing spacing scale / layout grid
  - Existing button components (primary, secondary, ghost) — reuse, do not redesign
  - Existing border-radius values
  - Existing shadow/elevation tokens
  - Existing card/panel components
  - Existing form input styles
  - Existing logo asset (GA monogram + "GPT Agent" wordmark)
  - Existing frontend architecture/framework conventions (component structure, file organization, styling approach — e.g. Tailwind config, CSS variables, design tokens file)
- **Logo:** Use the existing approved GA monogram + GPT Agent wordmark exactly as-is. No redesign, no alternate lockups, no new icon.
- **Routing:** Only link to routes that actually exist in the application (e.g. login, signup/get started, docs, pricing). If a route referenced in this spec (e.g. `/pricing`, `/docs`) does not exist yet, the implementing agent must either omit that nav item or link it to the closest existing equivalent — never fabricate a dead link.
- **No new component library:** Reuse existing UI primitives (buttons, inputs, badges, cards) from the current app rather than creating parallel one-off styled elements for this page alone.
- **Copy is directional, not final legal copy:** Headlines and microcopy in this spec are the intended message and tone. Minor wording refinement is acceptable; changing the meaning, structure, or claims is not.
- **"Get Started Free" wording:** Only use "Get Started Free" if the product's actual signup flow is free with no card required. Otherwise use "Get Started."

---

## 2. Product positioning (context for the implementing agent)

- **Category:** AI Sales Agent for any website (embeddable JS widget)
- **Eyebrow / category tag:** AI SALES AGENT FOR ANY WEBSITE
- **Core value proposition:** Turn website visitors into customers with AI.
- **What it does:** Businesses create an AI Sales Agent inside GPT Agent, then embed it on their website via a lightweight JavaScript widget. The agent answers visitor questions, captures leads, and helps convert traffic into customers — 24/7.
- **Tone:** Confident, precise, product-first B2B SaaS. Not hype-y, not "AI magic" marketing. Sounds like a tool serious businesses install, not a novelty chatbot.

---

## 3. Design direction

### 3.1 Reference quality bar (inspiration only — do not copy)
Aim for the craft level of Linear, Stripe, Vercel, and top-tier B2B SaaS marketing sites: restrained, typography-led, product-screenshot-driven, confident use of whitespace. The result must be an **original GPT Agent interface**, not a visual clone of any of these products.

### 3.2 Design qualities to hit
- Clean, minimal, premium, professional, confident
- Product-first: the product itself (the widget, the dashboard) is the hero, not illustration
- Spacious but efficient — generous whitespace without padding the page with filler
- Modern, fully responsive
- Looks hand-designed by a product designer and hand-built by an experienced frontend developer — not template-generated, not visibly "AI-generated"

### 3.3 Explicitly avoid
- Generic AI landing page tropes: robot illustrations, AI "brain" graphics, holograms, glowing circuit patterns, neon accents
- Excessive gradients or glassmorphism
- Large decorative/abstract graphics that don't represent the real product
- Excessive scroll animations or motion for its own sake
- Massive feature grids (6+ generic icon+text tiles)
- Large testimonial walls
- Fabricated statistics ("10,000+ businesses," "99.9% satisfaction") unless real numbers are supplied
- Fabricated customer logo walls
- Layouts that read as a generic SaaS template

### 3.4 Motion guidance
Subtle only: gentle fade/slide-in on scroll for section entrances, a light hover state on buttons/cards, and the hero widget mockup may have one small looping micro-interaction (e.g. a chat bubble appearing) at most. No parallax, no auto-playing carousels, no heavy scroll-jacking.

---

## 4. Page structure

The homepage is intentionally short: **5 main content sections**, plus a navbar and footer (not counted as content sections).

| # | Section | Purpose |
|---|---|---|
| — | Navbar | Navigation + account entry points |
| 1 | Hero | Communicate the product in ~5 seconds |
| 2 | How It Works | Explain the setup flow simply |
| 3 | Product Showcase | Show the agent in action / capabilities |
| 4 | Dashboard Proof | Show the real product/dashboard as proof of substance |
| 5 | Final CTA | Convert |
| — | Footer | Links, legal, secondary nav |

Do not add additional sections (no pricing teaser, no testimonials, no blog feed, no integrations grid) unless explicitly requested later. If a section feels necessary but isn't listed here, flag it rather than adding it silently.

---

## 5. Navbar

**Layout:** Single row, compact height (not oversized — this is a utility bar, not a hero element). Sticky on scroll with a subtle background/border-on-scroll treatment consistent with the existing app shell if one exists.

**Left:**
- GA monogram logo + "GPT Agent" wordmark (existing lockup, linked to `/`)

**Center / primary nav:**
- Product
- Features
- Pricing
- Docs

(Each item links to an in-page anchor or existing route — only use routes/anchors that actually exist. If "Product" and "Features" would point to the same place, consolidate to avoid a dead/duplicate link.)

**Right:**
- Login (secondary/ghost button style, links to existing login route)
- Get Started (primary button style, links to existing signup route)

**Mobile behavior:**
- Collapses to: logo (left) + hamburger menu (right)
- Mobile menu opens as a full-screen or slide-down panel containing all nav links
- Login and Get Started remain clearly accessible inside the mobile menu (Get Started should remain visually primary)

---

## 6. Section 1 — Hero

**Goal:** A visitor understands what GPT Agent is and who it's for within ~5 seconds, with zero scrolling required to grasp the core value prop.

### 6.1 Layout
Two-column layout on desktop (roughly 50/50 or 55/45 split, text-left / visual-right). Stacks to a single column on mobile with text first, then visual.

### 6.2 Left column content
1. **Eyebrow label:** "AI SALES AGENT FOR ANY WEBSITE" — small, uppercase or letter-spaced, muted/secondary color, possibly in a subtle pill/badge using an existing badge component if one exists.
2. **Headline (H1):** "Turn website visitors into customers with AI."
3. **Supporting copy (subheading, 1–2 lines):** "GPT Agent answers questions, captures leads, and helps your business sell 24/7."
4. **CTA row (horizontal on desktop, stacked on mobile):**
   - Primary button: "Get Started" (or "Get Started Free" only if applicable per Section 1 rules) → links to signup
   - Secondary button: "See How It Works" → scrolls/anchors to the How It Works section

### 6.3 Right column — hero visual
**This must depict the real product, not abstract AI imagery.**

Show a realistic, polished mockup of the embedded chat widget as it would appear on a customer's website. This should be built as an actual styled UI mockup (using real component styling — card, shadow, radius from the design system), not a stock illustration.

Reference structure for the widget mockup:

- **Header bar:** "GPT Agent" label + a small "● Online" status indicator (green dot + "Online" text)
- **Body:**
  - Agent message bubble: "Hi! How can I help you?"
  - Two quick-reply chip/button options side by side, e.g. "Pricing" and "Products"
  - A follow-up suggested action button, e.g. "Book a Demo"
- **Footer / input bar:** A text input styled as "Type your message..." with a send icon/arrow

Presentation notes:
- Render this inside a card with realistic elevation (shadow) as if it's floating above a soft/neutral backdrop or a subtle browser-window/website-frame chrip to reinforce "this lives on your site."
- Keep colors consistent with the existing light theme and primary brand color (used sparingly — e.g. on the send button or the primary quick-action).
- Optional subtle motion: one message or quick-reply chip animating in on load/scroll, nothing more.
- Do not add decorative elements around the widget (no floating icons, sparkles, or abstract shapes).

---

## 7. Section 2 — How It Works

**Goal:** Make the setup process feel effortless and fast. Establish credibility that this is a real, easy-to-deploy product — not a black box.

### 7.1 Format
A simple 3-step horizontal sequence on desktop (numbered steps, stacked vertically on mobile). Avoid turning this into a large feature grid — 3 steps only.

### 7.2 Suggested steps
1. **Create your AI Agent** — Configure your Sales Agent with your business info, tone, and knowledge in minutes.
2. **Embed the widget** — Add one lightweight JavaScript snippet to your website. No developer required.
3. **Start converting visitors** — Your agent answers questions, captures leads, and works around the clock.

Each step: a small number/index treatment (e.g. "01," "02," "03" or a simple numbered badge using existing style tokens), a short title, and one supporting sentence. No icon illustrations required — if icons are used, keep them simple/line-style and consistent with any icon set already used in the app (e.g. an existing icon library already in the codebase).

---

## 8. Section 3 — Product Showcase

**Goal:** Demonstrate real capabilities of the AI Sales Agent, grounded in the actual product, not generic "AI features."

### 8.1 Format
A focused showcase of 3 (max 4) real capabilities, each paired with a small, real product visual (widget states, not abstract icons). Avoid a 6+ tile generic feature grid.

### 8.2 Suggested capabilities (adapt to actual product features — do not fabricate capabilities the product doesn't have)
- **Answers questions instantly** — Trained on your business content to give accurate, on-brand answers in real time.
- **Captures and qualifies leads** — Collects visitor details and intent automatically, ready to hand off to your team.
- **Works on any website** — Drop-in JavaScript widget that works with any stack, no rebuild required.
- (Optional 4th, only if real): **Available 24/7** — Never miss a visitor, even outside business hours.

### 8.3 Presentation
Each capability can be shown as a card with a short headline, one supporting sentence, and — where possible — a small real UI snippet (e.g. a cropped view of a lead-capture form inside the widget, or an answer bubble). Prefer real, small, faithful UI fragments over icons.

---

## 9. Section 4 — Dashboard / Product Proof

**Goal:** Prove GPT Agent is a real, substantial software product — not just a marketing-page widget mockup. This section builds trust through product substance.

### 9.1 Content
A large, high-fidelity screenshot (or realistic mockup matching the actual dashboard) of the GPT Agent dashboard — e.g. the agent configuration screen, conversation/lead inbox, or analytics view (whichever best represents the real, currently-existing dashboard).

### 9.2 Presentation
- Framed in a browser-chrome or clean device frame consistent with how the rest of the app presents screenshots (if a convention already exists in the codebase, reuse it).
- Should sit inside a container with soft elevation/shadow to visually "lift" it off the page.
- A short supporting headline above it, e.g. "One dashboard. Full visibility." or "See every conversation, every lead." — copy should match whatever the dashboard screenshot actually shows.
- One or two short supporting sentences, no bullet list needed here — let the screenshot do the work.

### 9.3 Important
Do not use a fake/placeholder dashboard image. If a real dashboard screenshot isn't available at implementation time, flag this as a blocking content dependency rather than inventing fake data/metrics in a mockup.

---

## 10. Section 5 — Final CTA

**Goal:** Clear, low-friction final conversion moment.

### 10.1 Content
- Headline: Something direct and confident, e.g. "Start turning visitors into customers today." (tone-match to hero headline; do not introduce a new voice here)
- One short supporting line, e.g. "Set up your AI Sales Agent in minutes."
- Primary CTA button: "Get Started" (same signup destination as hero/navbar — consistency matters)
- Optional secondary link/button: "Talk to Sales" or "View Pricing" — only if those destinations exist

### 10.2 Presentation
Should feel like a clean, confident closing statement — can use a subtly distinct background treatment (e.g. a soft tint using an existing secondary background token) to separate it from the preceding section, but must remain within the light theme and existing palette. No heavy colored banner, no gradient background.

---

## 11. Footer

Standard SaaS footer, consistent with existing app footer if one already exists elsewhere in the product (e.g. in the dashboard shell or existing marketing pages).

Suggested structure:
- Logo + short one-line product description
- Link columns (only using real, existing routes), e.g.:
  - **Product:** Features, Pricing, Docs
  - **Company:** About, Contact (only if these pages exist)
  - **Legal:** Privacy Policy, Terms of Service (only if these pages exist)
- Bottom bar: copyright line, e.g. "© 2026 GPT Agent. All rights reserved."

Do not fabricate social links, blog links, or legal pages that don't exist in the product yet.

---

## 12. Responsive behavior summary

- **Desktop (≥1024px):** Full two-column hero, horizontal 3-step "How It Works," multi-column showcase cards, full-width dashboard screenshot.
- **Tablet (~768–1023px):** Hero may remain two-column with a smaller visual, or stack if the widget mockup becomes too cramped — implementer's judgment, prioritize legibility. Showcase cards may reduce to 2 columns.
- **Mobile (<768px):** Everything stacks vertically in reading order: eyebrow → headline → supporting copy → CTAs → hero visual → How It Works (stacked) → Showcase (stacked) → Dashboard screenshot (full width, scrollable if needed) → Final CTA → Footer. Navbar collapses to hamburger menu per Section 5.

---

## 13. Content dependencies / open questions for implementation

Flag rather than fabricate:

- [ ] Confirm actual signup flow is free/no-card before using "Get Started Free."
- [ ] Confirm real routes for Pricing and Docs before linking them in navbar/footer.
- [ ] Obtain a real, current dashboard screenshot for Section 4 (Dashboard Proof).
- [ ] Confirm which 3 (or 4) capabilities in Section 3 are real, shippable features today.
- [ ] Confirm existing design tokens (colors, type scale, spacing, radius, shadows) by inspecting the current codebase before writing any styles.
- [ ] Confirm existing icon library/component set in use, if any, to avoid introducing a second one.

---

## 14. Definition of done

The homepage implementation is complete when:

1. It uses only the existing design system (colors, type, spacing, components, logo) — no new visual language introduced.
2. It remains in the light theme throughout.
3. It contains exactly the 5 defined content sections (plus navbar/footer) — no extra sections added.
4. The hero communicates the product clearly within ~5 seconds via real product visuals, not generic AI imagery.
5. All links point to real, existing routes.
6. It is fully responsive per Section 12.
7. It avoids every item listed in Section 3.3.
8. Any unresolved content dependency from Section 13 has been explicitly resolved or flagged — not silently guessed.
