Launching from Stealth
Role
UX Lead & PM
Industry
AI / Insurance Platform
Engagement
IA, Copy, Design, Prototype, Handoff
Timeline
Alpha to Public Launch, 2024/2025
2 min overview / 6-8 min with details
Overview
Nevado AI moved from full stealth to a public launch. I led the end-to-end site program: information architecture, copy, design, prototype, and developer handoff, so the launch build could go live cleanly.
The challenge was transforming a single-page stealth presence into a credible, launch-ready site with clear story, pathways, and conversion. All while minimizing rework amid limited product visuals and a product accelerating in scope across multiple verticals.
Earlier work was handled as alpha builds to validate structure and messaging. The current site is the public launch build, designed to scale as the platform grows.
My Role
- Information architecture Defined site structure, page hierarchy, and navigation logic across audiences
- Content strategy Wrote copy for all core pages; established narrative flow and CTA logic
- Design & prototype Desktop and mobile layouts; clickable prototype with core navigation wired
- Developer handoff Single source of truth for behavior, anchors, and CTA rules enabling implementation without blocking on visuals
Impact
- Public site shipped on the planned launch build
- Stakeholders endorsed the information architecture, principles module, and audience system
- Development moved early on structure and prototype; visuals layered in with minimal rework
- Audience/solutions system and IA ready to absorb additional verticals as product footprint grows
Reflection
This project reflects how I approach launches under uncertainty: lock structure and copy first, treat visuals as a final pass, and design systems that absorb change rather than resist it. The alpha-to-launch ladder meant going live was an additive step, not a redesign.
Details
Approach & Design Principles
Alpha to Launch Ladder
Run alpha builds privately to lock IA and copy first; keep visuals/motion as a final pass. Advance the public launch build with the same spine, so going live is additive, not a redesign.
Truthful Prototypes & Clean Handoff
Ship a clickable prototype that represents structure and flow with core navigation wired. Use a single source of truth for behavior, anchors, and CTA logic so engineering can implement without blocking on final graphics.
Visual Direction
No stock or literal "AI" imagery. Abstract, data-viz-inspired geometry with restrained brand accents. Clear, precise language; avoid "final/fully integrated" claims during iteration.
Information Architecture & Content
Homepage Narrative
Problem → Solution → How it works (Connect → Activate → Scale) → Audiences → Principles (6 chips) → Insights teaser → CTA.
Audience Pages
Reusable white-variant system. Primary insurance segment (MGAs) at launch: challenges (legacy/fragmentation) → AI-native platform → Connect/Activate/Scale → results (speed, compliance, control) → CTA. Additional segments scaffolded as drafts for future verticals.
Supporting Pages
Company (team/about hybrid): single-line hero and mission, three beliefs, team mosaic. Insights: blog index and article template ready for thought leadership. Contact: standalone page with global CTAs pointing here.
Navigation & Conversion Logic
Context-aware CTA behavior (homepage vs. audience page targets). Clean top-level nav with expandable Solutions/Audiences pattern that accommodates future segments.
Timeline & Collaboration
Alpha Cycles (Pre-Launch)
IA and copy locked; prototype shared; visuals staged as a final pass.
Public Launch
Launch build goes live; visuals and motion continue as incremental enhancements.
Post-Launch
Expand content depth and audiences as product coverage widens; evaluate CMS for publishing workflows.
Collaboration
My role: UX lead & PM covering information architecture, copy, layouts, audience system, prototype, and developer handoff. Client team: engineering owned implementation; design/graphics layered in as assets landed.
Artifacts & Deliverables
