epicways-client-intelligence

name	epicways-client-intelligence
description	Build TheEpicWays client intelligence systems for Estefania Badra. Use when working on TheEpicWays, Estefania, FrankX allies/friends pages, leadership/workshop/event offer architecture, client-service AI loops, installable Codex or Claude skill/plugin packs, public-safe partner assets, or premium rounded/liquid UI for her operating system.

EpicWays Client Intelligence

Overview

Design TheEpicWays as a human-led leadership company with a private intelligence layer behind it. Keep Estefania's voice, room energy, and trust in front; use FrankX systems backstage for preparation, memory, follow-up, outcomes, and content reuse.

Non-Negotiables

• Do not replace her public language with a technology narrative.
• Do not default to blockchain, NFTs, smart contracts, tokens, or marketplace language unless Frank explicitly asks in that turn.
• Do not invent private biography, client names, claims, metrics, revenue, or credentials.
• Keep the public voice warm, modern, direct, and easy for her to approve.
• Make the system useful to her clients: clearer diagnosis, better rooms, stronger follow-up, and measurable behavior change.
• Use premium rounded surfaces, icon-led controls, liquid glass depth, and workflow diagrams. Hard rectangular card walls fail this surface.
• Use GSAP, Framer Motion, XYFlow, or Mermaid only when they clarify loops or make the system inspectable.

Grounding Sources

Use public-safe source material first:

• TheEpicWays official site and approved public profiles.
• User-provided screenshots, notes, photos, or copy.
• Existing FrankX design, skill, agent, and plugin conventions.
• Any explicit approvals from Estefania or Frank.

If a source is missing, label the item as a proposed internal system, not a public claim.

Operating Loop

Build around five loops:

1. Signal: capture client context, team tensions, leadership gaps, event goals, language, and constraints.
2. Shape: turn the signal into a clean offer: workshop, program, 1:1, event, or retainer.
3. Room: prepare agendas, exercises, facilitation notes, prompts, and live-room energy cues.
4. Memory: turn the room into summaries, decisions, next actions, manager scripts, and client records.
5. Growth: reuse approved insights as proposals, case studies, talks, newsletters, clips, and future programs.

Agent Pack

Use these agents as conceptual modules, Claude/Codex skills, plugin skills, or later product agents:

• Client Signal Agent: prepares intake questions, reads notes, extracts tensions, and identifies the strongest workshop angle.
• Offer Architect: packages TheEpicWays work into clear products, tiers, outcomes, and proposal language.
• Workshop Designer: turns a client need into agenda, exercises, room flow, facilitation prompts, and materials.
• Room Memory Agent: converts session notes into decisions, commitments, owner lists, and follow-up packs.
• Impact Analyst: maps qualitative room change to practical measures: clarity, ownership, retention risk, decision speed, energy.
• Content Repurposer: transforms approved workshop themes into posts, scripts, newsletters, talks, and event assets.
• Client Portal Steward: keeps client deliverables organized across docs, decks, sheets, recordings, and next-step trackers.

Offer Ladder

Prefer a simple ladder:

• Diagnostic Session: leadership room readout, gap map, and recommended path.
• Intensive Workshop: focused room for communication, ownership, alignment, or manager confidence.
• Leadership Lab: multi-session program with repeatable behavior change and manager tools.
• Event / EpicVoices: interviews, panels, curated rooms, and community-led leadership experiences.
• Client Intelligence Retainer: ongoing preparation, follow-up, measurement, and content support.

Public Design Direction

Use a 2026 liquid-system direction without becoming decorative:

• Large rounded surfaces: rounded-[2rem], rounded-[2.5rem], and rounded-full CTAs.
• Layered translucent material over meaningful gradients or workflow visuals.
• Lucide icons for tasks, loops, controls, and agents.
• XYFlow or Mermaid for architecture and delivery maps.
• GSAP only for accent motion, glowing connectors, and workflow life; never animate reading text.
• Reduced-motion fallback must preserve meaning.

Build Checklist

Before shipping:

• Check the first viewport shows a real system or workflow, not just a slogan.
• Confirm all claims are public-safe or clearly proposed.
• Verify mobile and desktop screenshots.
• Check no visible text clips, overlaps, or hard rectangular card walls dominate the page.
• Run type/build checks when code changes.
• Read references/system-architecture.md for the full loop model when designing deeper assets.

Reference

• references/system-architecture.md: detailed loop architecture, agent outputs, data boundaries, and deliverables.