# Migration Notes — prospero.systems

> Phase 1 output. Review this document in full before signing off to proceed to Phase 2 (style guides).

## 1. Executive summary

- **Source:** Squarespace site at `https://prospero.systems` (currently bilingual EN + DE; English only is in scope).
- **Scale:** ~85 unique English pages. 13 core marketing pages, 12 platform capability pages, 15 solution pages, 9 case studies, 30+ blog posts (Insights), 4 legal pages, a handful of utility/booking pages.
- **Target:** Localhost-only static site with three side-by-side design versions.
- **Phase 1 deliverables are complete:**
  - Verbatim content extracted for 8 **priority** pages (see §6). Full extraction for the remaining ~77 pages is **deferred** until a design direction is picked — see §11 for the reasoning.
  - Full-site URL inventory compiled from sitemap + homepage nav crawl (see §2).
  - 60 images catalogued for the priority pages (see `content/_images.md`).
  - Repo structure initialized: `versions/v1..v3/` scaffolds, chooser `index.html`, `.gitignore`.
- **Key external inputs already available** (in `resources/`, see §10):
  - UX audit (score 6.2/10) with concrete IA recommendations.
  - Marketing/positioning deck with buyer personas and competitor comparison.

---

## 2. Full-site page inventory

Paths are site-relative. Prepend `https://prospero.systems` for absolute URLs. Every URL below is an **English-language** page; the German `/de/...` mirror is out of scope.

### 2.1 Core marketing pages

| URL | Purpose | Priority-extracted? |
|---|---|---|
| `/` | Home | ✅ `content/home.md` |
| `/detectx` | Platform overview (DetectX®) | ✅ `content/platform.md` |
| `/about-us` | Company + management team | ✅ `content/about.md` |
| `/contact-us` | Contact / offices / book-demo CTA | ✅ `content/contact.md` |
| `/partners` | Partner programme / enquiry form | ⚪ inventory only |
| `/detectx-trial-request` | Trial request landing | ⚪ inventory only |
| `/detectx-book-demonstration` | Booking page (Squarespace Scheduling widget) | ⚪ inventory only |

### 2.2 Mega-menu landing pages (Squarespace-specific)

These are **separate Squarespace pages** that render as mega-menu overlays in the nav. In a static redesign, they should become real `<ul>` dropdowns in the header; the pages themselves can be deleted.

| URL | Role |
|---|---|
| `/detectx-industries` | Industries mega-menu host — **delete in migration** |
| `/detectx-solutions` | Solutions mega-menu host — **delete in migration** |
| `/detectx-platform` | Platform mega-menu host — **delete in migration** |
| `/resources-menu` | Resources mega-menu host — **delete in migration** |
| `/company-menu` | Company mega-menu host — **delete in migration** |

### 2.3 Industries (4)

| URL | Priority-extracted? |
|---|---|
| `/banking` | ✅ `content/industries-banking.md` |
| `/insurance` | ⚪ inventory only |
| `/capital-markets` | ⚪ inventory only |
| `/industries-other` | ⚪ inventory only — **rename proposed** (see §4) |

### 2.4 Solutions (15)

Nine appear in the Solutions mega-menu. Six more are only linked from the homepage or industry pages — they're "hidden" solutions that procurement buyers can't find without guessing.

**In mega-menu:**
- `/adverse-media-search`
- `/detectx-anti-money-laundering`
- `/detectx-asset-screening`
- `/detectx-credit-risk-rating`
- `/detectx-digital-identity`
- `/detectx-fraud-detection`
- `/detectx-know-your-customer`
- `/detectx-name-screening`
- `/risk-based-profiling`

**Not in mega-menu but linked elsewhere:**
- `/detectx-customer-retention`
- `/detectx-sales-optimisation`
- `/detectx-demand-forecasting`
- `/detectx-supply-chain-optimisation`
- `/detectx-sales-forecasting`
- `/detectx-customer-risk-score`

