# Innovexus Interactive Product Tour — Storyboard

**Format:** Self-guided click-through demo. Visitors land on `innovexus.io/tour` (TBD) or click "Take the tour" from the homepage. They click through guided steps with hotspot highlights and one-line copy per step.

**Tooling target:** Navattic, Arcade.software, Storylane, Reprise, or Walnut.io. All five offer free trials sufficient to ship the first version. Recommendation: **Arcade** — fastest setup (Chrome extension records the click path in 10 minutes), strongest free tier, native dark-mode rendering that won't fight the antichromatic theme.

**Total runtime:** ~3 minutes if a buyer reads every step. Each step should be self-explanatory if skipped.

**CTA:** End-of-tour modal: "Trial this against your real fleet" → `/auth/register`. Secondary: "Talk to an engineer" → `/demo`.

---

## Tour flow

```
[Step 1: Login]
     ↓
[Step 2: Pod overview]
     ↓
[Step 3: Device discovery]
     ↓
[Step 4: Brokered SSH session] ─→ [Branch A: View session recording]
     ↓
[Step 5: Configuration drift]
     ↓
[Step 6: Compliance export]
     ↓
[Step 7: Pricing + CTA]
```

Branch A is optional — buyers who care about audit evidence will click through it; buyers focused on operational fit will skip it.

---

## Step-by-step storyboard

### Step 1 — Login (FIDO2)

- **Screen:** Innovexus login page
- **Hotspot:** YubiKey login button
- **Step copy (top of frame):** *"Login starts with a hardware key. No passwords. No phishable factors."*
- **Click target:** "Login with YubiKey" button
- **Click result:** Animated YubiKey prompt → success
- **Tooltip below click:** *"Every session ties back to the specific physical device that authenticated. Audit attribution survives even if usernames are shared at the device level."*

---

### Step 2 — Pod overview

- **Screen:** Dashboard landing page after login
- **Hotspot:** The "POD / US-EAST-01" badge in the top-right
- **Step copy:** *"This is your dedicated per-tenant pod. Not multi-tenant SaaS — physically isolated infrastructure on Tier 3/4 audited data centres."*
- **Click target:** Pod badge
- **Click result:** Side panel slides out showing pod telemetry — region, uptime, last verification, infrastructure compliance status
- **Tooltip:** *"Status is verified live against the underlying infrastructure on every page load. The /compliance page shows the full posture."*

---

### Step 3 — Device discovery

- **Screen:** Devices list view, populated with sample inventory (realistic mix: ~30 devices across Cisco IOS, Juniper Junos, FortiGate, Linux servers)
- **Hotspot:** The role-based access filter
- **Step copy:** *"You see only the devices your role permits. Discovery is a security boundary, not just a list view."*
- **Click target:** A specific Cisco device (e.g., `core-rtr-01`)
- **Click result:** Device detail page opens. Shows: device class, last config baseline, last drift check, last session, current vault state for this device's credential.
- **Tooltip:** *"Every device has its own audit history. Click any timestamp to jump to the corresponding session recording."*

---

### Step 4 — Brokered SSH session

- **Screen:** The Cisco device detail from Step 3
- **Hotspot:** "Open SSH session" button
- **Step copy:** *"Click to open a session. The vault provides credentials. You never see them."*
- **Click target:** "Open SSH session"
- **Click result:** In-browser terminal panel slides up. SSH session opens to the device. Banner shows: `Session brokered through innovexus-pod-us-east-01 · recording active · cert TTL 15min`
- **Pre-staged command demo:** Show `show version`, `show running-config | i interface GigabitEthernet0/0`, brief output rolls in
- **Tooltip:** *"This is a real session, brokered through your pod, recorded as it happens. The recording is searchable across the entire fleet history."*

#### Branch A — View session recording (optional)

If the visitor clicks "View this session in audit", branch into:

- **Screen:** Session playback view
- **Hotspot:** Search bar above the timeline
- **Step copy:** *"Audit teams can search every session across the fleet. Try searching for 'write erase' or 'configure terminal'."*
- **Click target:** Pre-populated search demo — `interface gigabit`
- **Click result:** Search results list highlights every session that matched, with timestamps and engineer attribution
- **Tooltip:** *"Cryptographically signed at recording time. Tamper-evident. SOC 2 / NERC CIP / IEC 62443 audit-ready."*
- **Continue button:** "Back to operational tour →" returns to the main flow at Step 5

---

### Step 5 — Configuration drift

- **Screen:** Drift detection view (sample data: 3 alerts from the past 24 hours)
- **Hotspot:** A drift alert at the top of the list
- **Step copy:** *"Drift detected on `core-sw-04` 47 minutes ago. Not from an Innovexus session — meaning it was changed outside the platform."*
- **Click target:** The drift alert
- **Click result:** Drift detail page. Shows the diff — old config vs new config side-by-side, change-line highlighted in red. Below the diff: timeline showing when last approved, by whom, and which engineer triggered the alert.
- **Tooltip:** *"Approved changes inside Innovexus auto-promote the baseline. Drift outside the platform fires an alert immediately. This is what 'continuous compliance' looks like operationally — not a marketing slogan."*

