FLY Sales Bot v2 — Build Briefing

Resolved

What's Been Decided

These decisions are locked in from your input-form responses and our architecture review. No further action needed.

✓

Content Delivery

Delivered March 11 — 53 documents, 236 slides, 10 videos

✓

Delivery Mechanism

Standalone web app + QR code

Mobile-first design — prospects scan QR at live events

✓

Infrastructure

Independent deployment (not sharing HHE systems)

Separate database, separate server, separate domain — clean isolation for FLY brand

✓

Blake Marketing Intro

Not needed for now

Blake is focused on HHE/SEO pipeline — separate from FLY

Delivered

Content Inventory

You delivered a substantial corpus — everything we need to build a deeply knowledgeable sales bot. Here's what we received and how we'll use it.

558K

Words of Content

236

Presentation Slides

6.5h

Video Content

53

Unique Documents

Content Breakdown by Segment

pie title Content by Word Count
    "NAAP 30-Day Modules" : 214000
    "Facilitator Training" : 309000
    "Marketing Transcripts" : 10000
    "Sales & Ad Copy" : 5000
    "Guidebook" : 20000

Content Segment	Files	Volume	Bot Usage
NAAP 30-Day Modules	31 transcripts	~214K words	Core knowledge base — methodology depth
Facilitator Training	6 transcripts	~309K words	Expertise demonstration — "how it works"
Marketing Videos	10 transcripts	~10K words	Sales voice — objection handling, hooks
Scripts & Ad Copy	5 documents	~5K words	Prospect-facing language patterns
NAAP Guidebook	1 reference	~20K words	Methodology reference — 3 core principles
Presentations	3 PPTX (236 slides)	105 w/ notes	Visual framework for concept cards
YouTube Videos	10 URLs	~6.5 hours	Live delivery patterns, Q&A handling

Note: The "Learn to Fly 2-Hour Event" folder was empty in the delivery. If those recordings exist, they'd be valuable additions — but we can proceed without them.

Your Input Needed

5 Decisions to Advance the Build

These decisions are blocking specific parts of the build. Your responses will directly shape the MVP experience.

1. First Live Event Date

A) Set a specific date | B) Keep TBD, build without event CTA | C) Use placeholder "upcoming event"

Recommendation: A — Event-driven urgency is the #1 conversion lever in your sales pattern. "Seats are limited" + countdown = commitments. Without a date, the bot loses its strongest CTA.

HIGH VELOCITY IMPACT

2. Custom Domain for the Bot

A) fly.noboxai.com | B) fly-model.com (new) | C) app.fulfilllifeyourself.com (subdomain)

Recommendation: C — Leverages your existing domain authority and aligns with the FLY brand. Prospects see fulfilllifeyourself.com in the URL = trust.

MEDIUM VELOCITY IMPACT

3. Learn to Fly 2-Hour Event Content

A) Provide recordings/transcripts | B) Not available, proceed without | C) Will provide later

Recommendation: A if available — This is your prospect-facing event format. The bot would learn exactly how you present to new audiences. If not available, we have enough to proceed.

LOW VELOCITY IMPACT

4. Bot Personality Voice

A) LaMonte's direct voice ("I've helped...") | B) FLY brand voice ("The FLY model helps...") | C) Hybrid (brand voice + LaMonte quotes)

Recommendation: C (Hybrid) — Brand voice scales beyond you personally. But your personal stories and quotes build irreplaceable credibility. Best of both worlds.

MEDIUM VELOCITY IMPACT

5. What Should the Bot Drive Prospects Toward?

A) Event registration | B) Free 1:1 consultation booking | C) Program enrollment page | D) Multi-CTA (context-dependent)

Recommendation: D (Multi-CTA) — The bot detects what the prospect is interested in and serves the right next step. Curious about methodology? → event registration. Ready to commit? → enrollment. Need personal touch? → consultation booking.

HIGH VELOCITY IMPACT

How Your Decisions Feed the Build

sequenceDiagram
    participant L as LaMonte
    participant F as Input Form
    participant B as Build Pipeline
    participant MVP as Sales Bot MVP

    L->>F: Submit 5 decisions
    F->>B: Event date → CTA design
    F->>B: Domain → QR code generation
    F->>B: Voice → System prompt tuning
    F->>B: CTA targets → Intent routing
    B->>MVP: Build with all parameters
    Note over MVP: March 25 target

Architecture

How the Bot Works

The sales bot uses a 4-layer knowledge retrieval system trained on all your content. When a prospect asks a question, the bot searches your content four different ways simultaneously, then generates a grounded response using only verified FLY methodology.

Standalone Web App

Mobile-first design. Prospects scan a QR code at your events and land directly in the conversation. No app download, no login — instant engagement.

4-Layer Knowledge Search

Semantic meaning + topic relationships + exact keyword matching + intelligent fusion. Finds the right answer from 558K words in milliseconds.