### 2.5 Platform capabilities (12)

All under the Platform mega-menu. One representative page (`/transaction-monitoring`) has been priority-extracted.

- `/detectx` (overview — already in §2.1)
- `/alert-management`
- `/behavioural-analysis`
- `/business-rules-designer-and-engine`
- `/clustering-and-modelling`
- `/enhanced-ai-search`
- `/evolutionary-learning`
- `/link-analysis`
- `/natural-language-processing`
- `/pattern-recognition`
- `/profiling-and-scoring`
- `/transaction-monitoring` ✅ `content/solutions-transaction-monitoring.md`

### 2.6 Case studies (9)

- `/case-studies` (listing)
- `/case-studies/helvetia` ✅ `content/case-helvetia.md`
- `/case-studies/finnova-ag-bankware` (a.k.a. Finnova analytical framework)
- `/case-studies/generali` (a.k.a. Generali Switzerland)
- `/case-studies/finanz-informatik`
- `/case-studies/pluscard`
- `/case-studies/risk-solution-network`
- `/case-studies/sparkasse-zollernalb`
- `/case-studies/lkh-feldkirch`

Filter pages (category-based): `/case-studies?category=Banking`, `?category=Insurance`, `?category=Life+Sciences`.

### 2.7 Insights / blog (30+)

Index: `/insights` ✅ `content/insights-index.md`. Individual posts are listed in `content/insights-index.md` and enumerated in the sitemap. Full post content is **out of scope** for this phase (see §11).

### 2.8 Resources

- `/case-studies` (already listed)
- `/insights` (already listed)
- `/detectx-downloads` (PDF library)
- `/glossary`
- `/compliance-and-technology-research`
- `/detectx-videos`

### 2.9 Legal

- `/terms-and-conditions`
- `/privacy-policy`
- `/cookie-policy`
- `/marketing-preferences`

### 2.10 Utility / vestigial

- `/cart` — empty Squarespace cart. **Remove.**
- `/compliance-crisis-webinar` — specific campaign landing. Migrate if still active; otherwise deprecate.
- `/s/Prospero_Case_Study_Helvetia_en.pdf` — static PDF asset. Move into `versions/v{1,2,3}/assets/pdfs/` per version, or a single shared `/downloads/`.

---

## 3. Current IA (as-is)

```
/
├── /                                Home
├── Industries (mega-menu)
│   ├── Banking
│   ├── Insurance
│   ├── Capital Markets
│   └── Other Industries
├── Solutions (mega-menu)
│   ├── Adverse Media Search
│   ├── Anti-Money Laundering
│   ├── Asset Screening
│   ├── Credit Risk Rating
│   ├── Digital Identity
│   ├── Fraud Detection
│   ├── Know Your Customer
│   ├── Name Screening
│   └── Risk-Based Profiling
├── Platform (mega-menu)
│   ├── DetectX® Overview
│   ├── Alert Management
│   ├── Behavioural Analysis
│   ├── Business Rules Designer
│   ├── Clustering & Modelling
│   ├── Enhanced AI Search
│   ├── Evolutionary Learning
│   ├── Link Analysis
│   ├── Natural Language Processing
│   ├── Pattern Recognition
│   ├── Profiling & Scoring
│   └── Transaction Monitoring
├── Resources (mega-menu)
│   ├── Case Studies
│   ├── DetectX Downloads
│   ├── Insights (blog)
│   ├── Glossary
│   ├── Compliance & Technology Research
│   └── Videos
└── Company (mega-menu)
    ├── About Us
    ├── Contact Us
    └── Partners
```

