# About Flowgear Video - Full Spoken Script **Status:** Draft for Taylor approval. Do not share to Basecamp until approved. **Runtime target:** 2:15-2:45 **Word count (VO only):** ~380 **Companion strategy:** [2026-07-21-about-fg-video-strategy.md](./2026-07-21-about-fg-video-strategy.md) **Voice:** Integration Development Environment. V2. Builder MCP. Workflow MCP. Conversational spoken register. **Thesis:** Build Integrations at the Speed of AI. **Written CI:** US English. Title case on-screen. Full "and". No em or en dashes. Hyphens only, sparingly. No `&` in running copy. **Legend** - `VO` - spoken line - `[VISUAL]` - picture / capture / B-roll - `[ON SCREEN]` - title or lower-third text (US English, title case) - `--- SHORT CUT ---` - clean in/out for a 30-45s vertical or square cut - **Rule:** Every short cut must say **Flowgear** at least once in spoken VO. --- ## Chapter 1 - The Shift (~0:00-0:30) --- SHORT CUT A OPEN --- `[VISUAL]` Dark Pitch field. Green energy line threads systems into a simple network. Soft dissolve into product world later. Keep abstract here. `[ON SCREEN]` The Integration Layer **VO:** Most teams are not stuck because they cannot spin up another app. They are stuck because the systems they already run (ERP, CRM, warehouse, finance) do not talk to each other clearly. And AI is making that gap bigger. Features move fast. The integrations underneath still have to be right. That is the problem Flowgear is built for. --- ## Chapter 2 - Who Flowgear Is (~0:30-0:55) `[VISUAL]` White Flowgear logo resolves on dark. Cut to leadership on stage with Flowgear banner behind them. Brief Flowgear Build / breakfast / end-of-year cutaways. Faces, room energy, then settle. `[ON SCREEN]` Flowgear Integration Development Environment **VO:** Flowgear is an Integration Development Environment. You design, run, and govern business integrations here, visually or in code. There is a compiled runtime underneath, and AI that works inside real guardrails, not on a blank canvas. We have been doing this in production for sixteen years. Now the same engine helps you build at AI speed without losing control. --- SHORT CUT A OUT (must include a line that names Flowgear) --- --- ## Chapter 3 - How You Build (~0:55-1:30) --- SHORT CUT B OPEN --- `[VISUAL]` Screen capture: Designer canvas, a workflow taking shape. Toggle to declarative code view (parity). AI assistant: prompt to scaffold to diagnostics. Human confirms a connection. No black-box magic. `[ON SCREEN]` Build at the Speed of AI You Stay the Engineer **VO:** Describe what you need. Watch it take shape. In Flowgear, the canvas and the code stay in sync, so you can work the way you prefer. You can build and query integrations right from AI chat, too. AI helps build, test, and repair through governed tools. You stay in review. You approve the connections. You keep the audit trail. Fast enough to keep up. Controlled enough to ship. --- SHORT CUT B OUT --- --- ## Chapter 4 - The MCP Era (~1:30-2:00) --- SHORT CUT C OPEN --- `[VISUAL]` Builder MCP: agent or IDE outside the Console driving Flowgear's build surface. Then Workflow MCP cue, approved workflows as callable tools. Cut to roles, keys, logging. Governance visible, not slideware. `[ON SCREEN]` Builder MCP and Workflow MCP Stay the System of Record **VO:** Your team does not have to live only inside our Console. With Flowgear Builder MCP, you can build and refine integrations from the AI tools and IDEs you already use. And with Flowgear Workflow MCP, the workflows you approve become tools assistants can call. Agents get the outcome. You keep the credentials, the approvals, and the execution on your terms. --- SHORT CUT C OUT --- --- ## Chapter 5 - Why It Holds (~2:00-2:25) --- SHORT CUT D OPEN --- `[VISUAL]` Runtime: live progress counters, payload preview, logs. Hybrid cue (cloud and local) if clean. Optional 1-2s CI line-icon pulse (compiled / observable / governed). Not a feature checklist montage. `[ON SCREEN]` Compiled. Observable. Governed. **VO:** Speed only matters if the layer underneath holds. Flowgear's durable layer compiles workflows to binaries, shows you what is running, and scales without a redesign when volume jumps. Hybrid when you need it. Capacity pricing you set. No metered surprise at the end of the month. That is the kind of engineering AI cannot casually recreate. And it is where you stay in control. --- ## Chapter 6 - Invitation (~2:25-2:45) `[VISUAL]` Soft dissolve from product to dark end card. White registered logo. Green accent line. Hold. `[ON SCREEN]` Start Building. 90 Days Free. Or Book an Integration Assessment. flowgear.net **VO:** Want to try it yourself? Start free for ninety days. Want a roadmap first? Book an Integration Assessment. Build integrations at the speed of AI with Flowgear. And govern them with confidence. --- SHORT CUT D OUT on last two lines + logo hold --- `[VISUAL]` 5-8s logo hold. Optional URL lower-third. Fade. --- ## Full VO (continuous read-through) Most teams are not stuck because they cannot spin up another app. They are stuck because the systems they already run (ERP, CRM, warehouse, finance) do not talk to each other clearly. And AI is making that gap bigger. Features move fast. The integrations underneath still have to be right. That is the problem Flowgear is built for. Flowgear is an Integration Development Environment. You design, run, and govern business integrations here, visually or in code. There is a compiled runtime underneath, and AI that works inside real guardrails, not on a blank canvas. We have been doing this in production for sixteen years. Now the same engine helps you build at AI speed without losing control. Describe what you need. Watch it take shape. In Flowgear, the canvas and the code stay in sync, so you can work the way you prefer. You can build and query integrations right from AI chat, too. AI helps build, test, and repair through governed tools. You stay in review. You approve the connections. You keep the audit trail. Fast enough to keep up. Controlled enough to ship. Your team does not have to live only inside our Console. With Flowgear Builder MCP, you can build and refine integrations from the AI tools and IDEs you already use. And with Flowgear Workflow MCP, the workflows you approve become tools assistants can call. Agents get the outcome. You keep the credentials, the approvals, and the execution on your terms. Speed only matters if the layer underneath holds. Flowgear's durable layer compiles workflows to binaries, shows you what is running, and scales without a redesign when volume jumps. Hybrid when you need it. Capacity pricing you set. No metered surprise at the end of the month. That is the kind of engineering AI cannot casually recreate. And it is where you stay in control. Want to try it yourself? Start free for ninety days. Want a roadmap first? Book an Integration Assessment. Build integrations at the speed of AI with Flowgear. And govern them with confidence. --- ## Short cut brand check | Short | Chapters | Spoken "Flowgear" | |-------|----------|-------------------| | A | 1 + open of 2 | "That is the problem Flowgear is built for." / "Flowgear is an Integration Development Environment." | | B | 3 | "In Flowgear, the canvas and the code stay in sync…" | | C | 4 | "With Flowgear Builder MCP…" / "with Flowgear Workflow MCP…" | | D | 5 + CTA | "Flowgear's durable layer…" and "…with Flowgear." | --- ## Messaging and written CI self-check - [x] Leads with Integration Development Environment (not iPaaS) - [x] Problem-led open (systems talking clearly) before product pitch - [x] Build and query from AI chat named in Ch 3 - [x] Conversational spoken cadence (you / your team / plain language) - [x] AI claims tied to governed behavior (build/test/repair, approve connections, audit) - [x] Customer as builder ("you stay in review") - [x] Builder MCP + Workflow MCP named correctly - [x] Dual CTA (Start Building + Assessment) - [x] US English spelling and register - [x] No em dashes or en dashes in VO or on-screen copy - [x] Full "and" (no `&` in running copy) - [x] Title case on-screen headings - [x] No competitor names; no invented metrics - [x] Each short cut names Flowgear in spoken VO - [x] Shorts marked chapter by chapter - [x] No survival / contested-ground drama ## Notes for review 1. Talent: single confident VO preferred for master. Optional short on-camera open from leadership if Rixie wants face-forward (keep under 8s). 2. Music: low pulse under Ch 1-2. Lift slightly under product demos. Resolve on end card. Never drown VO. 3. Caption file: burn-in for shorts. Website master can use optional subtitles. --- *Revision: v04 - 2026-07-21 - clearly/bigger word swap + AI chat build/query. Awaiting Taylor approval before Basecamp.*