Intent-Aware Responses

Bot detects whether the prospect is curious, skeptical, interested in pricing, or ready to commit — and adjusts its response strategy accordingly.

Anti-Hallucination Guard

Every response is validated against your actual content. The bot will never make up claims about NAAP or FLY — only verified methodology.

4-Layer Retrieval Pipeline

sequenceDiagram
    participant P as Prospect
    participant BOT as FLY Sales Bot
    participant INT as Intent Classifier
    participant S as Semantic Search
(meaning match)
    participant G as Graph Search
(topic connections)
    participant K as Keyword Search
(exact phrases)
    participant RRF as Fusion Engine
    participant LLM as Response Generator
    participant VAL as Grounding Check

    P->>BOT: "How does FLY help with anxiety?"
    BOT->>INT: Classify intent
    Note over INT: Intent: methodology_question
    INT->>S: Search by meaning (50%)
    INT->>G: Search by topic links (35%)
    INT->>K: Search exact terms (15%)
    S->>RRF: 5 relevant passages
    G->>RRF: 4 related passages
    K->>RRF: 2 exact matches
    RRF->>LLM: Top 8 passages (deduplicated)
    LLM->>VAL: Draft response
    VAL->>VAL: Verify against NAAP principles
    VAL->>BOT: Validated response
    BOT->>P: Grounded answer + concept card

In Progress

Build Pipeline

Six parallel workstreams, all active. Content ingestion and infrastructure provisioning are happening now — your content is being processed into the knowledge base today.

Content to Production Pipeline

sequenceDiagram
    participant SRC as Your Content
(53 docs + 10 videos)
    participant PROC as Processing
(text + video extraction)
    participant VAULT as Knowledge Vault
(analysis + tagging)
    participant PROD as Production Database
(search-ready)
    participant BOT as Sales Bot
(live on web)

    SRC->>PROC: DOCX transcripts (558K words)
    SRC->>PROC: PPTX slides (236 slides)
    SRC->>PROC: YouTube videos (6.5 hours)
    PROC->>VAULT: Tagged documents
(principle, exercise,
question, story, testimonial)
    VAULT->>VAULT: Entity mapping
Topic clustering
Relationship discovery
    VAULT->>PROD: Optimized chunks
+ search metadata
+ graph edges
    PROD->>BOT: 4-layer retrieval
ready for queries
    Note over BOT: QR code access
at live events

•CP-1: Content Ingestion — Processing all 53 documents + 3 PPTX into structured knowledge vault
•CP-2: YouTube Extraction — Extracting transcripts + visual context from 10 videos via Gemini API
•CP-3: Infrastructure — Provisioning Railway: PostgreSQL, Redis, FastAPI service
•CP-4: Agent Core — Building LangGraph sales bot with intent classification + 4-layer retrieval
•CP-5: Schema Migration — Evolving vault schema → production database with search optimization
•CP-6: Frontend — Mobile-first vanilla JS web app with chat + concept cards + CTAs

Timeline

March 11 → March 25: MVP Critical Path

14 days to MVP. Content ingestion and infrastructure are on the critical path. Your 5 decisions (above) unblock CTA design and domain setup — the sooner we have them, the more polished the MVP will be at launch.

MVP Build Timeline

gantt
    title FLY Sales Bot MVP — March 2026
    dateFormat YYYY-MM-DD
    tickInterval 1week
    section Content
    DOCX + PPTX ingestion     :active, ing, 2026-03-11, 3d
    YouTube extraction        :active, yt, 2026-03-11, 4d
    Schema optimization       :schema, after ing, 3d
    section Infrastructure
    Railway provisioning      :active, infra, 2026-03-11, 2d
    Database + Redis setup    :db, after infra, 2d
    Production ingestion      :prod, after schema, 2d
    section Agent
    LangGraph core build      :agent, 2026-03-14, 5d
    Intent classification     :intent, after agent, 2d
    Sales voice tuning        :voice, after intent, 2d
    section Frontend
    Chat UI + artifacts       :fe, 2026-03-16, 4d
    CTA integration           :cta, after fe, 2d
    QR code + domain          :qr, after cta, 1d
    section Launch
    Integration testing       :crit, test, 2026-03-23, 2d
    MVP Deploy                :crit, milestone, deploy, 2026-03-25, 0d

Next Steps

What Happens Now

LaMonte's Action Items

•Submit 5 decisions via the input form
•Set first live event date (CPI-1)
•Choose domain for QR code (CPI-2)
•Provide 2-Hour Event content if available (CPI-3)

Jonathan's Build Actions

•Complete content ingestion (today)
•Provision Railway infrastructure
•Build LangGraph agent core
•Deploy MVP by March 25

Phase 2 Preview: After the sales bot proves its value, the same knowledge base powers a full coaching agent — your 30-day NAAP program delivered digitally. Everything we build now carries forward.