**Issues surfaced in the UX report** (score 6.2/10):
1. No "Why DetectX" page — differentiation story is buried inside the `/detectx` scroll.
2. Three large scroll-animation voids on the home page (content at opacity:0 until in-view) that read as "broken".
3. LCP > 3s because particle background + autoplay video load simultaneously.
4. Generic AI-stock imagery on solution cards undermines trust on a compliance brand.
5. Root URL auto-redirects to German — English prospects land on `/de`.
6. Case studies (strong proof) only reachable from Resources, never from solution pages.
7. Naming collision: `/transaction-monitoring` is a Platform capability; deck proposes renaming `/detectx-credit-risk-rating` to "Transaction Monitoring" which would conflict.
8. Mixed-language copy on German AML page.
9. Six "hidden" solutions (customer-retention, sales-optimisation, demand-forecasting, supply-chain-optimisation, sales-forecasting, customer-risk-score) aren't in the Solutions mega-menu.

---

## 4. Proposed new IA (applied in V2 and V3; V1 keeps current IA)

```
/
├── /                                Home
├── Why DetectX                      ★ NEW — differentiation narrative (currently missing)
├── Industries
│   ├── Banking
│   ├── Insurance
│   ├── Capital Markets
│   └── Third-Party Risk & Due Diligence   ★ renamed from "Other Industries"
├── Solutions
│   ├── — FSI Compliance —
│   │   ├── Anti-Money Laundering
│   │   ├── Know Your Customer
│   │   ├── Name Screening
│   │   ├── Adverse Media Search
│   │   ├── Asset Screening
│   │   ├── Credit Risk Rating
│   │   └── Fraud Detection
│   ├── — Risk & Identity —
│   │   ├── Digital Identity
│   │   ├── Risk-Based Profiling
│   │   └── Customer Risk Score         ★ promoted (previously hidden)
│   └── — Business Intelligence —       ★ new grouping for the 5 "hidden" solutions
│       ├── Customer Retention
│       ├── Sales Optimisation
│       ├── Sales Forecasting
│       ├── Demand Forecasting
│       └── Supply Chain Optimisation
├── Platform
│   ├── DetectX® Overview
│   ├── — Universal Capabilities —
│   │   ├── Alert Management
│   │   ├── Business Rules Designer & Engine
│   │   ├── Enhanced AI Search
│   │   ├── Link Analysis
│   │   └── Transaction Monitoring
│   └── — Analytics Engines —
│       ├── Behavioural Analysis
│       ├── Clustering & Modelling
│       ├── Evolutionary Learning
│       ├── Natural Language Processing
│       ├── Pattern Recognition
│       └── Profiling & Scoring
├── Customers                        ★ renamed from "Case Studies" — active word, surfaced higher
│   ├── — by Industry —
│   │   ├── Banking
│   │   ├── Insurance
│   │   └── Life Sciences
│   └── 9 case studies (existing)
├── Resources
│   ├── Insights (blog)
│   ├── Downloads
│   ├── Glossary
│   ├── Research
│   └── Videos
└── Company
    ├── About Us
    ├── Partners
    └── Contact
```