---

### Step 6 — Compliance export

- **Screen:** Compliance / Audit tab
- **Hotspot:** "Export evidence bundle" dropdown
- **Step copy:** *"Pre-built export bundles for the frameworks your auditor is asking about."*
- **Click target:** Dropdown opens, showing options: SOC 2, ISO 27001, NERC CIP, IEC 62443, HIPAA, PCI DSS
- **Sub-click:** Visitor selects "SOC 2 (Trust Services Criteria)"
- **Click result:** Brief loading state, then a download begins (sample PDF/ZIP showing the bundle structure — control mapping, evidence index, signed audit chain summary)
- **Tooltip:** *"What used to be a 2-week evidence-collection project is a 30-second click. The bundle is signed by your pod's identity key — auditor can verify integrity independently."*

---

### Step 7 — Pricing close + CTA

- **Screen:** Pricing tab inside the app (or transition to `/pricing` public page)
- **Hotspot:** Three tier cards
- **Step copy:** *"$199 / $499 / $999 per month. Same price for everyone. No quote process, no multi-year commitment."*
- **Click target:** "Start free trial" button
- **Click result:** Modal: *"Tour complete. The 5-day trial runs against your real fleet — pod deploys in minutes, no card required. Or schedule a 30-minute walkthrough with an engineer if you'd rather have someone narrate."*
- **CTA buttons in modal:**
  - Primary: "Start trial →" (`/auth/register`)
  - Secondary: "Schedule a walkthrough" (`/demo`)
  - Tertiary: "Restart tour"

---

## Hotspot copy guidelines

Each step's hotspot copy should:
- Be one sentence
- State an outcome, not a feature
- Avoid jargon that doesn't already appear elsewhere on the site (no "AAA", "RBAC sprawl", etc. without context)
- Read in the same voice as the rest of the antichromatic copy — direct, slightly understated

Bad: *"Click here to see our patented vault architecture!"*
Good: *"You see only the devices your role permits. Discovery is a security boundary, not just a list view."*

---

## What to record vs. what to mock

**Record real:**
- Login flow with actual YubiKey
- Dashboard layout (use the production app on a demo tenant)
- Compliance export download (use a real bundle)
- Device list view with realistic sample inventory

**Pre-stage / mock:**
- The drift alert in Step 5 (needs a specific drift event with a clear diff — easier to stage than to wait for one to happen organically)
- The session search results in Branch A (needs realistic-looking matches with timestamps)
- The pricing tier cards inside the app (or just transition to the public pricing page)

**Do not mock:**
- The session recording itself. Use a real recording. Mocked terminal output reads as fake within 5 seconds.

---

## Setup checklist (for whoever builds it in Arcade/Navattic/Storylane)

- [ ] Set up a dedicated demo tenant (`acme-demo` or similar) with realistic but anonymised data
- [ ] Pre-create the sample device inventory — 30 devices, mixed vendor classes
- [ ] Pre-create the sample drift alert — needs an actual config diff
- [ ] Pre-record a sample session for the audit playback step
- [ ] Pre-build the SOC 2 evidence bundle so download is instant
- [ ] Capture each step in your tool of choice (Arcade extension records click paths in real time — easiest path)
- [ ] Add hotspot copy per step
- [ ] Add the CTA modal at end
- [ ] Test the branch logic (Branch A optional pathway)
- [ ] Embed at `innovexus.io/tour` (new route — placeholder for now)
- [ ] Add CTA on homepage hero: "Take the interactive tour →"
- [ ] Track tour completion as a conversion event in your analytics

---

## What this storyboard deliberately doesn't include

- **Admin / configuration steps.** Buyers don't want to see how to configure RBAC during evaluation; they want to see the operational workflow. Admin tours are for post-purchase onboarding.
- **Settings menus.** Skip them — they tell the buyer "this product has settings", which they assume.
- **The Inno chat agent.** Don't surface the AI chat in the tour. Save the agent reveal for the help flow.
- **Comparisons to competitors.** That's `/compare`. The tour is about *our* operational workflow, not "look at all the things CyberArk doesn't do."
- **Pricing edge cases (volume discounts, multi-year terms).** That's the pricing page.

---

## Distribution

Once the tour is built:

1. Embed at `innovexus.io/tour` (new dedicated route)
2. Hero CTA on homepage: *"Take the 3-minute tour →"* (alongside "Book a demo")
3. Embed inside `/platform` as the primary feature exploration tool (replaces or supplements the current DeepDive accordion)
4. Embed inside `/services/noc` and `/services/soc` with the relevant subset of steps highlighted
5. Send to enterprise prospects pre-call ("watch this 3 minutes before our discovery call so we can spend the time on your environment specifically")

---

## Licence

CC BY 4.0. Same terms as the rest of the resources collection.

## Source

[innovexus.io/resources/innovexus-interactive-tour-storyboard.md](https://innovexus.io/resources/innovexus-interactive-tour-storyboard.md)