**Structural changes (applied to V2 + V3):**
- **Add "Why DetectX"** as a top-level nav entry.
- **Rename "Other Industries"** → "Third-Party Risk & Due Diligence" (the UX report's wording).
- **Rename "Case Studies"** → "Customers" and promote to top-level (currently nested under Resources).
- **Group Solutions** into three semantic clusters (FSI Compliance / Risk & Identity / Business Intelligence) so buyers scanning for their use case can orient faster.
- **Surface the six hidden solutions** (customer-retention etc.) so procurement can evaluate breadth.
- **Split Platform** into Universal Capabilities vs. Analytics Engines (matches the UX report's restructure proposal).
- **Surface case studies from solution pages** — add a "Proof: customers using this" rail on every solution page.

**V1 (iteration) does NOT apply these** — V1 keeps the current IA intact. V1 only: adds "Why DetectX", replaces hero stock imagery, fixes scroll-animation voids and LCP, removes the `/cart` link, makes English the default language.

**V3 (user-story refactor)** restructures around personas rather than feature taxonomy. Its top-level nav is:

```
/
├── /                                Home — persona router
├── For FSI Compliance Teams         ★ persona-entry page
├── For Non-FSI Risk Teams           ★ persona-entry page
├── For Buyers Evaluating Vendors    ★ comparison/procurement page
├── Platform                         (unchanged structure)
├── Customers                        (flat list, surfaced everywhere)
└── Contact
```

Each persona-entry page walks that persona through the questions they ask in the order they ask them: capability coverage → industry fit → proof → integration story → next step. No mega-menu — the nav is flat because personas shouldn't need to drill through a feature taxonomy to find their path.

---

## 5. Squarespace-specific features → replacement strategy

| Feature | Where it's used | Replacement strategy |
|---|---|---|
| **Mega-menu as separate pages** (`/detectx-industries` etc.) | Primary header nav | Replace with semantic `<ul>` dropdowns in the header partial. Delete the 5 mega-menu host pages. |
| **`/cart` (empty Squarespace Commerce)** | Header icon | **Remove.** Confirmed vestigial — site doesn't sell anything. |
| **`/detectx-book-demonstration`** (Squarespace Scheduling) | Many CTAs across site | Prototype phase: link to a placeholder page with email/phone. Scale-up phase (near-term follow-up): wire to Calendly / Cal.com / a self-hosted link. Document in Phase 5 README. |
| **`/detectx-trial-request`** (Squarespace form) | Nav CTA | Visual-only `<form>` on localhost (no action endpoint). Comment in HTML flags the decision; localhost = no backend. |
| **`/contact-us`** (no inline form — just a booking CTA) | Contact page | Keep the structure as-is; add an optional visual `<form>` block in V2/V3. |
| **Insights blog CMS** | 30+ posts | Out of scope for Phase 1. In scale-up: each post becomes its own HTML file under `/insights/<slug>.html`; pagination handled by a handwritten index file. Non-technical editors duplicate a template and edit copy. |
| **Case study templating** | 9 case studies | Each becomes its own HTML under `/customers/<slug>.html` in the chosen version. All use the same partial-driven layout. |
| **Image CDN** (`images.squarespace-cdn.com`) | ~60 images on priority pages | Download, convert to WebP + JPEG fallback, rename descriptively, store under `versions/v{n}/assets/images/`. See Phase 5. |
| **`/s/Prospero_Case_Study_Helvetia_en.pdf`** and similar `/s/` assets | Case studies + downloads | Download all referenced PDFs; store under `versions/v{n}/assets/pdfs/` or a shared `/downloads/`. |
| **On-page scroll animations** (opacity:0 → in-view) | Homepage + solution pages | Remove entirely — content visible by default. If any animation is kept, use `prefers-reduced-motion` guards. Fixes UX report's "scroll voids" issue. |
| **Particle background + autoplay video in hero** | Homepage | Drop both. Use a single static hero image (or type-only hero in V2/V3). Fixes LCP. |
| **Root URL auto-redirect to German** | Squarespace i18n | Not applicable — the static site is EN-only. Link to a `/de` mirror only if DE is re-added in a future phase. |

---

## 6. Priority content extraction — what's in `content/`

| File | Source URL | Words (approx) | Notes |
|---|---|---|---|
| `home.md` | `/` | 1,500 | Full hero, solutions grid (15 cards), webinar promo, customer stat-quotes, footer copy. |
| `platform.md` | `/detectx` | 900 | DetectX® narrative, analytics engines list, integration story. |
| `solutions-transaction-monitoring.md` | `/transaction-monitoring` | 1,000 | Platform capability page, serves as template for other capability pages. |
| `industries-banking.md` | `/banking` | 1,400 | Industry positioning, named solutions, named customers (Finnova, Sparkasse, Finanz Informatik), stats. |
| `case-helvetia.md` | `/case-studies/helvetia` | 500 | Customer quote, challenge/solution narrative, PDF download link. |
| `about.md` | `/about-us` | 1,500 | Company story, four-person management team (Schaefle, Scott, Tsirkin, Pölzlbauer), LinkedIn links. |
| `contact.md` | `/contact-us` | 600 | Vaduz HQ + London office, phone, email, booking CTA. No inline form. |
| `insights-index.md` | `/insights` | 1,500 | Index of 20 articles + 3 featured + 11 category filters. Article URLs listed but not fetched. |
| `_nav-links.md` | header + footer + mega-menus | — | Full URL inventory (this file's §2 is derived from it). |
| `_images.md` | priority pages | — | 60 images with source URL, page context, alt text, proposed filename. |

Total priority extracted: ~8,900 words across 8 content pages.

---

## 7. Design direction briefs

Per the approved plan, the three versions differ in **scope of intervention**. The briefs below translate that into concrete direction per version.

### V1 — Iteration & fixes

**Verbal description:** the current prospero.systems, polished and de-bugged. Stakeholders who see V1 should say "that's our site, but it works now" — not "that's a new site".

**What stays the same:**
- Current IA (mega-menu structure, same navigation labels, same URL slugs).
- Primary brand colour `#e63946` (the crimson red currently in use).
- System-UI / Segoe UI type stack (or a near equivalent that's self-hostable).
- Sans-serif, high-contrast, card-based layout vocabulary.

**What changes (the "fixes"):**
- Eliminate scroll-animation voids — all content visible on load.
- Drop particle background + autoplay video; single static hero image.
- **Add a "Why DetectX" page** in primary nav.
- Replace AI-stock imagery on solution cards with better stock or geometric SVG.
- Apply a consistent 3-section layout to every solution page (header / capabilities / cross-links to Platform).
- Remove `/cart`, make English the default route.
- Preserve Squarespace-era typography hierarchy but tighten line-heights and spacing rhythm.

**Reference points (visually):** the current prospero.systems, but cleaner — think "same tailor, better fit". Deliberately NOT reference a visually new brand.

**Palette (V1):**
- Primary: `#e63946` (current red, kept).
- Ink: `#0a0e1a` (current deep navy, kept).
- Paper: `#ffffff`.
- Muted: `#f0f0f0`.

### V2 — Selective redesign

**Verbal description:** same structure, new skin. Visually confident, editorial, restrained. Swiss sensibility matches Zurich/Vaduz positioning and deliberately separates Prospero from hawk.ai's navy-and-coral corporate look.

**Visual principles:**
- Typography is the main design element. A strong display serif or high-contrast sans for headlines, paired with a grotesque or mono for UI/body.
- Asymmetric 12-column grid with intentional whitespace — not every section needs centered content.
- Restrained colour — two neutrals and one considered accent. The existing `#e63946` is a candidate for refinement toward a deeper oxblood or a muted signal colour; alternative: a confident blue-grey with a warm accent.
- Geometric SVG illustrations replace stock photography entirely.
- Proof elements (customer quotes, named logos, stats) treated with editorial prominence — not ghettoised to testimonials page.

**References to explore:**
- Bureau Mirko Borsche — editorial asymmetry, type as main event.
- Linear (the app's marketing, circa 2023) — restrained colour + strong type hierarchy.
- Stripe Press — typography-led storytelling for a technical audience.
- Werkplaats Typografie portfolio — Swiss lineage, confident use of whitespace.
- Base Design (base-design.com) — brand systems for serious institutions.

**Palette (V2), to be proposed in Phase 2:**
- Candidate A — Refined heritage: ink `#0e1014`, paper `#f6f4ef` (warm), accent `#8b1e2b` (deeper oxblood replacing the current red), muted `#c9c3b8`.
- Candidate B — Editorial cool: ink `#0a2240` (deep blue-black), paper `#f5f6f7`, accent `#d97706` (warm amber), muted `#cbd5d6`.

### V3 — User-story refactor

**Verbal description:** rebuilt around how buyers actually evaluate. The homepage is a persona router, the rest of the site is narrative journeys rather than feature taxonomies.

**Structural principles:**
- Nav is flat, not mega-menu driven. Persona-entry pages + Platform + Customers + Contact.
- Each persona entry is a single long-scroll narrative: "here's your question in the order you ask it".
- Proof is woven throughout each narrative (quote → stat → logo → next question) rather than compartmentalised.
- Comparison page ("Prospero vs. the alternatives") borrows hawk.ai's "The Hawk Difference" pattern but with a frame that's advantageous to Prospero (full lifecycle + non-FSI coverage).

**Visual principles:**
- Dense at the top (persona router has 3 options side-by-side with distinguishing visual treatments), relaxed in the narratives.
- Data-forward — quantified claims (98% false-alert reduction, customer stats) get outsize typographic weight.
- Colour coding per persona path (e.g. FSI = deep blue, Non-FSI = terracotta, Procurement = graphite). Not garish — muted, named.

**References to explore:**
- Segment's solution landing pages (pre-Twilio acquisition) — clear persona routing.
- Vercel's enterprise sales pages — narrative-led rather than feature-grid-led.
- Notion's "For <team>" pages — persona framing done editorially.
- Linear's "Why Linear" page — comparative narrative without naming competitors.

**Palette (V3), to be proposed in Phase 2:**
- Neutral chassis (ink `#111`, paper `#fafaf9`, muted `#d0cfcc`) with three persona accents:
  - FSI path: `#17365d` (deep banker blue).
  - Non-FSI path: `#b05a3b` (terracotta).
  - Procurement path: `#3c3f4a` (graphite).

---

## 8. Competitive context — hawk.ai

The marketing deck in `resources/` names five direct competitors (Hawk, FinScan, IMTF, Pythagoras, Polixis). hawk.ai is the closest and the user's reference. A short contrast summary so the design directions read meaningfully against it:

- **Hawk.ai visual system:** deep navy `#060973` + coral `#ff4d00` accent; all-caps geometric sans-serif; carousel hero with static imagery (no video, no particles); dense IA with deep solution sub-pages; "Hawk Difference" comparison table as its main proof artefact.
- **Proof pattern:** analyst badges (Forrester, Chartis, Datos, Celent) rather than customer logos; quantified stats ("3-5x more risk detection", "70% fewer false positives"); short testimonial quotes embedded on every solution page.
- **Overall read:** polished, corporate, enterprise-safe. Confident but not distinctive — hawk.ai looks like competent hawk.ai, not like a brand a designer loved.

**Implications for the three versions:**
- V1 stays away from this territory by preserving Prospero's red/navy rather than chasing hawk.ai's blue/coral.
- V2 should actively *differentiate* from hawk.ai, not echo it — Swiss editorial is the move here.
- V3 borrows the **comparison pattern** structurally but executes it with less corporate polish and more narrative voice.

---

## 9. Key messages the new site must communicate

Pulled from the marketing deck in `resources/`:

1. **Integrated platform, not point solutions.** DetectX covers the full financial-crime lifecycle (onboarding → monitoring → investigation).
2. **FSI and non-FSI.** Prospero is unusual in serving both financial institutions AND manufacturers/utilities/life-sciences.
3. **Quantified outcome:** 98% false-alert reduction (Swiss Retail Bank, footnote already present on the homepage).
4. **Named customers:** Generali, Helvetia, Finnova, Sparkasse Zollernalb, Finanz Informatik, PlusCard, Risk Solution Network, LKH Feldkirch. This is Prospero's strongest asset — surface it from every solution page.
5. **Swiss/Liechtenstein credibility:** Vaduz HQ + London presence; data-sovereignty and GDPR positioning.
6. **Technical depth:** ten named analytics engines (pattern recognition, behavioural analysis, evolutionary learning, NLP, clustering, profiling/scoring, link analysis, enhanced AI search, business rules, alert management) — credible to a technical procurement committee.

---

## 10. `resources/` — reference inputs already on disk

Folder name is `resources/` (single-s — Windows normalised from the original French spelling).

| File | Purpose |
|---|---|
| `report-prospero-systems-en-v2-2026-04-16.html` | UX audit. Scored current site 6.2/10. Concrete IA proposals applied in §4. Design tokens (colour palette, spacing) referenced in §7. |
| `260305_MarketingMessage.pptx` | Positioning deck. Core messages in §9, persona definitions and competitor comparison in §8. |

Treat both as **source of truth** during Phase 2 — don't re-derive positioning from scratch.

---

## 11. Scoping decisions (and open questions)

### 11.1 Deferred content extraction

Full verbatim extraction of all ~85 pages was **not** performed in Phase 1. Only 8 priority pages were extracted — the pages that will become prototype pages in Phase 4. Rationale:

- Phase 4 only builds ~6 pages per version. We need verbatim source copy for those pages, not for the 77 that aren't built in the prototype.
- Full extraction for the remaining pages belongs in the **scale-up follow-up** (after a design direction is picked) — at that point we extract ~80 pages and paste them into the winning version's templates. Doing it twice is wasted work.
- The URL inventory in §2 is complete; every deferred page has a known URL that the scale-up phase can re-fetch on demand.

**Flag this with the user if:** you wanted a full content archive now as an insurance against losing Squarespace access later. If so, we can run a dedicated content-archive pass (estimated: 1–2 hours of agent time) that dumps all 85 pages to markdown without any further processing.

### 11.2 Image assets

60 images inventoried from priority pages. **Not downloaded yet** — downloads happen in Phase 5 (per the approved plan). If the Squarespace site is at risk of being taken down mid-project, we should bring the Phase 5 download step forward.

### 11.3 Forms & booking

Localhost has no backend, so `<form>` submissions won't go anywhere. Current design is "visual-only forms, code comment explains how to wire a backend if the site ever goes public". The `/detectx-book-demonstration` page is handled as a placeholder link in the prototype. If you want the booking flow to actually work during the localhost demo (e.g., to show stakeholders a full click-through), we need a decision: Calendly embed, Cal.com embed, or `mailto:` fallback.

### 11.4 Blog / Insights

30+ articles, out of scope for this phase. Blog architecture question deferred to the scale-up phase: do we keep a blog in the static repo, or move blogging to a headless CMS + published export? Not urgent — none of the three prototype versions surface a blog post.

### 11.5 Open questions for your Phase 1 sign-off

1. **IA proposal (§4).** V2 and V3 apply the new IA. Are the three Solutions groupings (FSI Compliance / Risk & Identity / Business Intelligence) the right cuts? Is "Customers" the right word for what's currently "Case Studies"?
2. **Hidden solutions (§2.4).** Six solutions (customer-retention, sales-optimisation, demand-forecasting, supply-chain-optimisation, sales-forecasting, customer-risk-score) aren't in the current Solutions mega-menu. Should they be surfaced (my proposal — see §4), quietly deprecated, or kept hidden intentionally?
3. **V2 palette (§7).** Two candidate palettes proposed (Refined heritage vs. Editorial cool). Preference before Phase 2 starts?
4. **V3 comparison page.** Should the comparison mention competitors by name (hawk.ai, FinScan, etc.) or be framed as "Prospero vs. legacy point solutions" without naming?
5. **Full content archive (§11.1).** Run a full-site content dump now as insurance, or rely on the URL inventory and re-fetch during scale-up?

---

## 12. Phase 1 complete — next gate

Phase 2 (design system ×3, style guides) is blocked until you review and sign off on this document and answer the open questions in §11.5. The repo is committed; the chooser page `index.html` is viewable via `python -m http.server 8000` at the repo root.